The context
The client is a multi-crew landscaping operator running residential and commercial routes across a regional footprint. Founder-led, growing fast, and quietly losing margin to a stack of half-fitting tools.
The problem
Lead-to-cash was strung together across:
- A scheduling spreadsheet shared between dispatchers
- A separate CRM the office team rarely opened
- A texting thread per crew lead
- An accounting tool with manual invoice triggers
- A receipts folder somebody screenshot-ed once a month
The cost of that wasn't a single line item — it was the rounding errors in every step. Forgotten add-ons. Late invoices. Slow payment cycles. A lot of office time recreating what crews already knew.
What we did
We ran a two-week operations audit, watched a full week of dispatch and a full week of office close-out, and quantified where the leaks actually were. Then we configured Opsvara around the way this team already wins:
- Route-aware dispatch with drag-and-drop crew assignment
- A single customer record that carries leads, estimates, jobs, and invoices
- Crew-side mobile flow that closes jobs on site (notes, photos, sign-off)
- Automatic invoicing on job close, with weekly batch options for commercial
- A leadership dashboard with margin per route and per crew
We trained dispatchers, crew leads, and office leadership in their own language, with documentation written for the way the business actually runs.
The outcome
- Five tools replaced by a single platform the team prefers
- Invoicing lag dropped by ~80%, with most jobs invoiced the same day they close
- 20+ hours of office time freed every week, redirected to upsell and retention
- A leadership team that finally has a real-time view of crew-level margin
What we shipped beyond the rollout
Per their request, we built a custom add-on inside Opsvara to handle their specific commercial pricing model — a feature that would have been a year-long backlog item with a generic vendor.
"We thought we needed five different tools to glue our business together. Turns out we needed one — and someone willing to actually shape it around how we work." — Operations lead, anonymized