Route density is your real margin.
A residential weekly account at $150/month with three other stops on the same street is one number. The same account 14 miles out with no other stops nearby is a completely different number. Most shops don't price this gap, and don't qualify by it. We do.
The economics most shops ignore.
A $150/month weekly residential customer at 30 stops/day route density is gross revenue $1,800/year per labor hour invested. The same customer at 12 stops/day route density (because they're isolated) is closer to $720/year per labor hour. Same customer, half the unit economics.
Yet shops book both, because nobody wants to say no to revenue. The math catches up at year-end when the route is "full" but margin somehow keeps shrinking.
How the AI runs density qualification.
New lead inquiry comes in. Before the booking happens, AI does three things:
Geocode the address against your existing route map. Where does this stop fall? How many existing stops are within 1 mile? Within 3 miles? Same neighborhood, or 20 minutes off-route?
Calculate the route impact. Adding this stop, what does it do to drive time per stop on the affected day? Adds 4 minutes? 22 minutes? AI knows your current route, knows your stops-per-day target, calculates the delta.
Recommend the right response. Three outcomes:
- High-density fit: Standard quote, standard booking, customer thinks they got the routine response.
- Medium-density (route-stretch): AI quotes at a slightly elevated rate that protects unit economics. Customer either accepts the math or self-selects out.
- Low-density (route-killer): AI politely declines, suggests a competitor in their area, and writes the lead's contact info to a "future expansion" list. When you grow into that ZIP later, you have a warm prospect waiting.
Why nobody else does this.
Most generic AI receptionists and booking systems are paid per booking. Their incentive is to book everything. Ours isn't, we're flat monthly. Our incentive is to make your shop profitable so you stay subscribed.
Pool service software like Skimmer and PoolBrain track route data beautifully but don't pre-qualify by it, the customer is already booked by the time the route impact gets calculated. We move the qualification step earlier, before the commitment.
Stop saying yes to route-killer accounts.
In the prototype we'll set up route-density qualification with your real ZIPs and have you watch how it would respond to a few historical low-density customers. The math gets visible.