Problem
Arclight's scheduling platform was built for a handful of pilot clinics. As adoption grew past 200 locations, the system that once felt generous started dropping bookings during peak hours, and every clinic's data lived in a separate silo.
Strategy
Instead of a rewrite, we scaled the existing scheduling core outward — introducing a proper sync layer with clinics' EHR systems and a notification service — so growth wouldn't mean starting over.
A central scheduling core serves both the patient-facing app and clinic staff portal, synced against each clinic's EHR system in near real time, with a dedicated notification service handling reminders and confirmations at volume.
Solution
We rebuilt the booking path to handle concurrent writes safely at far higher volume, added real EHR synchronization so clinic staff stopped double-entering data, and scaled notifications independently from the booking path itself.
Impact
The platform now comfortably handles 40x its original peak load, no-show rates dropped as reminders became more reliable, and the clinic network kept growing without another rebuild.
Peak load handled
No-show rate
Clinics onboarded