Key takeaways
- Model and token costs are only part of AI ownership economics. McKinsey's 2026 analysis of agentic workflows found that, in one banking customer-service example, human oversight accounted for 70-75% of variable run costs versus 20-25% for tokens; infrastructure and orchestration add additional fixed costs.
- The frontier-model layer is extraordinarily capital intensive and concentrated among a small number of model providers and hyperscaler partnerships. For most enterprises, the strategic question is not whether to recreate that layer but which differentiated capabilities to own above it.
- JPMorgan and BCG both concentrated proprietary investment above the frontier-model layer — in enterprise access, workflow integration, governance, proprietary knowledge, and employee capability — rather than trying to recreate frontier models. JPMorgan (more than 200,000 employees with access to its model-agnostic LLM Suite platform) and BCG (enterprise-wide AI upskilling plus the OpenAI Frontier Alliance) both illustrate the pattern.
- The Model Context Protocol meaningfully reduces integration lock-in by standardizing how AI applications connect to tools and data sources — though switching frontier-model providers can still require changes to prompts, evaluations, and orchestration.
- Menlo Ventures reports that in 2024, 47% of enterprise AI solutions were built internally and 53% were purchased; by 2025, 76% of AI use cases were purchased rather than built internally. The survey establishes the sourcing shift, not a single explanation for it.
A dangerous assumption sits inside most AI strategies right now: that building is the easy choice, because the tools have gotten so good. It used to be a reasonable assumption — if you built something, you owned it, you controlled it, no vendor risk, no dependency, no lock-in. But the economics of AI have quietly inverted that logic, and most mid-market companies and their PE backers haven't caught up yet.
Here is what actually happened: AI tools made the act of creating software dramatically cheaper. What they didn't change — and what keeps getting more expensive — is the cost of owning what you built.
The prototype is cheap. The production system is not. And in a market where the underlying technology evolves every six months, you're not just maintaining what you built — you're constantly rebuilding it to keep pace.
01The cost nobody is counting
When a team builds an AI capability today, the build cost is visible. The ownership cost is not.
AI ownership economics extend well beyond model usage. McKinsey's 2026 analysis of agentic workflows found that, in one banking customer-service example, token costs represented only 20-25% of variable run costs while human oversight represented 70-75%. Infrastructure, memory, management, analytics and agent orchestration add further fixed costs. The precise mix varies by workflow, but the strategic point is clear: token price is not total cost of ownership.
This is the trap. The question isn't whether you can build. You can. The question is whether you should own the whole stack when owning the whole stack is exactly the wrong place to spend your competitive energy.
02Where the market actually went
To understand the strategic reality, you need to understand what happened at the infrastructure layer over the last two years.
The frontier model layer has become extraordinarily capital intensive and concentrated. A small number of model providers, anchored by deep hyperscaler partnerships — Microsoft-OpenAI, Google-Anthropic, Amazon-Anthropic, and Meta among them — now account for the overwhelming majority of frontier AI compute and model development. The compute requirements, the research talent, and the capital needed to compete at this level are simply not available to the vast majority of companies. Building your own foundation model is not a strategic option for mid-market firms. It is a distraction.
What this consolidation means for you is actually clarifying: the question of whether to build at the model layer is already answered. The real question is which layers above that model layer represent genuine competitive differentiation for your business — and which ones do not.
03The layer that actually matters
JPMorgan figured this out faster than most. Rather than attempting to build or fine-tune foundation models, JPMorgan built LLM Suite, a model-agnostic generative AI platform their teams use to access AI capabilities across the organization. At its 2025 Investor Day, JPMorgan Chase reported that more than 200,000 employees globally had access to LLM Suite. The proprietary investment wasn't in the model. It was in the orchestration, the governance, the data integration, and the workflow layer around the model. That's where their competitive advantage lives.
BCG made a similar calculation. They built GENE, a proprietary chatbot that incorporates BCG research and proprietary interviews, while continuing to partner with frontier-model providers at the model layer rather than attempting to compete with them. BCG began rolling out a four-phase AI certification program across its 33,500-person workforce, embedding that capability advantage into the human layer of their business. In February 2026, BCG and OpenAI announced a multiyear expansion of their relationship through the OpenAI Frontier Alliance. CEO Christoph Schweizer described BCG's role as helping organizations redesign functions and workflows, upskill people, and create changes in P&L performance — rather than simply increasing model or token usage.
The pattern is consistent across the most sophisticated AI deployments: find the layer where your proprietary data, your domain expertise, or your customer relationships create genuine differentiation, and own that layer. Everything else is a candidate for partnership or purchase.
04Partnership isn't what you think it is
There is a mental model problem that holds many mid-market companies back from smart partnerships. They hear "partner with an AI vendor" and think of outsourcing, dependency, loss of control.
That's the wrong frame. The right frame is this: you are accessing a rapidly evolving capability at a cost basis you could never replicate internally, while retaining full ownership of the layer where your business actually differentiates. Partnership in the current AI market is how you stay current without burning your engineering capacity on infrastructure that is not your core business.
A growing set of companies in Anthropic's customer ecosystem — including Block, Apollo, Arctic Wolf, Augment Code, and others — are building differentiated products on top of Claude rather than building frontier models themselves. These are not companies that outsourced their AI strategy. They partnered at the model layer and built differentiated products on top. Gainsight offers a useful illustration of the same logic from the other direction: its Staircase AI product launched an MCP connector in the Anthropic Claude Store — a software company exposing its proprietary workflow and customer context to external AI systems rather than attempting to own the frontier-model layer. The partnership gives access to frontier capabilities. The proprietary workflow and data give differentiation. Neither alone would be sufficient.
05Open standards are reducing one important source of lock-in
The most legitimate concern about AI partnerships has always been lock-in. What happens when the vendor relationship changes? What happens when you're dependent on a capability you don't control?
That concern is now substantially addressed by an open standard called the Model Context Protocol, originally introduced by Anthropic in late 2024 and now adopted across the major AI providers including ChatGPT and Claude. MCP functions as what its documentation describes as a "USB-C port for AI" — a standardized interface between AI models and the data sources, tools, and systems they need to work with.
MCP meaningfully reduces integration lock-in by standardizing how AI applications connect to tools, data sources, and enterprise systems. That makes it easier to reuse the same external capabilities across different AI clients and model ecosystems. It does not make frontier models fully interchangeable: switching providers can still require changes to prompts, evaluations, orchestration, security controls, and model-specific behavior. But the integration layer is becoming substantially more portable than it was two years ago. One important component of partnership risk — integration portability — has become meaningfully lower.
06What the data says about how companies are actually deciding
If you're wondering whether your instinct to buy more and build less is supported by how sophisticated organizations are moving, the answer is yes — decisively.
In our own engagements, the companies that combine internal teams with external AI vendors tend to reach production faster than those insisting on building everything themselves. That is an operating observation, not a measured finding — but it is consistent with what the sourcing data shows.
Menlo Ventures' data shows a sharp shift toward purchased AI capabilities: in 2024, 47% of enterprise AI solutions were built internally and 53% were purchased; in its 2025 data, 76% of use cases were purchased rather than built internally. That shift happened in twelve months. The survey establishes the sourcing shift, not a single explanation for it. Our view is that rapidly improving vendors, ownership burden, and the value of preserving optionality are all contributing.
The portfolio approach — different sourcing strategies for different layers — is not a hedge or a compromise. It is the mature operating model. Vista Equity Partners formalized this logic into what they call an Agentic AI Factory approach across their portfolio companies, creating shared frameworks, shared evaluation criteria, and shared implementation patterns rather than leaving each portfolio company to figure out AI strategy independently. The PE model for AI is increasingly portfolio-level rather than company-level, and the firms that recognize this early are compounding their advantage.
07The framework you actually need
Before deciding what to build, buy, or partner on, there are six questions worth sitting with honestly: Does this capability create genuine strategic differentiation, or is it table stakes every competitor will have? How quickly is the external market evolving in this area — fast enough that anything you build today might be obsolete in eighteen months? Do you have a realistic right to win, given your current talent, data, and domain expertise? How reversible is the decision if you get it wrong? What is the true operating burden — not just the build cost, but the ongoing cost of running, maintaining, securing, and evolving this over three years? And most importantly: where does your proprietary advantage actually reside in this capability area?
The answers should drive you toward one of four positions.
Build and own
Your proprietary data or domain expertise creates a durable moat that external options cannot match.
Partner at the frontier, build on top
The JPMorgan and BCG model. Rent the fast-moving parts. Own the parts that are uniquely yours.
Buy a mature solution
Don't waste engineering cycles on commodity capabilities. Buy and move on.
Rent and learn
Preserve optionality. Avoid lock-in on capabilities that are still maturing. Stay light until the market clarifies.
Most companies, when they work through this honestly, find that they have overinvested in the Build quadrant and underinvested in the Partner and Rent quadrants. The result is too much engineering overhead on capabilities that don't differentiate, and too little investment in the orchestration and workflow layers where real competitive advantage is built.
08The honest strategic conversation
The companies winning in AI right now are not the ones who built the most. They are the ones who made the clearest decisions about what to own and why.
JPMorgan's differentiation is not the foundation model; it is the enterprise layer around it. BCG's differentiation is not frontier-model research; it is proprietary knowledge, workflow redesign, and human capability built on top of frontier models. The pattern across every compelling AI success story in enterprise right now is the same: disciplined clarity about which layer matters, followed by concentration of proprietary investment at exactly that layer.
If you are a mid-market CEO or PE principal and you haven't yet had the honest conversation about layer-level AI strategy — not just "what should we build" but "where does our proprietary advantage actually live in an AI-enabled world" — that conversation is overdue. The market is moving fast enough that the cost of delayed clarity is no longer abstract. It is compounding every quarter.
References
- McKinsey & Company. (2026, August 24). Where AI agents pay off: A practical guide to the economics of agentic workflows. In a banking customer-service example, human oversight accounted for 70-75% of variable run costs versus 20-25% for tokens.
- McKinsey & Company. (2024, May 22). Strategic alliances for gen AI: How to build them and make them work.
- JPMorgan Chase. (2025, May 19). 2025 Investor Day Transcript. Reports more than 200,000 employees globally with access to LLM Suite, JPMorgan's model-agnostic generative AI platform.
- Boston Consulting Group. (2024, September 27). Introducing GENE: BCG's Advanced AI Chatbot.
- Boston Consulting Group. (2026, February 23). BCG and OpenAI Expand Partnership With OpenAI Frontier Alliance.
- Menlo Ventures. (2025, December 9). 2025: The State of Generative AI in the Enterprise. Reports enterprise AI solutions shifted from 47% built internally / 53% purchased (2024) to 76% purchased (2025).
- Gainsight. Staircase AI MCP connector, Anthropic Claude Store. Cited as an example of a software company exposing proprietary workflow and customer context to external AI systems.
Note on evidence: third-party findings are cited above. Statements describing what we see "in our engagements" are StatsLateral operating observations from client work, not industry benchmarks. The four-quadrant framework is our strategic model, not an empirical finding.