Hourly vs Project Pricing for Freelancers: How to Pick (and When to Switch)

Most freelancers default to hourly on day one and never revisit the choice. That quietly caps their income. The right model depends on the work, not on what feels familiar — and the answer usually breaks down like this: hourly fits genuinely undefined scope, project pricing fits work you can estimate within roughly twenty percent, and a third option, value-based pricing, fits the rare engagement where the client can quantify the impact. The rest is mechanics. Know the trade-offs, pick the model on purpose, switch when the situation changes. Below is the short version, then the longer one.

The five common pricing models, briefly

Freelancers use roughly five pricing models, and Stripe's guide to getting paid as a freelancer lists them cleanly: hourly billing, retainer agreements, productized services, value-based pricing, and project-based or fixed-fee pricing. Day rates and weekly rates are variations of hourly — bigger units, same logic.

Most arguments freelancers have with themselves are really about hourly versus project. Retainers show up once you have repeat clients. Productized services and value pricing arrive once you've built a track record. So we'll focus on the two defaults and treat value pricing as a senior option later in the article.

How hourly actually pays you (and where it quietly costs you)

When hourly makes sense

Hourly is the right call when scope is genuinely undefined, when the engagement is short — under a few hours — or when you're doing a brand-new type of work and have no data to estimate from. Discovery sessions. Debugging an unfamiliar codebase. Ad-hoc consulting calls. You can't quote a fixed price for work you can't bound.

The hidden costs

The deeper problem with hourly is structural. As one Indie Hackers contributor put it bluntly, hourly billing pays you for being slow. The faster and more skilled you get, the less you make for the same outcome. Every process improvement you invest in cuts your own income.

Then there's the overhead nobody bills for. A separate Indie Hackers piece on the $10k–$20k profit leak walks through the math: a freelancer at $50 an hour who loses just five hours a week to proposals, calls, admin, revisions, and context switching is leaving roughly $13,000 a year on the table. None of that time shows up on an invoice, and hourly gives you no mechanism to recover it.

If you're billing hourly, the workaround is to track focused work in clean blocks. A 25-minute Pomodoro is a useful unit because it forces you to log only the time you actually spent heads-down on the client's problem, not the half-attention time you spent thinking about it. That's a truer read on capacity than calendar time.

How project pricing actually works

The model

Project pricing means a fixed amount, agreed before work begins, for a clearly defined deliverable. Harvard Business Review's guide to pricing consulting services covers the trade-off well: project fees align incentives. The freelancer keeps the upside of finishing faster. The client gets cost certainty. Both sides are buying the outcome instead of haggling about the inputs.

What it demands from you

Fixed pricing has prerequisites. You need a written statement of work — one page is enough — that lists exactly what's included and, just as important, what isn't. You need historical time data, which means you've been tracking your hours even when you weren't billing by them. And you need a change-order process: any request outside the statement of work gets a separate quote.

The honest trade-off is that when you underestimate a project, you eat the difference. Fixed pricing isn't a free upgrade. It transfers estimation risk from the client to you. The protection is doing it on work you've done before.

When to switch

Three concrete signals tell you a particular kind of work is ready to move from hourly to fixed:

1. You can estimate similar work within roughly twenty percent of actual time, based on tracked data from past engagements.
2. Clients keep asking for a fixed quote up front, and you keep hedging.
3. You've made a process improvement — a template, a tool, a sharper workflow — that means you finish twice as fast as you did six months ago, and your hourly income just dropped to match.

Any one of those is a good reason to test a project price on the next quote. You don't have to switch everything at once. A realistic migration: keep hourly for new client types and discovery work, quote fixed for repeatable engagements you've done three or more times.

A third option: value-based pricing

The senior move is value-based pricing — setting the price by the impact on the client's business, not the time it takes you to deliver. HBR's quick guide to value-based pricing frames it as the most discussed and most misunderstood pricing concept, which is fair. It needs a structured discovery conversation with the buyer to quantify the dollar impact of a successful engagement, then anchors price to that figure.

It works on high-leverage work — a website rebuild that lifts a SaaS company's conversion rate by a measurable amount, a launch campaign tied to a revenue target — where the buyer can name the number and your work moves it. It doesn't work on commodity tasks where the value is just "the thing is done." Don't force it. When it fits, value pricing usually pays better than fixed on the same project; when it doesn't, fixed is still the right call.

How Pomlo fits in

Pomlo is a beautifully simple time tracker for iOS, Android, and the web, built for freelancers, indie hackers, and small teams who want to bill accurately and ship more. It doesn't pick your pricing model for you. It gives you the data both models need.

Three features matter for the choice in this article. Projects and clients lets you keep separate buckets per engagement, so an hourly client and a fixed-fee client sit side by side without leaking into each other. Built-in invoicing turns tracked hours into an invoice in one tap on hourly work, and keeps a clean historical record on fixed-fee work so the next quote is grounded in real numbers. Reports show you where the week actually went — the data that tells you when you're ready to switch a particular kind of work from hourly to fixed.

Try Pomlo on the App Store or Google Play.

Frequently Asked Questions

Is hourly or project pricing better for new freelancers?

Hourly is usually safer when you're new. You can't accurately estimate work you've never done before, and a fixed price you underbid is a money-losing project. Once you've done a particular type of work three or four times and can estimate it within twenty percent, project pricing usually wins.

What should I do if a client wants a fixed price but my scope keeps shifting?

Write a one-page statement of work that lists exactly what's included, then quote the fixed price for that scope. Anything outside the list is a change order, billed separately. The statement of work is the conversation tool — not a legal document — that lets you say "happy to do that, here's the change-order quote" instead of absorbing it for free.

How do I know when to switch from hourly to project pricing?

Three signals: you can estimate similar work within twenty percent of actual time, your clients keep asking for a fixed quote up front, or you've made a process improvement that means you finish twice as fast and your hourly income just dropped. Any one of those is a good reason to test a project price on the next quote.

Should I still track time if I'm billing a flat fee?

Yes — it's how you find out whether the project was profitable and what to quote for the next one. Time logs on fixed-fee work become your estimating data; without them, you're guessing every time.

A short conclusion

Hourly fits undefined or unfamiliar work. Project pricing fits repeatable work you can estimate within roughly twenty percent. Value-based pricing fits high-leverage engagements where the client can name the dollar impact. The mistake isn't picking one. It's picking one early and never revisiting it. Review the model every six months — the work changes, your speed changes, your clients change. For more freelance ops writing, see the rest of the Pomlo articles index.