📊 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 models directly into enterprise operations using a Palantir-like ‘forward-deployed engineer’ approach. This move aims to capture the large services market and deepen operational dependencies, but raises questions about scalability and margins.

In early May 2026, Anthropic and OpenAI announced simultaneous, large-scale efforts to embed AI models into enterprise workflows through a new deployment approach modeled on Palantir’s forward-deployed engineer (FDE) strategy. This move signals a shift from simply providing models to integrating them deeply into client operations, aiming to capture the expanding services market and create operational dependencies that generate ongoing revenue.

Within 72 hours in early May, Anthropic revealed a $1.5 billion enterprise-services venture with firms including Blackstone, Hellman & Friedman, and Goldman Sachs, focusing on embedding Claude into mid-market companies. Hours later, OpenAI announced its $4 billion deployment company, ‘DeployCo,’ with 19 investors and the immediate acquisition of Tomoro, a consulting firm with 150 engineers. Both initiatives adopt the Palantir-inspired FDE model, where engineers work directly with clients to deploy, integrate, and optimize AI systems within business processes. This approach emphasizes operational embedding over traditional model licensing, aiming to capitalize on the six-to-one services-to-software spending ratio and address the bottleneck in enterprise AI adoption—namely, integration and workflow redesign, not model performance.

Experts note that this strategy transforms the AI labs into entities resembling the consulting industry they aim to disrupt. The embedded engineers are tasked with building production systems, creating dependency, and enabling expansion through token-based revenue models. While powerful in creating lock-in and revenue growth, the approach is labor-intensive and raises questions about scalability and margins, as the FDE model resembles consulting more than software licensing, potentially limiting profit margins as the client base grows.

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 Embedding AI into Enterprise Operations

This shift signifies a fundamental change in how AI companies aim to monetize their models. By owning the deployment process and embedding engineers directly into client workflows, these labs are seeking to capture the large, lucrative services market and create sustained operational dependencies. This strategy could reshape enterprise AI adoption, making it less about model performance and more about integration, workflow redesign, and ongoing support. However, the labor-intensive nature of the FDE model introduces risks related to scalability and margins, potentially transforming these AI labs into entities resembling traditional consulting firms. This move also deepens the lock on enterprise clients, potentially stifling competition and accelerating AI-driven enterprise transformation.

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.

From Model Licensing to Operational Embedding

Prior to May 2026, AI labs primarily focused on developing and licensing advanced models, with deployment handled by clients or third-party integrators. The shift toward embedding engineers directly into client operations marks a strategic evolution, inspired by Palantir’s successful FDE model used in defense and intelligence sectors. The move reflects an understanding that model performance alone no longer constrains enterprise AI adoption; instead, the bottleneck lies in integration, workflow redesign, and change management. The move was prompted by research indicating that 95% of generative AI pilots fail to move beyond experimentation, highlighting the need for deeper operational integration.

Both Anthropic and OpenAI are now adopting this approach, with OpenAI’s DeployCo acquiring a consulting firm and deploying engineers alongside clients to build and maintain AI systems. This transition aligns with broader industry trends toward service-based revenue models and reflects a recognition that the future of enterprise AI depends on embedding models into business processes, not just licensing them.

“The labs are adopting Palantir’s FDE model because the model layer is becoming commoditized, and the real value lies in deployment and operational integration.”

— Thorsten Meyer

Multi-Agent AI Systems with MCP and A2A: Engineer Your Own AI Agent Framework with Tool Integration, Production-Ready Multi-Agent Workflows, and Shared Memory

Multi-Agent AI Systems with MCP and A2A: Engineer Your Own AI Agent Framework with Tool Integration, Production-Ready Multi-Agent Workflows, and Shared Memory

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Uncertainties Around Scalability and Margins

It remains unclear whether the FDE model will scale profitably over time. While initial deployments aim to create lock-in and ongoing revenue, the labor-intensive nature of embedding engineers may limit margins as the client base expands. There is also uncertainty about whether margins will expand as the platform standardizes or remain compressed due to proportional FDE hours required for new clients. The long-term viability of this approach as a dominant enterprise AI deployment strategy is still uncertain and will depend on how well the labs can standardize and automate these processes.

The Complete Guide to AI Prompt Engineering Training & Consulting

The Complete Guide to AI Prompt Engineering Training & Consulting

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps in Enterprise AI Deployment Strategies

Expect further announcements from Anthropic and OpenAI as they expand their deployment efforts and refine the FDE model. Industry observers will monitor whether the model achieves scalable margins or remains labor-dependent. Key milestones include the standardization of deployment processes, automation of engineering work, and the development of token-based revenue models that can grow without proportional labor increases. Regulatory and security considerations will also influence how widely and deeply this approach can be adopted across different industries.

Local LLM Inference Optimization: A Comprehensive Guide to Quantization, Hardware Acceleration, and Efficient Private AI Deployment

Local LLM Inference Optimization: A Comprehensive Guide to Quantization, Hardware Acceleration, and Efficient Private AI Deployment

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

What is the forward-deployed engineer (FDE) model?

The FDE model involves engineers working directly with clients to deploy, integrate, and optimize AI systems within their workflows, creating operational dependencies and ongoing revenue streams.

Why are AI labs adopting this approach now?

They aim to overcome the bottleneck in enterprise AI adoption—namely, integration and workflow redesign—by embedding engineers who can build operational systems, thus capturing the large services market and deepening client lock-in.

What are the risks of the FDE model?

The approach is labor-intensive, which may limit scalability and margins. There is a risk that margins could compress as the client base grows, unless processes are standardized and automated.

How does this strategy affect the future of enterprise AI?

If successful, it could shift enterprise AI deployment from model licensing to operational embedding, creating sustained revenue and lock-in, but it also risks transforming AI labs into entities resembling traditional consulting firms.

Source: ThorstenMeyerAI.com

You May Also Like

Why Token Streaming Breaks Beautiful UIs: Backpressure for Humans

Great UIs falter when token streaming overwhelms systems, and understanding backpressure is key to maintaining seamless, engaging experiences—discover why.

IdeaClyst: The Engine That Decides What’s Worth Building

IdeaClyst, an AI-powered idea engine, transforms rough concepts into validated, targeted product initiatives by analyzing roadmaps and market opportunities.

The Power Bottleneck: AI Data Centers and the Grid Cliff Approaching 2027-2028

Power availability limits AI data center expansion, with grid expansion lagging behind hyperscaler capex. Key developments point to a looming energy bottleneck by 2027.