You send the same brief to three engineers and get quotes of £8,000, £25,000, and £65,000. This is surprisingly common — and it is almost never because one of them is wrong.
It is because your brief left enough ambiguity that each engineer built a different mental model of what they were being asked to price. They are all quoting accurately — but for different projects.
The five things engineers fill in when your brief is unclear
When a brief is thin, engineers make assumptions. Here are the five most common ones — and why they diverge so much:
- 1Quality bar — prototype quality vs. production quality costs are fundamentally different. A prototype-grade firmware stack might take 2 weeks. A production-quality equivalent with test harness, logging, error handling, and documentation might take 8.
- 1Scope of integration testing — who tests the whole system? If your brief says "BLE module" without specifying whether you need a protocol validator, the engineer decides.
- 1Enclosure — "the device" to one engineer means bare PCB. To another it means PCB + enclosure + labelling.
- 1Documentation — some engineers include a full handover package by default. Others assume code comments are sufficient.
- 1Revision cycles — "build it" to one engineer includes one round of client feedback. To another it is a fixed deliverable with no revision.
The most expensive assumption: quality bar. Two engineers with identical skills quoting the same brief can differ by 4x based solely on whether they plan for prototype or production quality.
Why a pre-brief sprint almost always saves money overall
A paid scoping sprint (Blueprint Sprint) typically costs a fraction of the quote variation it eliminates. If your quotes range from £15k to £60k, a £2k scoping exercise that collapses that range to £22k–£28k has an immediate, clear financial return.
The sprint produces a specification that all engineers quote against. With the same spec, the remaining variation reflects real differences in experience, overhead, and approach — not ambiguity.
What to clarify before sending a brief
A short clarification checklist: - Is this prototype or production quality? - Does the scope include enclosure/mechanical? - What documentation is in scope? - How many revision rounds are included? - Who manages component procurement? - What definition of done gates the final payment?
Adding answers to these six questions to your brief will cut quote variation significantly — even before running a formal scoping sprint.