What is a forward-deployed engineer? A plain answer
What a forward deployed engineer is, how the role differs from a consultant, a software engineer and an agency, and how it works in a mid-sized company.
Devvion · Published
You've bought software that nobody uses. You've paid for a strategy deck that's still in a shared folder. You've run an AI pilot that looked good in the demo and never reached production. Somewhere in that history, someone has probably mentioned a forward deployed engineer, and you want to know whether it's a real way of working or a new job title for the same thing.
It's a real way of working. Here's what it means and where it fits.
A forward deployed engineer works inside your business until the system runs
A forward deployed engineer works inside a customer's business, alongside the people who do the work, and stays until the system is running and used. Put simply: our engineer works inside your business, not from a ticket queue. They sit in the meetings, watch how work actually moves, and build against what they see.
The term comes from how large AI and data companies deliver to their biggest customers. Instead of handing over software and a support address, they put engineers to work inside the customer's operation. The reason is simple: the real process is never the one described in a kickoff meeting. The exceptions, the workarounds and the spreadsheet nobody mentioned all show up in the first week on site.
Most people searching the term are looking at it as a job. This article looks at it from the other side: what it means for a company that buys this way of working.
Forward deployed engineer vs consultant, software engineer and agency
| | Where they work | What they deliver | When they leave | |---|---|---|---| | Consultant | Mostly outside, in workshops | Recommendations and a plan | When the report is accepted | | Software engineer | Inside the vendor's team | Features for many customers | Never there in the first place | | Agency | In their own office, from tickets | What the brief specified | When the scope is delivered | | Forward deployed engineer | Inside your operation | A working system your team runs | When it's running and owned by your people |
The difference with a consultant is that the advice and the build stay with the same people, so nothing is lost in a handover. The difference with a software engineer is that they build for one customer's operation, not for a product roadmap. The difference with an agency is that the brief isn't fixed on day one. It changes as the real process shows itself, and the person who sees it is the one deciding what to build.
What it costs to not have one
The usual pattern without someone working inside the business is a pilot that works on clean test data and stalls on real data. Meanwhile the manual work continues.
What made the difference wasn't a better AI model. It was someone noticing that a third of the documents came in a format nobody had mentioned, and building for that in week two instead of finding it in month four.
The fixed flow: rules first, AI on judgment
Request to Rules decide most to AI judges the rest to Person can override
- Request
- Rules decide most
- AI judges the rest
- Person can override
A forward deployed engineer usually automates the rule-based steps first, because they are cheaper to build, easier to test and make up most of the work. AI agents take only the judgment calls that remain, like reading an unusual request. Every AI step logs its reasoning, and a person can override it. That's the practical answer to "where does AI fit here": after the rules, on the decisions that are left.
How Devvion applies it to mid-sized companies
Until recently, this way of working was priced for enterprise accounts. We've run this at scale in large-enterprise operations, and Devvion brings it down to companies of 50 to 500 people.
Forward-deployed engineering is one of our two services. The other is business consulting, for when the process itself needs redesigning before anything is built. Both follow the same six stages: assess, map, mature, automate, optimise, run. Consulting lives mostly in the first three, engineering in the last three, and most clients buy both in sequence.
On the engineering side, we step in as the engineering expert. Our engineer joins your operations meeting every week, maps the workflow inside the tools you already use, decides what to automate first and builds it. They're on site for the start and the key weeks, and remote in between. The people you meet stay on your work from the first day to the last.
Engineering engagements run 6 to 16 weeks. Weeks one and two are the two-week assessment. By around week six, the first automation is live and measured on your data. The remaining weeks add the next automations, AI where judgment is needed, documentation and training. Then you take it over, or keep us on a capped run retainer. You keep the code, the prompts and the accounts. More on how forward-deployed engineering works with us.
What to do this week without us
- Pick an owner. Name one person inside who will own the process after any outside help leaves. Without that person, no model works.
- Sit with the work for a day. Have that owner shadow the people doing the process, not their manager. Note every exception.
- List the decisions. Separate the steps that follow rules from the ones where someone uses judgment. That list tells you where AI might belong and where it doesn't.
- Check your last pilot. If an AI pilot stalled, find the step where it met real data. That's usually the gap a forward deployed engineer fills.
When to call us
Call Devvion when the process crosses several systems, when previous projects stalled between the plan and the build, or when nobody inside has the time to own both. We start with the two-week assessment, with the fee credited if you continue, and we keep to a handful of clients at a time. See how this applies in our use cases.
FAQ
What is a forward deployed engineer at Devvion?
At Devvion, it's an engineer who works inside your operation and stays until the system runs. They join your weekly operations meeting, decide what to automate first and build it. The people you meet stay on your work from the first day to the last.
How is a forward deployed engineer different from a consultant?
Devvion's engineers build what they recommend. A consultant typically advises and leaves; a forward deployed engineer stays until the change runs in your tools, is measured and is owned by your people. When the process needs redesigning first, our business consulting service does that part.
Is a forward deployed engineer the same as a software engineer?
Devvion's forward deployed engineers are software engineers, but the job is different. A software engineer usually builds a product for many customers. A forward deployed engineer builds for one customer's operation, from inside it, and spends as much time on the process and the people as on code.
Why not just hire an agency?
Devvion works differently from an agency because the brief isn't fixed on day one. An agency builds what was specified. Our engineer changes the plan as the real process shows itself. For a single, well-understood task, an agency can be the cheaper choice.
Does Devvion's model work for a company of 50 people?
Devvion designed it for companies of 50 to 500 people. At the smaller end, our engineer often works directly with the owner or COO. What matters more than size is having repeated weekly processes and one person inside who will own the result.