How we work
The engagement path for legacy modernization and codebase recovery — from first inventory to a roadmap your team can own.
AmberPath engagements follow a repeatable sequence shaped by legacy system modernization work, not by a product onboarding checklist. Use this page to brief sponsors before you request an assessment.
Triage conversation
A short call to learn what still runs, what has already been tried, and whether recovery must happen before any redesign talk. We decline work that needs only a greenfield build with no legacy constraint.
Access & inventory
Read-only repository access, environment notes, and a catalogue of applications, batch jobs, and data stores. Incomplete history is recorded as a fact, not brushed aside.
Recovery & reading
Where source and production diverge, we reconstruct enough of the tree to reason about behaviour. Interviews with operators catch the rules that never made it into comments.
Findings workshop
Sponsors and engineers review risks, load-bearing interfaces, and modernization options with trade-offs stated plainly — including timelines that may disappoint an eager board.
Roadmap & handover
A written plan with phases, decision checkpoints, and coaching notes so your team can continue without inventing a second dependency on us.
What we need on day one
- A sponsor who can prioritise “must not break” processes
- Technical contacts with time for paired reading sessions
- Honesty about prior rewrite attempts and political constraints
Where this leads
Most clients continue into our Legacy system modernization flagship engagement or stop after a Codebase recovery assessment once the gaps are clear. Rates explain how quotes are formed; Contact starts the triage conversation.