Forward deployed engineer vs consultant
A consultant is accountable for the quality of the recommendation. A forward deployed engineer is accountable for whether the system is in production and being used. That single difference changes the contract, the timeline, the skill set, and who carries the risk when it does not work.
Both roles start the same way — someone from outside comes in, learns your business, and tells you something true about it. They diverge at the moment the analysis ends.
Where they actually differ
| Management consultant | Forward deployed engineer | |
|---|---|---|
| Deliverable | Analysis, recommendation, roadmap | A system running in your production environment |
| Ends when | The document is accepted | The system is in daily use and your team can run it |
| Core skill | Structured problem-solving, communication | The same, plus shipping production software |
| Measured by | Quality of thinking | Whether the number moved |
| Who builds it | You, or a third party they recommend | Them |
| Risk if wrong | You paid for a document | They are still standing there |
| Typical shape | Team, a few weeks to months, off site between sessions | One or two people, embedded, on site for the parts that need it |
The honest case for the consultant
Not a straw man — there are real situations where the consultant is the right buy:
- The question is strategic, not operational. Which markets, which acquisition, how to restructure. No amount of engineering answers that.
- You need the brand. A board or a lender sometimes needs a name on the cover. That is a legitimate business need even when it is not a technical one.
- You already have the build capacity and genuinely only lack the analysis.
- The problem spans the whole company. FDE work goes deep on one workflow. It is the wrong tool for a company-wide diagnostic.
Where the consultant model breaks down
It breaks on the same thing every time: the recommendation is not the hard part.
Ask anyone who has run an operations improvement project which phase killed it. It was almost never the analysis. It was the integration nobody scoped, the exception handling nobody knew about, the team that never adopted it, or the six months between the deck and anyone touching a keyboard.
By the time those surface, the consulting engagement is over. The document was correct. The problem is still there. And nothing in the arrangement made anybody responsible for that outcome.
The industry's own version of this distinction
JC Christian, president of the executive search firm Christian & Timbers, drawing the line between an FDE and what came before:
“Without the technical skills, professionals will operate more like consultants from years past, and without the business transformation piece, professionals will struggle to translate their technical expertise into business outcomes.”
Source: Nathan Eddy, “Forward-Deployed Engineer Shortage Is Holding Back Enterprise AI ROI”, Dice, 19 August 2026.
Note what he is saying: both halves are required. Technical skill without business transformation produces something nobody uses. Business transformation without technical skill produces a consultant. The role is defined by the intersection, and that is why the pool is small.
How to tell which one you are actually being sold
The title is not reliable — a lot of consultancies have relabelled their practice. Three questions cut through it:
- “Who writes the code?” If the answer involves a partner, a subcontractor, or “your team, with our guidance,” you are buying consulting with an engineering wrapper.
- “What is the last deliverable in the engagement?” If it is a document, a training, or a handover pack, the engagement ends before production. If it is a system in use, it does not.
- “What is your fee tied to?” Time and materials rewards duration. An engagement priced against the measured cost of the workflow rewards removing it.
What we do
We measure the workflow on site, price the engagement against that measured cost, build into your stack on your accounts, and stay through adoption. There is no document phase, and no phase that exists to justify the next phase.
If the measurement says the workflow is not expensive enough to be worth fixing, we say so and there is no engagement. That happens, and it is the reason the ones we take are good.
How the engagement runs → · How the number is arrived at →
What is a forward deployed engineer? · Hire one or buy an engagement · How an engagement runs
Get in touch
Email solutions@ikonic303.dev to start with the measurement. ikonic303 is based in Colorado and works with clients nationwide.