Why We Run Discovery Before Quoting a Single Hour

A client asks what it will cost to build their app. The honest answer at that moment is a range so wide it is useless — and quoting a confident number anyway is how projects end badly for both sides.

What a fixed bid on vague scope actually does

It transfers all the uncertainty onto whoever guessed lowest. If the agency guessed low, they cut corners to survive the number. If they guessed high, the client overpaid for risk that never materialised. Either way the relationship starts with a hidden argument nobody has had yet.

What one week of discovery produces

• A written problem statement both sides agree on, which is more often contested than anyone expects.
• Success metrics with numbers attached, so 'done' is not a matter of opinion.
• A map of the systems this has to integrate with, including the one nobody mentioned in the first call.
• A phased roadmap where the first phase is small enough to be estimated honestly.
• A cost range with the assumptions written down next to it.

It also lets either side walk away

Sometimes discovery shows the project should not be built, or not yet, or not by us. That is a good outcome delivered cheaply. We would rather lose the work in week one than deliver something the client did not need in month four.