📊 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 moves to embed AI engineers directly into client operations, adopting Palantir’s deployment model. This shift aims to capture more value from enterprise AI, but raises questions about scalability and margins.

In early May 2026, Anthropic and OpenAI announced major initiatives to embed AI engineers directly into client operations, adopting a deployment model inspired by Palantir. This move signifies a strategic shift from merely providing models to owning the entire deployment process, aiming to deepen enterprise engagement and revenue streams.

Anthropic revealed a $1.5 billion enterprise-services venture with major financial firms to embed Claude AI into mid-market companies. Hours later, OpenAI announced its $4 billion ‘DeployCo’ initiative, including the immediate acquisition of consulting firm Tomoro to deploy 150 engineers directly with clients. Both labs are adopting the Palantir-inspired forward-deployed engineer (FDE) model, where engineers work onsite with clients to integrate AI into workflows, build operational systems, and ensure production readiness. This approach aims to capture the six-to-one service-to-software revenue ratio, addressing the bottleneck in enterprise AI adoption—namely, integration, security, and workflow redesign—rather than model performance itself. The move reflects the labs’ recognition that the real value lies in deployment and operational dependency, not just model access.

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 Engineers into Enterprise AI Deployment

This strategic shift indicates that the AI industry is moving toward full ownership of the deployment cycle, potentially transforming the enterprise software landscape. By embedding engineers directly into client operations, the labs aim to generate expanding, token-metered revenue streams, creating operational dependency and switching costs that could lock in clients long-term. However, this approach also introduces risks related to scalability and margins, as the FDE model is labor-intensive and resembles consulting more than software licensing. Success depends on whether deployment can scale efficiently or remains a costly, labor-bound process.

AI Engineering Starter Kit: The Practical Guide to Build, Train, and Deploy Real AI Applications with LLMs, MLOps, and Cutting-Edge Tools – Step-by-Step Projects for Aspiring AI Engineers.

AI Engineering Starter Kit: The Practical Guide to Build, Train, and Deploy Real AI Applications with LLMs, MLOps, and Cutting-Edge Tools – Step-by-Step Projects for Aspiring AI Engineers.

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Background on AI Industry and Deployment Challenges

Over the past decade, AI labs have primarily focused on developing models, with enterprise adoption lagging due to integration and workflow challenges. Research from MIT indicates that 95% of generative AI pilots fail to move beyond experimentation, highlighting the importance of deployment and operational integration. Historically, consulting firms have handled this layer, capturing a six-to-one revenue ratio over software licensing. The labs now see an opportunity to disintermediate traditional consulting by adopting Palantir’s FDE model, which combines engineering, deployment, and operational responsibility into a single, embedded service. This approach aims to accelerate enterprise AI adoption and lock in clients through operational dependency.

“The move signals a strategic shift from merely providing models to owning the entire deployment process, aiming to deepen enterprise engagement and revenue streams.”

— 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 Around Scalability and Margins of FDE Model

It remains unclear whether the FDE model will scale efficiently or remain labor-intensive, akin to consulting. The question is whether margins will expand as deployment standardizes or remain a permanent drag due to the high labor costs involved. The long-term viability of this approach depends on the ability to automate or standardize deployment processes at scale, which is still uncertain.

OpenCode Custom Workflows: Building Intelligent Automation with AI Agents (AI Agent Tools)

OpenCode Custom Workflows: Building Intelligent Automation with AI Agents (AI Agent Tools)

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps in Deployment and Industry Adoption

The immediate next steps involve the labs implementing these models at scale within client organizations and assessing their impact on margins. Monitoring how deployment costs evolve and whether standardization can reduce labor intensity will be critical. Additionally, industry observers will watch for further moves by other AI and enterprise firms to adopt or counter this embedded engineering approach, shaping the future landscape of enterprise AI deployment.

Amazon

on-site AI deployment hardware

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 embedding engineers directly into client organizations to build, deploy, and maintain AI systems in operational workflows, creating operational dependency and long-term revenue streams.

Why are AI labs adopting this deployment approach?

Labs see the deployment layer as the key to unlocking scalable enterprise AI adoption, capturing more value, and deepening client lock-in, especially as model performance is no longer the main bottleneck.

What are the risks associated with this strategy?

The main risks include high labor costs, potential inability to scale efficiently, and the possibility that margins could compress if deployment remains labor-intensive rather than automated or standardized.

How does this shift impact traditional consulting firms?

This move could disintermediate traditional consulting firms by internalizing deployment, turning what was once a service into a product-like, recurring revenue stream controlled by the labs.

What is the significance of the 6-to-1 service-to-software revenue ratio?

This ratio highlights that most enterprise AI spending is on services like integration and workflow redesign, not on the models themselves, emphasizing the strategic importance of deployment.

Source: ThorstenMeyerAI.com

You May Also Like

The stake. Why the answer to automation is broad-based ownership, not a bigger transfer.

The core response to AI-driven value shifts should be expanding ownership of capital, not increasing transfer payments, argues Thorsten Meyer.

The rails. Why European agentic commerce is co-defined by two converging regimes.

European agentic commerce is being shaped by two converging regulations: PSD3/PSR rebuilding payment rails and the AI Act’s high-risk AI standards, creating a complex legal infrastructure.

Readiness: Before You Fund The Answer

A new diagnostic tool offers companies a 20-minute assessment to determine if their AI projects are ready, preventing costly failures.

Portfolio. The synthesis.

A comprehensive analysis of six European institutional AI projects reveals a strategic framework for policy ahead of the EU AI Act enforcement in August 2026.