Case study
29 team-weeks of scheduling platform, built in 2 days
Calendars, resources and bookings for a homecare service, delivered with every acceptance criterion traced to a test.
A European healthcare distributorHealthcareAnonymised client work
QuotedDelivered
The problem
A regulated healthcare business needed a scheduling service that its own teams and partner systems could rely on. The internal estimate was three phases and roughly 29 weeks for a team of five.
How I approached it
- Three written phase plans with acceptance criteria before the build
- A shared multi-tenant access-control framework built first, with 822 automated tests
- Each phase built by parallel agents and closed only when its acceptance suite passed
What was built
- Scheduling domain, availability engine, holds and bookings
- Role-based, row-level security across tenants
- A reference client and phone-friendly calendar
- Infrastructure as code and deployment pipeline
Stack
- .NET 10
- Dapr
- Azure SQL
- Angular
- Bicep
Outcomes
- Acceptance criteria mapped to tests
- A reusable security framework for later projects
- Production hardening scheduled as a normal next step
Next step
Want the same result on your problem?
In 30 minutes you'll know whether to fix it, buy it, build it or leave it. No pitch deck.