Gartner expects that by 2028, companies using multi-agent AI across most of their customer-facing work will pull ahead of everyone else, and that ninety percent of B2B buying will run through AI agents, moving more than fifteen trillion dollars (Gartner, Oct 2025). The same firm expects more than forty percent of agentic AI projects to be canceled by the end of 2027 (Gartner, June 2025). One of its own analysts says plainly: past a certain point, more AI does not mean more productivity. And in 2026 it predicted that by 2030, half of AI agent deployment failures will trace to governance platforms that fail to enforce capabilities and multisystem interoperability at runtime.
Read those together and something is off. The firm forecasting agent dominance is the same one forecasting the shakeout.
One analyst saying this would be a footnote. The big advisory firms all say some version of it. The firms telling you to scale agents across the enterprise are the same firms publishing the evidence that scaling is where the value dies.
Every advisor is arguing with itself
Look closely and each of the big advisory voices carries two messages at once.
Gartner’s loud message is the proliferation math above. Its quiet message is the cancellations.
Accenture carries both messages inside one report. Its mid-2026 study presses companies to move now, warning that “the cost of delay is not temporary but structural”. A few pages later it says the leading companies do not move faster, they move deliberately, and it names “systemic readiness” as the binding constraint. Push hard, and readiness is what actually gates you.
PwC has a more disciplined public voice. Its 2026 predictions say agentic workflows are “spreading faster than governance models” can handle. A few predictions later, it offers the cure: an AI orchestration layer that, it says, will let you “control AI anywhere in your company”.
BCG showed the whipsaw most starkly of all. Its July CIO playbook led with speed. Five weeks later its global chair told CEOs the first thing to protect is the enterprise’s own knowledge and judgment, not speed. Same firm, five weeks apart, the emphasis inverted. I worked through that shift in a prior post.
Credit them all. But there is a gap.
The gap they keep circling
The loud message prices capability, meaning how much you can deploy. The quiet message prices readiness, meaning whether you built the muscle to deploy well. Neither one prices the thing that actually breaks once you scale, which is coherence.
Coherence is a plain idea. It is whether the systems you deployed still serve the enterprise once they run together. Readiness is a gate you clear once, before you scale. Coherence is a property that erodes after you clear it, and it erodes faster the more you deploy. That is why a company can pass every readiness check, launch aggressively, and still land in Gartner’s forty percent.
These firms describe the gap.
Follow the mechanism
The failure has a shape, and Accenture describes it. In a siloed rollout, every team builds its own agent on its own data. The invoicing agent has no view of supplier records. Procurement is walled off from finance’s process. Where those pieces should hand off, they break instead, and people get pulled back in to bridge the gap, which is the opposite of what the agents were for. Accenture calls it the “hidden tax of siloed transformation”. Every agent worked on its own. The cost lived in the seams between them.
Gartner points at a related failure. Its sales analyst warns of a value ceiling, where piling more prompts and tools onto already complex workflows overwhelms the people working them and stops adding value past a point.
PwC’s own safeguard shows the reflex. It suggests using agents to check other agents, and pulling in a second vendor’s model for higher-risk work. A sensible control, and also a tell, because the instinct is to answer agent sprawl with more agents.
What each firm reaches for
Each names the coordination problem, and each reaches for a build to solve it.
Accenture is the most explicit. It describes the cross-functional collapse above and prescribes a multi-year rebuild it calls the intelligent superhighway: unified data, redesigned workflows, and a reinvented operating model. Much of that is what coherence requires.
Gartner traces half of its projected agent failures to poor multisystem interoperability, then reaches for a universal semantic layer, which it calls the only way to align multiagent systems and stop costly inconsistencies before they spread.
PwC prescribes the orchestration layer, a way to combine agents from different vendors into one process and, it says, stay in control.
These are serious answers, and much of what they prescribe is real work, most of it ongoing rather than one-and-done. Here is what none of it produces. These layers standardize and route what passes between systems, which is the substrate coherence needs to exist at all. Run them well and keep running them, and coherence still does not follow, because it is a separate job. A layer will not judge whether the actions those systems take still add up to what the business wants, or decide whether two agents chasing different goals have started working against each other. It will not own the space between them, or put the state of that space on a number anyone reads. Coherence is the property all this infrastructure is meant to yield, and it is the one property none of them names or measures. I traced the same gap through McKinsey’s operating-model argument in an earlier piece: the rewiring these firms recommend routes around the old coordination layer and builds a new one underneath, machine-speed and owned by no one.
There is a fair objection. They would all say they already preach discipline, and that the failures are the undisciplined ones. Grant it. Discipline applied one system and one program at a time still does not produce a standing measure of whether the whole keeps serving the enterprise. That measure is what is missing.
What actually closes the gap
The fix is structural, and it is the one thing none of these firms can sell you, because it is not a product at all. It is how the enterprise is wired to hold together as it fills with autonomous systems.
Start with what does not work. The reflex, once a leader feels this, is to watch everything and keep people “in the lead” of every agent, as Accenture puts it. The instinct is right and the framing is not enough. You cannot lead a hundred systems running at machine speed by paying closer attention, and once human vigilance is the thing holding the company together, the company has already outrun it. Supervision does not scale to the speed of software.
What scales is structure, and it runs as a stack. You have to see the whole before anything else works. Most leaders can say how accurate a model is and how many agents are in production, and cannot say whether those agents still agree with one another. Instrument the coordination state so the portfolio is visible in aggregate, because every move below this one runs blind without it.
Then constrain. Give each system an action space defined and enforced ahead of time, not written into a prompt and hoped for, so whole classes of incoherence cannot form at all. In a 2026 red-team study, an agent told to keep a secret resolved the dilemma by destroying its own email server. It held the right value and had no limit on what it could touch. The limit is the fix, and it lives in the architecture, not the pep talk.
Contain what the constraints miss. Partition the enterprise so a failure in one system stays in one, rather than racing through dependencies nobody mapped. Containment is what makes aggressive deployment survivable on the day a boundary slips, which it will.
Then price it. Put coordination cost on the scoreboard the business actually reads. Judge a redesign by a single question: did the company grow more coherent or less as it scaled? Speed of shipping and the number of agents live are the vanity metrics that hide the debt underneath. The cost you decline to measure is the one that compounds in the dark.
Human judgment sits on top of that stack, held back for the exceptions. It is worth something precisely because the layers beneath it carry the volume, so scarce attention lands on the few decisions that are expensive and hard to reverse instead of drowning in what the structure should have caught. Underneath it, every system has a named owner who can reach in and correct it when it drifts. This is what keeping people in charge looks like at machine speed: a human at the top of something built to need one only where it counts.
Sense, constrain, contain, price, and reserve judgment for the top. That is the architecture the whole field keeps gesturing at and will not name, and it is what turns autonomy from a liability into something safe to scale. The companies that build it deploy more than the ones that mistook the control panel for control, because they can finally trust what they shipped.
The unpriced category
Coherence is missing from the forecasts for the reason technical debt and systemic risk went unpriced before their reckonings. The market prices what it can measure, and no one has been measuring this.
The most influential voices in enterprise AI have now walked right up to it. They name the coordination failure, they prescribe unified data and orchestration and human oversight, and they still stop at the edge of naming the property itself. That is not a knock on their work. It is a sign the category is real and still unnamed.
It needs a name, and it needs a different picture of the job.
Everything these firms offer is a permitting office, and a good one. It checks each plan against the code before the plan may proceed. That is what governance does when it clears an agent to ship, and what a readiness program does when it certifies a company to scale, and it is worth having.
The collisions happen after the gate. Two agents that each passed the desk converge on the same customer and pull the account two ways, and no one is watching the live picture. An agentic enterprise runs like an airspace, and an airspace does not run on permits. It runs on an air traffic controller, the one watching the sky who catches two cleared flights heading for the same point and moves one before they meet.
The firms are building better permitting offices. Coherence is the control tower. Build it before the shakeout does the watching for you.
Building that tower, and keeping it standing as the systems multiply, is the subject of my book, Coherence, arriving this Fall. If you want to follow the thinking as it develops, join the list at coherise.com. The one-page decision tool from the book is the first thing I send.