01The problem
Dispatchers juggled three disconnected tools and a spreadsheet to schedule a single route. Errors were frequent, onboarding took weeks, and the vendor behind the legacy system had stopped shipping fixes. Leadership feared a rewrite would freeze operations for a year.
02Our approach
We rebuilt the platform module by module, running the new system alongside the old one so operations never stopped. Weekly releases went straight to a pilot team of dispatchers whose feedback set the next sprint's priorities. The riskiest module — route scheduling — shipped first, on purpose.
