Software rescue for projects a previous developer left unfinished or unstable.
If your developer has gone, your app broke after a hosting or database upgrade, or a licensed script won't run reliably in production, we assess what's there, stabilise it, finish what's missing and keep it running.
Signs you need this
- The developer who built it is no longer available.
- Things broke after a server, PHP or database upgrade.
- Nobody can deploy or update the product with confidence.
- A licensed script you bought won't behave in production.
What’s included
Codebase and architecture assessment
A clear picture of what you have, what's broken and what it would take to fix it, before any commitment to a plan.
Production stabilisation
Fixing what is failing now, from database compatibility errors to broken downloads and misconfigured hosts.
Cloud storage migration
Moving uploads off a single server onto object storage, so the app is no longer tied to one machine.
Upgrade paths for licensed platforms
A repeatable way to apply vendor updates without losing your customisations.
Documentation as we go
API documentation and configuration notes, so the next developer never inherits the same mystery.
Completion and ongoing support
Finishing the features that were left undone, then continuing development and support.
How it works
Four steps, agreed before any code is written.
Step 01
Assess
We review the code, hosting and data, and tell you plainly what state it is in.
Step 02
Stabilise
Production issues first, fixed properly rather than switched off or patched over.
Step 03
Complete
Unfinished features finished, against a scope agreed in writing.
Step 04
Continue
Ongoing development and support, with the codebase left documented and easier to change.
Projects that prove it
Real work, anonymised. Each one is in our library.
How we approach it
Field notes on rescue your software.
Legacy PHP on Modern MySQL: Fixing Strict-Mode Failures Without Switching Strict Mode Off
How we moved a legacy PHP platform onto modern MySQL: find failing queries with temporary logging, fix them properly, and keep strict mode on.
4 min read
Before You Build a Business on a Licensed Script: What We Check First
Buying a ready-made script? The checks we run first: file storage, database compatibility, configuration, update path, API and core workflow fit.
4 min read
Customise It, Then Keep It Patchable: Running a Licensed Platform After Launch
How to customise a licensed SaaS script and still apply vendor updates: a self-update path, isolated customisations and a clear shared workflow.
3 min read
Questions
Rescue Your Software: common questions.
Do we have to rewrite the software?
Usually not. Rewrites throw away years of fixes and pause the product. We stabilise and improve in place, and only recommend a rewrite when the architecture blocks what the product needs next.
Can you take over code with no documentation?
Yes. It's a common starting point. We map the codebase as part of the assessment and write documentation as we go, such as OpenAPI descriptions of an undocumented API.
Can you fix a licensed script or marketplace template we bought?
Yes. Several projects in our library are licensed platforms we deployed, migrated to cloud storage, hardened and made upgradeable. We're clear about which parts are the vendor's.
Our app broke after a server upgrade. Is that fixable?
Almost always. Older code often relies on permissive database or language settings that newer versions reject. We find the failing parts and fix them properly, without turning safety settings off.
What do you need from us to start?
Access to the code repository and hosting, and a description of what's broken or unfinished. We reply within one business day and start with the assessment.
Have something you need to build?
Whether you’re starting with an idea, improving an existing product, or trying to rescue unfinished software, we’ll help turn the next step into a clear plan.
No sales presentation. We start with the problem.