A stalled project is not a lost cause
When a software project grinds to a halt, it is easy to feel that the time and money are simply gone. In reality, most stalled and abandoned projects can be rescued when they are approached methodically rather than in panic.
The difference between recovery and further loss is order. Rushing to add features or begging an absent developer to return wastes energy. A calm, structured sequence turns a scary unknown into a concrete plan you can act on.
Step one: secure your assets
Before anything else, take control of everything the project depends on. If access is lost later, recovery gets far harder, so this comes first.
- Source code in whatever repository holds it.
- Domain registration, ideally confirmed in your name.
- Hosting and server or cloud account credentials.
- Databases and any data exports you can obtain.
- Third-party keys for M-Pesa, payment gateways, SMS, and WhatsApp.
- The paper trail: contracts, invoices, and chat history with specifications.
Step two: get an honest audit
Do not take anyone's word on how complete the work is. "Ninety percent done" is one of the most misleading phrases in software, and the last ten percent is frequently where the hardest work hides.
Have an independent, capable team examine the code, run the system, and test the integrations. A proper audit tells you what genuinely works, what is missing, how sound the foundation is, and what finishing will realistically take. This clear picture is the foundation for every decision that follows.
Step three: decide to continue, refactor, or rebuild
With the audit in hand, choose deliberately. If the foundation is solid, continuing from it preserves the most value. If the code works but is fragile, targeted refactoring of the weak parts may be the right balance. If it is fundamentally unsound, an honest rebuild avoids throwing good money after bad.
Resist the pull of sunk cost. What you already spent is gone regardless; the only question that matters now is which path gets you to working software for the least additional time and money.
Step four: stabilise before you build
Whichever path you choose, resist the urge to immediately pile on the features you have been waiting for. Inherited software needs to be understood and stabilised first. That means getting it running reliably, fixing the foundation where needed, and documenting how it works.
Building new features on an unstable base just multiplies the problems. A short investment in stability now makes everything that follows faster, safer, and cheaper.
Step five: protect the next phase
As you restart, put in place the disciplines that were probably missing the first time. Own your code, domain, and credentials outright. Insist on regular working demos so progress is always visible, and tie payments to milestones rather than promises.
Make sure more than one person understands the system and that documentation stays current. These habits cost nothing and are what stop a rescued project from stalling all over again.
The local advantage in a rescue
Taking over unfinished work benefits enormously from proximity. A local team can move quickly on the audit, meet you to talk through options, and give you a realistic plan without the delays of a time-zone gap. Accountability is real because you can hold them to it.
For Kenyan projects, local knowledge also matters at the technical level. M-Pesa, eTIMS, and statutory integrations are often exactly where the previous work stalled, and a team that handles these routinely can get past the blockage that stopped the last developer.
How Upeosoft rescues stalled projects
Upeosoft regularly takes on half-finished and abandoned software for Kenyan businesses. We begin with a clear-eyed audit so you know exactly what you have, then give you an honest recommendation to continue, refactor, or rebuild, with a realistic timeline and cost.
We stabilise the system, handle the local integrations that so often cause the stall, and get momentum back. Because we are local, you can meet us and hold us accountable. If your project has stalled, reach out and we will help you turn it back into working software.
