📊 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 engineers directly into client operations, adopting a Palantir-inspired model. This move aims to accelerate enterprise AI deployment and capture new revenue streams, but raises questions about scalability and margins.

In early May 2026, Anthropic and OpenAI announced simultaneous, large-scale initiatives to embed their AI engineers directly into client enterprises, marking a strategic shift toward vertical integration within the services layer. This approach aims to accelerate enterprise AI adoption by turning deployment into a product and revenue stream, fundamentally changing how AI is operationalized in business environments.

Anthropic revealed a $1.5 billion enterprise-services venture involving Blackstone, Hellman & Friedman, and Goldman Sachs, focusing on embedding Claude AI within mid-market companies. Hours later, OpenAI announced its $4 billion Deployment Company, ‘DeployCo,’ valued at $10 billion pre-money, with 19 investment partners and an immediate acquisition of consulting firm Tomoro. This move adopts the Palantir-inspired forward-deployed engineer (FDE) model, where engineers are embedded with clients, learn workflows, and develop operational systems that integrate AI models into business processes.

The rationale behind this shift is rooted in the understanding that the bottleneck in enterprise AI adoption is no longer model performance but the complexity of deployment, integration, and workflow redesign. According to MIT research, 95% of generative AI pilots fail to progress beyond experimentation, highlighting the need for deeper operational integration. The labs view the FDE model as a way to turn AI deployment into a recurring, token-metered revenue stream, embedding operational dependency and switching costs that promote retention and expansion.

While powerful, the FDE approach is labor-intensive, resembling consulting more than traditional software licensing. The key question is whether this model can scale profitably, with margins expanding as the platform standardizes or remaining a labor-heavy drag as customer base grows. The labs are betting that product formation, not services overhead, will drive long-term value, but this remains uncertain.

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

This development signifies a strategic shift by leading AI labs to own the entire deployment process, moving beyond model provision to operational embedment. By adopting a Palantir-like FDE model, they aim to capture the six-to-one services revenue ratio, creating a new revenue engine that deepens customer lock-in and operational dependence. This move could reshape enterprise AI adoption, making deployment a continuous, scalable product rather than a one-off service.

However, the approach introduces risks: the labor-intensive nature of FDEs may limit margins, and the long-term scalability of this model remains unproven. The success of this strategy could determine whether AI labs dominate enterprise AI deployment or face margins compression as the model matures.

Amazon

AI deployment management software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Background on AI Labs and Deployment Strategies

Prior to 2026, AI labs primarily focused on model development and licensing, with deployment handled through third-party consulting or client-side integration. The recognition that deployment and integration are the main bottlenecks led to a shift toward embedding engineers directly into client operations. Palantir pioneered the FDE model in defense and intelligence, refining it over decades, and now AI labs are adopting it for broader enterprise markets. The move coincides with research indicating that most AI pilots fail to scale beyond initial testing, emphasizing the need for deeper operational embedding to realize enterprise value.

This strategic shift reflects a broader trend of AI companies aiming to own the full value chain, from model access to operational deployment, to maximize revenue and customer retention.

“The AI labs are adopting the Palantir FDE model because the bottleneck is no longer the model but the deployment process itself, which they aim to own and embed.”

— Thorsten Meyer

Amazon

enterprise AI integration tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Uncertainties About Scalability and Margins of FDE Model

It is not yet clear whether the FDE model will be scalable in the long term or whether margins will remain compressed due to the labor-intensive nature of deployment. The key question is whether the platform can standardize enough to reduce costs and expand profit margins or if each new customer will require proportional FDE hours, limiting growth and profitability.

Additionally, the actual impact on enterprise AI adoption rates and whether this approach will significantly accelerate deployment remain to be seen, as the strategy is still in early implementation phases.

Amazon

AI engineer embedded solutions

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for AI Labs’ Deployment Strategy

AI labs will likely continue expanding their embedded engineer programs, testing scalability and margin dynamics. Monitoring how customers respond, whether deployment costs decrease over time, and how revenue growth compares to traditional licensing will be critical. Further, observing regulatory and security challenges as the embedded model becomes more widespread will shape future deployment practices.

Industry analysts will also watch for how competitors respond and whether this model becomes the dominant enterprise AI deployment strategy or remains a niche approach.

Amazon

AI workflow automation platform

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 enterprise AI deployment by integrating models directly into workflows, creating operational dependency, and capturing ongoing revenue streams through embedded, token-metered services.

How does the FDE model differ from traditional consulting?

Unlike traditional consulting that recommends solutions, FDEs build and implement operational AI systems on-site, becoming responsible for outcomes and creating ongoing revenue through embedded deployment.

What are the risks associated with the FDE approach?

The approach is labor-intensive, which may limit margins and scalability. It also risks creating long-term operational dependence that could be difficult to standardize or automate.

Will this strategy accelerate enterprise AI adoption?

Potentially, as embedding engineers reduces deployment friction, but whether it will significantly increase adoption rates remains uncertain and depends on scalability and cost management.

What does this mean for traditional AI and software companies?

It signals a shift toward owning deployment and operational integration, potentially disrupting traditional licensing models and increasing competitive pressure in enterprise AI services.

Source: ThorstenMeyerAI.com

You May Also Like

Open Banking Explained: How Your Financial Data Is Shared Securely

Learn how open banking securely shares your financial data and discover the powerful benefits it can bring to your financial management.

The NVIDIA Earnings Preview: What Q1 FY27 Will Reveal About the AI Cycle

NVIDIA reports Q1 FY27 earnings with a forecast of $78 billion revenue, revealing key signals about the AI cycle and data center demand.

Forward-Deployed Engineer Economics 2.0: The Unit Economics Math, Six Months Later

Six months after initial analysis, FDE unit economics reveal profitability at enterprise scale but risks at lower levels, influencing AI lab scaling strategies.

A War Room for Your Next Idea: Inside IdeaClyst

Discover how IdeaClyst transforms idea development into a focused, collaborative war room—empowering founders and teams to make smarter, faster decisions.