Route density changes what a cancellation costs

A plan price is not a margin

Two accounts can carry identical plan prices, identical intervals and identical service scopes and still be worth different amounts to the business that serves them. The difference is geography. A recurring visit costs technician time on the property plus the travel required to get there, and travel is set by where that address sits in a sequence of other stops. Density - how tightly serviceable addresses cluster on the same cycle - is therefore a revenue variable that appears nowhere on the plan record. The pest control revenue architecture holds price in one system and the cost of delivering that price in another, and nothing in the ordinary monthly reporting cycle requires the two to be reconciled.

What a cancellation removes

When an account cancels, the retention report performs one subtraction: a plan value leaves the recurring base. The routing module records something else. A stop disappears from a sequence, the addresses either side of it are now further apart, and travel rises as a share of every visit that remains on that day. Where enough of a sequence goes, the route day stops filling a technician's shift, and the fixed cost of that shift is carried by fewer paying stops. None of that is a line in the churn report, and none of it is visible in a plan-value subtraction. Facts that change at a cancellation and are absent from the churn report:

• Stops actually served on the affected route day, before and after the loss.
• Sequence distance between the remaining stops, and the travel time the mobile application recorded rather than the time the plan assumed.
• Whether the route day still fills a technician shift, or now runs short against the hours it is staffed for.
• Whether the accounts left on that day still share an interval, or whether the day has become a mix that cannot be cycled cleanly.
• Whether the cancelled address is cheap to resell, because it neighbors a stop already being driven, or expensive, because it was an outlier.

Acquisition inherits the same variable

Canvassing, neighbor offers and saturation mail on already-served streets are density instruments before they are anything else: each selects addresses by where they sit relative to a sequence a technician already drives. An address next door to an existing stop adds little travel to a sequence that is already being driven, while an isolated one adds a leg of its own - at the same sold price. The channels themselves do not accept this as an input. Google enumerates the categories eligible for Local Services Ads and "Pest control services" appears among them ^[SRC-08], but eligibility and targeting on a channel like that are expressed in terms the platform defines, not in terms of which route day an address would land on. Route geometry lives inside the routing module, so density-aware targeting has to be assembled on the operator's side and pushed outward as an audience or a mail list, never pulled from the ad platform.

Instrumenting density without inventing a benchmark

1. Pick route days that lost accounts in a trailing period and pull the route sheet for each of those days before and after the loss.
2. Record stops served, sequence order, and the arrival and departure timestamps the technician mobile application captured, rather than the planned durations.
3. Group the cancellations themselves by route day and service area instead of by month, so the loss is expressed in the geometry it happened in.
4. Compare the interval mix on the affected days, since a day holding more than one interval cycles differently from a uniform one.
5. Check reinstatements and new sales landing on the same days, which may have refilled the sequence before anyone looked at it.

Even a clean version of this reconciliation stops short of causation. Route boundaries are redrawn for reasons that have nothing to do with retention, technicians are reassigned, seasonal programs add and remove stops on their own calendar, and a route that thinned may have been thinned deliberately. What the exercise does establish is that a cancellation has two prices - the plan value, and the delivery-cost change on everything that remains - and that the second one is currently unmeasured. That is a reporting gap rather than a verdict about any route.

Which system holds which answer

The measurement boundary around geographic targeting

Where density-aware acquisition is built as audience work - mail to a served street, retargeting inside a service area, lookalikes built from the active base - two conditions bound what the campaign reporting can say. Browser-level measurement is not static: Google has stated that Chrome will maintain its current approach to offering users third-party cookie choice, while a list of Privacy Sandbox technologies including the Attribution Reporting API, Protected Audience and Topics is being retired ^[SRC-16]. And where users deny consent for storage, consent-aware tags send measurements without cookies, and Google products use those pings to model metrics ^[SRC-18]. Neither fact prevents density-aware targeting. Both mean the campaign-side numbers describing it are partly modelled, while the route sheet and the appointment table are not.

Where this sits

Route economics is the second half of a retention question whose first half is billing. What a failed charge does to a stop is covered in a failed payment is a routing event, and the full mechanic set - non-autopay cohorts, skipped stops, agreement expiry, duplicate field-sold accounts - is mapped on the pest control industry page. If you want the outside-in read first, the Revenue Leak Scan documents what public signals suggest and marks everything requiring your own exports as exactly that.