← Solutions

Application health check and technical due diligence

An independent, evidence-based assessment of a codebase, its architecture and the team behind it — for investors, acquirers or new technology leaders.

Typical timing
2–4 weeks
Engagement
Fixed scope
Delivery framework
User researchDiscoveryAlphaBetaLive

Give decision-makers a clear, independent view of a software asset: how well it is built, how risky it is, what it will cost to scale or fix, and whether the team can deliver the roadmap. Used before an investment or acquisition, when inheriting a system, or when delivery has slowed and nobody can say why.

  • An investment, acquisition or supplier change is on the table
  • A new CTO or product owner has inherited an unfamiliar platform
  • Delivery keeps slipping and the reasons are disputed
How it runs

Activities, step by step

The plan follows our delivery framework. Steps that do not apply to this kind of work are left out rather than padded.

  1. 02 · Discovery1–2 weeks

    Evidence gathering

    • Automated code, dependency, licence and security scanning
    • Architecture, infrastructure and cost review
    • Interviews with engineering, product and operations
  2. 03 · Alpha1 week

    Analysis

    • Risks rated by likelihood and business impact
    • Delivery metrics reviewed: lead time, change failure, recovery
    • Remediation options costed
  3. 04 · Beta2–3 days

    Report and walkthrough

    • Findings presented to decision-makers
    • Red flags separated from normal technical debt
    • Questions answered before the report is final

Deliverables

What you keep at the end.

  • Technical due diligence report with executive summary
  • Risk register rated and prioritised
  • Security, dependency and open-source licence findings
  • Costed 90-day remediation plan

Outcomes

What it is built to change.

  • An investment or acquisition decision made on evidence
  • Price, warranties or conditions informed by real risk
  • A clear first 90 days for the new owner