Aged care
From stalled development to production readiness in under 30 days
Grail took over delivery of an inherited care-services marketplace codebase and rebuilt the production platform around a modern architecture, automated delivery controls, granular permissions, durable workflows and observable operations.
The challenge
An inherited platform remained incomplete and unstable after an extended development cycle. Requested changes were slow and frequently created regressions, leaving the business without a dependable path to production.
What Grail built
We recovered the existing system, rebuilt the application architecture, and connected delivery pipelines, permissions, workflows, testing, infrastructure and observability into one production system.
React
TypeScript
Postgres/PostGIS
TemporalWorkOS
AWSImpact
The client-agreed production-readiness milestone was reached in under 30 days from Grail taking over delivery. The inherited repository contained about 1.5M lines of code. More than 400 work items went through rolling client review, and the release repository included 700+ automated test files.
Impact summary
| Primary result | About 1.5M inherited lines in the repository |
|---|---|
| Operational result | 400+ work items reviewed |
| System scope | 700+ automated test files |
| Delivery note | Production-readiness milestone in under 30 days |
How the work progressed
We began with recovery rather than assumptions. The team mapped the inherited system, agreed the behaviours that had to work, rebuilt the platform in controlled increments, and moved each release through testing and client review.
- Grail reviewed the inherited repository, infrastructure and unfinished work.
- The team mapped critical behaviours, user roles and production risks.
- Architecture, workflows and delivery controls were rebuilt as one system.
- Changes moved through automated tests and rolling client review.
- The agreed production-readiness checks were completed before release.
Control and review
The control points were specific to the system, so delivery could move faster without taking sensitive decisions away from the people responsible for them.
- The client reviewed work continuously instead of waiting for a final handover.
- Roles and permissions limited access across sensitive workflows.
- Automated tests checked the rebuilt system before release.
- Monitoring made production behaviour visible to the operating team.
What shipped
The implementation centred on these delivered pieces:
- Recovered system map and production architecture.
- Automated build and delivery pipelines.
- Granular roles and permissions.
- Durable operational workflows.
- Regression and release test coverage.
- Production infrastructure, monitoring and operating controls.