When This Is Worth Buying
You have a proposal in front of you, a significant amount of money attached, and no way to judge whether it is reasonable.
That is the situation this exists for, and it is a common one. Businesses without technical staff are asked to make expensive, hard-to-reverse decisions on the basis of documents written by the party being paid. A few hours of independent opinion beforehand is cheap insurance.
Other cases worth it: inheriting a system nobody understands, deciding whether to rebuild or repair, evaluating an acquisition’s technology, or a supplier relationship that has stopped working and you cannot tell whether the fault is theirs. If the software was built with AI and the question is whether it can be relied on, AI Sign-Off is the narrower route: a developer reviews it against what it should do, fixes what fails and signs off that version.
What We Actually Do
Read the proposal properly. What is included, what is conspicuously absent, whether the estimate is consistent with the scope, and what the commercial terms mean for you in two years.
Ask the questions you would ask if you knew what to ask. Which parts are standard and which are genuinely hard, what happens when it is wrong, who owns the code, what maintenance costs afterwards.
Look at what exists. For an inherited system: what it is built on, whether it is maintained, where the risks are, and what it would take for somebody else to take it over.
Give a straight answer, including that the proposal is fine and you should sign it. That happens, and saying so is the point of being independent.
What We Will Not Do
Tell you that you need a rebuild so we can quote for it. If the honest answer is that your existing system is fine and needs maintenance rather than replacement, that is the answer, and it is frequently the case.
That is the whole basis of buying independent advice: the value depends on us having no stake in the outcome. Where we would be a candidate for the work, we say so upfront and you should weigh the advice accordingly.
Where It Pays For Itself
Scope that was never going to be delivered for that number. Visible from the outside more often than you would think.
Ownership terms. Which account holds the code, and whether you can leave. Discovered late, this is expensive; discovered before signing, it is a paragraph.
Missing maintenance costs. A build quoted without the annual cost of keeping it running is half a price.
The rebuild that was not needed. The most common finding on inherited systems, and the largest saving.
What Moves The Price
How much material there is to read. A proposal is hours; a codebase review is days.
Whether access is available. Reviewing a system without access to it is guesswork.
Whether you need a written report or a conversation. The conversation is usually enough and considerably cheaper.
Questions To Ask Whoever You Engage
- Do you want the work you would be reviewing? The answer should be volunteered, not extracted.
- What would make you say do nothing? Somebody who cannot answer will always find something.
- Have you built this kind of system yourself? Advice from people who have not is theory.
A Brief You Can Send Anyone
The decision: [what you are trying to decide]
What you have: [proposal, existing system, or both]
The money involved: [ballpark]
The deadline: [and who set it]
What you are worried about: [in plain terms]
Access available: [code, systems, the supplier]
How We Do It
Usually a conversation and a short written summary rather than a formal report, because that is what most decisions need and it costs less.
Where the outcome is that you should build something, we will tell you what to ask for rather than assume it should be us. Where it is that you should do nothing, that is a legitimate outcome and it is the one that saves the most money.
Get in touch with the proposal or the system, and the decision you are stuck on.