What goes on the month-two handoff page?

Four lines and a rule. The promise, which is the pre-contract handshake's three columns updated to what shipped, what is still being built and by when, and the no's. The signal, which is the customer's eval rows run on a schedule with the go-live pass rate as the floor. The watch list of what this customer is most likely to switch off or route around. The keys, the named person at the customer who can change the customer layer. Then the recall rule: rows under the floor, a reversal on the watch list, or a new workflow brings the FDE back.

Should the CSM take over the FDE's configuration work?

No. Jason Lemkin at SaaStr describes a CSM as covering 8 to 12 accounts and an FDE as embedding with 1 to 3 customers, and says they are barely the same profession. Chad Horenfeldt called FDEs-as-CSMs a trap because getting into the weeds of solutions takes CSMs away from understanding their customers' outcomes. The CSM inherits the page and the signal. Edit rights on the customer layer go to a named person at the customer.

When does the handoff start?

At go-live. The CSM joins the week the customer starts running on the deployment and overlaps with the FDE until day 60, when both sign the page. A handoff that starts the day the FDE leaves transfers a document and leaves the context in the FDE's head.

How do you know a deployment has landed?

Someone who is not the FDE can change it. If a named person at the customer can change a prompt, a rule, or a threshold and watch the eval rows run afterward, the deployment has landed. If the only person who can change it has left the building, the customer has a dependency.

What brings the FDE back after the handoff?

Three triggers: the customer's eval rows fall under the go-live pass rate, something on the watch list happens, or the customer wants a new workflow. Put a clock on the answer, two business days is a reasonable one. Three customers recalling for the same reason is a product signal and goes to the owner of the handback.

Where can I read the whole FDE series?

The FDE Transition on falkster.com, a twice-weekly series for people in the seat and the leaders building around it. It starts with the thesis that the FDE is the Product Builder arriving from services and continues through the handback to product, the contract with engineering, the promise with sales, month two with customer success, metrics, career, comp, and when not to hire FDEs at all.

Who Owns the Customer After the FDE Leaves

Who owns the customer after a forward deployed engineer leaves?

THE SHORT ANSWER

Customer success owns the account's trajectory from day 60, and a named person at the customer owns the keys to the customer layer. Raj Bheda at GainTrace describes the split: the forward deployed engineer owns the technical outcome at deployment, the CSM owns the business outcome across the term, and the handoff between them is the point most companies never write down. Write it down as one page, signed by both at day 60, with four lines. The promise: the pre-contract handshake's three columns, updated. The signal: the customer's eval rows on a schedule, with the go-live pass rate as the floor. The watch list: what this customer is likely to switch off. The keys: the person at the customer who can change a prompt, a rule, or a threshold without calling the vendor. Add a recall rule that says what brings the FDE back and how fast. The CSM joins at go-live and does not inherit edit rights. If the keys line is blank at day 60, the deployment has not landed.

The forward deployed engineer's attention is what holds a new deployment together. At day 60 that attention goes away, and the account moves to a customer success manager who covers many more customers and can't read the configuration. What survives that move is whatever got written down.

So write one page. The promise, the signal, the watch list, the keys, and a recall rule. The CSM owns the account from there. A named person at the customer owns the ability to change the customer layer, and if nobody does, the deployment is still being held up by the engineer who built it. Gartner's September 29, 2026 forecast, that 70% of enterprises will abandon agentic AI built by vendor forward deployed engineering by 2028 because they are "unable to evolve it on their own," is that blank line added up across a market.

Part 6 of The FDE Transition, Month Two: The FDE Leaves, the Workflow Has to Stay, makes the case in full. The handbook chapter on building the FDE team covers the pairing behind it: adoption is a deliverable, owned by name.

Last reviewed 2026-10-06 · 1 min read

Who owns the customer after a forward deployed engineer leaves?

SOURCES

THE LONG VERSION

RELATED ANSWERS