Owning software · 5 min

What a Reality Check on your software covers, and what it costs

Published
Updated
Reading time
5 min

Short answer: a Reality Check is our fixed-price written verdict on software someone else built. It tells you what is really there, what it costs to run, who controls access, what will break first, and whether to keep, fix or rebuild it. It costs from €1,800 and takes 3 to 5 working days. If you then start a project or a partnership with us within 60 days, the full fee is credited.

When it is worth doing

You need one when the people who built your software are no longer the people who will run it. The usual versions:

  • The freelancer who built it took a full-time job and answers email once a week.
  • The agency finished the contract, sent a zip file and moved on.
  • You bought a small SaaS business and the founder is leaving after the handover.
  • The build stalled somewhere around 80% and nobody can say how far it really is.

In each case you are about to spend money on the next developer, and you do not yet know what they are walking into. Neither do they. The Reality Check is how both sides find out before the invoices start.

What the Reality Check covers

What is actually there

Not the architecture diagram from the original proposal. The code as it is: how it is structured, which parts are tested, which parts only one person understood, and which parts are unused. The report names the two or three places where a change is most likely to break something.

What it costs to run

Hosting, databases, email, payments, error tracking, the AI bill. Read from the invoices, not from memory. Services nobody uses any more and hosting sized for traffic that never arrived are common in software that changed hands, and sometimes the savings cover the cost of the check.

Who holds the keys

The domain, the cloud account, the app store listings, the payment provider, the code repository. One of the most damaging findings in a takeover is not bad code. It is a critical account sitting in the previous developer's personal email. The report lists every account, who owns it now, and what it takes to move it.

Security and data

Where customer data lives, who can reach it, whether secrets are in the repository, and how backups work. The question that matters: has anyone ever restored a backup? If not, you do not know that you have one.

How it ships

How code gets from a laptop to production. A deploy that one person runs by hand from their machine is a risk you are paying for every week.

The verdict: keep, fix or rebuild

Keep, fix or rebuild, with reasons. Most systems are worth keeping and fixing. Rebuilding is the expensive answer and the right one less often than developers suggest, because a new team always prefers its own code. The report also says which parts to leave alone.

The first 90 days

What to fix first, what can wait, and roughly what each costs. This is what you hand to the next developer, whoever that turns out to be.

How it works

  • Price: fixed before we start, from €1,800. Larger systems cost more, and you know the number before you commit.
  • Time: 3 to 5 working days.
  • What we need: read access to the code and the hosting, and one call with whoever knows the history.
  • What you get: a written report with the verdict and what to do first. You can read a sample report on one of our own products to see the format.
  • Credit: if you start a project or a partnership with us within 60 days, the full fee is credited.

More on our codebase audit is on the Reality Check page.

How the price compares

We compared the published prices of small European and UK studios in September 2026. Fixed-price takeover audits cluster between €1,500 and about €2,500, with larger or regulated systems going higher. Some sellers offer a short assessment under €500. What that includes varies a lot, so ask how many days of reading the code you get.

Be wary of two things:

  • Free audits. Reading a codebase properly takes days. Free means the time is paid for by the rebuild they are about to recommend.
  • Hourly audits with no cap. You cannot budget for them, and the incentive runs the wrong way.

Red flags you can check yourself today

You do not need a developer for these:

  1. Do you, personally, have admin access to the domain registrar, the hosting account and the code repository? If any of those logins belong to the previous developer, fix that first.
  2. Can anyone other than the previous developer deploy a change?
  3. When did someone last restore a backup to check it works?
  4. Do you know your monthly running cost, line by line?

If the answer to any of these is no, the software has a risk that has nothing to do with code quality.

What to do with the result

The report is yours. Give it to your own team, use it to brief a new developer, or use it to decide the software is not worth saving. If the honest answer is that you do not need us, the report says that too.

We build and run our own products, GarageHub among them with paying subscribers, so we read a system the way its owner would. If you are buying a software business rather than inheriting one, this page covers what changes.

Already have software?

A written verdict in 3 to 5 days, from €1,800: keep, fix or rebuild, and what to do first. Credited if we carry on together within 60 days.