Application Modernisation Assessment
A costed, sequenced modernisation plan — and a clear answer on what to rebuild, replace, keep or retire.
A two-week review of your application portfolio, dependencies and delivery capability, ending in a costed modernisation roadmap your board can approve.
Duration
2 weeks
Pricing
on request
Deliverables
7 included
The figure above covers this initial engagement. Where discovery shows the work needs more, we continue on an optional time-and-materials basis.
What's included
- Application portfolio inventory with ownership and dependency mapping
- Technical debt, security and end-of-life risk assessment
- Process mapping for two priority business workflows
- A rebuild, replace, retain or retire recommendation for each application
- Licence and vendor spend analysis
- Costed roadmap sequenced across 12–24 months
- Board-ready summary and findings presentation
Most modernisation programmes fail before delivery starts, because the plan was written from ambition rather than evidence. Nobody counted the applications, nobody traced what depends on what, and nobody costed the sequence.
This assessment produces the evidence base first.
How it runs
Week 1 — Portfolio and dependencies. We inventory your applications, integrations and licence spend, identify overlap, shelfware and end-of-life risk, and trace which systems depend on which. We also map two priority business workflows end to end, because the case for modernising an application is usually made by the process running through it.
Week 2 — Capability and roadmap. We assess how software is planned, built, released and supported today, then sequence the findings into a costed 12–24 month roadmap — ordered by value against effort and dependency, and presented in a form your board can act on.
What makes it different
Every application gets an explicit verdict: rebuild, replace, retain or retire. “Retain” is a real answer, and it is the right one more often than a modernisation pitch usually admits — a stable system that nobody needs to change does not need your capital.
The roadmap also includes what to stop doing. Retiring shelfware and consolidating overlapping tools usually funds a meaningful share of the work, and that finding lands better with the licence numbers attached.
Where it leads
Where the verdict is rebuild or replace, the roadmap feeds into a modernisation or custom build engagement. Where it is retain, it often leads to an ongoing support arrangement instead — see Application Modernisation & Custom Software. Where service management turns out to be the real constraint, it feeds into the ITSM Health Check.
Interested in Application Modernisation Assessment?
Tell us about your environment and we will confirm the starting scope and price before any commitment. If a different package fits better, or if you need something else entirely, we will say so.