Service 13 · Technical review
Before you buy it, or inherit it
You are about to buy a system, inherit one, or sign off on one. Somebody who did not build it should look at it first.
Fig. 13 — Technical review
What this usually looks like
- A vendor's system that nobody outside the vendor understands.
- A codebase inherited from a developer who has left.
- A spreadsheet system that is the business, and only one person can run it.
- A quote for work that may not be necessary.
What you get
- A written read of what is actually there, in plain language.
- The specific risks, ranked, with what each one would cost to fix.
- Whether the claimed capability holds up when tested.
- A one-page summary you can take into the decision.
Reviewed an inherited codebase and a production database's authorisation model, and reported findings with reproduction steps rather than opinions.
Questions
Will you sign an NDA?+
Yes. We do not keep client code or data after the engagement.
How long does a review take?+
Two to five days for a system of moderate size. The report is short.
Do you tell us not to buy?+
Sometimes. If the honest answer is that the thing is fine, you get that too, and it is worth having in writing.
Next step
Tell us what is not working
Describe the problem in a few lines. You get a plain answer about whether it is worth fixing and what it would take, before any money changes hands.
Start a conversation →