Most enterprises we talk to are not short on automation. The bots are deployed. The APIs are wired in. The first AI agents are moving out of the lab and into production. On paper, the estate looks healthy.
The trouble lives in the gaps between all of it. Work gets handed from one system to the next, and nobody owns what happens in between. That part of automation rarely gets designed on purpose. We have spent a decade buying capable tools, each one good at its own job, and almost none of us were ever handed the layer that makes those tools behave like one system. So the coordination ends up held together by schedulers, scripts, and people watching dashboards for the moment something breaks.
Gartner has put a marker down on where this goes. Their view is that by 2029, 90% of enterprises deploying AI agents across multiple platforms will run an abstracted universal orchestrator as a control layer for agents, bots, and humans inside a business process. The same research expects more than 40% of agentic AI projects to fail by 2027, and the reasons given are unclear value and weak governance, not weak technology.
Read those two findings together and the conclusion is hard to avoid. The next phase of automation maturity gets decided at the orchestration layer, by how well you can coordinate intelligent components you do not fully control, made by vendors you did not standardise on.
Which raises the question that matters more than any individual feature. Who owns that layer?
The pull toward bundling
The pull is strong and easy to understand. Every major automation vendor is moving up the stack, adding orchestration, AI, and governance to the execution tools they already sell. The pitch is convenience. One environment, one relationship, one roadmap.
The difficulty is architectural, not commercial. When orchestration is owned by the same vendor that runs your execution, your ability to coordinate work becomes a dependency on that vendor. The layer that is supposed to give you control over the whole estate only really sees the part of the estate that vendor sells.
Gartner names the risk directly. They recommend treating the universal orchestrator as a vendor-neutral abstraction layer, kept deliberately separate from execution. They warn that embedding it inside a heavy application platform recreates the same coupling and rigidity the orchestrator was meant to resolve. On the agent side it gets sharper still. Hard-code agent logic into specific applications and you end up with agent monoliths that cannot be upgraded or swapped later, which is the opposite of what anyone adopting agents at scale actually wants.
What independence actually means
I want to be honest about the word, because it gets overused. Being vendor-neutral by design does not mean an orchestrator magically reaches into anything. A system has to be API-addressable to be orchestrated. The honest version of independence is that the orchestration layer treats every addressable tool the same way, without bias toward one vendor’s stack, and without forcing everything to standardise before it will cooperate.
That is a claim about architecture. It is one a bundled platform structurally cannot make about itself.
There is a reason analysts and enterprises keep landing on the same principle. The orchestration layer should outlive any single tool choice. Tools will change. Vendors will rise and fall. The agent frameworks that look essential this year may look dated in three. Through all of it, the layer coordinating your work needs to stay yours.
When orchestration is bundled into an execution platform, you inherit the lock-in that comes with it. When governance is owned by a vendor, the objectivity you need to make clear-eyed decisions about that vendor quietly disappears.
The decision in front of you
It is not whether to use the big platforms. Most enterprises will, and often should. The decision is whether the layer that coordinates them belongs to one of them, or to you.
That is the call worth getting right before the estate grows past the point where the answer is easy to change. The honest first step is to look at your own estate and ask how much of your coordination already depends on tools you do not control, and what it would cost you to move.
Decouple before you’re coupled.
C TWO is the independent orchestration layer for enterprise automation.
