Why fixed-scope beats open-ended hourly

The default way software gets bought is by the hour. The default way software goes over budget is also by the hour. That is not a coincidence.

The incentive problem

When you pay by the hour, every inefficiency is billable. There is no built-in reason for the work to be tight, the scope to be clear, or the estimate to be honest. The supplier carries none of the risk of things taking longer — you do. The longer it takes, the more they earn. Even with the best intentions on both sides, the incentives point the wrong way.

What fixed-scope forces

A fixed-scope, fixed-price engagement changes who carries the risk. To quote a fixed price, the supplier has to:

• Understand the problem properly before committing — which front-loads the thinking that hourly work tends to skip.
• Define "done" explicitly, so both sides know what they are agreeing to.
• Absorb their own inefficiency, because overruns come out of their margin, not your budget.

You trade a little flexibility for a lot of predictability. For most SME projects, that is exactly the right trade.

"But my requirements will change"

They will — and that is fine. The answer is not open-ended hourly billing; it is phased fixed scope:

1. A short, fixed discovery phase to de-risk and cost the build.
2. A fixed build phase against the scope discovery produced.
3. Clearly-priced change requests for anything genuinely new.

You get predictability and the ability to change direction — without signing a blank cheque.

What good looks like

• An itemised quote, not an hourly range.
• A written definition of done per feature.
• Demos at milestones, so you see progress and can course-correct early.
• You own the source code and can take it elsewhere at any point.

If a supplier will not quote a fixed price for a well-defined scope, that tells you something about how confident they are in the estimate. Predictability is not a luxury — it is the baseline you should expect.