The Forward Deployed Engineer Is Coming for the System Integrator’s Business Model – And That’s Not Entirely a Bad Thing
Every few years, enterprise IT gets handed a new three-letter acronym that quietly redraws who gets paid for what. This time it’s FDE – Forward Deployed Engineer. In roughly six months, AWS, Microsoft, Google Cloud, OpenAI, and Anthropic have all stood up their own FDE organizations, backed by something like $5–7 billion in combined committed capital. For an industry that has spent thirty years selling the labor that makes platforms actually work inside messy enterprises, that’s not a footnote. It’s a direct move into the System Integrator’s core business. So what actually is an FDE, why are hyperscalers and model labs suddenly building armies of them, and what should any of this mean to someone running or advising an IT services business? Below, I’ll walk through where this creates real opportunity for SIs, and where, if we’re honest, it quietly erodes the economics that have funded the industry for decades. What is a Forward Deployed Engineer, really? Palantir coined the term in the early 2010s. Its government and intelligence customers often couldn’t articulate requirements up front, the work was too sensitive, too undocumented, too tangled up in institutional tribal knowledge to spec out remotely. So instead of gathering requirements from a distance and shipping a document, Palantir embedded its own senior engineers physically inside the customer’s environment. They sat in on standups, wrote production code against the client’s actual data, and stayed until the thing worked. Palantir called them “Deltas,” and by 2016 the company employed more FDEs than conventional product engineers. The role was never a delivery afterthought, it was the primary way Palantir figured out what its product needed to become. That distinction is worth holding onto, because it’s what separates an FDE from every services role that already existed. A Solutions Architect designs a system and hands off a document. A Consultant advises and plans, usually while a separate delivery team does the building. A traditional SI delivery engineer builds against a signed statement of work, typically offshore-leveraged, priced by effort, and structurally walled off from the vendor’s own product roadmap. An FDE, by contrast, writes and ships production code inside the customer’s own environment, gets measured on operational outcomes rather than billable hours, and critically feeds what they learn in the field back into the core product itself. Then there’s the version of this role showing up inside IT services companies that aren’t themselves ISVs or platform owners, and it’s worth being precise about it, because SIs are already using the FDE label pretty loosely. An SI-side FDE is a senior, product-fluent engineer who embeds with a client to build and ship working software against someone else’s platform like Claude, Bedrock, Azure AI Foundry, Gemini Enterprise, an ERP, whatever the account happens to run on rather than the SI’s own IP. They don’t have a product roadmap to feed insights into, the way a Palantir or OpenAI FDE does. What they can offer instead is something the platform vendor’s own FDE structurally cannot: neutrality across platforms, account relationships built up over years, accumulated industry and regulatory context, and a willingness to stay accountable for a system long after the vendor’s engineers have rotated on to the next flagship logo. That’s the SI’s real moat. It’s just narrower than it used to be. The land grab, with numbers The pace here is what should get a services executive’s attention. In roughly a thirteen-week window in early-to-mid 2026, AWS committed $1 billion to a new Forward Deployed Engineering unit, which it says will grow to thousands of engineers working in pods of five or six per customer, alongside AI agents. Microsoft launched Microsoft Frontier Company, a $2.5 billion initiative it describes as going “beyond” the standard FDE model while explicitly saying it’ll lean on SI partners to help it scale. Google Cloud went on a public hiring push for dozens of forward-deployed roles, with CEO Thomas Kurian framing it as scaling “customer AI transformation,” and in the same breath promising to extend engineering support to its largest SI partners rather than simply competing with them. OpenAI launched the OpenAI Deployment Company, capitalized at more than $4 billion with TPG, Advent International, Bain Capital, and Brookfield as backers, and acquired a European deployment-engineering firm to get a roughly 150-person delivery team out of the gate. At the same time, OpenAI is running a “Frontier Alliances” program that certifies McKinsey, BCG, Accenture, and Capgemini as delivery partners, making those same four firms both OpenAI’s channel and, in the very same accounts, its competitor. And Anthropic formed a joint venture reportedly valued above $1.5 billion, with Blackstone, Hellman & Friedman, and Goldman Sachs, to embed Claude-focused engineering resources inside a standalone enterprise services company aimed at the mid-market. Why now, specifically? Because the adoption gap has become impossible to ignore. By the end of 2025, close to nine in ten companies had deployed AI in at least one business function, according to McKinsey and yet 94% reported no significant, measurable financial benefit from that spend. Hyperscalers and labs that have collectively committed hundreds of billions of dollars to AI infrastructure need that spend to convert into visible enterprise value, and fast. Handing a customer a model API and a support ticket queue clearly isn’t converting fast enough. Sending in your own senior engineers to make it work does. Where this genuinely helps SIs It would be a mistake to read this purely as an attack. There are real openings here for services firms, and the more capable ones are already going after them. Certified delivery capacity, for one, is turning into a kind of currency, and SIs are racing to build it up. Tavant rolled out W2W CoPilot to its entire workforce and has been training people across AI models more broadly. Accenture has put roughly 30,000 practitioners through a dedicated Anthropic business group focused on regulated industries. Deloitte has rolled Claude out across its full 470,000-person global workforce. Cognizant has done the same for 350,000 employees and is layering