Hourly versus project pricing is one of the oldest debates in freelancing. Here is a more useful way to think about it.
The Problem With Pure Hourly
Hourly pricing benefits the client when you are experienced. As you get faster, you earn less for the same output. You are penalised for your skill.
Hourly also creates a tension: the client wants you to work fewer hours, you are paid for more hours. You are not incentivised the same way.
The Problem With Pure Project Pricing
Project pricing requires accurate estimation. If you underestimate, you absorb the cost. On complex or ambiguous projects, this risk can be significant.
A Practical Middle Ground
For well-defined, repeatable work: project pricing. You know the scope, you know roughly how long it takes, you can price confidently.
For exploratory or complex work: time and materials with a cap. You bill hourly up to a maximum. The client has cost certainty. You have protection against underestimation.
For ongoing relationships: a monthly retainer. Predictable income. Predictable availability for the client.
The Conversation That Makes This Work
When presenting a project price, explain what is included and what happens if scope changes.
'This price covers [specific deliverables]. If we discover the requirements are significantly different from what we have scoped, I will flag it before continuing and we will agree on the path forward.'
This is not a legal document. It is a shared understanding that protects both sides.
The Freelance Starter Pack includes a Notion OS for managing project pricing and finances plus AI prompts and a rate reset programme. EUR 29.
Top comments (0)