SC
Strategy Map›Layer 6 · Operating Model›Capabilities+ from outside the named canon

Forward-Deployed Engineering

What is Forward-Deployed Engineering?

A forward deployed engineer (FDE) is a software engineer who works inside a customer's operations, with its real users, data and workflows. FDEs stay until the product does the job, and what they build on site goes back into the core product, so later customers need less custom work. Palantir made the role well known.

Also calledforward deployed engineersFDEembedded engineering

How Forward-Deployed Engineering works

An engineer on site sees the real problem and can fix it in days, without long chains of handoffs. When the fix goes into the core software, the next customer starts with it already in place, so each deployment needs less custom work. Palantir's engineers adjusted the product on site and demonstrated it to the intelligence analysts who would use it, skipping the IT department. In 2016, soldiers in the 82nd Airborne did work in hours with Palantir that took days with the Raytheon-integrated system.

Embedded engineering teams are expensive. The model fails when each deployment stays a separate custom build, which turns the company into a consulting firm.

Embed with usersEngineers work on site with analysts
Solve the real problemAdjust the product to the mission data
Return it to productThe fix becomes part of shared software
Next deploymentStarts with less custom work
Each deployment improves the core product
The forward-deployed cycle as Palantir ran it with government analysts, where on-site fixes fed back into the software every customer uses.

How companies won with Forward-Deployed Engineering

From the win chains in Strategy Canon case studies: what the winner did, and what its rival did at the same step.

vs. Raytheon · 2006–16

Palantir

Forward-deployed engineers win the analysts directly

What it did
Engineers adjusted the product on site instead of selling from Virginia
Raytheon
Raytheon integrated to program requirements; soldiers asked to 'make it easier to use'
Read the Palantir case study →

Forward-Deployed Engineering vs. Implementation Services and Professional Services

What it isHow to tell it apartExample
Forward-Deployed EngineeringEngineers working inside customer operations, with fixes returned to the shared productLook for on-site engineering work that later customers reusePalantir engineers adjusting the product with analysts on site
Implementation ServicesMigration, configuration and training that get a purchased system into useGets one customer live; nothing needs to return to the productAn EHR rollout migrating records and training staff
Professional ServicesA sold line of human delivery that also feeds the product businessA separate revenue line; the people need not be engineersCrowdStrike's incident-response practice before its first product

How to tell if a company has it

  1. Engineers working inside customer operationsNamed engineering staff on site or embedded with users, working with their data and workflows.
  2. A consequential problem solved in useA real operational problem fixed in live work, beyond a demo or pilot.
  3. The fix returns to the productThe solution enters the shared product and is reused in another deployment with less custom work.
  4. Better results than the alternativeFaster adoption or better outcomes than a rival or the customer's previous approach delivered.

Who names it

AuthorWhat they call it / where it appears
Palantir +Forward Deployed Engineering — company terminology