How FDEs work with product and sales teams
Updated
The three interfaces that make or break field work: what sales needs, what product needs, and what the FDE owes both.
FDE work sits between the promise and the product. These interfaces decide whether that position is leverage or a trap.
Interface 1: FDE and sales
Sales sells the future; the FDE owns the present. The contract that works: the FDE attends late-stage calls, states scope and risk on the record, and never lets a deck promise what the brief does not contain. In return sales brings the FDE in before the promise, not after.
Worked example: a fictional deal (fictional) promises "AI triage in two weeks." The FDE reframes on the call: rules-based triage in two weeks with measured accuracy, model trial in week five if the data supports it. The deal still closes; the delivery survives.
Interface 2: FDE and product
Product needs field truth, not anecdotes. The FDE owes: every recurring ask logged with customer count, every workaround documented with its cost, every "the product cannot do X" with the revenue attached. Quarterly, the FDE brings the top three with numbers. That is how field work steers roadmaps.
Interface 3: FDE and the customer team
The customer team is the real successor owner. The FDE trains them from week one: shared runbook, joint incident review, named owners per component. Handover is a date, not a hope.
Checklist: healthy interfaces
- No commitment made without the FDE in the room.
- Every promise has a brief line behind it.
- Field asks reach product monthly with counts.
- The customer team can run the system before you leave.
Related reading
Straight answers
Frequently asked questions
Do FDEs report to sales?
Usually not. The healthy pattern is a delivery line with dotted accountability to the deal: committed dates, honest status, no shadow commitments.
What does sales need from the FDE?
A demo that survives questions, a scope line that protects the deal, and early warning when reality diverges.
What does product need?
Field evidence in writable form: recurring asks with counts, workarounds in use, and the cost of not building.