Recover
We study the code, live behaviour and staff knowledge, then record the rules and dependencies the business relies on.
Approval gateYour team confirms the current behaviour.
Our approach
Replace the system, not the knowledge inside it.
One senior Grail lead owns the work from system review through release. Your team approves the current-state record, target scope, acceptance tests and production release.
Define
We agree the target system, delivery sequence and acceptance tests before implementation begins.
Approval gateYour team approves the scope and tests.
Rebuild and test
AI speeds up implementation inside a controlled engineering system. Every change must pass the agreed checks.
Approval gateReviewed evidence is required before work moves forward.
Release and improve
Users move in stages while the live system is monitored. Releases, tickets and further improvements remain connected in Grail Platform.
Approval gateYour team approves the production release.
What we need from you
A clear owner and access to the real system.
Repository access, a business owner, a technical reviewer and an agreed security boundary.
What you receive
The evidence needed to release and operate.
A system map, approved build plan, release evidence and operating guide.