翻訳待ち：What Founders Should Steal from the Forward-Deployed Engineer Model

AI サービスが一時的に利用できないため、復旧後に翻訳を補完します。

ESSAYAUG 202618 MIN READ What Founders Should Steal From the Forward-Deployed Engineer Model (and What to Leave) Every serious buyer of AI now gets the same thing: a senior engineer embedded in the business, judged on production outcomes. The real thing starts at $1 million a year. Five of its mechanics translate to founder scale, and this is the buyer's guide to them. Nabeel Qureshi joined Palantir in the summer of 2015. He later moved to Toulouse and spent a year working four days a week inside the factory where Airbus builds the A350. His team's software tracked work orders, missing parts and non-conformities across the production line. He calls it "Asana, but for building planes," and writes that it "ended up helping to drive the A350 manufacturing surge and successfully 4x'ing the pace of manufacturing while keeping Airbus's high standards of quality." The same essay holds the opposite memory. On other accounts, "you'd have a company buying an 8-12 week pilot, and we'd spend all 8-12 weeks just getting data access, and the final week scrambling to have something to demo." Same firm, same software, same hiring bar. What varied was where the engineer sat and how much license he had to push back. A decade later, the biggest names in AI have picked a side. In May 2026 OpenAI launched a Deployment Company with $4 billion from a nineteen-firm syndicate led by TPG. "Our customers tell us they need help going from pilot to production," said COO Brad Lightcap. "Deployment Company will put our engineers inside their teams, with the resources to ship." At the end of June, AWS announced a $1 billion Forward Deployed Engineering organization: pods of five or six engineers, forty-five-day engagement cycles. Two days later Microsoft unveiled Frontier Company, a $2.5 billion unit of some six thousand engineers and industry experts embedded inside customers. And in mid-July Anthropic, Blackstone and Hellman & Friedman, with Goldman Sachs among the investors, capitalized Ode with $1.5 billion to do the same work against live enterprise data. Every serious seller of AI has converged on the same delivery model: a senior engineer inside the customer's business, judged on production outcomes rather than demos. Here is the part that concerns you, the founder of a company doing $3 million to $15 million a year. None of this is being built for you. OpenAI charges at least $10 million per client for this kind of work, per The Information. The smallest deal size Palantir even discloses is $1 million, and its average customer is worth about $4.7 million a year to them ($4.475 billion in revenue across 954 customers, per the FY2025 10-K; the division is ours). You cannot buy the real thing. You can understand why it wins, and buy the five mechanics that survive translation to your scale. That is what this essay is for. (Disclosure, early and plainly: Mercury, the firm publishing this, sells senior advisory and engineering of the kind the last third argues for. Read accordingly.) The numbers everyone quotes, corrected You have probably seen the claim that 95% of AI pilots fail. It is a misquote, and since this essay will lean on the underlying study, the correction matters. The source is MIT's NANDA initiative, whose July 2025 report drew on 52 organization interviews, 153 leader surveys and 300+ public initiatives. What it found: despite $30 to 40 billion of enterprise investment in generative AI, 95% of organizations were getting zero return, meaning no measurable P&L impact roughly six months after their pilots. The pilot-level numbers are separate, and worse in a more specific way: of custom, task-specific enterprise tools, about 5% reached production. Generic LLM tools reached production around 40% of the time. The report is preliminary, self-described as "directionally accurate," and drew fire for its methodology (Futuriom: "The 95% figure is presented in one sentence, but the authors offer no detail on where they came up with that number"). Treat it as one loud data point, corroborated by quieter ones. The quieter numbers point the same way. S&P Global's 451 Research surveyed 1,006 IT and business professionals and found the share of companies abandoning the majority of their AI initiatives jumped from 17% to 42% in a year; on average, 46% of projects were scrapped between proof of concept and broad adoption. Gartner forecasts that over 40% of agentic AI projects will be canceled by the end of 2027; a forecast, and a directional one. The headlines skip why. RAND interviewed 65 practitioners and found 84% of them citing leadership-driven root causes, misunderstanding or miscommunicating what problem needed solving, as the primary reason AI projects fail. Data quality came second. BCG's survey of 1,000 executives attributes 70% of implementation difficulty to people and process, 20% to technology, and 10% to the algorithms themselves. McKinsey's State of AI survey tested 25 practices for their effect on EBIT impact from generative AI; redesigning workflows had the biggest effect, and only 21% of the companies using generative AI had done it at all. Read those side by side and the models stop looking like the problem. Projects die in data access and workflow fit, with nobody owning the outcome. The failure is in how AI gets delivered into a business. Which is precisely the problem the Forward-Deployed Engineer model was invented to solve, nineteen years before the current wave of announcements. The waiter and the kitchen In 2006, Alex Karp asked Shyam Sankar, Palantir employee number thirteen, why French restaurants are so good. His answer: the waitstaff work as part of the kitchen. They know the food, they course-correct the diner, they carry information both ways. Karp asked him to build that, for engineering. Sankar did, and in 2007 named it "forward deployed engineering," in his words "in homage to our customers." His summary of the idea has aged well: "we didn't believe in throwing our software over the wall in the hopes the customer would divine the correct meaning from it." Palantir's internal structure makes the idea concrete. The company splits engineering in two: Devs build the product ("one capability, many customers"), Deltas, the forward-deployed engineers, live inside a single customer ("one customer, many capabilities"). Until around 2016, Palantir employed more FDEs than product engineers. The company's own S-1 put it in one sentence: "Our forward deployed engineers ('FDEs') have travelled to bases in Afghanistan and factories in the industrial Midwest to deploy our platforms." Wall Street hated it. On May 19, 2016, Bill Gurley polled a room of investors on what they would pay for Palantir; zero hands went up above $1.5 billion, and the verdict in the room was "unprofitable consulting biz." The services-heavy model looked unscalable, low-margin, everything software investors are trained to run from. The verdict did not survive contact with the numbers. In 2023 Palantir posted a GAAP gross margin of 80.6%: $2,225.0M of revenue against $431.1M cost of revenue, per SEC filings (revenue, cost). Qureshi's comparison: "These are software margins. Compare to Accenture: 32%." The overfit, customer-specific work the Deltas did was continuously distilled by the Devs into products, and one of them, Foundry, now drives more than half of Palantir's revenue. In 2024 Palantir was the best-performing stock in the S&P 500, up 340.5%. Fiscal 2025 closed at $4.475 billion in revenue, up 56%, with US commercial revenue growing 137% in the final quarter. The consulting-shaped company turned out to be a product company with a better intake mechanism. One more detail from inside the model, courtesy of Ted Mabrey, a Palantir commercial leader, because it will matter later: the waitstaff in that French restaurant are not order-takers. "If you want to order the wrong wine with the fish, the wait staff will simply tell you no." The skeptics are mostly right Before you take any of this to your own company, sit with the objections, because they are strong and mostly correct. The cheap version first. When OpenAI's FDE hiring hit Hacker News, the recurring framing was dangus's: "Forward Deployed Engineer is just a title change for Solutions Architects." Another commenter, Avicebron: unless the FDE has real pull with the core product team, they are "nothing more than a glorified field engineer/technical consultant." Thomas Otter reduced it to an invoice test: "If you invoice this work to the customer it is consulting, if you don't it is customer success, support or presales." The serious version comes from inside Palantir. Mabrey wrote an essay in September 2024 titled, without ambiguity, "Sorry, that isn't an FDE." The companies now hiring "forward deployed engineers," he argues, are "replicating the form but not the function of the FDE." He calls them tribute bands. Ex-Palantir FDEs who joined them describe the experience "as feeling like they are in jail." The function, in his telling, rests on things a job title cannot carry: FDEs trained to act "as if you are the CEO, but with zero authority," an organization that wants its engineers yearning for scope creep because the customer's mission demands it, and economics that can absorb the cost. He is direct about those economics: over $1.1 billion a year from Palantir's top twenty clients, core products that took "10-20 different custom implementations before they could be synthesized," and "enormous key-man risk" the whole way. His essay ends by refusing the premise of essays like this one: the lesson is "to not copy the FDE but to provoke you to ask what assumptions are you making about the fabric of your company, and if you should be copying anything at all." Hold on to all of that, because it is true, and one more thing is also true: most of what is currently sold to mid-market companies under the FDE label is exactly what Mabrey says it is. A body shop with a new business card. But the refusal misses something at your scale. Mabrey's alignment problem, how you keep an embedded engineer loyal to the customer's mission when nobody has formal authority over anyone, is a big-company problem. Palantir solves it with training, culture and $10-million-plus multi-year contracts that make the customer's mission commercially existential. At a 40-person company most of that machinery has nothing to do, because the alignment exists in the room. The actual CEO, you, sits across the table. The data gatekeeper who can stall an enterprise pilot for twelve weeks is, at your company, one ops manager whose cooperation you can arrange by Thursday. The NANDA numbers back this up: mid-market top performers moved from pilot to full implementation in about 90 days, against nine-plus months for enterprises. The honest question left over is what disciplines the vendor, since a boutique's engineer still works for a firm that likes billable work. The answer has to be structural there too, only cheaper: a fixed fee instead of a running meter, a kill option after diagnosis, ownership passing to you at the end. The checklist at the bottom of this essay is that structure spelled out. What does not transfer, and should not be imitated: armies of embedded twenty-somethings, scope creep as a growth strategy, months of free pilots (Palantir's own S-1 concedes the model "often requires us to spend months … on pilot deployments at no or low cost"), five-year land-and-expand arcs, and the product-leverage economics that turn overfit gruntwork into 80% margins. Those parts belong to Palantir and to the four billion-dollar deployment ventures. Leave them. The menu, priced Strip the vocabulary away and a founder wanting serious AI help in 2026 has six options. Prices below are sourced or derived; where a number comes from a vendor talking their own book, it says so. OptionEntry costRealistic first-year all-inTime to a production [truncated for AI cost control]