Half-built apps are more common than finished ones. A freelancer vanishes, an agency folds, a budget runs dry — and you're left with a codebase you can't read and a decision you can't dodge: pay someone to finish it, or write it off and rebuild. This guide gives you the framework to decide: the three questions that determine salvageability, a 30-minute smoke test you can run yourself, the checklist a professional audit works through, and the honest economics of rescue versus rebuild.
Three questions decide whether an abandoned app is worth finishing: do you have the code, does it run, and is the architecture sane? Yes to all three and finishing is almost always the cheapest path. Yes to the first two but the code is a mess, and a refactor-and-finish sits in the middle. No to any of them — no repository, nothing boots, or the wrong foundation entirely — and a rebuild is usually the honest answer, and frequently the cheaper one. Everything below is how to answer those three questions with evidence instead of hope.
Not screenshots, not a live URL, not "it's on his laptop" — the actual source code, in a repository or archive you control. Without it there is nothing to finish; a deployed app without its source is a photograph of a building, not the building. Recovering the code is always job one, and it is worth real effort: a written request citing your contract, settling a disputed invoice, even paying for a handover often costs far less than a rebuild.
Code that boots on a fresh machine is a going concern; code that only ever ran on the departed developer's laptop may effectively not exist. If a new engineer can install the dependencies and start the app locally, every remaining problem is a known, fixable quantity. If nobody can get it running, the cost of finishing it is unknowable until someone does — and sometimes it never does.
This is the question only a professional can answer, and the one that decides cost. Sane doesn't mean elegant — it means a recognisable structure, a maintained framework, a data model that matches the business, and no decisions that have to be undone before work can continue. Messy-but-sane code can be finished. Code built on the wrong foundation has to be fought, commit by commit, and that fight is what makes "finishing" cost more than starting over.
Before you pay anyone for anything, you can gather real evidence yourself. None of these steps requires you to read code — they test whether the project is a functioning artefact or a pile of files. Work through them in order and write down where you get stuck; that note alone will make any professional audit faster and cheaper.
An honest caveat: if these steps feel alien — you don't know what a terminal is, or the instructions below read like another language — don't force it. Fumbling through commands you don't understand proves nothing either way, and one wrong move against a live database can make things worse. Pay for a professional audit instead: it's a small fixed cost, and a wrong salvage-or-rebuild decision is an expensive one to get cheap advice on.
npm install, composer install or similar). A clean install is a strong health signal; a wall of errors and deprecation warnings is data too.Four passes means you very likely have a salvageable project. One or two failures means the audit below matters. Total failure at step one means skip ahead to the red flags section.
A proper takeover audit reads the code before promising anything about it. Whoever you hire, this is roughly what they should be checking — and if a provider offers to quote your rescue without doing most of this list, that quote is fiction.
The output you should expect isn't a score — it's a decision: finish, refactor-and-finish, or rebuild, with a costed scope attached. That's exactly what a Meridianstacks app rescue audit produces, and the audit is useful even if you take the plan elsewhere.
Sunk cost is the enemy here. What you've already spent is gone either way; the only question is which path forward is cheaper from today. As a rule of thumb:
| What the audit finds | Verdict | What it costs |
|---|---|---|
| Code runs, architecture is sane | Finish it | The cheapest path — a code takeover with completion of a defined scope, typically £8,000–£12,000 via our app rescue service |
| Code runs, but it's a mess | Refactor and finish | The middle path — takeover plus targeted rework of the worst areas before new features; scoped from the audit, usually landing between the takeover band and a rebuild |
| Doesn't run, no code, or wrong foundation | Rebuild | The honest reset — priced as a normal build (a validation-stage web MVP is £12,000–£20,000). Often cheaper than fighting a broken base, because every pound buys progress instead of archaeology |
Prices published from our Open Price Book (v1.0 · July 2026 · next review October 2026). All prices exclude VAT.
The counterintuitive part: a rebuild is frequently less expensive than a rescue of bad code. Engineers untangling someone else's broken decisions move slowly and unpredictably; engineers building on a clean base move fast and to a schedule. Full build bands for every project type are in the Open Price Book.
Some projects should not be rescued, and the kindest thing an honest engineer can tell you is to stop paying for the old one. Any single flag on this list is survivable; two or more together almost always mean the rebuild column is your answer.
If that's where you land, don't treat it as a total loss. The abandoned build usually leaves behind the most expensive part of any software project: a tested understanding of what the product actually needs to do. Founders who rebuild after a failed first attempt tend to scope tighter, choose better, and ship faster — because this time they know.
What a professional handover looks like when the previous developer is still reachable — access transfer, knowledge capture and a clean break.
The first-48-hours playbook: securing accounts, recovering code and money, and deciding who finishes the build.
Send us the repository and we'll run the full audit — build, dependencies, secrets, data model, licences — and give you a straight verdict with a costed plan, in your business hours. If the honest answer is "rebuild", we'll tell you that too.
Start an app rescue →