Skip to content

What a software review or code audit should tell you first

Before you fix, take over or rebuild a system, a review should rank the risks and say what to fix first. What a good one contains, and the warning signs.

Rosaan Ramasamy · 4 min read

In short

A useful software review tells you what the system is and runs on, how it is built and released, what is fragile, the risks ranked by what they would cost the business, what to fix first and roughly how big each fix is, and whether to fix, improve or rebuild, with the reason. It should also say what it couldn’t check. Be wary of a pasted scan report, or a “rebuild everything” verdict from the firm that would quote the rebuild.

When a system isn’t working and nobody can say exactly why, the tempting move is to pick a fix straight away: bring in a new vendor, patch what hurts, or start again. A software review, or code audit, comes first. It is the cheapest point at which to find out what you actually have.

But reviews vary a lot. Some are a tool’s output with a cover page. Some are a sales pitch for a rebuild. Here is what a useful one should give you.

What a useful review contains

  1. What the system is. Its parts, what each one does, and what it runs on, with each part’s end-of-support date. Why a working system can still be a risk explains why those dates matter.
  2. How it is built and released. Where the code lives, how changes reach the live system and how it is backed up and restored.
  3. What is fragile. The parts that break often, that nobody understands, or that only one person can change.
  4. The risks, ranked by business impact. Not a list of 200 findings in a row, but which ones could stop sales, leak data or lose records, and which can wait.
  5. What to fix first, with a rough size for each fix, so you can plan and budget.
  6. A recommendation: fix, improve, take over or rebuild, with the reason in plain words.
  7. What it couldn’t check, and why. Missing access, missing people, missing documents.

What a review can’t tell you

  • An exact price for a rebuild. It can tell you whether a rebuild is justified and roughly how big it is. A firm price needs a scope.
  • Whether your staff will use something new. That comes from the people, not the code.
  • Anything it wasn’t given access to. A review without the code or the server is an opinion about the screens.

What the reviewer needs from you

  • Access: the code repository, the hosting account, read-only access to the database and an admin login. If you don’t have these, getting them back is the first finding. Who should own the code, hosting and accounts? covers what to hold.
  • People: someone who uses the system every day, and anyone who knows its history.
  • The problem in your words: what goes wrong, how often and what it costs you.
  • The decision you face: keep or replace, which vendor, what to fix this quarter.

Warning signs of a poor review

  • A pasted scan report. Automated tools are useful, but their raw output isn’t a review. Someone has to say what matters for your business.
  • “Rebuild everything” without a reason you can check, especially from the firm that would quote the rebuild.
  • No ranking. If everything is critical, nothing is.
  • No “what we couldn’t check”. Every review has limits. One that admits none is hiding them.

Ranking by what the business needs

TCE Baby’s expo platform came to us live, with problems from before, and the expos couldn’t stop. So the expo calendar set the order: production problems first, then what the next event needed, then new features and longer-term work.

That is the habit a review should give you. It shouldn’t just list what is wrong. It should put the problems in the order your business needs them fixed.

Common questions

Will a review just tell us to rebuild?

It shouldn’t. A good reviewer understands the system first, repairs what can sensibly be repaired, and recommends a rebuild only when there is a real reason. Rebuilds are expensive and slow, and the old system usually holds rules nobody wrote down.

Do we need a review before a new team takes over?

Not always. If the system is small and well understood, a takeover can start directly. A review earns its cost when there are unknowns that make quoting or taking responsibility unsafe. Taking over software from another vendor covers what to check first.

Can our current vendor stay while someone reviews the system?

Yes. A review needs their cooperation on access and history, and the results are often useful to them too.

What is the difference between a code audit and a software review?

A code audit looks at the code. A software review also looks at how the system is hosted, released and used, and at the decision you face. For most business decisions, you need the wider one.

Our two sizes of review

If you are about to spend money on a system you are not sure of, start here.

  • A Decision Review, for RM1,000: a written second opinion on one decision, such as which of three quotes to accept, or whether to keep or replace a system.
  • A System Review, for RM5,000: an investigation into one system, what to fix first and in what order. It is delivered within 10 business days of us having the access and the interviews.

Either way, the fix budget then goes to what matters first, not to whatever hurts loudest. You are free to take the findings to any team. If you want us to do the work, a contained fix can be a Fix Sprint, and a longer list runs on Managed Delivery. Both sizes are on the Review page.

Rosaan Ramasamy

Founder and Managing Director, Antdragon

Rosaan started Antdragon in 2020 to be the team that stays accountable once software goes live, and works with business owners on the systems they rely on every day.