Fixed scope vs hourly billing: which fits your project?

The commercial model should follow the work

A defined website, campaign system or first product release can often be scoped around clear deliverables and decision points. Open-ended optimisation, embedded support and research-heavy work may be more honest as a retainer or time-boxed discovery.

Problems begin when the model disguises uncertainty. A fixed price with a vague scope creates conflict later. An hourly engagement with no priorities can turn every useful conversation into a concern about the meter.

When fixed scope works

Fixed scope works when the desired outcome, audience, integrations and approval process can be described before delivery begins. It gives both sides a shared definition of done and makes trade-offs visible early.

A good scope does not pretend nothing will change. It explains what is included, what assumptions the estimate relies on and how new information will be handled. Change orders are not a failure when they record a genuine change; they are a failure when they reveal that the original scope never meant anything.

When a retainer or time box is more honest

Ongoing content, campaign optimisation and operational improvement rarely have a natural finish line. A retainer can be the right structure when it buys a clear capacity, an agreed priority process and transparent reporting on what shipped.

Discovery should also be time-boxed when the team cannot responsibly quote the build yet. Its deliverable is not more meetings; it is a decision-ready brief, an evidence-backed recommendation and a clear next step.

Questions to ask before signing

Ask what is fixed, what can move and how a decision changes cost or timing. Ask who has authority to approve work, what feedback window the schedule assumes and what happens if a dependency arrives late.

The best commercial model is the one that makes incentives and uncertainty visible. If you cannot explain how the engagement will respond to change, the headline price is not the most important unknown.

• What exactly will exist at the end?
• Which assumptions affect the quote or capacity?
• How are changes documented and approved?
• Who owns accounts, files and source material?