What goes on the pre-contract handshake page?

Every outcome in the proposal, not features, sorted by the FDE into three columns. Ships: the product does it today or it lives in the customer layer (prompts, rules, thresholds, connectors), and the FDE puts a date on it. Builds: it needs a harness change by pull request, so the FDE writes the estimate and names the engineer who has to say yes, with a date range. No: it needs a core change, or the product will not do it this year. Sales owns the number, the FDE owns the columns, both names go on the page, and it is attached to the contract.

Should a forward deployed engineer carry a quota?

No. Henley Wing Chiu's analysis of 1,000 FDE job postings found exactly zero percent are quota-carrying roles and only 8 percent mention on-target earnings. Joe Schmidt at a16z wrote that it is rare to find implementation leads who want a quota, that it leads to counterproductive behavior, and that services should be sold at cost. Pay variable on the customer's outcome and the renewal or expansion it produces. A net-new-revenue accelerator tied to deployments shipped, the drift Perspective AI's comp report describes, pays the FDE to call more outcomes shippable than are.

Who gets deal credit when the FDE is in the room before the signature?

The booking is the account executive's, all of it. The FDE's credit is the expansion, the second workflow, and the renewal, paid on the outcome that earned it. Splitting the booking builds a second sales engineer, and leaving the FDE off the expansion tells them the part after the signature does not count.

How does Ace Waves put FDEs on the sales team?

Per Ron Schmelzer at Forbes, Antanas Bakšys, founder of Ace Waves in Kaunas, Lithuania, says about a third of the company does forward deployed engineering, the engineers participate before a contract is signed to show what the technology does inside the prospect's own environment, the goal is a working system in the first month, and contracts pay on successful customer service resolutions. Ramūnas Zavistanavičius at Gritmind takes the opposite approach, small teams and workshops before committing an engineer, because the firm does not want to give its key engineers to someone.

How should a pre-contract week with an FDE work?

Cap it at a week, not a pilot. The FDE who scopes is the FDE who lands. The week produces the three-column handshake page and the first twenty eval rows from the customer's own cases, the same rows the codebase contract wants attached to harness pull requests and the handback wants in the packet. A company that cannot spare the engineer should run workshops first and not call the workshop team FDEs.

Who Owns the Promise Between a Forward Deployed Engineer and Sales

Who owns the promise between a forward deployed engineer and sales?

THE SHORT ANSWER

Sales owns the number and the FDE owns the scope, and the two meet on one page before the signature. The promise to a customer is made in the deck and on the second call, by someone whose number is bookings, and the forward deployed engineer inherits it the moment the contract is signed. So before any contract with an FDE attached is signed, the FDE sorts every outcome in the proposal into three columns: ships (the product does it today or it lives in the customer layer, with a date), builds (it needs a harness change, with an estimate and the name of the engineer who has to approve it), or no (it needs a core change, or the product will not do it this year). Both names go on the page and it is attached to the contract. The FDE does not carry a quota: Henley Wing Chiu's Bloomberry analysis of 1,000 FDE job postings found exactly zero percent are quota-carrying roles, and Joe Schmidt at a16z wrote that implementation leads rarely want one and that services should be sold at cost. Variable pay goes on the customer's outcome and the renewal or expansion it produces, never on bookings and never on an accelerator for deployments shipped, which is a quota with a lab coat on. Credit splits at the signature: the booking is the account executive's, the expansion is the FDE's. Ron Schmelzer's Forbes piece of September 19, 2026 quotes Antanas Bakšys of Ace Waves, whose FDEs are part of the sales team and participate before the contract is signed, with contracts that pay on resolutions; that is the strongest form of the handshake, and the one-page version is what a company does when it cannot send an engineer to every prospect.

The promise to a customer is made before the forward deployed engineer's accountability starts, in the deck and on the second call, by someone whose number is bookings. A Forbes piece this month put FDEs on the sales team before the signature, and the job data says none of them carry a quota. The gap between those two facts is where promises get made that nobody owns.

Part 5 of The FDE Transition closes it with a one-page handshake: three columns, sales owning the number, the FDE owning the scope, and both names on the page before the signature, plus the quota and credit rules that keep the FDE from becoming a second sales engineer. The handbook chapter on the line between an FDE and a sales engineer is where the accountability test comes from, and building the FDE team has the reporting line and comp rules the post restates.

Last reviewed 2026-09-29 · 1 min read

Who owns the promise between a forward deployed engineer and sales?

SOURCES

THE LONG VERSION

RELATED ANSWERS