The deployment. How the AI labs verticallyintegrated into the serviceslayer — the Palantir modelat scale.

📊 Full opportunity report: The deployment. How the AI labs verticallyintegrated into the serviceslayer — the Palantir modelat scale. on ThorstenMeyerAI.com — validation score, market gap, and execution plan.

TL;DR

In early May 2026, Anthropic and OpenAI announced major investments to embed AI deployment directly into enterprise services, adopting Palantir’s model of forward-deployed engineers. This shift aims to capture the massive services market but introduces significant risks related to labor intensity and scalability.

In early May 2026, the two largest AI labs, Anthropic and OpenAI, announced simultaneous initiatives to embed their AI models directly into enterprise operations through a new deployment approach inspired by Palantir’s forward-deployed engineer model. This move marks a strategic shift from focusing solely on AI model performance to owning the entire deployment and integration process, aiming to secure a larger share of the enterprise AI services market.

Anthropic revealed a $1.5 billion enterprise-services venture with Blackstone, Hellman & Friedman, and Goldman Sachs to embed Claude into mid-market companies. Hours later, OpenAI announced its $4 billion Deployment Company, ‘DeployCo,’ valued at $10 billion pre-money, which acquired consulting firm Tomoro to deploy 150 engineers immediately. Both initiatives adopt Palantir’s model, where engineers are embedded within client operations to build and refine AI systems directly on-site, ensuring operational integration.

This approach emphasizes that the bottleneck in enterprise AI adoption is no longer model performance but integration, security, workflow redesign, and change management—areas where the labs see significant growth potential. The labs aim to turn deployment work into a recurring, token-metered revenue stream by embedding engineers who develop operational dependencies, creating switching costs and expanding revenue with each client.

The Deployment — Thorsten Meyer AI
DEPLOY
● DISPATCH / MAY 2026
THORSTEN MEYER AI · ENTERPRISE REORG · § 03
ENTERPRISE REORG · 03
FDE / DEPLOY
Essay · Deployment-Architecture Forensic · 2026-05-29

The deployment.
How the AI labs vertically
integrated into the services
layer — the Palantir model
at scale.

