A local government organisation was replacing a storage platform through a competitive procurement. One response was heavily discounted. On the spreadsheet, it looked attractive. The price was aggressive, the vendor wanted the reference, and the commercial pressure to accept the saving was obvious.
The technical review found a fundamental mismatch between the proposed design and the documented requirement. The product itself was credible, but the quoted configuration could not meet the organisation's capacity, performance, resilience and growth expectations.
There is a difficult moment in these projects where the numbers look good and the technical judgement does not. At that point, signing off the design would have been easier politically but wrong professionally. We declined to approve it because the gap between the proposal and the requirement was not a rounding error; it was structural.
The organisation proceeded with the purchase. Six months later, the limitations were no longer theoretical. Additional hardware and associated work were required to reach the capability that should have been present from the beginning.
The additional cost was around £120,000. The cheapest tender had not reduced cost. It had deferred it, moved it into the delivery phase, and removed options from the people who had to operate the platform.
Discounting was not the mistake. The mistake was allowing procurement scoring to stand in for engineering validation. A capable product can still be the wrong fit for a particular environment.
Engineering lessons
- A low price is not a technical control.
- Procurement should include engineering challenge before the decision is locked.
- The wrong architecture can turn a saving into a delayed cost.
Read the engineering principles behind this work →
Confidentiality: Engineering Notes are based on real engagements. Client identities, timelines and identifying details may be changed to protect confidentiality. The engineering decisions and lessons remain representative of the work undertaken.