Most freelancers arrive at their price the same way: they think of a number that feels slightly uncomfortable, say it out loud, and then apologise for it. That works until you meet a client who doesn't flinch — at which point you realise the number was never connected to anything.
Hourly billing has one honest virtue: it's easy to explain. Everything else about it works against you.
The faster you work, the less you earn for the same result. The more experienced you get, the more you're penalised for it. And it invites a conversation about your speed rather than the outcome — clients start watching the clock instead of the work, and a project that goes well financially is one that took longer than it should.
It also caps you absolutely. There are only so many hours, and you cannot charge for the fifteen years that let you do in two hours what used to take two days.
A fixed price fixes the client's risk and moves it onto you. That's fine — you're better placed to estimate than they are — but only if two things are true: you know roughly how long this kind of work takes you, and the scope is written down precisely enough that "finished" is not a matter of opinion.
Without the second, fixed price is just hourly billing where you absorb the overruns. The scope document is not paperwork; it's the thing that makes the model survivable.
The idea is simple and the execution is where people fall down: price against what the work is worth to the client rather than what it costs you to produce.
A booking system for a clinic whose average patient is worth £800 a year, and which currently loses enquiries because the form breaks on a phone, is worth a different number than the same system for a hobby business. Same code, different value, defensibly different price.
What it requires is a conversation most designers skip. You have to know their average job value, how they get customers now, and what the broken thing is costing them. If you don't know those numbers, you're not doing value pricing — you're just charging more and hoping.
The key idea: value pricing is not a confidence trick, it's a research obligation. If you can't say what the work is worth to this specific client in their own figures, you have no basis for the price and you'll fold the moment they push.
Whatever model you use, you need a number beneath which work is actively losing you money. Work it out once:
The number that falls out is usually much higher than people expect, and it's a floor rather than a target. Knowing it changes how you respond when someone asks for a discount.
Quote a single price and the client decides yes or no, where no is easier. Quote three and they decide which — a far better question.
Make the middle one what you'd actually build, say so plainly, and let the cheap one be genuinely viable rather than a straw man. Most people take the middle. Some take the top, which you'd never have found out by quoting one number.
Don't drop the price. Drop the scope, visibly, and let the price follow.
"I can do it for £1,800 instead of £2,600 — that's five pages instead of nine, and you write the copy." Now the number means something. Discounting without removing anything teaches the client that your first price was invented, and every future quote gets negotiated.
Pricing conversations are much easier with prospects who have an obvious, costly problem. A business whose site fails on mobile and loses enquiries will discuss what that's worth. One that just fancies a refresh will discuss your hourly rate.
That's an argument for qualifying before you quote rather than after. Knowing which businesses in your area have genuinely broken sites — and what specifically is wrong — means you spend your quoting time on the conversations where value pricing is even possible.
LeadCrawlr scans Google Maps, scores every business website 1–10, and flags the ones that need you most. $49/year, unlimited scans.
Get LeadCrawlr — $49 / year