FDE vs consultant: delivery vs advice
Updated
Recommendations end in slides. FDE work ends in a system the customer runs without you.
Consulting scales advice across clients. FDE work concentrates delivery inside one customer until the system runs alone.
The short answer
Consultants are measured by recommendations accepted. FDEs are measured by systems operating after handover, with the metric to prove it.
The decision table
| Axis | Consultant | Forward deployed engineer |
|---|---|---|
| Deliverable | Report, roadmap, options | Running system plus handover |
| Production risk | Borne by the client team | Shared until handover, with stop lines |
| Code | Optional, illustrative | Required, tested, deployed |
| Timeline | Study then recommend | Slice, ship, measure, repeat |
| Proof | Accepted findings | Outcome metric on a date |
Worked example: the same recommendation, two endings
A fictional study (fictional) recommends consolidating returns lookup. Ending one: a 40-slide report and a handoff meeting. Ending two: the FDE ships the lookup page, cuts lookup under 3 minutes for 9 of 10 cases, and the runbook passes the silent-watch test. The advice was identical; only the second ending changed Tuesday. The handover post defines the test; the outcomes post defines the proof.
Checklist: which game
- You love structured analysis across clients: consulting. You love owning one system to handover: FDE.
- Slides are your best artifact: consulting. Readouts with numbers: FDE.
- Travel without pager duty suits you: consulting. Pager until handover is fine: FDE.
Related reading
Straight answers
Frequently asked questions
Is FDE just consulting with code?
No. Consultants advise and leave the build to others; FDEs build, ship, measure and hand over the running system themselves.
Which one do customers trust more?
Customers trust whoever owns the outcome through production. Advice plus delivery in one person is the FDE pitch.
Can consultants move into FDE?
Yes, and discovery plus stakeholder skills transfer directly. The gap to close is production craft: tests, deploys, rollbacks, runbooks.