Project-based vs hourly pricing: which one should you use?

The hourly versus fixed fee argument gets treated as an identity question, as if you have to pick a camp and defend it. It is not. Both models are tools with different failure modes, and experienced freelancers switch between them depending on what the project looks like.

What each model actually optimises for

Hourly transfers risk to the client. If the project takes twice as long, the client pays twice as much. It is honest, it is easy to quote, and it caps your income at hours times rate. It also creates a perverse incentive structure: you earn less as you become more skilled, and the client watches the clock rather than the outcome.

Fixed fee transfers risk to you. If you finish early you keep the difference, which means expertise finally pays. If you estimate badly, you eat it. The client stops caring how long it takes and starts caring about the result, which is a much better conversation.

When hourly is the right call

• The scope genuinely cannot be defined yet, such as ongoing maintenance or open ended consulting.
• The client is prone to changing direction and you would otherwise be renegotiating weekly.
• The work is support-shaped: unpredictable arrival, small units, no clear finish line.
• You are new to this type of work and have no estimation data yet. Charge hourly for two or three of these projects, collect the data, then move to fixed fee.

When fixed fee is the right call

• The deliverable is describable in a paragraph and you have done something similar before.
• You are faster than average at this specific thing. Fixed fee is how skill converts into money.
• The client wants budget certainty, which is nearly always.
• The project has a natural end.

The hybrid that solves most cases

Fixed fee for the defined scope, hourly for anything outside it, stated in the same paragraph:

"The project fee is 6,400 and covers everything in the scope list, including two rounds of revisions. Requests outside that list are billed at 95 per hour, quoted and agreed before I start them."

This gives the client certainty on the main body of work and gives you protection on the part that historically destroys margins. It also makes scope creep a visible, priced event rather than a slow leak.

Estimating a fixed fee without gambling

• Break the project into tasks small enough that you can name a number for each, then sum. Whole project guesses are wrong far more often than the sum of small guesses.
• Add a contingency of 20 to 30 percent. Not padding, a realistic reserve for the parts you have not thought of yet.
• Cross check against your target effective hourly rate. If the fee divided by your honest hour estimate lands below your rate, the fee is too low.
• Track actual hours on every fixed fee project even though you are not billing them. After five projects you can stop guessing.

The number that tells you if it worked

Effective hourly rate: total fee divided by hours actually spent. It is the only number that compares an hourly project to a fixed fee project honestly, and it is the reason Timely tracks hours against fixed fee work by default.

TL;DR

• Hourly moves risk to the client and caps your income. Fixed fee moves risk to you and rewards skill.
• Hourly for undefined, unpredictable, or unfamiliar work. Fixed fee for defined work you have done before.
• Use the hybrid: fixed for scope, hourly for everything outside it.
• Estimate by task, add 20 to 30 percent contingency, and track hours regardless so you can price the next one from data.