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 large-scale investments to embed AI engineers directly into client operations, adopting Palantir’s deployment model. This move aims to control the entire enterprise AI deployment process, shifting from model development to operational integration.

In early May 2026, Anthropic and OpenAI announced simultaneous, large-scale initiatives to embed their AI engineers directly into client organizations, marking a strategic shift toward vertical integration into the enterprise services layer.

Anthropic revealed a $1.5 billion enterprise-services venture with Blackstone, Hellman & Friedman, and Goldman Sachs to embed its Claude AI into mid-market companies. Hours later, OpenAI announced its $4 billion ‘Deployment Company’ (DeployCo), with 19 investment partners and an immediate acquisition of consulting firm Tomoro, deploying 150 engineers to client sites from day one. Both initiatives mirror Palantir’s model of forward-deployed engineers (FDEs), who work onsite with clients, learn workflows, and build operational AI systems directly into business processes. This approach aims to address the bottleneck in enterprise AI adoption, which research shows is not model performance but integration, security, and workflow redesign. By owning the deployment process, these labs seek to generate ongoing revenue streams and deepen client dependency, moving beyond mere model provision to operational control.

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 Embedding Engineers into Clients

This strategic shift signifies a move by AI labs to dominate the entire enterprise AI value chain, transforming from model providers into operational partners. By embedding engineers, they aim to generate recurring revenue, reduce reliance on third-party consultants, and create operational dependencies that can lead to expanded, token-based revenue streams. This approach also risks increasing labor intensity and operational costs, raising questions about scalability and margins in the long term.

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.

Background of the Forward-Deployed Engineer Model

The FDE model, pioneered by Palantir in defense and intelligence sectors, involves engineers working directly within client organizations to build, deploy, and maintain operational systems. Historically, this model has been labor-intensive but highly effective at creating switching costs and operational dependency. The recent adoption by AI labs marks a significant shift, applying this approach to the broader enterprise market, aiming to accelerate AI adoption by integrating deployment into core workflows. The move responds to research indicating that most generative AI pilots fail to scale beyond experimental phases, primarily due to integration challenges rather than model performance.

“The labs are adopting Palantir’s deployment model to embed engineers directly into client operations, transforming AI deployment into a product formation process that generates expanding, token-metered revenue.”

— Thorsten Meyer

The AI Composer's Workstation: From Prompt to Production: A Hybrid Music Logbook for Suno, Udio & DAW Creators

The AI Composer's Workstation: From Prompt to Production: A Hybrid Music Logbook for Suno, Udio & DAW Creators

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Uncertainties About Scalability and Margins

It remains unclear whether the labor-intensive deployment approach will scale profitably over time. The key question is whether margins will expand as the platform standardizes or remain compressed due to the high costs of deploying and maintaining engineers for each client. The long-term viability of this model depends on whether deployment can evolve into a more automated, software-driven process.

Workflow Automation with Microsoft Power Automate: Design and scale AI-powered cloud and desktop workflows using low-code automation

Workflow Automation with Microsoft Power Automate: Design and scale AI-powered cloud and desktop workflows using low-code automation

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps in AI Deployment and Market Adoption

Following these announcements, further details are expected to emerge on how AI labs will manage deployment costs and scale their embedded engineer model. Monitoring client adoption rates, margin trends, and the development of standardized deployment platforms will be critical to assessing whether this strategy leads to sustainable, high-margin revenue streams or remains a labor-intensive approach.

StarTech 24U Enterprise-Grade Server Rack Cabinet Kit, 19in Enclosed 4-Post Rack with Shelf and Cable Management, 29in (75cm) Mounting Depth, 992lb (450kg) Capacity

StarTech 24U Enterprise-Grade Server Rack Cabinet Kit, 19in Enclosed 4-Post Rack with Shelf and Cable Management, 29in (75cm) Mounting Depth, 992lb (450kg) Capacity

ADJUSTABLE DEPTH: 4- Post 24U 19" server rack enclosure with 4 vertical rails and adjustable mounting depth 1.8"…

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

Why are AI labs embedding engineers into client companies?

To accelerate AI deployment by integrating models directly into business workflows, reducing reliance on third-party consultants, and creating operational dependencies that generate ongoing revenue.

How does this move compare to Palantir’s model?

Both approaches involve deploying engineers onsite to build operational systems, but AI labs are applying this to enterprise AI, aiming to control the entire deployment process and capture more value.

What are the risks of this deployment strategy?

The main risks include high labor costs, potential margin compression, and the challenge of scaling labor-intensive deployment as client needs grow.

Will this strategy lead to higher margins long-term?

It depends on whether the deployment process can be automated and standardized over time, reducing labor costs and increasing margins.

What does this mean for the future of enterprise AI?

It suggests a shift toward operational embedding and ownership of deployment, which could reshape how enterprise AI is adopted and monetized.

Source: ThorstenMeyerAI.com

You May Also Like

The City That Watches Itself: The Living Digital Twin, And The God’s-Eye View We’re Building

Cities are now developing real-time, AI-powered digital twins that monitor and simulate urban life, raising both planning opportunities and surveillance concerns.

Synthetic Biology: Designing Organisms for Agriculture and Industry

Synthetic biology is revolutionizing agriculture and industry by enabling precise organism design; explore how these innovations are shaping the future.

The New Divide Between Smart Devices and Smart Experiences

Lurking behind smart device promises lies a growing gap in personalized, secure experiences—discover how to bridge this divide and reclaim control.

The Continual Learning Research Map: Where the Memento Constraint Stands in May 2026

An update on the research landscape of continual learning for frontier AI models, highlighting the Memento constraint and current progress as of May 2026.