The situation
The business ran its back-office on ageing applications installed locally on desktops, running off an onsite server. It worked — until you looked at the risk. The software was on an unsupported, dead-end platform increasingly at odds with newer versions of Windows; the whole operation depended on a single physical server and a fragile backup routine; and years of critical business logic and rules were locked inside the old application, largely undocumented. On top of the technical risk, the day-to-day admin had become a drag — manual steps, workarounds and inefficiencies that had built up over years and were holding the business back.
What I built
A full legacy modernisation, then ongoing improvement — grown over 3–4 years:
- Recovered the hidden business logic. I reverse-engineered the rules, calculations and edge cases out of the legacy application and its code — the undocumented "why it works that way" that a rebuild has to get right.
- Rebuilt the back-office as a cloud-native web platform. The locally-installed system became a modern web application — no onsite server, accessible anywhere, backed up and secure.
- Streamlined the administrative workflows. Rather than copy the old process, I removed the manual handoffs and inefficiencies — so the new system is genuinely faster and easier to run day to day, not just newer.
The result
- Legacy technical risk removed. No more dead-end, unsupported platform; no more single onsite server and hand-managed backup as the only line of defence.
- Administrative & workflow efficiency. The manual steps and workarounds that had built up were designed out — day-to-day admin is faster and less error-prone.
- Cloud-native and scalable. A platform that grows with the business instead of holding it back.
- The business logic preserved and improved — the rules that made the old system work were carried across, documented, and built on.
- A multi-year, growing engagement — continuously enhanced and expanded over 3–4 years.
- [Hard metrics — admin time saved, error reduction, volume handled — to confirm and add.]
Why it matters
This is legacy modernisation done properly. The easy part is writing new code; the hard part — the part AI tools and offshore shops skip — is recovering the rules buried in the old system so the rebuild is better than the original, not a broken copy of it. That's the work I specialise in, and I've stayed on the platform for years since.