About AmberPath
A Sydney consulting practice built around the unglamorous work of understanding old systems before replacing them.
Why we exist
Too many modernization programmes start with a preferred stack and a slide deck. AmberPath started because clients kept asking for someone who would open the forgotten branches, sit with warehouse supervisors, and admit when source code simply was not there.
We are a small software consulting practice based in Sydney. Our focus is narrow on purpose: legacy system modernization and codebase recovery for organisations that still depend on systems built long before the current team joined.
Origin
AmberPath grew out of recovery projects in distribution, professional services, and mid-size manufacturing — places where a single VB or Java monolith still posts the day’s revenue. The brand name reflects the work: follow the amber path of what still runs, rather than pretending the past never existed.
How we work with clients
- We write findings in plain language for sponsors and precise notes for engineers.
- We prefer evidence from production behaviour over architecture diagrams drawn from memory.
- We stay long enough to hand over a plan your team can own; we do not invent dependency on a product we sell.
People
Principal consultant — Mira Hale leads most flagship modernization engagements. She has spent years reconstructing incomplete repositories and negotiating phased cutovers with operations staff who cannot pause month-end.
Engagement analyst — Tom Rees supports inventory work, dependency mapping, and workshop facilitation across Australian time zones.
Values that show up in the work
Respect for operators who keep brittle systems alive. Honesty about missing source. Patience with institutional knowledge that only surfaces mid-conversation. Care with data paths that touch money, stock, or regulated records.
Australia context
We quote and contract under Australian norms, meet in Sydney when useful, and schedule remote sessions that respect interstate time differences. Office visits use the address published on our contact page.