Hourly vs value-based pricing for freelancers: which to use
The argument is usually staged as two options, and there are four. The two everyone fights about are the two fewest experienced freelancers actually use.
North
2026-06-17 · 5 min read

I price projects, and I still keep an hourly figure in my head. It never appears in a proposal. It exists so that when a fixed price and a realistic estimate collide, I find out before the client does rather than in week five.
That is a boring position, and it is roughly where the argument lands once you have run it a few dozen times. Which is a problem for the genre, because "hourly versus value-based" is written up everywhere as a two-sided fight with a correct answer, and it is neither.
There are four ways to sell your work, not two. Hourly. A day or week rate. A flat price for a defined project. And a price derived from what the outcome is worth to the buyer. The two that get argued about online are the two ends, and the two in the middle are what most experienced freelancers actually charge. Ranking them as good and bad misses what is really going on, which is that each step along that line hands a bit more risk from the client to you, and pays you for taking it.
Hourly puts all the risk on the buyer. If the job takes three times as long as anyone thought, they pay three times as much. That is why hourly survives, and it is a genuinely good fit for work whose shape nobody can see yet: an audit, an exploration, a rescue job on somebody else's half-finished site. Anyone telling you to never bill hourly has not done much of that work.
The day rate is the first real step up, and it is underrated to the point of being invisible in most guides on this question. A consultant on Hacker News gave the clearest reason for it I have read: hourly always invites discussions, for example how are phone calls billed. That is the whole case. The hour is a small enough unit that both sides start policing it, and the policing costs more than the disputed time is worth. A day is big enough that nobody counts. In the same thread another put the ladder at its logical end with a rate of ten thousand a week, prepaid monthly, which is a project price wearing a calendar.
Then the flat project price, where you carry the estimating risk entirely. And then value pricing, where the number stops being derived from your effort at all and starts being derived from the buyer's upside. That last step is the one with the full method behind it, and it is also the one that most often collapses back into the flat project price, because the client cannot supply the number it needs.
So the practical question is not which camp you belong to. It is how big a unit you are willing to quote at a fixed price, given how well you can see the work. That is a judgement you make per job, and a competent freelancer moves up and down the ladder all week.
A note on retainers, which get shoved into this argument and do not belong in it. A retainer sells availability, not output, and the arithmetic is peculiar in a way worth understanding before you agree one. Patrick McKenzie walked through his version: a three-week project at eight thousand a week, then maintenance at three thousand a month for two committed days, with the observation that most clients do not ask for any work in most months. Read quickly that sounds like money for nothing. It is not. You are selling the reserved capacity and the guarantee, and the months where nobody calls are the product working. Price it as insurance and you will price it correctly. Price it as hours you expect to bill and you will underquote it every time.
Where does the market actually sit? The one figure worth having is that in a 2025 survey of web designers, 82% used package or project pricing rather than hourly (State of Web Designer Pricing, Web Designer Academy, 2025). That is a coaching-survey population and it skews, so treat it as a direction rather than a census. The direction is unambiguous, and it points at the middle of the ladder rather than at either end.
One caveat that the better guides on this question get right and that I do not want to skip. If you are early, hourly is often the correct rung, and not as a confidence problem. Quoting a fixed price well requires knowing how long your own work actually takes, and the only way to acquire that is to have measured it on a few dozen jobs. Billing hourly while you build that record is how you earn the right to quote fixed later. The mistake is not starting there. It is staying there once you can predict yourself.
If you are moving, move one job at a time and start with a new client rather than an existing one, because changing the unit on someone mid-relationship reads as a price rise even when it is not. Quote the next defined piece of work as a flat price. Keep the hourly figure private, as a floor. Then, when a client volunteers what the work is worth to them, take the step up.
And keep the ladder in view rather than picking a rung and defending it. The freelancers who get stuck are usually the ones who decided, once, that they were a project-price person or an hourly person, and then kept selling the wrong unit for the job in front of them.
Frequently asked questions
- Is value-based pricing better than hourly for freelancers?
- For work with a defined deliverable, usually — but the comparison is a false binary, because the day rate, the week rate and the flat project price all sit between them and are what most experienced freelancers actually charge. The useful question is not which of the two extremes to adopt. It is how large a unit of your work you are willing to sell at a fixed price, and every step up that ladder moves risk from the buyer onto you.
- Should I tell a client my hourly rate if they ask?
- You can, and the more interesting move is to answer with a larger unit instead. One consultant's stated reason for quoting days rather than hours is that hourly billing invites arguments about what counts — whether a phone call is billable, whether thinking time is. A day rate ends that conversation because the boundary is the day, not the task.
From the blog
Plain-spoken guidance on the business side of your craft.
- PricingValue-based pricing for freelancers: how to do it, including the hard part
Every guide on this tells you to charge for the outcome. Almost none of them tell you what to do when the client cannot say what the outcome is worth, which is most of the time. This one is mostly about that conversation.
NNorth
2026-06-22
PricingHow much should you charge for a logo? (2026)We ran the published logo-price tables through verification and none survived. What's left is the method: a logo priced end to end, usage rights included, with the arithmetic on the page.
NNorth
2026-06-19
ProposalsWhat to include in a freelance proposal: the complete guideThe seven-part answer takes about forty seconds to give, and it is the least useful true thing anyone can tell you. This is the rest of it: who actually reads the document, what to take out, and where the close-rate numbers you keep seeing come from.
NNorth
2026-06-16