DEV Community

Landolio
Landolio

Posted on

Why I stopped quoting hourly rates (and what I charge instead)

Hourly billing punishes efficiency. The faster you get, the less you earn. After 3 years of freelancing, I switched to value-based pricing and my income went up 40% while working fewer hours.

Here's how the shift worked:

The hourly trap

Year 1: I charged £50/hour. A website took me 40 hours = £2,000.
Year 2: I got faster. Same website, 25 hours = £1,250.
Year 3: Even faster. 15 hours = £750.

I was literally earning less for being better at my job.

What I do now

I quote per project, based on the value to the client — not the time it takes me.

That same website? It's worth £3,000-5,000 to the client regardless of whether it takes me 15 hours or 40. So I quote £3,500 and deliver it in 2 weeks.

How to calculate your project rate

  1. Estimate the value — what's this worth to the client?
  2. Set your floor — minimum acceptable hourly rate × estimated hours
  3. Quote between floor and value — usually 10-30% of the value
  4. Add a scope buffer — 15-20% for inevitable changes

I built a free project quote calculator that does this maths for you. Enter your phases, expenses, and buffer — it spits out a professional quote breakdown.

The conversation that makes it work

Client: "What's your hourly rate?"
Me: "I price per project. Tell me what you need, and I'll give you a fixed quote with a clear scope."

Most clients actually prefer this — they want budget certainty too.

What about scope creep?

This is where contracts matter. My contract includes:

  • Clear deliverables list
  • Change request process (with pricing)
  • Kill fee if they cancel mid-project

I use a freelance contract generator to build these — it covers scope, payment terms, IP, and even IR35 clauses for UK contracts.

Tools that help

All free, no sign-up, built them myself.


Anyone else made this switch? What's your experience with project-based pricing vs hourly?

Top comments (0)