Frontier Transformation Assumes a Decision You Haven’t Made

Microsoft has built a serious, well-funded answer: a new suite (Microsoft 365 E7), an agent control plane (Agent 365), an intelligence layer (Work IQ), and a partner channel paid to sell all of it. It is a capable answer. The problem is the question it answers.

Frontier Transformation tells an organisation how to adopt Microsoft’s AI at scale, safely. It does not tell you whether you should, how far, or what to skip. Those are architecture decisions, and they come first — before the suite, before the agents, before the renewal conversation. This is the step the motion skips.

What Frontier Transformation actually is

Strip the language back and it’s three things stacked together. A licensing upgrade — E7 bundles E5, Copilot, Entra, and Agent 365 into one per-user price. A governance product — Agent 365 registers, monitors, and secures the agents you deploy. And a services motion — the partners selling it package advisory, deployment, and adoption on top, often part-funded by Microsoft.

None of that is criticism. The stack is strong, and the governance layer in particular addresses a real problem: agents proliferate faster than most IT functions can see them. If you have already committed to Microsoft as your operating substrate, Frontier Transformation is a coherent way to adopt at scale without losing control.

That conditional — if you have already committed — is doing all the work.

Who it’s for

Frontier Transformation is for organisations that have made two decisions already:

• that their operating model should be rebuilt around AI, and
• that Microsoft is the platform it’s built on.

If both are true and settled, the motion fits. The staged model Microsoft describes — secure the foundation, start with role-based adoption, expand, normalise — is a reasonable sequence for rolling out a platform you’ve chosen.

The trouble is that most mid-market organisations haven’t made either decision deliberately. They’ve made them by default — because the Microsoft account team got there first, because E7 was the easy box to tick at renewal, because “everyone’s doing agents.” A default is not a decision. And Frontier Transformation is built to convert defaults into purchases.

Why the people selling it can’t help you here

Read Microsoft’s own partner material and the incentive is explicit. Partners are coached to anchor on renewals, lead with bundles, and create urgency. The monetisation ladder runs from licensing revenue to services revenue, tiered by how much you buy. In Microsoft’s own worked partner example, upgrading 100 users to E7 carries roughly USD $50k of Microsoft funding behind the services attached to it.

That funding is the tell. The partner in the room is paid to grow your seat count. They are good at what they do, but they structurally cannot tell you to buy less, adopt slower, or skip a module — because every one of those answers costs them revenue, and some of it costs Microsoft the funding it extended to win you.

This is the inconvenient layer. Someone has to own the decision that sits above the adoption motion: how decisions get made in your business, how work actually flows, where AI genuinely belongs and where it doesn’t. It is the one layer no vendor sells and no funded partner can own without a conflict — which is exactly why it’s usually missing.

Why you need us first

We are the architecture layer that comes before the suite. Five pillars, in sequence: strategic direction, decision architecture, workflow architecture, execution cadence, and only then intelligent operations — the AI and tooling. Frontier Transformation lives in that last pillar. It is a good answer to pillar five. It is no answer at all to the four that precede it.

We have spent twenty-five years inside this stack — Dynamics, Power Platform, the Microsoft estate at enterprise scale — so we assess it on its merits, not from the outside. And we make no money on what we recommend. We don’t resell E7, we take no margin on seats, and we draw no vendor funding. So when we tell you to adopt aggressively, that’s the architecture talking. When we tell you to buy a third of what you were about to, that’s the architecture talking too. There is no incentive sitting behind either answer — and that is the only condition under which “buy less” is a sentence you will ever hear in this conversation.

That doesn’t make us anti-Microsoft. For many organisations the right answer will be to adopt Frontier Transformation — fully. We just think you should decide that on the merits of your operating model, not on a renewal date and a discount that expires.

The order matters

Frontier Transformation is a fine answer. Architecture is the question. Get the question right first, and the answer — whatever it turns out to be — will be one you actually chose.

If you want to find out which question your organisation is actually answering, the Architecture Index is where you start asking it — a free, self-serve diagnostic, no call required.