AI Strategy Consultancy
Responsible AI roadmaps that prioritize value, data readiness, and ethical adoption.
Read moreReplatform
Legacy Rebuild
A rebuild is worth doing when the constraint is the architecture itself, not the interface on top of it. The discipline is knowing which of the old system's behaviours are real business rules worth carrying forward, and which are twenty years of accumulated accident.
When this helps
You are probably reading this because of one of these.
- The architecture blocks changes the market now requires
- The user experience is costing you renewals or sales
- Partners need APIs the current system cannot expose
- Maintenance consumes the budget that should fund new features
How we help
A delivery sequence, not a discovery phase that never ends.
Every stage produces something you can act on independently, so the engagement can stop at any point without leaving you stranded mid-programme.
Excavate
Recover the real business rules from code, data, and the people who work around the system daily.
Design
Architect for the load, integrations, and change rate you expect next, and redesign the experience around actual tasks.
Rebuild
Deliver in vertical slices that go live, so the rebuild returns value before it is finished.
Migrate
Move users and data in controlled cohorts, with the old system available until each cohort is settled.
Efficiencies driven
The measurable change this engagement is aiming at.
Where teams usually start
- Business rules known only through the old code
- Screens shaped by legacy database structure
- Integrations built by screen-scraping or direct DB access
Where the engagement leaves you
- Rules documented and covered by tests
- Interfaces shaped around the work people actually do
- Versioned APIs partners can build against safely
Slices
Live before the rebuild completes
Cohorts
Migrated with rollback each
Documented
Rules, not folklore
What you receive
Artefacts that outlive the engagement.
- Documented business rules recovered from the existing system
- Target architecture and redesigned user experience
- Rebuilt product delivered in live vertical slices
- Versioned, documented public and partner APIs
- Cohort migration plan with rollback per cohort
Next step
Scope a rebuild.
A short call is usually enough to work out whether this is the right engagement, and what it would cost. If it is not, I will say so.
Engagement
Replatform
Not reskinned