Evidence
Everyone is hiring forward deployed engineers. No one is building the system.
Forward deployment went from niche to boom in two years, and every platform and every consultancy answered the same way — hire more engineers. The market’s own numbers say that can’t scale — and the one company that made it scale did it by building the system, not hiring the most. No named clients, no private benchmarks; public data, sourced and dated.
§ 01 · The boom
The role exploded. The talent pool didn’t.
Forward deployment was a Palantir idiosyncrasy for two decades. In two years it became every AI-Native platform’s hiring priority — and the supply of engineers who can actually do the work never caught up. The press already has a name for the bottleneck: “the new AI limiting factor.” CIO · 2026
Year-over-year growth in forward deployed engineer postings, January–October 2025.
Bloomberry · Revealera data · 2025
Forward deployed engineers committed to a single platform’s field motion.
Salesforce · 2026
Deployment engineers OpenAI took on by acquiring Tomoro — buying the team rather than hiring it.
OpenAI · Tomoro · 2026
Enterprises predicted to abandon vendor-run agentic engagements by 2028 — scarce headcount they can’t sustain.
Gartner · via TechRepublic · 2025
§ 02 · The scramble
Everyone reached for the same answer: hire.
Read the numbers above and one pattern jumps out — platforms and consultancies alike are racing to staff forward deployment. The whole market is talking about the engineers. Almost no one is talking about the system that makes them compound.
The platforms
The labs and platforms are buying capacity any way they can — one committed a thousand-engineer team, another acquired a deployment startup outright rather than hire, a third named the role the limiting factor on its own growth.
Salesforce · OpenAI / Tomoro · Anthropic via CIO · 2025–2026
The consultancies
The integrators followed. EY stood up a dedicated forward deployed engineering practice; delivery consortiums formed around the labs to sell the same staffing answer at scale. The product everyone is selling is more people.
EY · trade press · 2025
Headcount is the universal answer — and the universal bottleneck. The engineers are finite; the operating model isn’t.
Everyone is talking FDE. Almost no one is talking system — and that gap is the whole opportunity.
§ 03 · The compounding proof
Palantir already proved the other path.
The company that invented forward deployment didn’t win by hiring the most engineers. It built the system around them — and the public filings show what that compounds into: output grows faster than the org chart, because field work flows through R&D as product formation, not the cost of revenue.
Revenue growth across 2020→2025 — on a base of roughly 4,400 employees.
Palantir 10-K filings · 2025
Headcount growth over the same period — revenue outran the org chart by nearly 4×.
Palantir 10-K filings · 2020→2025
Adjusted gross margin — higher than peers with a deep field motion, because compounding work becomes product, not cost of revenue.
Palantir · Q4 2025 investor materials
The same shape is observable across the frontier — Anthropic, Databricks, Snowflake, Stripe, HashiCorp. Patterns, not claimed clients. The +311% / +82% figures are computed from the 2020 and 2025 10-Ks.
§ 04 · The read
Hiring harder loses. The operating model wins.
The demand curve and the supply line diverge structurally. No hiring plan closes a gap that compounds.
The programs that win turn each deployment into the next one’s starting position. That isn’t a staffing change; it’s an operating model. The numbers above are the market’s; the method that compounds them is the work.
Start with one conversation.
These are the market’s numbers, not ours. If they describe the wall your program is hitting, one conversation establishes whether a Forward Deployed System fits — and the Maturity Map reads where you stand against them. Not a pitch, not a deck. You reach Cory directly, and you’ll hear back within a day.