What are the four things in the FDE handback packet?

The delta, what the customer runs that the product did not ship, written as configuration (prompts, rules, tools, thresholds) rather than narrative. The eval rows, the customer's cases that failed on arrival and pass now, runnable by the product team. The reversals, what the customer turned off or overrode and the FDE's best guess why. And the count, how many other customers by name share the problem. One page. No deck.

When should the handback happen?

Three moments. Two weeks in, a landing note on what the sales promise did not cover and what the FDE will build to close the gap. At go-live, the full packet, due the week the customer starts running on it. At day 60, a reversal update on what held after the FDE stopped watching, which doubles as the handoff to customer success.

What does product owe the FDE in return?

A named owner who reads every packet and is measured on what got generalized. A written decision within two weeks with three options, generalize, keep as configuration, or kill, sent back to the FDE with the reason. And when the answer is generalize, the eval the generalized version must pass on every customer in the count, written before engineering starts. Packets sent into silence stop coming.

Why does the handback matter more when a partner does the deploying?

Because a partner's engineer has every incentive to keep the customization inside the partner. Palantir's September 10, 2026 release naming Fujitsu a Global FDE Partner is the case in point. If the vendor wants the learning, the same packet, channel, and decision window have to be in the partner agreement, with the customer's configuration and eval rows belonging to the customer and portable.

Is there evidence that FDE learnings are not reaching product today?

Perspective AI's State of Forward Deployed Engineering 2026, a survey of 1,500 FDEs across 154 companies, found 64 percent describing their dominant work as deploying an existing product with significant customization, and FDEs typing customer notes into Notion, then a deal review, then a research write-up for the product team. The customization is the delta, and it is being written three times in formats a product person cannot act on. It is the firm's own survey, so treat the figures as an estimate.

What a Forward Deployed Engineer Hands Back to Product

What does a forward deployed engineer hand back to product?

THE SHORT ANSWER

A one-page packet with four things, not a story. The delta between what shipped and what the customer actually runs, in configuration terms. The customer's eval rows, the cases that failed on day one and pass now. The reversals, what the customer turned off and why. And the count, how many other customers by name have the same problem. It is due two weeks in, at go-live, and at day 60. Product owes back a named owner, a written decision within two weeks (generalize, keep as configuration, or kill), and the eval the generalized version has to pass on every customer in the count. Akshay Krishnaswamy, Palantir's chief architect, put the job as absorbing pain and excreting product; the packet is the pipe. Palantir naming Fujitsu a Global FDE Partner on September 10, 2026 makes the point sharper: when a partner does the deploying, the handback has to be a contract term with a format and a date, or the vendor pays to learn things about its own product that the partner keeps.

The handback is the half of the FDE model that decides whether the company is a software business or a services business with a software company's burn. Every deployment produces a delta between what shipped and what the customer runs. Either that delta becomes a decision on the product side, or it becomes a bespoke fork nobody reads.

Part 3 of The FDE Transition writes the handback down: the packet, the three moments, and what product owes back. The handbook chapter on the deployment-to-product loop is the mechanism the packet feeds, and what has to change in the product before FDEs can work is where the configuration boundary that makes the delta a diff comes from.

Last reviewed 2026-09-24 · 1 min read

What does a forward deployed engineer hand back to product?

SOURCES

THE LONG VERSION

RELATED ANSWERS