Old software rescued before it lets you down
We take over the system nobody else wants to touch, make it safe, and modernise it in steps your business can live with.
In plain English.
Plenty of businesses run on software written ten or fifteen years ago. It might be a PHP 5 web app, a Microsoft Access database on a shared drive, or a Visual Basic program only one person understands. It still works, mostly, but the original developer has gone, nobody dares change it, and the server it lives on is long out of support.
We start by reading the code and writing down what it actually does. Then we make it safe: proper backups, a copy running in a test environment, and urgent security fixes. Only then do we talk about modernisation, which might mean upgrading to PHP 8.3, moving the data to MySQL or PostgreSQL, or rebuilding piece by piece.
Rebuilding piece by piece matters. Rather than a risky all-at-once switchover, new parts take over from old ones one at a time while the business keeps running. If you simply want someone reliable to maintain the old system as it is, we do that too.
It suits you if.
- The developer who built your system has left or retired
- Your software runs on an old PHP version, Windows server or Access database
- Small changes take weeks because everyone is scared of breaking it
- You have no recent backup or test copy of the system
- Your insurer or a Cyber Essentials check has flagged unsupported software
What we do.
Code health check
A written report on what the system does, how it is built, where the security risks are and what to tackle first.
Safety net first
Backups, version control in Git and a separate test copy, all in place before any change touches the live system.
Upgrades in steps
PHP, framework and database upgrades done one version at a time, tested against the way your staff really use it.
Gradual rebuild
New modules replace old ones one by one, sharing the same data, so there is never a risky switch of everything at once.
Ongoing maintenance
A monthly arrangement for fixes, small changes and security updates, agreed up front.
How it runs.
- 01
Free call
Tell us what the system does, what worries you about it and who has access to the code and server.
- 02
Assess
We get access, take a full backup, read the code and give you a written report with clear priorities.
- 03
Stabilise
We fix the urgent issues, set up version control and a test copy, and make sure a failure can be recovered from.
- 04
Modernise or maintain
You choose a staged upgrade or rebuild, a steady maintenance arrangement, or a mix of the two.
Questions people ask.
We have lost contact with our original developer. Can you still help?
Usually, yes. As long as you can give us access to the server or hosting account where the software runs, we can retrieve the code and database. If the login details have been lost, we can help you recover access through the hosting company as the account holder.
Is it cheaper to fix it or start again?
It depends on the state of the code and how well it fits your business today. Our assessment report answers that question with reasons you can check. Often the answer is a middle path: keep the parts that work, and rebuild the parts causing trouble first.
Will the system be down while you work on it?
We avoid that wherever possible. Changes are made and tested on a separate copy first. Where a switchover is needed, such as moving to a new server, we plan it for a quiet time, agree it with you in advance and keep the old version ready to switch back to.
How much does it cost?
The initial assessment is a fixed price agreed after the free call. From there, each stage of fixes, upgrades or rebuilding is quoted separately, so you decide how far to go and when. Ongoing maintenance is a monthly fee agreed up front.
Your next chapter starts with a conversation.
Nottingham & Derby / UK-wideLet’s build
what’s next.
15 minutes with Garreth.
A real conversation about your business.
