Route-based service businesses: proving recurring revenue to a buyer

What counts as recurring revenue in a route business?#

Recurring revenue in a route business is revenue from customers on a standing service schedule who are billed again without a new sale. A weekly pool stop, a quarterly pest plan, a lawn maintenance route and an HVAC maintenance agreement all qualify, but buyers do not treat them as one category.

Most buyers sort the book into layers. Contracted revenue rests on a signed agreement with a term. Scheduled revenue comes from customers who stay on the route by habit and can stop at any time. Repeat revenue comes from one-time customers who keep coming back, such as an annual drain cleaning. Each layer needs different proof, and a buyer will ask which layer each customer sits in.

The checklist: reports that prove recurrence#

A recurrence package is a short set of reports, each generated from a raw export the buyer can rerun. Polish matters less than repeatability: a buyer's analyst should be able to take your billing export, follow your written definitions and land on the same totals.

• 1Active customer roster: every recurring customer with customer ID, service area, start date, visit frequency, current price and payment method.
• 2Monthly recurring billing by customer: invoice-level totals for each recurring customer across the full history you still hold.
• 3Cohort retention table: customers grouped by the month or quarter they started, showing how many are still billed in each later period.
• 4Cancellation log: date, customer ID, stated reason, and whether the stop was a move, a price objection, a service complaint or a switch to a competitor.
• 5Price change history: every increase by date and customer group, so growth from price is separated from growth in customers.
• 6Agreement register: term, renewal method, cancellation notice, price escalation and assignment language for every written agreement.
• 7Route density summary: stops per route day and the area each route covers, tied to the same customer IDs.
• 8Reconciliation sheet: recurring billing totals matched to the general ledger and to bank deposits for the same periods.

How do you build cohort and churn reports from a billing export?#

Cohort and churn reports come from the most granular billing data you have, usually invoice lines rather than monthly summaries. Jobber, ServiceTitan and Housecall Pro each export invoices and jobs differently, so pull the widest date range your system allows and keep the raw file untouched.

Jobber's help center, for example, describes exporting CSV-format reports by choosing a report, setting the date range and clicking Export Excel Copy. Whatever the system, record the menu path and the date of each export, because a buyer will ask how the numbers were produced.

• 1Key every row to a stable customer ID, never to a name or an address, both of which change.
• 2Set each customer's start date as the date of the first recurring invoice, not the first one-time job.
• 3Write down your churn rule, such as no recurring invoice for a stated number of billing cycles, and apply it the same way to every cohort.
• 4Flag seasonal holds separately, so a pool closed for winter is not counted as lost and then won again.
• 5Merge customers who cancelled and re-signed under a new ID, and note each merge.
• 6Split revenue changes into price, frequency and customer count before you show growth.

Contract terms decide which revenue moves with the deal#

Agreement terms decide whether recurring revenue transfers to a buyer or stays behind. A maintenance agreement that allows assignment to a successor moves cleanly in an asset sale; one that requires customer consent may need a notice campaign before closing.

Build the agreement register from the documents themselves, not from memory. Many route companies carry several generations of terms at once: an old paper form, a website checkout page, terms printed on invoices and a newer e-signed version. Record which version each customer accepted and when.

Red flags that make buyers discount recurring revenue#

Buyers discount recurring revenue when the reports cannot be rebuilt or when the definitions flatter the result. The causes are usually mechanical rather than dishonest, and most can be fixed with a careful cleanup well before a sale.

Owner dependence deserves its own note. If the owner personally handles cancellations, sets prices by phone and knows which customers need special handling, write that knowledge into customer records and an operating manual so a buyer can see that retention does not leave with the seller.

• 1Duplicate customers after a software migration, which inflate the active count.
• 2Price increases masking customer losses, so revenue grows while the route shrinks.
• 3Prepaid annual plans counted as revenue in the month they were billed.
• 4Seasonal suspensions left in the active customer count.
• 5Key relationships held by one technician whose customers might follow them.
• 6Paper agreements that cannot be found for long-tenured customers.

Illustrative: a pool service company proves its routes#

Illustrative: a fictional pool and spa service company runs weekly routes from two yards and bills monthly by card on file. Visits and invoices sit in its field service platform, payments in its accounting system, and cancellations in a spreadsheet the office manager kept by hand.

Ahead of a sale process, the owner exports invoice lines for the full history, merges customers re-entered after a past migration, and marks winter closings as seasonal holds rather than cancellations. The office manager's spreadsheet becomes a cancellation log with standard reasons, matched to customer IDs.

The buyer's analyst rebuilds the cohort table and agreement register from the raw export without needing the owner in the room. Diligence questions move from whether the revenue is real to how dense the routes are and which technicians cover which areas.

How SourceX looks at route service records#

SourceX looks at route service records as operational history first and as a sale exhibit second. Years of scheduled visits with technician notes, water chemistry or treatment readings, missed-stop reasons and cancellation outcomes can be relevant to AI developers studying how recurring field work actually runs.

Any license follows the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Customer names, addresses and payment details are removed in preparation, the company keeps ownership, and nothing is shared during the initial fit check. If a sale is planned, disclose the license terms to the buyer so they become part of diligence rather than a surprise.