The context
A growing pool service company with a tight regional footprint and an experienced ops lead who knew exactly what was wrong — and didn't yet have software that could keep up with him.
The problem
Dispatch lived on a whiteboard and a group text. Customer history lived in the heads of long-tenured techs. New hires onboarded by shadowing because there was no other reasonable path. Cancellations and rescheduling cost hours of phone calls every Sunday night.
Leadership had no view of margin per crew, per route, or per service type — just the bank balance at the end of the month.
What we did
We mapped the route model, the recurring service templates, and the seasonal cycles. Then we configured Opsvara around them:
- Route-first scheduling with recurring service templates per pool
- Per-property service history (chemicals, equipment, photos) accessible from the field
- Customer self-serve reschedule and pause flows
- A live margin dashboard for leadership, by route and by crew
- A simple referral and reactivation campaign engine
The outcome
- All crews onboarded to the new system within two weeks
- Dispatcher decisions per day dropped roughly 60%, freeing the ops lead to focus on growth
- Customer complaints noticeably down — most reschedules now happen self-serve, before they become problems
- The leadership team has, for the first time, a real-time view of which routes and which service types actually print money
"I didn't need software that could do everything. I needed software that could do the five things I do every morning, faster than I do them — and then never get in my way." — Operations lead, anonymized