Project recovery
Software project takeover and codebase stabilisation
For business owners with broken, unfinished or abandoned custom software.
When this applies
- The developer who built your system is no longer reachable
- You do not hold the administrative access to your own software
- The application works, but nobody can safely change it
- The project was paid for and never finished
- You need to know whether to repair or rebuild before spending more
The four phases
- 01
Audit and control
Administrative access recovered and secured: cloud accounts, repositories, domains and API keys.
- 02
Stabilisation
Codebase freeze, isolated staging environment, and patching of critical database and security issues.
- 03
Improvement
High-value features deployed, plus accounting and compliance integrations relevant to your market.
- 04
Scaling
Multi-branch provisioning, automated onboarding and preparation for larger tenders.
What you get first
Every recovery starts with a written audit: what exists, who holds access, what condition the code and data are in, and an honest recommendation. Sometimes that recommendation is to rebuild, and we will say so even though repair would bill longer.
Inherited a system nobody can touch?
Send us what you know. The audit tells you where you actually stand.