Assessing software before buying or investing
A pitch deck shows what a product is supposed to do. The code shows what it does — and what it costs to keep running. A code review before the decision answers the questions the pitch leaves out: what was built and what was bought in, where the risks are, and how dependent the product is on somebody else’s services.
How it gets solved
What gets read is the code, the architecture and the dependencies — not the presentation.
The result names the technical risks and the running costs and assesses what was built in-house and what was bought in.
At a fixed price, with results within five working days.
What drives the effort
- The size and state of the codebase
- How many systems and services the product relies on
- Whether a quote or a technology decision should be assessed as well
Every quote is preceded by a free conversation in which the scope gets cut back as far as it will go.
How billing worksWhen it isn’t worth it
For small amounts, or when the technology plays no part in the decision, a review isn’t worth it. That gets said openly in the first conversation.
Common questions
- What do we get at the end?
- A written assessment that reads without a technical background: risks, costs, open questions and a clear recommendation.
- Is access to the code needed?
- Yes. Without the code it remains an assessment of the pitch. Confidentiality is agreed beforehand.
Something similar on your desk?
Describe briefly what it is about. You get an honest assessment back.