Assess Application Modernisation

Application Health Check

Know what you have actually inherited, and what it will cost to keep running.

A one-week audit of a single business-critical application — code, dependencies, security and deployment — ending in a risk register and a costed support recommendation.

Duration

1 week

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

  • Codebase review covering structure, test coverage and maintainability
  • Dependency and framework audit against end-of-life and known vulnerabilities
  • Security posture review of authentication, secrets handling and exposed surfaces
  • Build, deployment and environment assessment
  • Documentation and key-person-risk review
  • Prioritised risk register with remediation estimates
  • A costed support recommendation, sized to the system's actual condition

Who it's for

  • Organisations that inherited software when the people who built it left
  • Teams considering outsourcing support for an application nobody owns
  • Businesses deciding whether to keep investing in a system or replace it

Delivered on

Most support arrangements are quoted on a description of a system rather than the system itself. That works until the first month, when the dependency nobody mentioned turns out to be four major versions behind and the deployment process turns out to live in one person’s terminal history.

This audit replaces the description with evidence.

How it runs

Days 1–2 — Code and dependencies. We review the codebase for structure, test coverage and maintainability, then audit every dependency and framework against end-of-life dates and known vulnerabilities. This is usually where the first surprises appear.

Day 3 — Security and infrastructure. We assess authentication, secrets handling and exposed surfaces, then examine how the application is built, deployed and monitored, and what happens when it breaks.

Day 4 — Knowledge and key-person risk. We establish what is documented, what is not, and how much of the system exists only in somebody’s head. For inherited software this is frequently the largest risk on the register, and the one nobody has written down.

Day 5 — Findings. We present a prioritised risk register with remediation estimates, and a support recommendation costed against what the system actually needs rather than a standard tier.

Why it comes first

We do not quote application support without running this. A retainer priced on optimism is bad for both sides: you get a number that rises the moment reality arrives, and we get an agreement we cannot honour. Sizing the commitment against evidence is the only version that survives contact with the system.

Where it leads

Most engagements continue into an ongoing support arrangement — see Application Modernisation & Custom Software. Where the findings show the system is at the end of its useful life, the Application Modernisation Assessment sets that decision in the context of your wider application portfolio.

Interested in Application Health Check?

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.