Pricing Forward-Deployed Work — Value, Not Hours
Engineers price consulting the way they bill time: by the hour. It's the most natural instinct and, I think, usually the wrong one. Here's how I've learned to think about pricing work whose value has nothing to do with how long it takes.
Of everything in this series, pricing is the part engineers find most uncomfortable, and I include my past self. We’re trained to think in effort — story points, hours, days. So when it comes time to price an engagement, the hourly rate feels like the honest, rigorous choice. Charge for the time, and you can’t be accused of overcharging.
I’ve come to think that instinct, however well-meaning, quietly undermines both the client and the work. This essay is about why, and about what I try to do instead.
The problem with billing hours
Hourly billing has one virtue — it feels fair — and several deep problems that are easy to miss until you’ve lived them:
- It ties your pay to your inefficiency. The faster and better you get, the less you earn for the same result. You are, structurally, penalized for expertise. The consultant who solves in a week what others solve in a month earns a quarter as much, which is exactly backwards.
- It makes every improvement a negotiation. The client watches the clock instead of the outcome. A suggestion that would help but adds hours becomes a cost to resist rather than a win to pursue. You end up on opposite sides.
- It caps your value at your calendar. Hours are finite and roughly equal, so hourly billing silently asserts that an hour of crossing the demo-to-production chasm is worth about the same as an hour of anything else. It isn’t.
None of this means hourly work is dishonest. It means it measures the wrong thing. The client isn’t buying your hours. They’re buying the result, and the judgment that produces it.
Price the outcome
The alternative is to price the engagement against the value of the outcome, not the time it consumes. If a first production win unlocks a capability the client would gladly have paid a certain amount for, that number — not your hourly rate times an estimate — is the right anchor. This is the logic of value-based pricing, and it realigns everyone:
- The client pays for something they can evaluate — a result — rather than something they have to police — your hours.
- You’re rewarded for getting better, because efficiency is now yours to keep.
- Improvements become shared wins instead of billing disputes, because you’re both watching the same outcome.
In practice this usually means a fixed price for a clearly-scoped deliverable, which is exactly why scoping and pricing are inseparable. You cannot price an outcome you haven’t defined, which is another reason the paid discovery step earns its place: it’s what makes a confident fixed price possible.
Pricing is a trust signal, not just a number
Something I underestimated early: how you price communicates who you are before any work happens. A confident fixed price for a well-defined win says I’ve done this, I know what it takes, and I’m accountable for the result. An hourly rate with an open-ended estimate says, however unintentionally, I’m not sure what this will take, so let’s both find out on the clock. Clients feel the difference.
This is also why I try never to compete on being the cheapest. Forward-deployed work is a high-trust engagement; the client is letting you deep into their world. Being the low bid signals the wrong thing in that context — it invites the question of what’s wrong, not what’s cheap. The goal is to be clearly worth it, not clearly inexpensive.
A few honest caveats
Value pricing isn’t a magic trick, and I don’t want to oversell it:
- It requires the discovery to be real. If you fix a price before you understand the problem, you’ve just moved the risk onto yourself without the information to manage it. Price fixed only when you’ve looked closely enough to mean it.
- Some work genuinely is time-and-materials — ongoing support, exploratory R&D with no definable deliverable. For those, a retainer or a day rate can be the honest structure. The point isn’t to force every engagement into one mold; it’s to stop defaulting to hours out of discomfort.
- You will misprice some engagements. I have. You learn, you adjust, and you remember that a single mispriced project matters far less than a pricing philosophy that respects the value you create.
The deeper shift here isn’t a formula. It’s moving from selling your time to standing behind your outcomes — which, not coincidentally, is the same shift that separates a forward-deployed consultant from a rented pair of hands. In the next essay I’ll go back to the beginning of the engagement itself: the discovery phase, where you earn the understanding that everything else depends on.