01
Know what is there
Systems, dependencies, support status and key-person exposure across the agreed estate. The implicit map becomes explicit.
Legacy Estate Assessment & Modernisation Roadmap
Before you approve a rewrite, know what you actually own.
Three weeks inside one business-critical software estate, read-only. You leave with the risk mapped, the sensible options sequenced and a report the board can fund without a translator.
£7,950 fixed · ex VATThree weeksRead-onlyReport + 90-minute walkthrough
The deliverable
A decision, not another discovery phase.
The report is the product. It is yours whether the next step is with Epona, your own team, another supplier, or no project at all.
02
Know what matters
A risk map that separates urgent operational exposure from debt that is ugly but safe to leave alone.
03
Know what to do
A phased roadmap with effort bands, quick wins and decision points. No big-bang rewrite disguised as inevitability.
Fixed scope, fixed fee
£7,950
The fixed fee covers one defined business-critical estate and the surrounding dependencies that can be assessed properly in three weeks.
The fit call establishes the systems, repositories, data access and stakeholder availability before an agreement is sent. If the estate spans several divisions, access is missing or the scope is materially different, I re-scope it in writing before either side commits. It doesn't turn up later as an invoice surprise.
Read-only means Epona does not change production systems, source code or client data during the assessment.
How the three weeks run
Senior attention from day one to the final walkthrough.
Week 1
Inventory and interviews
NDA, read-only access, automated inventory and three focused conversations with the people who run, change and fund the estate.
Week 2
Risk and options
Dependencies, support status, change risk and delivery friction mapped. Roadmap options are tested with the lead engineer before they reach the board.
Week 3
Report and decision
Written report, quick wins and a 90-minute leadership walkthrough. Questions answered; next steps made explicit.
Qualify it before you buy it
It should be an obvious fit or an obvious no.
A good fit
- One software estate is business-critical or regulator-visible.
- Delivery, resilience or key-person risk has a real consequence.
- Read-only access and three stakeholder interviews are possible.
- A CTO, engineering leader or MD needs a decision, not extra hands.
Probably not a fit
- You only need a quote for a known feature.
- The system is modern, documented and changing safely.
- No one can grant access or make time for the assessment.
- You need certification, penetration testing or a compliance audit.
What leaves with you
- Estate inventory and dependency map
- Technical and operational risk map
- Key-person and support-status exposure
- Phased roadmap with indicative effort bands
- AI-readiness and safe-use guardrails where relevant
- Quick wins ready for your own backlog
- Written report and leadership walkthrough
See before you buy
The sample is fictional. The depth is not.
Harwick Mutual does not exist. The fourteen-system estate, risks and numbers are made up to show the structure and tone of the real deliverable without exposing a client's software. The support dates and recommended platform targets are checked against primary vendor sources and dated inside the report.
Open the sample report →Public recommendation
“He doesn't just tell you what a solution should be; he actually builds it as a proof of concept. You always get an honest, real-world view of the challenge.”Senior healthcare technology colleague · public LinkedIn recommendation · client references available before commitment
Find out whether the estate fits the fixed scope.
Twenty confidential minutes: what the system does, what prompted this now, and whether three weeks can produce a decision worth paying for.
No list. No sequence. No obligation to buy the assessment.