Skip to content
ENS.EG

Taking Over a Stalled Software Project from Another Company

17 Nov 2026

The developer disappeared, the previous company stopped, or the project has half-worked for months. Before deciding to finish it or rebuild from scratch, you need a calm assessment of what you actually own. This guide covers what to collect, how the code is assessed, and when finishing beats rebuilding.

A stalled project does not necessarily mean bad code. Sometimes the problem was communication, a scope that changed every week, or one developer who carried the whole thing and then got busy. Sometimes the code really is unusable. The difference does not show on the screens. It shows in what sits underneath them.

The biggest risk at this point is a hasty decision in either direction: a full rebuild that throws away what has already been paid for, or blind continuation on a foundation that costs more every month.

First, collect what you own

  • The complete source code, in a repository under your company’s name, not a zip file in a developer’s inbox.
  • Access to hosting, the database, the domain, the app store accounts, and the email and messaging services.
  • Any documentation, even WhatsApp messages with decisions in them or screenshots of the design.
  • A list of what runs in production today, and what only runs on the developer’s machine.
  • The contract and invoices, to know what was supposed to be delivered.

If the Google Play or App Store account, or the domain, is registered to the previous developer, that comes before the code. Recovering the account behind a published app is far harder than recovering files.

Second, assess the code

A useful assessment answers specific questions rather than giving a general impression:

  • Can the project be set up from scratch on a new machine by following written steps?
  • Are the language and library versions still receiving security updates?
  • Is the database well structured, and is the current data sound?
  • Where does the important business logic live, and is it understandable or scattered across hundreds of files?
  • Are there tests, and do they pass?
  • Are there obvious security holes: passwords written in the code, permissions left open?

Finish or rebuild?

Finishing is usually right when the foundation works, the data is sound, and the problem is missing parts or specific bugs. A rebuild deserves serious thought when the project cannot be run with confidence, when the technology is no longer supported, or when every small change breaks something else. There is a middle path that is often best: keep what works and serves customers today, and replace the weak parts one at a time.

Either way, the existing data has value: customers, orders, history. Any decision has to include how that data moves across without loss.

Third, the first two weeks after handover

Before adding any new feature, the first stretch goes into stabilising what exists. We set up a test environment separate from production, configure automatic backups, close the obvious security holes, and rotate every password and credential the previous party held. Then we fix the bugs that hurt customers daily, because that is the fastest way to restore confidence in the project inside the company.

Only then do we write the completion plan: the remaining work ordered by business impact, an estimate for each item, and short deliveries you can see and try. If it turns out during the work that a part needs rebuilding, it is raised as a separate decision with its cost and reason, never as a surprise halfway through.

What to expect from the written assessment

A short, clear report in non-technical language: what works, what is a risk right now, which options exist, and the rough cost and duration of each. You should be able to read it and decide, even if you end up continuing with someone else.

How to avoid a repeat

  • The code lives in a repository the company owns from day one.
  • Every external account is in the company’s name, with the developer added as a user.
  • Small deliveries you can try every two weeks, not one large delivery at the end.
  • Enough documentation for someone else to take the project over.

If the project is an internal system whose data has to move, read data migration to a new system, and to avoid stalling next time see the software development contract checklist. We take on these projects through custom software development and support and maintenance.

Send a description of the project and what you hold today from start your project, and we begin with a written assessment before any commitment to build.

Have an idea or a system that needs building?

Tell us about your project in three short steps. We will review it and contact you to agree on the next step.

Start a project