What value-based pricing actually means
Value-based pricing sets a fee against the financial outcome the work is expected to produce, rather than against the time it takes to produce it. If a project is credibly worth $200,000 to a client over two years, a fee of $20,000 is a straightforward proposition even if the work takes three weeks.
The idea is sound and the advice around it is frequently terrible. It gets sold as a universal upgrade, as though anyone still billing hourly simply has not seen the light. In practice it is a model with specific preconditions, and applying it where those conditions do not hold produces either an awkward conversation or a number you cannot defend.
The three conditions it requires
Value pricing is viable when all three of these hold. Two out of three is usually not enough.
- The outcome is measurable. Additional revenue, reduced cost, recovered time, avoided risk with a known price. "Better brand perception" is real but not measurable, and you cannot price a percentage of something nobody can size.
- The outcome is attributable to you. If six other things changed in the same quarter, nobody can say what your work produced. Attribution is why conversion work prices well and general awareness work does not.
- The client will discuss their numbers. You cannot price a share of a benefit the client will not quantify. A client who declines to talk about revenue, margin or cost is telling you to quote on scope instead.
Notice that none of these is about your skill. A superb designer working on an unmeasurable brief cannot value price it. An average consultant working on a quantified cost reduction can.
The conversation that makes it possible
Value pricing lives or dies in a discovery conversation held before you quote. The purpose is to establish, with the client, what the outcome is worth. Not to sell. Not to estimate effort. To size the prize, in their words and their numbers.
Useful questions, asked plainly:
- What happens to the business if this works? What changes?
- How would you know it worked? What number moves?
- What is that number worth over a year?
- What is the cost of leaving this as it is for another year?
- Who else has to agree that this is worth doing?
If the client can answer those four or five questions with actual figures, you can price on value. If the answers are vague, the honest response is to price on scope, and there is nothing wrong with that.
Before I put a proposal together, it helps to understand what this is worth to you if it works. Roughly what would a 10 percent improvement here be worth over a year?
I ask because it changes what I would recommend. There are versions of this project at very different scales, and I would rather propose the one that actually fits the opportunity.
Setting the number
Once the benefit is sized, the fee is typically a share of it. Engagements commonly land between 5 and 15 percent of a credible first-year benefit, though this varies a great deal by field and by how much of the outcome you genuinely control.
Two disciplines matter more than the exact percentage. First, be conservative about the benefit. If the client says a fix is worth $500,000 and you suspect $200,000, price against $200,000. A fee that looks reasonable against a pessimistic estimate survives scrutiny; one built on the client's most optimistic figure does not.
Second, always check the floor. Estimate the hours the work will realistically take and multiply by your true hourly rate. If the value-based fee comes out below that, the value calculation is wrong somewhere, and taking the work at that price means subsidising it.
Where it does not work
Being clear about the limits is what separates this from the sales pitch version.
- Maintenance and support. Keeping something running produces no discrete measurable outcome. Retainers exist for exactly this, and there is a separate guide on structuring them.
- Production work. When the client has already decided what they want and you are executing it, the value decision was made before you arrived. Price the scope.
- Work where you do not control delivery. If the client's team has to publish, implement or sell what you produce, and they are slow, your outcome does not land. Taking outcome risk you cannot manage is gambling, not pricing.
- Small engagements. The discovery conversation itself takes real time. On a $2,000 project it costs more than it recovers.
The structure most freelancers actually use
In practice the workable version is usually a hybrid rather than pure value pricing. A few structures that hold up:
- Paid discovery, then a value-priced build. A small fixed fee for a diagnostic phase that produces both the specification and the numbers you need to price the main engagement. This also de-risks the estimate for both sides.
- A base fee plus a performance component. The base covers your costs and makes the work viable regardless; the bonus reflects the outcome. Only accept the bonus half where you trust the client's measurement.
- Tiered proposals. Three versions of the engagement at three prices, each tied to a different scale of outcome. The client chooses the level of ambition, which is a far better conversation than negotiating one number down.
None of this makes hourly billing a failure. Hourly is the honest model when the value cannot be quantified, and quoting a scope-based fee you can defend beats improvising a value story you cannot.