Legacy readiness review

Who it is for

Organisations running a revenue-critical legacy application on premises or in a single-tenant host, with fewer than forty active maintainers and at least one integration that predates current staff. Common stacks include COBOL and mainframe job schedulers, Java EE monoliths, Progress OpenEdge, or heavily customised ERP extensions.

What you receive

• System inventory: languages, runtimes, scheduled jobs, and owner contacts
• Dependency sketch for up to three named integration points
• Risk register with likelihood, impact, and mitigation hooks
• Two to three migration pathways with indicative effort bands (person-weeks, not sales fantasy)
• Executive summary suitable for a steering committee pack

What we exclude

Production code changes, penetration testing, full data migration execution, and licensing negotiations with vendors. Those belong to follow-on engagements.

Process and timeline

Ten working days from kickoff, assuming access to a subject-matter expert for four hours per week. Days 1–3: interviews and repository access. Days 4–7: tracing and validation. Days 8–10: draft review workshop and final delivery.

Delivery

Hybrid: initial interviews on-site in Gauteng when practical; remote sessions for distributed teams. Written deliverables in English.

Preparation

Read-only source access, last three months of incident tickets, and a list of scheduled jobs. NDAs signed before access.

Pricing basis

Fixed fee published on Rates for the standard scope; additional integration points quoted separately.

Next step

Send a one-paragraph system description through contact and we will confirm fit within two business days.