Technical
Value-Based Pricing Applied Honestly
Value-based pricing is oversold by consultants and undersold in practice. Every article promises you will charge 10x by aligning fees to outcomes. The honest version is more nuanced. After a year of shipping retainers and projects on value-based terms, here is what actually works and where the framing breaks.
When Value-Based Actually Wins
Three conditions must be true together. Miss any one and hourly is better for both sides.
The outcome is measurable. 'Increase conversion from 2% to 3%' is measurable. 'Modernize the codebase' is not. If I cannot tell at the end of the engagement whether the outcome was reached, value-based pricing becomes a dispute, not a deal.
The client owns the outcome. If the result depends on the client shipping, marketing, and supporting the new thing, they must be accountable for that half. Otherwise I am pricing around something I do not control, which is a losing trade.
The value is big enough to share. If the outcome is worth $20k to the client, a $15k fee is fine. A $50k fee is not. The share must leave both parties better off. Gouging on value is how trust dies.
The Structure I Use
Base fee: fixed, paid upon kickoff. Covers my committed time.
Success fee: paid on outcome measurement. Covers the value share.
Measurement: defined in writing before the engagement starts.No success fee without a measurement clause. No measurement without a base fee. Both sides have skin; neither has unlimited downside.
Where I Go Hourly Instead
Maintenance retainers. Exploratory engagements where the outcome is not yet definable. Small scoped tasks where the overhead of a value-based contract exceeds the fee itself. In all three, hourly is honest and clean.
The Proposal Template
Every value-based proposal has three sections: the outcome (specific, measurable), the structure (base plus success), the measurement (how we will check in 90 days). Anything longer is padding. Anything shorter is under-specified. See Alan Weiss's model for the detailed framing; I apply the tight version.
The Honest Tradeoff
Value-based pricing aligns incentives when the work fits its shape. Forcing it on the wrong work creates friction that eats the relationship. Match the pricing model to the work, not the other way around.
Pricing is a tool, not a religion. Pick the one that fits.
Renegotiation Is Part of the Deal
Value-based contracts benefit from a planned renegotiation checkpoint. Half the scope in, both sides check whether the measurement is still tracking reality. If the market moved, the target may need adjusting. Without a checkpoint, the original contract freezes into either a windfall or a losing trade for whichever side got the environment wrong. Renegotiation is not a weakness; it is a feature of a mature commercial relationship. Writing it into the contract upfront removes the awkwardness later.
RELATED READING
The Consulting Shift I Am Making In Year Two
After a year of writing and building, my consulting practice is changing shape. Shorter engagements. Sharper outcomes.
ReadThe Frontend Shift: Shipping Less JavaScript In Year Two
A year ago I reached for Next.js for everything. This year I often reach for nothing.
ReadThe Serverless Lesson I Would Write On A Sticky Note
After a year of shipping serverless projects, one rule explains most of the wins and all of the losses.
Read