Fixed scope without fixed thinking

Fixed-scope software projects have a bad reputation, and they mostly earned it. The classic failure: a scope document written when everyone knew the least, defended for months as reality diverges from it, until the project ends in a standoff over what "done" meant.

The usual prescription is hourly billing. But hourly billing solves the vendor's problem, not the client's — it converts scope risk into an open meter, and now the client carries all of it.

We think the problem was never the fixed price. It was the fixed thinking.

Scope will change. Plan for the verb.

The most honest sentence in any software proposal is: some of this will turn out to be wrong. Discovery is good, but building teaches things discovery cannot. The question is not whether scope changes — it's whether your process treats a change as a betrayal or as Tuesday.

Our version: every change gets written up with a price and a schedule impact before work starts. The client decides with the facts in hand. The original fixed price stays honest because changes are priced at the moment of decision, not archaeologically at the end.

Weekly demos are the audit

A fixed-scope project without weekly demos is a trust fall. The scope document says one thing; nobody can see whether the build agrees until the reveal — and reveals go badly.

A weekly demo turns the scope document into a living checklist. Small divergences surface while they're small. "That's not what I meant" costs a conversation in week three and a rewrite in week thirteen.

The invoice before the surprise

The whole model reduces to one behavior: nobody learns about a cost after it's incurred. Change orders come before the work. Invoices match proposals. If something threatens the date or the number, the client hears it from us, that week — not from the schedule slipping quietly.

Where fixed scope genuinely fits

Fixed scope works when the outcome can be described concretely: a product with named capabilities, a migration with a definition of done, a pilot with a success measure. It works badly for open-ended research and for "we'll know it when we see it."

That's why we publish budget bands and scope to them, phase by phase, instead of pretending one number can hold a year still. Fix the scope. Keep the thinking loose. It's the only version of fixed-price that survives contact with a real project.