Codebase recovery assessment

Reconstruct what still exists when repositories are incomplete, authors have left, or production no longer matches the last known branch.

Format
Time-boxed assessment
Typical duration
2–4 weeks
Delivery
Remote-first; Sydney workshops as needed
Pricing basis
Fixed fee assessment

Purpose

When the last maintainer has left and the “official” repository is missing weeks or years of production fixes, a recovery assessment rebuilds a usable picture of what runs today.

Scope

We compare deployed artefacts with available source, reconstruct build steps, document shadow scripts, and produce a recovery report: what can be rebuilt, what must be treated as binary-only, and what knowledge interviews still need to capture.

Outcomes

  • A recovered working tree or clear gaps where source cannot be found
  • Notes on environment secrets and configuration drift (without storing secrets in our materials)
  • Prioritised list of recovery risks before any modernization spend

Next step

Ask for a Codebase recovery assessment via Contact. Bring whatever archives, installers, and old tickets you still have.