The AI era forces one architectural choice on every large enterprise. Most are making the expensive one without noticing they had a choice.

Every large enterprise is about to make the same decision, and most will make it by default.

The AI era has reopened the oldest question in enterprise technology: how do you connect a business that is many things to systems that were bought separately? For thirty years the answer was a layer in the middle — a technology organization that stood between what the business wanted and what its systems did, translating one into the other, with a growing stack of integration underneath it. The middle was where coordination happened. It was also where the waiting happened. For most of that time there was no way to remove it.

Agentic AI is now being sold as the way to perfect that middle. The dominant advice this year — from the largest advisory firms — is to build a smarter one: an orchestration layer, an “agentic mesh” that coordinates across systems and maintains a shared source of truth, a shared enterprise ontology so agents can reason across domains, a clean central core that everything still routes through. The instinct is understandable. It is also the wrong answer, and an expensive one.

There is a different answer, and it comes from taking the same facts seriously. The forces that make a smarter middle possible — vendors who now supply the hard systems, and AI that now does the translation — are the same forces that remove the reason for a middle at all. The middle existed to bridge a gap. If the gap has closed, you do not re-platform the bridge. You delete it.


What the Middle Costs

The middle never showed up as a line item. It showed up as time.

Every initiative that touched more than one system waited on a shared release calendar, a shared change board, a shared integration team, a shared source of truth that someone had to reconcile. The cost of the middle was the speed you did not have. A process change that should have been a decision became a program, because the program was how you got everyone in the middle to move at once.

The enterprise paid for this because the alternative was worse. Building and connecting systems was expensive, so consolidation won: fewer systems, fewer connections, one place to coordinate. The middle was the price of consolidation, and consolidation was the price of affordability. That bargain is what has changed.


The Enterprise Without a Middle

Picture the enterprise organized a different way.

It is a set of business-owned domains — the real divisions of the business, each owning its own systems — bought or built — its own decisions, and its own outcomes. The strategic things it builds for itself share a consistent framework, never a shared workspace: standards everyone meets, not a room everyone works in. Underneath them is a thin spine that the technology organization owns: infrastructure, security, and a data platform. That is the entire remaining footprint of central IT. Everything else — the applications, the delivery, the people who make technology serve the business — lives inside the domains, owned and funded by the business.

Two rules hold it together. No system sits inside the workflow of more than one business line. And anything shared that sits inside a workflow is not an economy — it is a blocker. The three spine services are allowed to be shared precisely because they sit underneath every workflow and inside none of them.

And the domains connect in exactly one way: by contract. A domain publishes what it will share — an appointment, a balance, a result, an action it will take on request — and the domain that needs it consumes that contract directly, peer to peer. There is no orchestrator in the middle moving work across. The domain accountable for an outcome reaches for what it needs. Ownership is never ambiguous: whoever publishes a contract owns that it is correct; whoever consumes it owns what they do with it. The crossing is not a place, so there is nothing in the middle to own.


What This Changes for the Business

This is not a technology reorganization. It is a change in who owns, funds, and runs the enterprise’s capabilities.

The technology organization stops trying to own teams embedded across every business line and shrinks to running the spine. The business stops waiting on a central function and takes ownership of the domains it already depends on — including the budget and the accountability that come with them. The customer-facing functions follow the same logic: support becomes a domain that owns the conversation and routes requests to the domains that can act; field service becomes a domain that receives them. No shared function reaches across everything to resolve anything, because reaching across is what rebuilt the middle in the first place.

What the business gets in return is the thing the middle always cost it: a change to a process becomes a decision, not a program.


The Honest Limits

A model earns trust by naming what it does not solve. Three things are real.

The end-to-end promise — the commitment made to a customer whose issue spans several domains — is owned by whoever faces the customer, but the clock runs inside domains they do not control. Action across a boundary — getting one domain to reliably act on another’s request — is harder than reading, and it is the genuine integration work that remains. And the economics of duplication — running two systems where you used to run one — rest on integration having become cheap: vendors now carve a separate instance per business line and share data between them at low cost, and AI has collapsed the price of connecting systems at all. That shift is real, but uneven across vendors, so the economics are strongest where your core platforms already support multiple instances and managed data sharing.

These are not reasons the model fails. They are the places where the real work is, once the structure is right. Everything else the old enterprise spent its coordination budget on was self-inflicted — the cost of a middle that no longer needs to exist.


What This Builds On, and What It Argues Against

None of this is built from nothing. The shape of it has been described before — by people who were right, and early, and held back by the same thing: the cost of implementation.

Team Topologies (Matthew Skelton and Manuel Pais) worked out how to organize teams for fast flow — but it was written for organizations that build and run their own software. MIT CISR’s work on the componentized organization (Jeanne Ross and colleagues) argued for business-owned components connecting through APIs, studied in large traditional enterprises rather than tech firms. Each described a version of the enterprise this series describes. Each ran into the same wall: building and connecting systems was slow and expensive, so the destination stayed mostly out of reach.

That wall is what has come down. The contribution here is not a new shape — it is that the shape is finally affordable, and that it extends past the data plane to the whole system estate and operating model.

Which is why the current consensus is worth arguing with. The dominant 2026 advice — most clearly from McKinsey, in its work on enterprise architecture and ERP for the agentic era — reads the same moment and reaches the opposite conclusion: build a smarter central layer. An “agentic mesh” acting as a coordination fabric with a shared source of truth; a shared enterprise ontology so agents can reason across domains; a clean central core that everything still routes through. It is a serious position, argued by serious people. It is also the instinct to perfect the middle at exactly the moment the middle became optional — and a better middle still charges, in a new currency, the tax the middle always charged.


The Choice

So the decision in front of every enterprise is not whether to adopt AI. It is what to do with the middle that AI makes optional.

One path builds a better one: a smarter orchestration layer, a shared brain, a cleaner core — and keeps paying, in a new currency, the tax the middle always charged. The other deletes it: business-owned domains on a thin spine, connected by contracts, accountable where the work lands.

Most enterprises will build the middle, because it is the familiar move and the one the market is selling. The ones that delete it will be faster, and they will spend the AI era removing coordination instead of re-buying it.

This is the argument in brief. Three companion pieces work it out in full: the shape of the organization, the boundaries of the systems, and why there is nothing in the middle to own.

Related reading: The Mesh Keeps Coming Back. The Reason For It Doesn’t. — why the agentic mesh is the latest in a long lineage, and why its cost case has expired.

Posted in ,