📊 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 their AI models directly into enterprise services using a Palantir-like forward-deployed-engineer approach. This shift aims to capture more value from deployment and deepen enterprise dependencies.

In early May 2026, the two largest AI labs, Anthropic and OpenAI, announced major initiatives to embed their AI models directly into enterprise services, adopting a strategy inspired by Palantir’s forward-deployed-engineer model. This move signals a significant shift in how AI companies plan to capture value beyond just providing models, focusing instead on the deployment and operational integration layer that is currently a bottleneck in enterprise AI adoption.

Anthropic revealed a $1.5 billion enterprise-services venture with firms including Blackstone, Hellman & Friedman, and Goldman Sachs, aimed at integrating Claude into mid-market companies. Hours later, OpenAI announced its $4 billion deployment-focused 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 adopt a Palantir-like model where engineers, called forward-deployed engineers (FDEs), work directly with clients to embed AI solutions into operational workflows, rather than just providing models or recommendations.

This approach emphasizes that the bottleneck in enterprise AI is no longer model performance but integration, security, and workflow redesign. The FDE model transforms deployment from a consulting-like service into a product-formation mechanism that creates operational dependency, switching costs, and recurring revenue, especially in a token economy where customer engagement scales with AI work.

Experts see this as a strategic move by AI labs to own the entire deployment and operational layer, shifting from a model-centric to a deployment-centric business. The approach also risks becoming labor-intensive, resembling consulting more than software licensing, raising questions about scalability and margins as the model is tested at scale.

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 move fundamentally alters the enterprise AI landscape by shifting value capture from model licensing to deployment and operational integration. It increases dependency on the AI providers, potentially creating a lock-in effect and expanding revenue streams through ongoing engineering work. The strategy also signals a recognition that AI’s real impact depends on how effectively it is integrated into business processes, not just model quality.

However, the labor-intensive nature of the FDE approach raises questions about whether margins will expand as platforms standardize or remain constrained by deployment costs. The success of this strategy could redefine enterprise AI adoption, making AI providers not just software vendors but operational partners embedded within client organizations.

Avid Pro Tools Artist - Music Production Software - Perpetual License

Avid Pro Tools Artist – Music Production Software – Perpetual License

This item is sold and shipped as a download card with printed instructions on how to download the…

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Model to Deployment: The Shift in Enterprise AI Strategy

Prior to 2026, AI companies primarily competed on model capabilities, with enterprise adoption often hindered by integration challenges. The industry recognized that model performance was no longer the main bottleneck; instead, the difficulty lay in operationalizing AI at scale, including security reviews, workflow redesign, and change management.

In 2024, research showed that 95% of generative AI pilots failed to move beyond experimentation, highlighting the need for better deployment strategies. The FDE model, pioneered by Palantir in defense and intelligence, proved effective in embedding complex systems into operational workflows. Both Anthropic and OpenAI are now adopting this approach to accelerate enterprise AI adoption and capture more value in the process.

“The move to embed AI models directly into operational workflows using a Palantir-inspired FDE model signifies a strategic shift from model licensing to deployment ownership, aiming to lock in clients and expand revenue.”

— Thorsten Meyer

The Machine Learning Solutions Architect Handbook: Practical strategies and best practices on the ML lifecycle, system design, MLOps, and generative AI

The Machine Learning Solutions Architect Handbook: Practical strategies and best practices on the ML lifecycle, system design, MLOps, and generative AI

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unclear Outcomes of the FDE Deployment Model

It remains uncertain whether the FDE approach will achieve sustainable margins as deployment scales. While the model is powerful in creating operational dependency, its labor-intensive nature may hinder scalability, and it is not yet clear if margins will expand or compress over time. Additionally, the long-term strategic impact on the traditional consulting industry and enterprise AI adoption remains to be seen.

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 Enterprise AI Deployment Strategies

Expect further announcements from AI labs and enterprise clients on the scaling of FDE-based deployment models. Monitoring how margins evolve and whether the approach leads to widespread industry adoption will be key. Additionally, regulatory, security, and operational challenges will influence how broadly these models are implemented across different sectors.

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.

Key Questions

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

The FDE model involves engineers working directly at client sites to embed AI into operational workflows, building and maintaining the deployment rather than just providing recommendations or models. It aims to create operational dependency and recurring revenue streams.

Why are AI labs adopting this deployment approach?

Because the main bottleneck in enterprise AI adoption has shifted from model performance to deployment, integration, and workflow redesign. Embedding engineers directly helps overcome these barriers and captures more value from AI solutions.

What are the risks of the FDE model?

The approach is labor-intensive, resembling consulting work, which may limit scalability and margins. It also creates operational dependency, which could be risky if clients seek alternative solutions or if deployment costs remain high.

How does this strategy affect the traditional consulting industry?

It displaces traditional consulting by integrating deployment work into the core product offering, potentially reducing reliance on third-party consultants and creating a new, embedded revenue model for AI providers.

Source: ThorstenMeyerAI.com

You May Also Like

The Bubble Is Not in Valuations: It’s in the Productivity Gap

Analysis of the emerging ‘productivity gap’ in AI, contrasting market valuations with actual measurable gains, and its implications for investors and companies.

Why AI Research Assistants Need Editorial Boundaries

Knowledge of editorial boundaries is crucial for AI research assistants to ensure fairness and trust, but the key reasons why remain…

AI Form Builders Explained: Build Your Funnel from Prompt to Finish in 60 Seconds

Discover how AI form builders turn simple prompts into complete lead funnels in under a minute. Fast, flexible, and game-changing for marketers.

Voice Dictation Software for Faster Blogging

Optimize your blogging speed with voice dictation software—discover how it can transform your writing process today.