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 initiatives to embed engineers directly into client operations, adopting Palantir’s deployment model. This strategy aims to dominate the services layer, which is six times larger than the model layer, to accelerate enterprise AI adoption and revenue growth.

In early May 2026, Anthropic and OpenAI announced simultaneous, large-scale initiatives to embed dedicated engineers directly into enterprise client operations, adopting a model inspired by Palantir’s deployment approach. This move signifies a strategic shift from merely providing AI models to integrating them deeply into business workflows, aiming to capture the vast services market and accelerate AI adoption across industries.

Anthropic revealed a $1.5 billion enterprise-services venture with firms including Blackstone, Hellman & Friedman, and Goldman Sachs, focused on embedding 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 the consulting firm Tomoro, deploying 150 engineers at launch. Both initiatives replicate Palantir’s forward-deployed engineer (FDE) model, where engineers sit with clients, learn workflows, and ship tailored AI solutions that become operational systems.

This strategy emphasizes the importance of the services layer—comprising integration, workflow redesign, and change management—which is roughly six times larger than the model layer. Industry research indicates that 95% of generative AI pilots fail to move beyond experimentation, highlighting the bottleneck in deployment and integration rather than model performance. The labs believe that owning the deployment process is key to scaling enterprise AI and capturing the associated revenue streams.

The FDE model is seen as both powerful and risky. It creates operational dependency and switching costs, potentially leading to scalable, token-based revenue. However, it is labor-intensive, resembling consulting work more than software licensing, raising questions about margin sustainability. The labs’ strategic goal is to embed themselves deeply enough to turn deployment into a product formation process, thereby expanding their influence and valuation.

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’ Shift to Deployment Integration

This development marks a fundamental change in how AI companies approach enterprise markets. By embedding engineers into client operations, labs aim to control the entire deployment process, creating operational dependencies that can generate recurring revenue and deepen client lock-in. This strategy also signals a move away from a model-centric focus towards owning the services layer, which is critical given that model performance alone no longer limits AI adoption. If successful, this could reshape enterprise AI economics, favoring firms that control deployment and integration over those that only provide models.

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 originated with Palantir, which refined it through defense and intelligence work, emphasizing embedded engineers who build operational systems for clients. In 2026, AI labs are adopting this approach to the broader enterprise market, recognizing that the bottleneck in AI adoption is not the model itself but the integration into existing workflows. Prior to this, AI companies primarily sold access to models, but recent research shows that most AI pilots fail to scale, underscoring the need for deeper deployment capabilities.

Both Anthropic and OpenAI’s recent moves are seen as attempts to replicate Palantir’s success, but at a much larger scale and with a focus on monetizing deployment work directly. This shift reflects a broader industry understanding that the services layer—covering integration, change management, and workflow redesign—is where the real value and revenue lie, and where AI companies are now directing their strategic efforts.

“The labs are applying the Palantir model to the broad enterprise market, embedding engineers directly into client workflows to build operational systems around AI models.”

— Thorsten Meyer

Amazon

AI engineer workstation

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 FDE model will sustain margins as it scales. The labor-intensive nature of embedding engineers resembles consulting work, which historically faces margin pressures as customer bases grow. Whether the labs can standardize deployment processes to achieve software-like margins or if deployment remains a labor-bound, high-cost activity is still uncertain. Additionally, the long-term strategic impact of owning the entire deployment cycle versus relying on standardized platforms is yet to be determined.

Amazon

AI integration software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps in Enterprise AI Deployment Strategies

In the coming months, further details will emerge on how these initiatives perform at scale. Monitoring the growth of DeployCo and similar ventures will reveal whether margins improve through standardization or decline with increased deployment complexity. Industry observers will also watch for client adoption rates, the development of standardized deployment tools, and the evolution of the labs’ revenue models, especially token-based recurring revenue streams. These developments will clarify whether the labs’ strategic bet on owning deployment will reshape enterprise AI economics.

Amazon

workflow redesign tools for AI

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 FDE model involves embedding engineers directly into client organizations to build, customize, and operate AI systems within their workflows, creating operational dependency and enabling scalable deployment.

Why are AI labs adopting this deployment strategy?

They aim to control the entire deployment process, reduce reliance on traditional consulting, and capture the large, recurring services revenue stream associated with integration and workflow redesign.

What are the risks of this approach?

The model is labor-intensive and resembles consulting work, which may lead to margin pressures as deployment scales. There is also uncertainty about whether margins can be standardized or if costs will remain high.

How does this shift affect the AI industry?

It signals a move toward owning the entire enterprise AI value chain, potentially reshaping revenue models, competitive dynamics, and the future of enterprise AI adoption.

What is the significance of Palantir’s influence?

Palantir’s successful deployment model serves as the blueprint for AI labs’ new strategy, emphasizing embedded engineering as a product formation mechanism that deepens client lock-in and revenue.

Source: ThorstenMeyerAI.com

You May Also Like

Advanced Testing Labs: What to Add After You’ve Mastered the Basics

Testing beyond basics unlocks new levels of precision and innovation—discover the advanced solutions that can elevate your lab to the next frontier.

Unlock the Secrets of Alpha and Beta Testing in Software Quality Assurance Automation

Learn about alpha and beta testing in software quality assurance test automation. Understand the differences, benefits, and how to effectively implement these testing methods in your software development process.

Agile QA Outsourcing

Agile QA outsourcing can streamline your software testing process. Learn how to effectively outsource your QA needs and ensure the quality of your product.

Exploring Agile Testing Methodologies | Best Practices

Agile testing is a crucial element of software development, ensuring the delivery…