Forward Deployed: What’s Real, And What’s Hype?
Dave McCann, Global Managing Partner, IBM Consulting Transformation Leader.
gettyYou’ve seen the headlines. You’ve read the LinkedIn posts. “Forward deployed” is everywhere.
I understand why. As someone helping transform global businesses, I spend a lot of time separating what creates value from what looks good on a slide. So, what’s my take?
Forward-deployed is real. Across industries, organizations are using AI-powered teams to accelerate delivery and unlock unprecedented value.
I’m seeing that momentum. Clients are moving beyond pilots and proofs of concept. They want a partner that can deliver results, not just recommendations.
But the market’s obsession with labels misses the point. The conversation has become fixated on a title: a forward-deployed engineer, a forward-deployed architect, a highly technical operator who understands the business problem, the technology and how to connect the two.
The title matters, but it’s only a fraction of the story. If the client is paying for an outcome, can a high performer with a trendy title deliver it alone?
From what I’ve seen, few enterprises struggle for lack of technical talent. They struggle when value creation breaks down between capability and adoption. Models get built, but processes don’t change. Use cases launch, but the business doesn’t trust them. Pilots work, but the operating models don’t exist to scale them.
Technical fluency isn’t enough to generate measurable value, as you also need a business case, industry expertise and an understanding of existing systems, governance and adoption.
At IBM, we call that team a forward-deployed unit (FDU). Unlike the individual-centric model dominating market conversation, a unit of experts brings the business context, industry knowledge, governance and decision-making required to move from strategy to implementation, while AI agents accelerate execution.
Enterprise transformation rarely succeeds in the hands of one exceptional person. A forward-deployed unit reflects that reality. Its composition may evolve from one engagement to the next, but its identity persists, allowing knowledge to accumulate, methods to improve and value to compound over time. The unit isn’t powered by a single engine, but a set of gears. It only functions when all of them are turning.
For decades, consulting scaled through labor: More people meant more output. AI is changing that equation. Output now depends on how effectively teams orchestrate technology, data, governance, expertise and reusable assets to solve business problems.
That shift changes more than just delivery. Many participants in the AI economy benefit when consumption increases: more tokens processed, more infrastructure deployed, more software licensed. But clients aren’t paying to consume technology. They’re paying for the value it creates. The most effective forward-deployed models are designed around that reality: maximizing impact, not consumption.
That’s why I think it’s important not to view transformation as a consulting abstraction, but as a practical challenge of connecting investments to measurable business results.
But not every client, nor every challenge, is suited to forward deployed delivery. This model can drive significant value in the right situation, but it isn’t a wholesale replacement for traditional consulting services.
If a client is primarily looking for additional capacity, has a clearly defined problem that can be solved through a repeatable methodology or doesn’t require ongoing collaboration and organizational change, more traditional delivery models may be a better fit.
Forward deployed units create the most value when success depends on a combination of technical expertise, business context, adoption and continuous learning to achieve outcomes.
The goal isn’t to chase the hottest industry trend. Two distinct swim lanes are forming.
The first is familiar: organizations continuing to purchase consulting services, augmented by AI. The tools are improving, productivity is increasing, but these clients are still, in effect, buying labor. Commercial models continue to evolve, with greater emphasis on value and outcomes, but the underlying transaction remains largely the same.
The second is different: organizations purchasing a highly focused solution with a full AI team and approach, responsible for delivering a defined outcome. This is the lane where forward-deployed models swim.
Technology is rarely the greatest challenge of transformation. People are. Try convincing a room of consultants to trade Excel or PowerPoint for AI-native workflows overnight. Change management is a core component of any successful forward-deployed model, not an afterthought.
Accelerating meaningful transformation and delivering future-ready outcomes requires a unit. One that combines industry depth, process expertise, data, application and integration knowledge, AI capabilities and the operational disciplines needed to drive adoption at scale. To achieve enterprise-wide impact, these capabilities must work together.
So yes, forward deployed is real, and its momentum is growing. Organizations are seeking rapid, measurable returns on their AI investments, fueling demand for outcome-oriented delivery models.
The question isn’t whether forward-deployed work matters. It does. But what form should it take? In my view, the future belongs to the unit, not the hero.
That conversation is worth having. The hype is not.
Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?
