Old systems replaced
without a big-bang switch
We replace ageing systems in stages. The old one keeps running until the new one has proved itself on real work, so the business never stops.
- Typical
- Phased
- Pricing
- Fixed price per phase
- Group
- Product engineering
What you get
Legacy system renewal
Replace ageing systems in stages, with the old one running until the new one has proved itself.
System archaeology
What the old system really does, including the rules nobody wrote down.
A staged plan
The system split into parts that can be replaced one at a time.
Side-by-side running
Old and new run together and their outputs are compared daily.
Retirement
The old part switched off only when the numbers match.
Where it fits
Good places
to start
- 01Systems nobody can change
Code whose authors have left and that everyone is afraid to touch.
- 02Unsupported technology
Platforms past end of life, with security and hiring risks.
- 03Failed rewrites
A previous big-bang replacement that stalled.
How it runs
Small steps,
shown every week
- 1–2 weeksDiscover
We map how the work happens today and agree what done looks like.
- 2–4 weeksPrototype
The riskiest flow first, on your real data, while change is cheap.
- 2-week sprintsBuild
Weekly demos and a shared backlog you can reorder at any time.
- OngoingRun
Monitoring, agreed response times and a monthly review of usage.
Questions
Before you start
How long does it take?
What about our data?
Who owns what you build?
Legacy system renewal
Tell us what
you need.
A 30-minute call with the people who would do the work, then a written proposal.