What Forward-Deployed Consulting Is — And Why It's Different

When people hear “consultant,” they usually picture one of two things. The first is the strategy consultant: smart, articulate, leaves behind a slide deck and a set of recommendations for someone else to implement. The second is the contractor: a pair of hands rented by the week, handed a ticket queue, measured by hours logged.

Forward-deployed consulting is a third thing, and the distinction matters enough that I want to be precise about it. This first essay in the series is about what the work actually is — because naming it well is the first step to doing it well.

The shape of the work

A forward-deployed consultant embeds with a team and builds a real, working result inside the client’s actual environment — on their data, against their constraints, alongside their people. The output isn’t advice about what could be built. It’s the thing itself, running, delivering value, understood by the people who will live with it after you leave.

The term comes from the Forward Deployed Engineer role pioneered at Palantir and now widely adopted across the AI industry. The core idea is deeply human: rather than throwing software over a wall and hoping it fits, you go to where the problem lives, learn the terrain, and build the solution in partnership with the people who have the problem. I’ve written about the technical craft of this in the Forward Deployed Engineering series; this series is about the consulting practice built around it — the business, the relationships, the engagements.

What makes it different

Three things separate forward-deployed consulting from the two more familiar models:

• It delivers a result, not a recommendation. A strategy engagement ends with a document. A forward-deployed engagement ends with a system that works. The measure is not the quality of the thinking in the abstract but whether something real now runs in the client’s world.

• It’s embedded, not arm’s-length. You’re not in a conference room once a week reviewing status. You’re in the codebase, in the data, in the standups, learning the client’s domain closely enough to make good decisions inside it. Proximity is the whole point.

• It optimizes for the client’s capability, not your utilization. A body shop wants to maximize billable hours, which quietly rewards making the work last. Forward-deployed consulting is measured by the opposite: how much stronger the team is when you leave. I think of this as the multiplier mindset, and it’s the standard I hold the work to.

Why this model, and why now

This way of working fits the current moment unusually well. In AI especially, the gap between a convincing demo and a dependable production system has never been wider or more consequential. A team can build something genuinely impressive in an afternoon — and then spend six months discovering that real data, real cost, real edge cases, and real trust are where the actual work lives.

That gap is exactly where a forward-deployed consultant earns their keep. Not by knowing more about frontier models in the abstract, but by having crossed the demo-to-production chasm before, on someone else’s hard problem, and being willing to do it again in the trenches with your team. The value isn’t a methodology. It’s judgment applied in context, next to the people who need it.

What this series is about

Over the next eleven essays I want to walk through the practice honestly, from both sides of the table: how the first client actually appears, how to scope a first engagement so it can succeed, how to think about pricing work whose value isn’t measured in hours, how to spend the first two weeks earning the right to be in the room, when to say no, how to hand off so the team keeps the capability, and how one good engagement quietly becomes a practice.

I’m writing it partly to clarify my own thinking, and partly because I wish something like it had existed when I started. None of it is theory I read somewhere. It’s what I’ve learned by doing the work, getting things wrong, and paying attention.

If building real results alongside your team — rather than handing you a deck — is the kind of help you’re looking for, I’d genuinely welcome a conversation. But mostly, I hope these essays are useful whether or not we ever work together.