Forward deployed engineering compared with the alternatives
Six ways to get software built and running. Pick one below and watch where the knowledge in your operation ends up: built into the system, known by your team, or lost.
Written by the Verne engineering team.
Last reviewed
- Written rules 8
- Exceptions handled from memory 10
- Workarounds 6
- built into the system
- 24/24
- known by your team
- 24/24
- not captured
- 0
Engineers learn the exceptions and workarounds on the floor, build them in, and hand the system to your team.
Pick your situation
Choose what you are trying to do. The table lights the model that fits and says why.
Best fit: Forward deployed team
The work has exceptions nobody wrote down and touches systems that must be connected. That is learned on the floor and built in place.
| Forward deployed team | Consultant | Solutions engineer | Staff augmentation | Outsourced project | In-house hire | |
|---|---|---|---|---|---|---|
| Where they work | Inside your operation, beside the people who do the work | Workshops, interviews and the boardroom | On calls and in your environment, for one vendor’s product | In your team, on the work you assign | In the vendor’s office, against a specification | In your team, permanently |
| What they produce | A working system on your data, and a team that can run it | Analysis, a recommendation and a plan | A configured and integrated product | Code on the tasks you set | Software that meets the specification | Whatever you direct, over years |
| Who directs the work | Shared: you own scope and priorities, the team owns how | The consultant, within the brief | The vendor’s product roadmap | Your engineering leads | The vendor’s project manager | You |
| Code and IP at the end | Handed to you at full delivery | Usually no code | The vendor keeps the product; you keep the configuration | Yours, as the work is done | Depends on the contract | Yours |
| How success is measured | One agreed metric, daily use and a handover test | Acceptance of the recommendation | The product live and adopted | Tickets closed | Sign-off against the specification | Performance reviews |
| Typical length | A two-week diagnostic, then 8 to 16 weeks per workflow | Weeks to months | The rollout of the product | Months, open-ended | The length of the project | Months to recruit, then years |
| How it is paid | Fixed diagnostic fee, then a monthly team fee | Day rate or fixed fee | Usually inside the product licence | Monthly per person | Fixed price or time and materials | Salary, benefits and recruiting cost |
Forward deployed engineer or consultant?
A consultant studies the operation and recommends what to change. A forward deployed engineer studies it and then builds the change in production, with the client’s data and people, and stays until the client’s team runs it. Choose a consultant for a decision; choose an FDE team when the decision is made and the hard part is making it work.
- Choose a consultant when
- the question is what to do, the options need an independent view, or the board needs a recommendation before any budget is set.
- Choose a forward deployed team when
- the problem is known, the fix runs through existing systems and exceptions, and you need it working rather than described.
Forward deployed engineer or solutions engineer?
A solutions engineer works for a software vendor and helps customers adopt that vendor’s product. A forward deployed engineer works for the outcome inside one client’s operation, across whatever systems it already runs, and writes production code where no product fits. The first sells and configures; the second builds and hands over.
- Choose a solutions engineer when
- you have bought a product and need it configured and integrated, and the vendor offers that help.
- Choose a forward deployed team when
- no single product covers the workflow, or the job is connecting the products you already own.
Forward deployed engineering or staff augmentation?
Staff augmentation adds engineers to your team to work on tasks your leads assign. A forward deployed team takes responsibility for one outcome: it discovers what to build, builds it and transfers it, measured by one agreed metric and a handover test. Augmentation adds capacity; FDE adds ownership of a result for a fixed period.
- Choose staff augmentation when
- your engineering leads know what to build and need more hands on the backlog.
- Choose a forward deployed team when
- nobody on your side has time to work out what to build, or the work sits in operations rather than in the product team.
Forward deployed engineering or outsourcing?
Outsourcing hands a specification to a vendor who builds it elsewhere and delivers against sign-off. Forward deployed engineering works where the specification is incomplete because the real process differs from the documented one. The team learns the gap on site, builds in short loops with the users, and ends with the client running the system.
- Choose an outsourced project when
- the requirements are stable, written and unlikely to change once users see the software.
- Choose a forward deployed team when
- users work around the official process, data sits in several systems, or past projects passed acceptance and then went unused.
Forward deployed team or an in-house hire?
Hiring builds permanent capability but takes months, and a first hire rarely has the range one workflow needs: discovery, integration, AI evaluation and operations. A forward deployed team brings that range for one engagement and hands the result to the people you hire, who pair with it during the build.
- Hire in-house when
- the work will continue for years and you can wait for the right people.
- Choose a forward deployed team when
- you need the first version working this quarter, and want your future hires to inherit a running system with a runbook.
Keep reading the guide
Questions about the alternatives
Is a forward deployed engineer the same as a solutions engineer?
No. A solutions engineer helps customers adopt one vendor’s product. A forward deployed engineer works toward an outcome inside one client’s operation, across all its systems, and writes production code where no product fits.
Is forward deployed engineering just consulting with code?
It shares the discovery work with consulting, but the deliverable is a running system, measured by daily use and handed to the client’s team after a handover test, not a report.
Can a forward deployed team work alongside our own engineers?
Yes. Your engineers pair with the team during the build and run the handover tests themselves, so the system moves to people who already know it.
Not sure which fits? Measure first
The two-week diagnostic measures one workflow and ends with a plan and a price. If the right answer is a product, a project or a hire, the plan says so.