In seventy-two hours, the two largest labs made the same move: embed engineers inside companies, the way Palantir does — because the model isn’t the bottleneck, deployment is.
Anthropic launched a $1.5B venture with Blackstone, H&F, and Goldman; hours later OpenAI launched its $4B Deployment Company (19 partners, $10B pre-money) and bought Tomoro for 150 forward-deployed engineers. The structure is copied from Palantir “almost line for line” — the engineer flies to the client, learns the workflow, ships software that wraps a model around the problem, and stays until production works. The reason is a ratio: for every $1 on software, companies spend $6 on services. The labs sold the software dollar; the services dollar is six times larger. The structural argument: the labs are vertically integrating into the services layer because the model commoditizes, the services layer is six times larger, and the FDE is not a consulting arm but a product-formation mechanism that converts deployment into uncapped, token-metered, operationally-locked revenue. The risk: the FDE resembles consulting more than software — and whether it scales is the open Palantir question they have all inherited.
72 hrs
Between the two labs making
the identical structural move
$1 : $6
Software dollar vs services dollar ·
the labs had the smaller half
~70%
Anthropic inference margin (from 38%) ·
why the embedded customer is rational
18-20%
Palantir services as % of revenue ·
the unresolved scalability question
THE DEPLOYMENT· ANTHROPIC $1.5B JV · BLACKSTONE / H&F / GOLDMAN· OPENAI DEPLOYCO $4B · $10B PRE-MONEY · 19 PARTNERS· TOMORO ACQUI-HIRE · 150 FDEs DAY ONE· COPIED FROM PALANTIR ALMOST LINE FOR LINE· $1 SOFTWARE : $6 SERVICES· THE MODEL IS NOT THE BOTTLENECK · DEPLOYMENT IS· 95% OF GENAI PILOTS FAIL TO LEAVE PILOT· FDE JOB POSTINGS +800% IN 2025· FDE = PRODUCT FORMATION, NOT SERVICES ARM· OPERATIONAL DEPENDENCY, NOT CONTRACTUAL LOCK-IN· SEAT PRICING → TOKEN PRICING · UNCAPPED CEILING· TOKENS ARE THE NEW COAL · PALANTIR IS THE TRAIN· BULL · PRODUCT FORMATION AT SOFTWARE MARGINS· BEAR · LABOR-BOUND SERVICES AT CONSULTING MARGINS· BECOMING THE CONSULTANTS THEY COMPRESS· THE DEPLOYMENT· ANTHROPIC $1.5B JV · BLACKSTONE / H&F / GOLDMAN· OPENAI DEPLOYCO $4B · $10B PRE-MONEY · 19 PARTNERS· TOMORO ACQUI-HIRE · 150 FDEs DAY ONE· COPIED FROM PALANTIR ALMOST LINE FOR LINE· $1 SOFTWARE : $6 SERVICES· THE MODEL IS NOT THE BOTTLENECK · DEPLOYMENT IS· 95% OF GENAI PILOTS FAIL TO LEAVE PILOT· FDE JOB POSTINGS +800% IN 2025· FDE = PRODUCT FORMATION, NOT SERVICES ARM· OPERATIONAL DEPENDENCY, NOT CONTRACTUAL LOCK-IN· SEAT PRICING → TOKEN PRICING · UNCAPPED CEILING· TOKENS ARE THE NEW COAL · PALANTIR IS THE TRAIN· BULL · PRODUCT FORMATION AT SOFTWARE MARGINS· BEAR · LABOR-BOUND SERVICES AT CONSULTING MARGINS· BECOMING THE CONSULTANTS THEY COMPRESS·
FIG. 01 — THE SIMULTANEOUS MOVE · TWO LABS, ONE STRUCTURE, 72 HOURS
When the two fiercest competitors make the identical move in three days, it is not a bet — it is a recognition
Both read the same constraint and reached the same answer: the model is not enough
Anthropic · May 4
PE-portfolio distribution
$1.5B
  • Blackstone, H&F, Goldman ($300M / $300M / $150M)
  • Apollo, General Atlantic, Leonard Green, GIC, Sequoia
  • Embed Claude in PE portfolio companies — hundreds of mid-market firms
  • Aligned with ~80% enterprise mix
OpenAI · May 11
Acqui-hire and scale
$4B
  • $10B pre-money · 19 partners (TPG, Bain, Advent, Brookfield)
  • Bought Tomoro — 150 FDEs day one (Tesco, Virgin Atlantic, Red Bull)
  • Builds the enterprise depth it lacked
  • ~2.7x the capital of Anthropic’s vehicle
OpenAI did not build the FDE org from scratch — it bought one (Tomoro) to start with 150 engineers already operating, a statement that the deployment work matters enough that building it organically was too slow. When competitors converge this precisely — standalone services entity, embedded engineers, investor-network distribution, FDE model — the move is not a differentiated bet; it is both companies concluding there is only one answer. Both labs are now, in addition to model companies, deployment companies — and they became so in the same week.
FIG. 02 — THE SIX-TO-ONE RATIO · WHY THE SERVICES LAYER IS THE PRIZE
The labs had been competing for one-seventh of the value their own technology unlocks
For every dollar on software, companies spend six on services
$1
Software
(the labs sold this)
$6
Services — implementation, integration, change management
(the deployment move claims this)
The ratio exists because making software work inside a real organization is harder than building it. For enterprise AI, the labs say model performance is no longer the bottleneck — integration, security review, evaluation harnesses, and workflow redesign are. MIT: 95% of GenAI pilots fail to leave the experimental phase. The scarce input is the engineer who understands both the technology and the business — FDE job postings rose 800% in 2025. The labs are reaching past the software dollar they own toward the services dollar they did not, by fielding the engineers who earn it.
FIG. 03 — THE PALANTIR MODEL · THE FDE IS PRODUCT FORMATION, NOT A SERVICES ARM
The most misread point — and the whole bet rests on it
Consultants operate downstream of the contract; FDEs operate upstream of the roadmap
The consultant
Delivers a recommendation — a deck, downstream of the contract. Accountable for the advice, not the outcome.
vs
recommend

