Presales, consulting, implementation, FDE: four jobs behind one confused title

"Is forward deployment just consulting with a new name?" is usually answered with adjectives: more hands-on, more embedded, more accountable. Adjectives cannot be checked. Dimensions can. Four roles diverge on five things that a contract, a budget line and a performance review each record separately.

What actually differs

The five dimensions are who signs the work off, who builds, who carries acceptance risk, what the deliverable is, and what counts as success. Acceptance risk here means a specific thing: who absorbs the cost when the promised result does not materialise.

Role	Signs off	Builds	Carries acceptance risk	Deliverable	Success
Presales	Seller, on the deal	No — demos and prototypes	No	Deck, demo	Deal closed
Strategy consulting	Partner, on the report	No	Low — advice, not execution	Report, roadmap	Recommendation accepted, next engagement
Implementation	Customer, on the statement of work	Configures, migrates, trains	Partial — go-live, not outcome	Configured system plus training	Acceptance signed, project closed
Product engineer	Internal review	Yes, for many customers	Low for any single customer	Platform capability	Feature shipped and broadly adopted
FDE	Customer's business owner, on the customer's own data	Yes	Yes — the result in production	Running system plus reusable assets	Customer no longer needs them

Success points in opposite directions

A forward deployed engineer has succeeded when the customer no longer needs them. A consultant's business depends on the customer continuing to need them: the next study, the next phase, the retained adviser. This is not a moral distinction. It is what the contract buys. One buys a working system and a team that can run it; the other buys access to judgement for a period, and access has to keep being bought.

The distinction survives the obvious counter-example. Deployment firms want renewal and expansion as much as anyone. The difference is what a renewal is for: the next problem, or the same problem that never shipped. An account that renews because the first deployment still is not finished is not a success story with a longer timeline; it is an implementation contract wearing the title.

Why acceptance risk outranks skill

One comparison that circulates in the field literature puts external suppliers at roughly three times the success rate of internal builds, and attributes it not to talent but to where the risk sits: the party paid for the outcome pays for defining the problem wrongly. That is the mechanism the fourth column encodes. A role that is paid for advice is not punished for a bad definition; a role that is paid for a result is. The column is therefore a better predictor of behaviour than any skill list on a job description.

It also explains why the four roles are not a hierarchy. A strong implementation consultant can be more valuable than a weak FDE on a given project. The question is which risk the buyer is trying to move off their own books.

The boundary is not fixed, and pretending otherwise would be dishonest. Large consultancies have sold outcome-linked engagements for years, and implementation firms increasingly keep a product team. The dimension still discriminates, because what defines a role is not the contract type it occasionally signs. It is what the role is structurally set up to deliver, and what it is punished for missing.

The financial test

Revenue per head separates the roles empirically. The figures cited in the source material run from about $49,000 per employee at a large IT services firm, through about $89,000 at a global consultancy, to roughly $1 million at Palantir. These are different businesses with different pricing structures, and the gap is not explained by how hard anyone works. It is explained by what is being sold: hours, judgement, or a result that keeps producing value after the invoice.

A practice whose revenue per head tracks the consulting line is running consulting. That is a legitimate business. It is not the thing the title claims, and the title will not change the economics.

The test

Before the salary question, ask two about any role carrying the title: what does this person own the day after go-live, and whose data decides whether it worked. Vague answers to either mean the job is one of the other four, whatever the offer letter says.

See what a forward deployed engineer is responsible for, or how the career ladder prices that responsibility.