Why we prototype before we give you a fixed estimate
Fixed-price contracts fail when the scope is a guess. A two-week prototype turns that guess into evidence — and it is cheaper than being wrong.
Priya Gurung
CT Tech Nepal
A prospective client asked us for a fixed price on a scheduling platform. Twelve screens, three user roles, calendar sync. On paper, that is a four-month build. We quoted a two-week discovery instead, and the prototype killed two of the twelve screens and introduced a fourth role nobody had mentioned.
Estimating from a written brief is estimating from fiction. The brief describes what someone imagined. The prototype describes what people actually do when they try to use it. The gap between those two things is where budgets go to die.
We are not arguing against fixed prices. We are arguing for earning the right to give one. Once a prototype exists, once the flows have been through a usability session, once the integration surface is known — a fixed price is a reasonable commitment. Before that, it is a number pulled from optimism.
The commercial structure that works: a small paid discovery with a defined deliverable, then a fixed-price build against the validated scope. The client gets certainty where it matters, and nobody is renegotiating mid-project because a screen behaved differently than imagined.
Key takeaways
- Written briefs describe imagination, not behaviour
- A two-week prototype is cheaper than a mispriced quarter
- Fixed price is fine — once it is anchored in evidence
- Structure discovery as a small paid engagement with real deliverables