The Forward-Deployed Strategist: The Job Enterprise AI Is Creating.

Picture two people working on the same AI transformation.

One understands the business incredibly well but can't build anything.

The other can build almost anything but doesn't understand the business well enough to know what matters.

Historically, we called the first person a consultant and the second an engineer.

AI is beginning to break that distinction apart.

Look at where the market is moving.

Deloitte is expanding forward-deployed engineering teams. EY launched dedicated FDE roles to take AI from experimentation into production. KPMG describes forward-deployed engineers as operating at the intersection of strategy, technology and operations. BCG X now employs Forward Deployed AI Engineers working alongside business and industry specialists. Accenture says its FDEs own outcomes such as time-to-value, adoption, reliability and scalability—not simply project milestones.

This isn't just a new engineering title.

It signals a larger change in how enterprise technology gets built.

The old handoff is too slow

Traditional transformations often look something like this:

Consultants diagnose the problem.

Someone writes requirements.

Product interprets them.

Engineering builds.

Change-management teams prepare the organization.

Users finally see the solution.

Then everyone discovers something important was misunderstood six months ago.

AI makes that model increasingly unnecessary.

Prototypes can now be created in days.

Software iterations happen dramatically faster.

The expensive part is becoming less about physically producing code and more about making thousands of good decisions about what should be built.

That requires a different kind of person.

We call that emerging role the Forward-Deployed Strategist.

What does a Forward-Deployed Strategist actually do?

The title matters less than the behavior.

They live close to the problem.

They can spend the morning with a COO understanding why a process is failing and the afternoon working with engineers on how the system should respond to an exception.

They understand enough technology to know what's possible.

Enough business to know what's valuable.

Enough product to know what shouldn't be built.

And enough organizational reality to know that a technically correct solution nobody adopts is still a failure.

Their work produces four things.

1. A value thesis

Before building anything, they define:

What problem are we solving?

What happens today?

What is that costing us?

What would materially better look like?

How will we know whether it worked?

Strategy becomes measurable.

2. A map of how the business actually works

Not just systems.

People.

Decisions.

Data.

Handoffs.

Exceptions.

Incentives.

Tacit knowledge.

The strategist understands the operating reality well enough that engineering is solving the real problem instead of a sanitized version of it.

3. A working product

This is where the role differs from traditional consulting.

The work shouldn't end in a recommendation.

The strategist stays close enough to technical delivery to test assumptions continuously.

Build.

Put it in front of users.

Watch what breaks.

Learn.

Change it.

Deploy again.

The feedback loop between strategy and execution becomes extremely short.

4. A value scoreboard

Once deployed, someone has to answer the uncomfortable question:

Did this actually work?

Revenue.

Margin.

Cycle time.

Capacity.

Risk.

Adoption.

Reliability.

Whatever was agreed upon at the beginning.

The strategist remains tied to the result.

The team around them matters too

This doesn't mean one magical generalist replaces everyone.

Deep expertise still matters.

A powerful enterprise AI team might combine:

Industry expertise — people who understand the economics, edge cases and realities of the sector.

Forward-deployed strategy — people who translate messy business problems into products and outcomes.

Deep engineering — people capable of building secure, reliable, scalable systems.

Bring those capabilities together early rather than throwing work over walls between them.

McKinsey's recent collaboration with Wonderful makes the same broader point: transformation expertise and forward-deployed engineering are being brought together specifically to close the gap between strategy and production.

That's the shift worth paying attention to.

The engineer of the future won't be judged solely by the quality of the code.

The consultant won't be judged solely by the quality of the recommendation.

Increasingly, both will be judged by the same thing:

Did the business get better because you were there?

‍