Claude leads enterprise orchestration while multi‑step agent use stays low
Anthropic's Claude leads enterprise agent orchestration by a wide margin, but the more revealing number in a VentureBeat Pulse survey of 101 enterprises is the gap between orchestration ambition and what those deployments actually do. Seventy-one percent of respondents say a quarter or fewer of their deployed "agents" are true multi-step orchestrated workflows, and only 10% have crossed the halfway mark. The platforms, budgets, and control architectures are being built ahead of the orchestrated portfolio they are meant to run.
The platform concentration is the part of the story that travels furthest. According to the survey, 40% of enterprises name Claude as their primary orchestration platform, more than double Microsoft at 18% or OpenAI at 13%. Anthropic, Microsoft, OpenAI, Google, and Amazon together account for roughly 80% of primary orchestration deployments (81 of 101). Open frameworks like LangChain and LangGraph, which dominate engineering discussion, sit in single digits. The respondents rate their chosen platforms at 3.94 out of 5 overall, a score the report itself characterizes as provisional acceptance, and 96% plan to change their orchestration approach within the year.
The selection logic behind that concentration is what the report calls model gravity. Native alignment with a state-of-the-art base model is the top factor at 21%, followed by flexibility across models and tools and ease of development, each at 17%. Enterprises pick the orchestration environment closest to the frontier model they have standardized on. Performance, in the form of latency and memory, lands last at 4%, which suggests that at this stage of adoption the binding constraints are model fit and optionality rather than raw speed.
The success metric that follows reinforces the same picture. Task completion reliability leads at 32% and multi-step workflow management at 28%, together accounting for 59% of responses. Developer productivity, prominent in framework discussions, comes in at 17%, with end-user experience at 9%. Orchestration, in the enterprise view, succeeds when it carries a task through multiple steps to completion. That reliability-first standard is exactly what makes the chatbot-trap finding pointed: enterprises define success by dependable multi-step execution while most of their deployed agents do not yet do multi-step work at all.
The control architecture that enterprises expect to put in place reveals the second structural tension. By the end of 2026, 51% expect a hybrid control plane combining provider-native orchestration with external layers, and only 6% expect to hand control fully to a provider-managed service. Adding hybrid, custom, and externally-abstracted architectures together produces 88% of respondents keeping at least partial control outside the provider. The reason surfaces directly: vendor lock-in leads the list of risks enterprises fear if control sits inside a model provider at 35%, ahead of security and permissioning limitations at 28% and inflexibility across models and tools at 21%. Compared to an April-May wave, lock-in moved from second to first place while security concerns dropped, a shift the report reads as enterprises moving past whether provider platforms can be secured toward whether they can be replaced.
Investment patterns point in the same direction. Agent workflow tooling leads the spend at 34%, followed by security and permissions enforcement at 25% and scaling infrastructure at 20%. Monitoring and debugging trails at 11%, with another 11% reporting flat budgets. The weight on tooling, permissions, and scaling over pure observability signals that enterprises are spending to build and harden orchestration rather than to watch it run.
Fiscal control is where the operational reality lags furthest behind. Twenty-seven percent of enterprises admit they have no real-time, programmatic way to stop an agent before a budget-breaking bill arrives, learning of overruns only from logs afterward. Another 32% rely entirely on native caps and throttles built into their primary platform, a control only as good as the provider's tooling and one that ties back to the lock-in concern above. The 23% building custom gateways and the 19% exploiting cross-model routing to arbitrage cost are the groups treating token burn as an engineering problem to control deterministically. Roughly one in three enterprises under 2,500 employees exercises only reactive control, against 20% of larger enterprises, a directional split consistent with the chatbot-trap pattern.
The strategic moves for the next 12 months cluster tightly around operational consolidation. Building in-house control leads at 25%, standardizing on one framework at 24%, and moving agents from sandbox to production at 23%, statistically indistinguishable from each other. Only 4% expect no change. The appetite for custom in-house control planes alongside platform concentration captures the same hybrid posture: enterprises are standardizing on model-provider platforms while planning to wrap them in control logic they own.
The defining constraint of the report is methodological rather than substantive. The survey draws from a single June 2026 wave of 101 self-selected respondents, a sample size robust enough for directional reading but not for precise measurement, and not a probability sample. The 71% chatbot-trap figure and the 40% Claude share both rest on that base. Whether the gap between orchestration ambition and orchestrated reality closes over subsequent waves, or whether the chatbot trap proves stickier than the roadmap assumes, is the question the source itself flags as open.