The Review That Reduced My Own Order: Independent Verdicts on Other People's Systems
Most of my portfolio is work I built. This is the other kind. A product owner sends me a specification his own team approved, or a founder forwards the architecture document of the vendor bidding against me, and asks whether it is the right approach. Recommendations from someone who profits from the answer are worth less, so each of these ships with the conflict named at the top and an alternative supplier named beside every recommendation.
- Role
- Independent reviewer. No build attached, and the conflict declared in writing.
- Tools
- Systems architecture ,Integration design ,GDPR Art 28 ,Technical due diligence
Watch the walkthrough.
The problem
An approved specification with the decision left open
Thirty-seven pages, twenty-three chapters, four versions in ten days, marked final and approved. It applied the right architectural principle to the external integration and never applied it inward to the company's own operating rules. So notification, approval and state-handling logic had no declared home, which meant it would land wherever the first developer put it.
A vendor bidding for the stage I was quoting
A two-page architecture overview from a competing supplier, forwarded to me four minutes after a pre-proposal call. Real engineering underneath. The load-bearing sentence was in the smallest type on the second page: the data sources the client needed at launch were demonstrated in bounded spikes and not yet admitted to production.
The solution.
Declare the conflict before the findings, not after
The vendor review opened by telling the client that if I called the engine good, that stage left my quote and my fee dropped, and if I called it weak it read as self-interest. So none of it was my opinion. Every finding quoted the vendor's own document, the client's own scoping document, or a public page, each naming its source so the client could check it without me.
Name the alternative supplier at every recommendation
The specification review's leading recommendation happened to mean more work for me. I wrote it, then wrote what to do if they did not do it with me, and then included a finding that pointed the other way and reduced what they would order. A verdict is worth something when its author says the same thing against his own interest.
Verify every claim before it reaches the client
The first draft of the specification review went through two independent verification rounds, one adversarial and one claim-by-claim against sources. Of 139 claims, 88 held, 33 were wrong and 18 were opinion. The adversarial round collapsed the entire lead argument table to zero surviving rows and it was rebuilt. An author checking his own paid work is not enough.
Hand over a question rather than a dependency
The product owner left with one sentence to put to his developers: if I want to change this in six months, is that a development ticket or a setting. The other client left with six neutral questions for the vendor, each of which served him whichever way the decision went, including the single artifact that would settle the whole argument.
The impact
What the reviews found
- A decision the specification deliberately left open, which would have decided itself in favour of whoever wrote code against it first
- The most critical integration contract missing at five separate touch points in a document marked final
- Multi-tenant isolation stated as a requirement with no mechanism, in a system where customers may be each other's competitors
- Four internal contradictions, each hiding a real development decision rather than an editing slip
- An appendix that silently overrode the body, so a developer reading only the main text would build something different
- Performance targets with no metric, device, network or percentile, which is an exemption rather than a requirement
How they landed
- The specification review was delivered a day early, and the client's own IT lead agreed with the leading recommendation on the review call rather than defending the document
- The vendor review's verdict was not to put the engine in the version one critical path, and to keep it alive as a phase-two option
- Neither review was repriced on the back of its own findings. The verdict travels in the covering note, never in the price
- One client has thanked me in writing, twice, for advice that cost me the sale
Have a similar problem?
Tell me what is going on and I will tell you what I would do about it. No obligation.