Skip to content
Boxed Online, home

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
Estimated 29 team-weeks, delivered in 2 days
Quoted versus deliveredPhase plans and 62 commits between 1 and 3 September 2026

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 we approached it

  1. Three written phase plans with acceptance criteria before the build
  2. A shared multi-tenant access-control framework built first, with 822 automated tests
  3. 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

What changed

  • Acceptance criteria mapped to tests
  • A reusable security framework for later projects
  • Production hardening scheduled as a normal next step
This build: estimate against delivery
  • Healthcare scheduling platform

    Estimated: 29 team-weeks. Delivered: 2 days

  • Multi-tenant access-control framework

    Estimated: 14 weeks. Delivered: 5 days

Bars are to one scale in working days, at five days to a week, using the lower figure of any range. A few hours is drawn as half a day, and the shortest bars have a minimum width so they stay visible. Builds that were never estimated are left out.

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.

We reply within 2 business days.