Modernise
Application modernisation
Bringing an ageing business application up to date without stopping the business that relies on it.

The health check
Every modernisation starts with a fixed-price health check. We read the code, review dependencies and versions, map hosting and deployment, check backups, and talk to the people who use and support the app. You receive a written report with risks ranked by likelihood and impact, and a recommended sequence of work. You can stop there and keep the report.
Typical modernisation work
- Upgrades
- Moving language runtime, framework and libraries to supported versions, one step at a time, with tests at each step.
- Refactoring
- Restructuring the riskiest parts of the code so they can be changed safely, without altering behaviour users depend on.
- Re-platforming
- Moving from an unmanaged server to managed hosting or containers, with infrastructure written down as code so it can be rebuilt.
- Automated delivery
- A build and deploy pipeline so releases become routine, with a quick way to roll back.
- Partial replacement
- Rebuilding a single module where repair costs more than it saves, while the rest of the app carries on.
Tradeoffs we will discuss
Speed against risk: big upgrades in one jump are faster but harder to debug. Cost against longevity: a minimal upgrade buys a year or two, deeper refactoring buys more. Feature freezes: some work is easier if new features pause for a few weeks. We set out each option with its consequences.
What we need
Repository and hosting access, a contact who knows how the app is used, any existing documentation, however old, and an agreed window for releases.