Software project rescue: what is it, and what should it cost?

Also searched as: Software project rescue services · Software project rescue company

Updated 3 October 2026

Short answer

Software project rescue means someone new takes over a project that's stalled, broken or abandoned, and gets it working, usually without starting again. A good rescue begins with an honest written assessment, agrees in writing what "done" means before any paid work, and ends with the code and every account handed back to you. Preventionlabs' version: a free written assessment, then, if we take it on, $10,000 AUD flat to get the app running, protected to MVP level and on scalable infrastructure.

What's the problem

You have a project that isn't finished, isn't working, or isn't live, and the person who was building it can't or won't finish. You need someone to take it over, and you're wary, because the last person you paid is why you're here.

Why it happens

  • Projects stall at the hard parts. Deployment, security, scaling and the last integrations are where builds slow down and developers move on.
  • Starting again looks attractive. Many developers would rather build fresh than read someone else's code. That's often the expensive choice.
  • Open-ended engagements drift. Without a written definition of done, "nearly finished" can last for months.

How to fix it

What to look for in anyone you hand the project to:

  1. An assessment before a quote. They should read the code and tell you, in writing, what's broken, what's missing, and what it takes, before asking for money.
  2. An honest "no". If the project isn't worth saving, they should say so rather than sell you a rebuild.
  3. A written scope and a definition of done, agreed before work starts, with a fixed price where possible.
  4. Your accounts, from day one. Hosting, domain, app stores and code in your name, not theirs.
  5. Security treated as part of "working", not an optional extra.
  6. A real handover: the code in your repository, control of every account, and documentation someone else could follow.

When to call Preventionlabs

This is what we do. Submit the project with a repository link, a live address or just a description. The assessment is free, and comes back as a written diagnosis. If we take it on, the Scope of Work sets out the checklists that define done: the app running in your own hosting account with your listed flows working, protected to MVP level, on infrastructure that scales through configuration. It's $10,000 AUD flat for projects up to 50GB, then handed back with code, accounts and plain-language docs. It doesn't include new features, users or revenue. If it can't be saved, we tell you, and you owe nothing.

Submit your project for a free assessment

Free assessment. $10,000 AUD flat to get it live, only if we take it on and you go ahead.

Sources

  1. Preventionlabs: Terms of Service, section 2our terms of serviceA review of your software project. We examine the codebase and any live deployment you designate, and send you a written diagnosis: what is broken, what is missing, what it would take to bring the project back, and whether we will take it on. No charge. No obligation.
  2. Preventionlabs: Terms of Service, section 5our terms of serviceThe checklists in the Scope of Work are the definition of done for your project.
  3. Preventionlabs: Terms of Service, section 6our terms of serviceAll code, in a repository you own or control
  4. Joel on Software: Things You Should Never Do, Part Isoftware engineering essayThe idea that new code is better than old is patently absurd.
← All of Getting help