Insights: Forward Deployed Engineering vs staff augmentation vs outsourcing
Three ways to bring outside engineers into your work, what each one provides, and how to choose between them.
Summary: The short answer
Staff augmentation provides capacity: professionals who work under the client's direction. Outsourcing takes over a defined piece of work or a function. Forward Deployed Engineering (FDE) runs the process of solving a defined problem together with the client's team and ends with a handover.
None of the three is better in general; each fits a different situation. The page on the Forward Deployed Engineering model has the short comparison; this article adds the dimensions that matter when choosing.
Logevon is a technology consulting and software engineering company. Logevon works in the Forward Deployed Engineering (FDE) model, so this article is written from that position.
Definitions: Three models, defined
The three models differ first in what the provider is asked to do.
- Staff augmentation
- Staff augmentation is a model in which an external provider supplies individual professionals who work under the client's own management and direction.
- Outsourcing
- Outsourcing is contracting an external company to carry out work or run a function on an organization's behalf.
- Forward Deployed Engineering (FDE)
- Forward Deployed Engineering (FDE) is a delivery model in which engineers work embedded with a client's teams and business environment to understand the problem, build the solution within existing systems and transfer the knowledge needed to operate it.
The definitions already contain the main difference. In staff augmentation the client manages the people. In outsourcing the provider manages the work. In FDE the provider and the client work on the problem jointly, and transferring knowledge is part of the definition.
Comparison: Five differences that matter when choosing
Beyond who directs the work, the three models differ on five points.
| Staff augmentation | Outsourcing | Forward Deployed Engineering | |
|---|---|---|---|
| What the contract buys | Capacity: people and their time | A defined deliverable or a running function | Joint work on a defined problem, with a handover |
| Management effort from the client | Highest: the client plans, assigns and reviews the work | Lowest day to day; effort goes into specifying and accepting | Shared: client people take part throughout the work |
| When requirements change | The client redirects the people | The contracted scope has to change | Scope is revisited jointly against the original problem |
| Where the risk sits | With the client, who directs the work | Provider for delivery, per the contract; client for what was specified | Shared; the provider answers for the problem-solving process |
| How the work ends | When the capacity is no longer needed | On acceptance, or when the service contract ends | With a planned handover to the client's team |
The FDE column describes the model in general. Logevon itself is accountable for the problem-solving process, and knowledge transfer is in scope from the start.
Fit: When staff augmentation is the right choice
Staff augmentation is the right choice when the client already knows what to build and how, and lacks only the people to do it.
- A working team with its own technical leadership needs more hands.
- A specific skill is missing for a limited stretch of work.
- Priorities are expected to shift, and the client wants to redirect people directly.
- The client wants the knowledge to build up inside its own process and tools.
The strength of the model is directness. The added professionals join the client's planning, follow the client's standards and can be pointed at something else when priorities move. The condition is management capacity: because the client directs the work, the client also carries the planning, the review and the result. Where that capacity exists, in Logevon's view, more provider involvement adds coordination the client does not need.
Fit: When outsourcing is the right choice
Outsourcing is the right choice when the work can be specified in advance and the organization does not need to do it, or learn it, itself.
- The deliverable has clear requirements and a clear acceptance test.
- A function has to run reliably but is not where the organization wants to build expertise.
- Internal people cannot be spared to take part in the work.
- A single party should answer for delivery under a contract.
The strength of the model is clarity. A contract states what will be delivered or how a service will perform, and the provider organizes its own people to meet it. The client's effort concentrates at the edges: specifying the work well and accepting it carefully. The condition is that the specification holds. When requirements are still being discovered, each discovery becomes a change to the contract.
Fit: When Forward Deployed Engineering is the right choice
FDE is the right choice when the problem is tied to how the client's operations and systems work, and the client wants to run the result itself.
- The solution has to work with systems already in place.
- People from the client's team can take part throughout the work.
- The client wants to run and extend the result itself.
- The problem is still being understood, so a fixed specification would be premature.
The strength of the model is that the problem is understood where it occurs, and transferring knowledge to the client's team is part of the work. The condition is participation, and it is a real cost: FDE asks more of the client's people than outsourcing does. FDE does not fit when the client only needs extra developer capacity under its own management, when the work is a fixed specification to build and hand back, or when no one from the organization can take part. In those cases another model fits better.
Decision: Five questions to ask before choosing
The choice between the three models comes down to five questions about the work and about your own organization.
Can the work be specified now?
If the requirements and the acceptance test can be written today, outsourcing is workable. If they have to be discovered inside the operation, FDE fits better.
Who will direct the work day to day?
If your own technical leadership will plan and review it, staff augmentation fits. If you want the provider to carry that, look at the other two.
Can your people take part?
FDE needs named people with time set aside. If nobody can be spared, outsourcing asks the least of your team during the work.
Who should run the result afterwards?
If your team will operate and extend it, knowledge transfer has to be in scope: by definition in FDE, by contract in outsourcing, by your own organization in staff augmentation.
What happens when the requirements change?
Ask how each model absorbs a change: by redirecting people, by amending a contract, or by revisiting scope together.
Combination: Using more than one model
The three models can be used side by side, and an organization can move from one to another as the work changes. An FDE engagement can solve and hand over a defined problem, after which the client's team continues with added capacity through staff augmentation. A function that is stable and well specified can be outsourced while a problem that is still being understood is worked on jointly.
What matters is that each piece of work has one model and that everyone involved knows which. In Logevon's view, the risk lies in mixed expectations: a team engaged as capacity but judged on outcomes, or a contract written for a deliverable but used for discovery.
Different models suit different needs.
Limits: What this comparison leaves out
This comparison describes the three models in general terms and leaves out three things.
Not covered
- Price. No rate or cost comparison is given, because this article has no sourced data for one.
- Contract law. How liability and ownership are written is a matter for the contract and for legal counsel.
- Variation between providers. A provider may use the same label differently, so ask how it works.
FAQ: Questions about choosing
Is Forward Deployed Engineering consulting?
FDE is a delivery model, and a consultancy can be the one that applies it. It goes beyond advice: the work includes building the solution inside existing systems and handing it over to the client's team. The model is the same across Logevon's services.
Does FDE suit a small team?
Size is not the deciding factor; participation is. FDE needs people on the client's side who can take part and take over. A small team that can commit that time fits the model, and a large one that cannot does not.
Sources
This article cites no external sources. It rests on Logevon's glossary definitions, what follows from them, and Logevon's own method and view where marked.