Software project rescue: take over a stalled build

Signs your project needs rescuing

Projects rarely fail in one dramatic moment. More often they drift until the business owner realises they are paying every month and not getting closer to launch. The usual patterns:

• The launch date has moved several times, and each new estimate sounds as confident as the last one.
• Every fix seems to break something else, and the same bugs come back.
• The developer or agency has stopped replying, or has said they cannot continue.
• You do not have the login for the code repository, the hosting account or the domain.
• The app works in demos but falls over with real users or real data.
• You have no clear picture of what is finished, what is half done and what was never started.

First, secure what you own

Before anyone writes a line of new code, make sure the business controls its own assets. If the relationship with the previous team is ending, ask for these while it is still friendly:

• The source code, ideally as access to the repository (for example on GitHub, GitLab or Bitbucket) with its full history.
• Admin logins for hosting, the database, the domain and DNS, and any app store accounts.
• API keys and accounts for third-party services such as payments, email and maps, moved into an account in your company’s name.
• Any designs, specifications, documentation and a list of known bugs.
• A recent copy of the production database.

What a code audit service covers

A code audit tells you what you actually have. Ours is written for the business owner, not for other developers, and looks at:

• Whether the code can be built and deployed from scratch by someone new.
• How the app is structured, and whether it was built in a way that can grow.
• Security basics: how passwords, user data and payment details are handled, and whether software libraries are badly out of date.
• How much of what was promised is actually finished and working.
• Automated tests, documentation and how hard the code is to change safely.
• A recommendation: keep and fix, fix in parts, or rebuild, with the reasoning behind it.

Fix it or rebuild it?

Rebuilding sounds tempting when a project has gone badly, but it is not always the right call. Working code, even messy code, holds months of decisions and edge cases. If the structure is sound and the problems are bugs, gaps and missing tests, fixing and continuing is usually faster and cheaper.

An app rebuild makes sense when the foundations are the problem: the wrong technology for the job, a database design that cannot hold your real data, security problems spread throughout, or code so tangled that every change is a gamble. Even then, a good rebuild reuses what it can, such as the designs, the data and the parts that work, and runs alongside the old app until the switch.

How a software project rescue works

1. Gather access and historyWe help you collect the code, logins and documents, and talk through what was promised and what went wrong.
2. Audit the codeWe get the app running on our side, review it, and give you a written report in plain English.
3. StabiliseWe fix the urgent problems first: crashes, security holes, broken backups and anything blocking your users.
4. Agree the planTogether we decide to fix, refactor or rebuild, map out what is left, and you get a written quote.
5. Finish in roundsWe work through the plan in rounds you review, with a project manager keeping you updated on what is done and what is next.

What it costs

Custom projects at Zoti start at $499/month, on a monthly plan covering design, development, hosting and ongoing changes. The price for a rescue depends on the state of the code, how much is left to build, and whether we fix or rebuild. You get a written quote before the main work begins.