Despite model performance convergence and unprecedented ease of technical substitution, only 11% of enterprise builders switched AI providers in the past year. This striking statistic from Menlo Ventures' latest market data reveals a paradox that redefines our understanding of AI competition: switching is technically trivial but organizationally impossible. The explanation lies in the emergence of orchestration lock-in as the dominant force in AI markets.
Three months after publishing Part 1 of the Agentic Era series—where I first suggested orchestration as the new moat for LLMs—this empirical validation sharpens and extends our analysis in unexpected directions. In Part 1, I argued that the frontier AI race had shifted from model superiority to orchestration quality. The thesis was contrarian then—while the market still obsessed over benchmark scores and parameter counts, I emphasized the coordination layer between models and applications as the emerging source of competitive advantage.
The artificial intelligence market has now definitively crossed this strategic inflection point. The era dominated by raw foundation model performance has come to a close, giving way to a landscape where orchestration, distribution, and ecosystem control drive asymmetric returns. Understanding this evolution is crucial for determining the winners and losers in the LLM race.
The Market Transformation: Beyond Our Original Thesis
Menlo Ventures' mid-year LLM market update offers compelling validation of our orchestration framework, while also revealing dynamics that extend beyond our original analysis. The headline statistics paint a picture of a dramatic market reconfiguration: model API spending has doubled to $8.4 billion (from $3.5 billion last year), Anthropic has surged to capture 32% of the enterprise market share, and OpenAI's share has declined from 50% to 25%.
The Switching Paradox Revealed
The most critical insight lies in a seemingly mundane statistic: 66% of builders upgraded models within their existing provider, while 23% did not switch models at all this past year. Only 11% switched vendors. This low churn rate cannot be attributed to standard enterprise inertia or long-term contracts—the Menlo report itself highlights the "unprecedented ease of technical substitution."
This switching paradox illuminates a transformation in how AI creates competitive moats. The market has evolved beyond our original orchestration thesis to something more powerful: orchestration lock-in through what I call "loop dependence.” Loop dependence refers to the intricate web of dependencies formed by repeated interactions within an AI system, where each cycle of input, processing, and output builds cumulative value that is deeply embedded in organizational processes. This includes refined prompts tailored to specific behaviors, integrated tool chains that automate workflows, and historical context that informs future decisions—creating a self-reinforcing system that resists disruption and makes switching not just technically simple but organizationally prohibitive.
Ultimately, the new moats in AI are being built around networks, not castles. The value lies not in possessing the single most powerful model—though being at the frontier is a prerequisite for orchestration—but in controlling the orchestration layer that connects a vast ecosystem of models, tools, developers, and enterprise workflows. A later essay tests this distinction against a single company: Palantir’s moat is deep on context and the open question is whether that converts into orchestration.
Understanding Orchestration Lock-In: A New Form of Competitive Advantage
The convergence in model capabilities has fully materialized. GPT-4.5, Claude 4 Sonnet, Gemini 2.5 Pro, and leading open-source models now perform within a narrow 5% band on standard benchmarks. While changing an API endpoint is trivial, the actual switching cost lies in recalibrating the entire orchestration loop—retuning prompts, validating tool interactions, and ensuring behavioral consistency. This organizational complexity has frozen the market.
How Orchestration Lock-In Differs from Traditional Software Lock-In
Understanding orchestration lock-in requires distinguishing it from traditional software lock-in mechanisms. Traditional enterprise software creates switching barriers through data gravity, proprietary formats, training investments, and contractual obligations. These barriers are tangible, measurable, and often surmountable, provided sufficient resources and motivation are available. A company can migrate from Salesforce to HubSpot by exporting data, retraining staff, and accepting temporary productivity losses.
Orchestration lock-in operates through fundamentally different mechanisms. Where traditional lock-in creates walls, orchestration creates webs. The distinction manifests across several dimensions:
Traditional lock-in is static—the switching cost remains relatively constant over time. Orchestration lock-in is dynamic, growing stronger with each interaction. Every prompt refined, every tool integrated, and every workflow optimized increases the switching penalty exponentially. A company using traditional CRM software faces similar migration costs whether it switches after one year or five years. A company deeply integrated with an AI orchestration platform faces dramatically higher switching costs with each passing month.
Traditional lock-in is visible and quantifiable. Companies can calculate data migration costs, estimate retraining time, and model productivity impacts. Orchestration lock-in is invisible and emergent. The actual cost only becomes apparent when organizations attempt to switch and discover that their entire operational rhythm depends on specific AI behavior patterns. The accumulated context, refined prompts, and behavioral expectations create dependencies that resist simple quantification.
Most critically, traditional lock-in is primarily technical, while orchestration lock-in is fundamentally behavioral. When an organization switches from Oracle to SAP, the underlying business processes remain essentially unchanged. When an organization attempts to switch AI orchestration platforms, it must rewire the cognitive patterns of every user who has adapted to specific model behaviors, interaction patterns, and output formats. This behavioral dimension explains why the 11% switching rate is so remarkable—it reveals lock-in operating at the level of organizational habit rather than technical constraint.
Orchestration Evolved: From Connection Layer to Control Architecture
Orchestration has evolved from a simple connection layer into a control architecture—the persistent system that governs how intelligence accumulates and compounds. Five critical dimensions define this architecture:
Context Persistence - Every interaction builds on previous ones, creating a deep well of company-specific knowledge that is expensive to rebuild
Tool Coordination - Defines not only which tools are used, but also their sequence and interaction logic, as well as patterns that become deeply embedded in workflows
Behavioral Consistency - Maintains stable agent personas, reducing cognitive load and enabling the trust required for autonomous operations
Workflow Integration - Embeds AI touchpoints throughout existing processes in ways that become difficult to extract without disrupting the entire business
Feedback Loops - Ensures outputs continuously improve based on usage, creating a system that gets better and stickier the more it’s used
These dimensions combine to create the 'Orchestration Moat,' a conceptual model we put forward when we introduced the Agentic Resilience Architectural Framework (ARAF)—a framework assessing how companies maintain structural integrity amid agentic shifts—where its strength is a function of two variables: Moat Strength ∝ (Context Depth) × (Workflow Frequency). This framework now governs competitive dynamics in AI markets. Companies that maximize these variables create lock-in that persists regardless of model performance differences.