definition
what is aforward deployedengineer?
the short answer
a forward deployed engineer (fde) is a senior engineer who works inside your team, in your codebase, and ships production software into your systems. the deliverable is running code, not a recommendation.
the model came out of ai companies that found the hard part was never the model. it was the integration: the crm, the erp, the ticketing queue, the billing system, and the fifteen exceptions nobody wrote down. an fde is the person who sits close enough to see those.
what a forward deployed engineer actually does
- works in your repo, on your stack, against your data.
- integrates with the systems you already run — crm, erp, ticketing, billing.
- handles the edge cases that never make it into a scoping document.
- leaves the code, the documentation and the governance plan with your team.
what it isn't
not a fractional cto
a fractional cto advises. an fde ships code. different deliverable, different week.
not a staffing contract
you are not renting a seat. the engagement is scoped to an outcome, with the scope and the exit clause written down before work starts.
not a slide deck
no strategy phase that ends in a recommendation. the engagement ends with software running in your operations.
what it costs, and how it is scoped
monthly engagement, scoped on a 30-minute discovery call. a common shape is 3 days a week, or 50% allocation dedicated to your work on those days. the scope, the ship date, the governance plan and the exit clause go in writing before you commit to anything, and the code is yours.
questions buyers actually ask
- what does fde stand for?
- forward deployed engineer. the term comes from ai and data companies that send engineers to work inside a customer's team rather than shipping software over the wall.
- how is a forward deployed engineer different from a consultant?
- a consultant produces analysis and hands it over. a forward deployed engineer produces production code in your repository. if the engagement ends and nothing new is running, an fde engagement failed and a consulting engagement did not.
- is a forward deployed engineer the same as a fractional cto?
- no. a fractional cto advises on technology decisions. an fde ships code. the two are complementary, and you can want both, but they are not substitutes.
- what if the engineer assigned isn't a fit?
- two-week chemistry window. if it is not right, we swap them at no cost. the point of naming the engineer is accountability, not lock-in.
- can the engineer work part-time with our team?
- yes. the common shape is 3 days a week, or 50% allocation, dedicated to your work on those days.
- who owns the code a forward deployed engineer writes?
- you do. the code is yours, in your repository, with the documentation and the governance plan alongside it. that is written into the terms before work starts.
- when do you actually need one?
- when you know roughly what you want ai to do, and the blocker is the integration rather than the idea. if you are still deciding whether to invest at all, readiness and strategy work comes first.
want one embedded with your team?
the enterprise implementation service is where this runs. terms, scope and exit clause in writing.
see enterprise ai implementation