build &
own
The forward-deployed engineer
Builds the production system, upstream of the roadmap. Accountable for whether it works. The bespoke build becomes the product.
The FDE is not a revenue-generating services business — it is the product-discovery and product-formation engine. The bespoke systems built inside clients become the patterns generalized into the product. Treating early deployment cost as a permanent margin drag rather than a product-formation investment is the systematic misread that has fooled Palantir’s investors for years. The dependency it creates is operational, not contractual — the system becomes woven into the institution’s operating fabric, a deeper lock than a license. Palantir’s answer to scale: the boot camp (12-18 month sales cycle → 5 days, >75% conversion, >$1M initial deal).
FIG. 04 — THE TOKEN ECONOMICS · WHY THE EMBEDDED CUSTOMER IS UNCAPPED
The FDE acquires an uncapped, token-metered annuity — which is why the high-touch cost is rational
A seat-based customer is capped by headcount; a token-based customer is bounded only by the work the AI does
The old unit · seat-based
Capped by headcount
A developer = a $20/month subscription. Revenue ceiling fixed by the number of seats. The deployment cost could never be justified against it.
The new unit · token-based
Bounded only by the work
That same developer = hundreds-to-thousands/month in tokens, scaling with the value the AI generates. The FDE’s job is to put the AI on more of the work.
Front-loaded deployment cost buys a recurring, expanding, uncapped token annuity — and with Anthropic’s inference margins reported at ~70% (up from 38% a year earlier), a high-margin one. That is what makes the high-touch acquisition cost rational: the labs are not buying a seat-capped subscription; they are buying an uncapped consumption stream and paying an engineer to maximize it. Palantir’s Shyam Sankar: “Tokens are the new coal. Palantir is the train.” The FDE is infrastructure for the token economy.
FIG. 05 — THE SCALABILITY QUESTION · WHAT DECIDES WHETHER IT WORKS
The whole vertically-integrated structure rests on whether the FDE scales — and that is genuinely unresolved
The FDE resembles consulting more than software · Palantir runs services at 18-20% of revenue after years
The bull case
The bear case
Product formation that scales. Token economics + boot-camp standardization make the FDE acquire uncapped, high-margin annuities; margins expand as the platform matures.
Labor-bound services that drag. Standardization lags the customer base; each new client needs proportional FDE hours; margins compress as it scales.
The labs capture the six-to-one services dollar at software margins — becoming something larger than software companies.
The labs run large, capital-intensive services operations at consulting margins — having become the consultants they set out to compress.
The token-economy tailwind (uncapped consumption, ~70% inference margins) genuinely differentiates the labs’ FDE from Palantir’s per-seat-era version — but it offsets the labor-cost question, by an amount not yet measured. Palantir, after years, runs services at 18-20% of revenue and a 50% adjusted operating margin — neither pure software nor pure services. The labs inherit that exact ambiguity, at larger scale and with less operating history. The bet is that the FDE is product formation that scales. The risk is that they have rebuilt consulting and called it product.
The labs have concluded the model is not the product — the deployment is — and moved, in the same week, to own the layer where the model meets the operation. Whether that makes them something larger than software companies or merely rebuilds a labor-bound consulting business at consulting margins is the Palantir question they have all inherited.
Thorsten Meyer · The Deployment · Enterprise Reorg 03

Implications of AI Labs’ Vertical Integration Strategy

This move signifies a fundamental shift in how AI companies approach enterprise deployment, emphasizing control over the entire operational pipeline. By embedding engineers directly into client workflows, the labs aim to lock in clients, generate ongoing revenue, and deepen their market dominance. However, the labor-intensive nature of this model raises questions about scalability and margins, as it resembles consulting work more than software licensing. The success of this strategy could reshape enterprise AI services, potentially displacing traditional consulting firms and establishing the labs as dominant providers of operational AI solutions.

AI Engineering and Agentic AI: Designing Autonomous Language Model Systems with Memory, Tools, and Safe Deployment

