Enterprise AI Has an Orchestration Gap, Not a Platform Problem

Across 101 enterprises, agent orchestration is consolidating onto model-provider platforms — Anthropic’s Claude leads by a wide margin — chosen for the gravity of the underlying model and judged on reliable multi-step execution. But the ambition runs well ahead of the reality: most deployed “agents” are still chatbot wrappers, the control plane enterprises expect is deliberately hybrid to avoid lock-in, and real-time fiscal control over token burn remains the exception.

This wave of VentureBeat Pulse Research examines enterprise agent orchestration: which platforms enterprises run on, what drives the choice, what they optimize for, how they expect agent control to be structured, and — most revealingly — how orchestrated their deployed “agents” actually are and how tightly they control the cost of running them.

The central finding is a gap between orchestration ambition and orchestration reality. Enterprises are consolidating fast onto the major model platforms: Anthropic’s Claude is the primary platform for 40%, more than double any rival, followed by Microsoft (18%) and OpenAI (13%). The choice is driven by “model gravity” — native alignment with a state-of-the-art base model (21%) — and success is judged by reliable, multi-step execution (task completion reliability 32%, multi-step workflow management 28%). Yet asked to assess their portfolios honestly, 71% say a quarter or fewer of their deployed “agents” are true multi-step orchestrated workflows rather than single-prompt chatbot wrappers, and only 10% have crossed the halfway mark. The orchestration layer is being built well ahead of the orchestrated portfolio it is meant to run.

That gap shapes the architecture enterprises are putting in place. By the end of 2026 a clear majority (51%) expect a hybrid control plane — provider-native plus external orchestration — and only 6% expect to hand control to a provider-managed service, because vendor lock-in (35%) is the risk they fear most if control lives inside a model provider. Investment follows the build-out: agent workflow tooling leads the spend (34%), with security and permissions enforcement (25%) behind. And fiscal control lags throughout — more than a quarter (27%) have no real-time way to stop a runaway agent before the bill arrives.

Methodology

VentureBeat fielded this survey as part of its ongoing Pulse Research series, focused on enterprise agent orchestration. Responses are filtered to organizations with 100 or more employees (n=101), drawn from a single June 2026 wave. Because this is one wave rather than a pooled multi-month sample, the report reads cross-sectionally and does not infer month-over-month trends.

By organization size, the sample is spread evenly across enterprise bands: 100–499 employees, 2,500–9,999, and 50,000+ (21% each), with 10,000–49,999 and 500–2,499 (19% each). By role it is senior and buyer-credible: product and program managers (15%), CIO/CTO/CISO (13%), consultants and advisors (13%), and a spread of data, AI, and engineering directors and VPs. On purchasing, 81% are recommenders, influencers, or final decision-makers for AI solutions (66% recommender/influencer, 15% final decision-maker). Technology/Software is the largest industry at 44%, followed by Financial Services (17%) and Healthcare/Life Sciences (8%).

At 101 respondents the sample is robust enough to read directionally with reasonable confidence, though it remains self-selected and is not a probability sample.

Finding 1: Orchestration Runs on Model-Provider Platforms

Anthropic’s Claude leads; open frameworks are marginal

Enterprises were asked which agent orchestration platform they primarily use today. The answer concentrates on the major model providers — and on one in particular.

• 40% use Anthropic’s Claude Platform & Agent Skills — more than double any rival platform
• 18% use Microsoft AI Foundry / Copilot Studio
• 13% use OpenAI’s Agents SDK / Responses API
• 8% use Google’s Enterprise Agent Platform — plus 2% on Amazon Bedrock Agents
• 6% use LangChain / LangGraph — 5% build custom in-house, 3% aren’t orchestrating yet

A note on reading these shares: respondents are self-selected, and this question asked for a single primary platform, so the figures measure which platform leads each enterprise’s deployment within an AI-active technical decision-maker audience. A sample built this way can diverge substantially from spend-weighted market measures, and vendor figures should not be compared across separate VB Pulse surveys. Read these shares as a portrait of where this cohort has placed its primary orchestration bet today, rather than as market share.

