Fixed price or hourly: which is better for the client

A fixed price is better when you know exactly what you want. Hourly is better when you are still discovering it. The difference is not which is fairer — both move risk, just to the opposite side.

It is one of the first questions a client asks, and "it depends" sounds like dodging. It is not. Let us break it down so you can decide for yourself.

What a fixed price means

We agree an exact scope and an exact figure. If the work takes longer than we expected, that is our problem, not yours. It sounds like a win for the client, and in part it is.

The catch is in the word "exact". A fixed price only works when the scope can be described precisely in advance. And a vendor always builds in a buffer for the unknown — so you are also paying for a risk that may never materialise. The less certain the brief, the bigger that buffer.

What hourly means

You pay for time worked. The risk of it taking longer is yours — but you are not paying a buffer for the unknown, and you can change direction at any point without renegotiating scope.

The worry is that hourly is a "bottomless pit". It is a fair worry, and it is handled with transparency: a regular account of what was worked on, and a ceiling that cannot be crossed without sign-off. Hourly without those two things genuinely is a risk.

When each fits

A fixed price makes sense for a clearly bounded thing: migrating an existing system, integrating two tools, a website from a finished design. You know what you want and you want certainty on cost.

Hourly makes sense for discovery: a new product that will change with feedback, or an AI feature where nobody knows up front what will work. Forcing that into a fixed price means either an enormous buffer or an argument over every change.

Why, for uncertain briefs, we prefer to start by understanding the problem rather than fixing a price ties into why context comes before code.

How to avoid a surprise on cost

It does not depend on the model, but on what is written down. With a fixed price, ask for an exact list of what is and is not in scope — the worst arguments are about things the client took for granted and the vendor did not. With hourly, agree a ceiling and a reporting interval.

We often combine the two: a fixed price for a clearly bounded first phase, hourly for what will evolve. It ties into why we charge for value, not hours.

If you are not sure which model fits your project, we will tell you in a free consultation — it is one of the things we work out there.