Hourly Rate or Fixed Price: Where the Real Project Profit Is

The question «charge by the hour or by the project» looks technical, but it actually decides how much you earn. An hourly rate and a fixed price are two different economies with different risks. And an agency that doesn't understand this difference regularly loses money where it could have made it — simply by choosing the wrong model for a specific project.

Let's break down how each model works, where the profit hides in each one and where the trap is, and look at a single example of how the same project delivers a different result depending on the model.

Two models — two different economies

In the hourly model you sell time: you get paid for the hours you put in. The overrun risk sits with the client — more hours, a bigger invoice. In fixed price you sell a result for a set sum, and the overrun risk now sits with you: go past the estimate and you eat into your own margin.

That's the key difference. Not «which model is better in general», but «who carries the risk that the work takes longer than it looked». And that's exactly why the same work delivers different profit under different models.

Hourly: when it pays off and where the risk is

The hourly model pays off where the scope is unclear up front: long-term support, flexible projects with a shifting spec, staff augmentation. You don't take on the risk of underestimating, and every hour worked gets paid. The risk here is different — idle time: if the team is underloaded, there are few billable hours, and the model starts to lose. A classic example of failed tracking in the hourly model is 20 developers, an hourly rate, and no idea how much the project earned.

Fixed price: when it pays off and where the trap is

Fixed price pays off on typical, well-understood projects where you know the scope well and can deliver faster than the estimate — then all the savings are yours. The trap of fixed price is underestimating and «creeping» scope: the client assumes small tweaks are included in the price, but they eat up hours. Without a built-in margin and control, fixed price easily goes into the red — that's the subject of Project margin: how not to work at a loss.

Example: the same project in two models

Take a project with an hourly cost of 640 UAH and an estimate of 100 hours. You've built in a margin and sell it either at a rate of 960 UAH/hour or for a fixed 96 thousand.

Scenario A — you fit within 100 hours. Hourly: 100 × 960 = 96 thousand, profit ~32 thousand. Fixed: 96 thousand, profit ~32 thousand. The same.

Scenario B — the project took 140 hours. Hourly: 140 × 960 = 134.4 thousand, profit ~44 thousand (the client paid for the overrun). Fixed: still 96 thousand, but the cost rose to 140 × 640 = 89.6 thousand — profit just ~6 thousand. The same work, and the result differs several times over.

The conclusion is simple: the greater the scope uncertainty, the riskier fixed price is and the safer hourly is.

How to choose the model for a project

Choose not your «favorite» model but the model for the specific project. A clear, typical scope that you deliver fast — go fixed and keep the savings for yourself. An unclear or shifting scope — go hourly, or fixed with clear boundaries and an extra charge for going beyond them. For large, uncertain projects a hybrid works: fixed for the understood part plus hourly for everything above it.

The main thing — track hours in both models

In any model, without tracking hours you don't know your profit. In fixed price, hours show whether the project ate up your margin; in hourly, whether the load is high enough for the model to pay off. Calculate your rate from the hourly cost, not from the market — as in Cost per hour: how to set your rate.

In Finmap, hours and project expenses roll up into profit regardless of the model — so you can see which model actually earns on which projects. Try it free for 7 days.