The model platforms dominate. Anthropic, Microsoft, OpenAI, Google, and Amazon together account for roughly 80% of deployments, while open frameworks (LangChain/LangGraph) and custom in-house builds sit in single digits. Anthropic’s lead — 40%, more than double the next platform — mirrors the “model gravity” selection logic in Finding 2: enterprises are choosing the orchestration layer that comes with the model they want to build on. A small 3% are not orchestrating at all.

Respondents rate the platforms they run at 3.94 out of 5 overall, with “value for money” also at 3.94 and “ease of implementation” the weakest score at 3.85. A rating just under 4 out of 5, from users of whom 96% plan to change their orchestration approach within the year, reads as provisional acceptance: the platforms work well enough to run today, but not well enough to stop the search for something better.

Finding 2: Model Gravity Drives Platform Selection

The base model, not the tooling, decides the platform

Enterprises were asked what most influenced their orchestration platform choice. The single largest factor is the pull of the underlying model, though flexibility and ease of development follow close behind.

• 21% name model gravity — native alignment with a state-of-the-art base model
• 17% name flexibility across models and tools
• 17% name ease of development
• 14% name security and permissions
• 11% name total cost of ownership — 10% cite control over agent execution

Model gravity leading is the selection-side explanation for Anthropic’s platform lead: enterprises pick the orchestration environment closest to the frontier model they have standardized on. But the next tier complicates the picture — flexibility across models and tools (17%) and ease of development (17%) indicate enterprises also want to avoid being trapped by that choice, foreshadowing the lock-in fear in Finding 6. Security and permissions (14%) and total cost of ownership (11%) round out a pragmatic buying logic. Performance (latency/memory) sits last at 4%, a reminder that at this stage of adoption the binding constraints are model fit and optionality, not raw speed.

Finding 3: The Job Is Reliable Multi-Step Execution

Enterprises judge orchestration by whether it completes the work

Enterprises were asked what they optimize for — their primary success metric for orchestration. Reliability and multi-step workflow management dominate; developer- and user-facing metrics trail.

• 32% name task completion reliability — the leading success metric
• 28% name multi-step workflow management
• 17% name developer productivity
• 9% name end-user experience
• 9% name operational stability

Task completion reliability (32%) and multi-step workflow management (28%) together account for 59% of responses: orchestration succeeds, in the enterprise view, when it reliably carries a task through multiple steps to completion. Developer productivity (17%) matters but is secondary, and end-user experience (9%) is a minor concern, consistent with orchestration being an internal execution problem rather than a UX one. This reliability-first standard is exactly what makes the chatbot trap finding so pointed: enterprises define success as dependable multi-step execution, yet most of their deployed “agents” do not yet do multi-step work at all.

The trap is not evenly distributed. Splitting the sample by organization size, 77% of smaller enterprises say a quarter or fewer of their agents do true multi-step work, against 62% of larger ones. Larger enterprises are meaningfully further into genuine multi-step deployment; the chatbot trap is, directionally, a mid-market condition.

Finding 4: Consolidate, Productionize, and Build In-House

Three strategic moves are nearly tied for the year ahead

Enterprises were asked what major change they anticipate in their orchestration strategy over the next 12 months. Three moves cluster at the top, almost evenly split.

• 25% will increase investment in custom, in-house orchestration control planes
• 24% will standardize on a single centralized framework
• 23% will expand agents from sandbox into production
• 9% will shift toward turnkey, natively embedded architectures
• 8% expect model-native autonomy or external frameworks — split evenly

The top three — building in-house control (25%), standardizing on one framework (24%), and moving agents from sandbox to production (23%) — are statistically indistinguishable and tell a single story: enterprises are moving from experimentation to operational consolidation. They want fewer frameworks, more production exposure, and more ownership of the control layer; only 4% expect no change. The appetite for custom in-house control planes is notable alongside the platform concentration in Finding 1 — enterprises are standardizing on model-provider platforms while simultaneously planning to wrap them in proprietary control logic, a pattern that reflects both confidence in the underlying models and persistent caution about ceding architectural ownership to any single vendor.