Pricing strategy

Hourly vs project pricing for freelancers

Why most experienced freelancers move to project pricing, when hourly is still the right call, and the math that makes both work.

·7 min read·Pricing

Quick answer

Use project pricing when scope is well-defined and your speed has improved with experience — it stops punishing you for getting better. Use hourly pricing for genuinely open-ended work like ongoing consulting, ad-hoc maintenance, or projects where the scope can't be defined upfront. Most established freelancers lean heavily on project pricing and reserve hourly for residual work.

Hourly versus project pricing is the most common pricing question freelancers ask, and the answer is rarely 'one or the other.' It's situational. This guide walks through when each model wins, the hidden tax of hourly pricing as you get better at your craft, and how to convert hourly engagements into project-priced ones over time.

What hourly pricing is good at

Hourly pricing fits work where the scope genuinely can't be defined upfront — ongoing strategic consulting, maintenance retainers with unpredictable incident volume, exploratory research projects, ad-hoc bug fixes. In these cases, the client is buying your time and attention, not a defined deliverable. Hourly is also the cleanest fit for short, ad-hoc engagements where writing a project quote would take more time than the work itself. The signal you should be hourly: you genuinely don't know how much work the engagement will involve, and a project price would either be wildly padded or risk going underwater.

What hourly pricing punishes

Hourly pricing has one expensive flaw: as you get better at your craft, the project takes you less time, so you earn less. A logo that took you 20 hours when you started might take 8 hours after a hundred logos. Hourly pricing means you charge less for that work, even though it's better and faster than what a less experienced freelancer would deliver. Project pricing decouples your fee from your speed — you charge based on the value of the deliverable, and your improving speed becomes increased margin instead of decreased revenue.

What project pricing is good at

Project pricing fits work where the scope is well-defined and the deliverable is the unit the client is buying. A logo, a website build, a 5-blog-post content package, a brand strategy doc, a tax return — these are all things a client is buying as a deliverable, not as someone's time. Project pricing also makes the buying decision easier: clients can compare a single price across vendors, budget for it cleanly, and don't have to babysit hours. The buying friction is meaningfully lower at project pricing than at hourly.

How to estimate a project price

Take the hours you genuinely think the project will take you, multiply by your minimum sustainable hourly rate, then add 25-50% as a buffer for the parts that always go longer than expected. Round to a clean number — clients trust round numbers more than precise ones. Don't tell the client your hourly rate or your hour estimate. Quote the price as a project price for a defined deliverable, and let the math stay yours. The buffer is not padding — it's the realistic accounting for the parts of every project that no one can predict accurately.

How to convert an hourly engagement into project pricing

If you're currently hourly and want to move to project pricing, the easiest path is the next engagement, not the current one. When the next project comes up, write a project quote: 'For the [deliverable], my fee is $[X]. This includes [list].' Most clients accept this readily, especially clients you've already worked with — they have a sense of what your work is worth and are usually relieved not to have to track hours. Move existing clients more carefully: at the next renewal or new project, propose project pricing as the new default.

Hybrid models that work

Some engagements benefit from a hybrid: a project price for the defined work, plus an hourly rate for additional scope or out-of-scope requests. This lets you anchor the price in the project value while preserving a clean way to charge for change orders without renegotiating the whole engagement. The contract reads: 'Project fee: $[X] for [scope]. Out-of-scope work billed at $[hourly rate], pre-approved by client.' This is often the cleanest structure for retainers, support relationships, and ongoing client work.

Key takeaway

Hourly pricing punishes the freelancer who's improved at their craft. Project pricing rewards it. For most experienced freelancers, project pricing is the default, with hourly held in reserve for genuinely open-ended work.

Quote, contract, and invoice — all from one tool

Build proposals, send contracts, and generate invoices from your project data in kinako. Project price or hourly — both work the same way.

Get started free

Free plan · No credit card required

Frequently asked questions

Should I tell clients my hourly rate when I'm doing project pricing?

No. Telling the client your hourly rate gives them a number to back-calculate your time against, which leads to comments like 'you finished it in 20 hours, that's $5,000 — that seems high for two days of work.' Project pricing exists to avoid that conversation. Quote the project, hold the math, and let the value of the deliverable be what they're buying.

What if the client asks how I came up with my project price?

A reasonable answer: 'It's based on the scope of work, the typical effort for projects at this complexity, and the value the deliverable creates for your business.' You don't owe the client your internal math any more than a contractor owes you a breakdown of materials and labour on a flat-fee renovation quote. The price is the price.

Can I charge more for the same project for different clients?

Yes — pricing on factors like project urgency, complexity, or the size of the client's business is normal and defensible. What's not defensible is pricing based on what you guess the client can pay; that creates inconsistent pricing that eventually leaks through your client base. Use a clear rate card with explicit modifiers (rush: +25%, enterprise: +20%) that you can articulate.

Is project pricing always better than hourly?

No. For genuinely open-ended work, hourly is the right model — it would be impossible (or very expensive) to estimate a project price for an engagement where the scope can't be pinned down. Hourly also fits short, ad-hoc engagements where the time to write a project quote outweighs the size of the project. Most experienced freelancers use both, leaning heavily project for defined work and reserving hourly for the rest.

Related templates

Consultant proposal template →Graphic Designer proposal template →

Built for

For consultants →For graphic designers →For copywriters & content writers →

Keep reading

Pricing · 9 min

How to set freelance rates that don't undersell you

A grounded approach to pricing — how to think about hourly versus project rates, how much to charge, and how to raise prices without losing clients.

Getting paid · 7 min

How to structure milestone payments on freelance projects

What to tie payments to, how many milestones to use, and the structure that protects your cashflow on projects longer than a month.

Pricing · 8 min

How retainer agreements work for freelancers

What a retainer is, the structures that work, how to price one, and how to convert a project client into a recurring one.