AI Engineering and Agentic AI: Designing Autonomous Language Model Systems with Memory, Tools, and Safe Deployment

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Strategic Shift Toward Deployment-Centric AI Business Models

Historically, AI labs focused on developing and licensing models, leaving deployment and integration to third-party consultants. Recent research, including MIT studies, shows that 95% of generative AI pilots fail to move beyond experimentation, primarily due to integration challenges. Palantir pioneered the forward-deployed engineer model in defense and intelligence sectors, which the labs now emulate to expand into enterprise markets. This shift reflects an understanding that model performance is no longer the primary barrier; instead, deploying and operationalizing AI effectively is the key to unlocking enterprise value.

The simultaneous announcements by Anthropic and OpenAI highlight a coordinated effort to adopt this integrated deployment approach, signaling a new phase in enterprise AI where the labs seek to own both the models and the deployment process.

“The labs are applying Palantir’s forward-deployed engineer model to the broad enterprise market, aiming to embed AI directly into client workflows and capture the massive services dollar.”

— Thorsten Meyer

The Enterprise Integration Architect Designing Secure, Resilient, and AI-Ready Digital Platforms

The Enterprise Integration Architect Designing Secure, Resilient, and AI-Ready Digital Platforms

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Uncertainties Surrounding Deployment Scalability and Margins

It remains unclear whether the embedded engineer model will scale sustainably or become a permanent labor-intensive drag, similar to consulting margins. The future profitability depends on whether deployment can be standardized or if each new client requires proportional FDE hours, potentially limiting margins and growth.

Your AI Survival Guide: Scraped Knees, Bruised Elbows, and Lessons Learned from Real-World AI Deployments

Your AI Survival Guide: Scraped Knees, Bruised Elbows, and Lessons Learned from Real-World AI Deployments

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps in AI Deployment and Market Adoption

Monitoring how the labs’ deployment initiatives perform across different industries will be critical. Key developments include whether margins improve as the model is standardized, how clients respond to embedded engineers, and if competitors adopt similar models. The success or failure of this approach will influence the broader enterprise AI market and the future role of traditional consulting firms.

AI Engineer Mug - AI Engineer Fuel Station - 11 oz Ceramic

AI Engineer Mug – AI Engineer Fuel Station – 11 oz Ceramic

DOUBLE-SIDED PRINT: Features the bold 'AI Engineer Fuel Station' design with a futuristic circuit board graphic printed on…

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

What is the forward-deployed engineer model?

The forward-deployed engineer (FDE) model involves embedding engineers directly within client operations to build, customize, and operationalize AI systems on-site, ensuring integration and ongoing support.

Why are AI labs adopting this deployment strategy?

Because model performance is no longer the main bottleneck; the real challenge is integrating AI into business workflows. Embedding engineers helps lock in clients, generate recurring revenue, and deepen market control.

What risks are associated with this approach?

The primary risks include high labor intensity, potential margin compression, and scalability challenges, as the model resembles consulting work that may not easily standardize or expand profitably.

How does this strategy compare to traditional AI licensing?

Unlike licensing, which involves selling software licenses, this approach focuses on ongoing deployment, customization, and operational support, creating a continuous revenue stream tied to client success.

Source: ThorstenMeyerAI.com

This content is for general information only and is not financial, tax or legal advice. Consult a qualified professional for decisions about your money.
You May Also Like

The Agent Trap: Why 90% of AI “Launches” Are Infrastructure Liars

Analysis of 2026 AI launches reveals 90% are features, not true infrastructure, risking vendor lock-in and misaligned expectations for enterprises.

The Door: Why the Interface Is Worth More Than the Model

SpaceX’s $60B purchase of a coding interface highlights the growing importance of the user interface over AI models, reshaping industry power dynamics.

The Eye Over the City: How Wide-Area Motion Imagery Works — and Where It Goes Blind

An in-depth look at WAMI technology, its capabilities, limitations, and evolving role in surveillance and defense.

Beyond Models: Tackling The Plumbing Challenges Of AI At Scale

Experts highlight that integration and orchestration bottlenecks, not model capabilities, are the main hurdles for large-scale AI deployment in 2026.