Choosing Between Hourly and Fixed Price

The hourly versus fixed price argument usually gets framed as a matter of preference. It is really a question about uncertainty, and the right answer changes from project to project.

Fixed price transfers risk to you

When you quote a fixed price, you are absorbing the risk of the estimate being wrong. If it takes twice as long, that is your problem. In exchange, if you are fast, the upside is yours.

Fixed price works when:

• The scope is genuinely well understood
• You have done something similar before
• The client can describe done precisely

Hourly transfers risk to the client

Hourly means the client carries the uncertainty. That is appropriate when nobody knows how long it will take, which is honest and common.

Hourly works when:

• The work is exploratory, like a bug hunt or an audit
• Scope will obviously change as you learn
• The relationship is ongoing rather than a single deliverable

The trap in each

Fixed price fails when the scope was never really agreed. You end up delivering an unbounded amount of work for a bounded fee.

Hourly fails when the client has no visibility. Without a cap or regular updates, every hour feels like an unpleasant surprise, and trust erodes even when your work is good.

The problem is almost never the pricing model. It is the amount of shared understanding underneath it.

A practical middle path

Quote a small paid discovery stage at a fixed price. A few hours to review the codebase, interrogate the brief and produce a plan. Then quote the main work fixed, from a position of knowledge.

The client gets a real estimate instead of a guess. You stop absorbing risk you were never paid for. And if the discovery reveals the project is a bad idea, both of you found out cheaply.