At 6:40 on a Tuesday morning, a technician is standing at the back door of a restaurant that closed at midnight and reopens at eleven. He has about ninety minutes. In that window he has to walk the exterior stations, work the dry storage and dish areas, check the interior monitors behind the line, note the gap under the receiving door that nobody has fixed since March, apply what the program calls for, and leave behind a record the general manager can hand to a district manager or a third-party auditor without flinching.
That last item is the account. Everything else is the work.
This is the structural difference between commercial and residential pest control, and it is the thing that trips up route operators who take on their first restaurant or warehouse expecting a bigger version of a house call. As of September 2026 the commercial side of the trade is still won and lost on the per-site service record — the history of what was applied, where, when, by whom, and what was found. A residential customer renews because they stopped seeing ants. A commercial customer renews because the binder, physical or digital, is complete.
Commercial is a different business wearing the same uniform
Start with who is buying. On a residential route the person paying is the person experiencing the problem. On a commercial account the person signing is usually a general manager, a facilities lead, or a property manager who is themselves accountable to somebody else — a corporate office, a landlord, an insurer, an auditor. They are not buying the absence of pests so much as the ability to prove the site is under an active, documented program.
That changes four things at once:
- The deliverable includes the record. A visit with no legible record is, from the customer's side, a visit that did not happen.
- The site is complex. A 90,000-square-foot distribution center is not one job; it is dozens of monitored points across zones that each behave differently.
- The money moves slower and larger. Net-30 terms, a purchase order number, a monthly statement, and an accounts payable department instead of a card at the door.
- The relationship survives staff turnover. The GM who signed will be gone in eighteen months. The record is what carries the account across that handoff.
Operators who run pest control work on both sides of that line quickly discover the systems overlap less than expected. Recurring residential service is fundamentally a scheduling and route-density problem. Commercial service is fundamentally a records problem with a scheduling constraint attached.
The per-site service record is the account
The single most useful discipline in commercial work is treating each physical location as its own customer record — its own address, contacts, access notes, device map, product history, and visit log — even when twelve of them are owned by one company.
A complete visit entry has seven parts, and each one exists because someone eventually asks for it:
- Site and areas covered. Not just the address — which zones, rooms, or buildings were actually walked this visit.
- Devices checked. Every station or monitor by its number, with condition and activity noted individually.
- Products applied. What, how much, and precisely where. Tracking chemical and product usage per treatment at the site level is what lets you answer a question about a specific application eight months later without guessing.
- Conditions observed. The unsealed door sweep, the standing water at the dock, the cardboard stacked against the wall. This is the section that protects you when activity spikes for reasons outside your control.
- Recommendations to the customer. Written, dated, and repeated on the next visit if unaddressed.
- Time on site. Arrival and departure, which quietly becomes the input to your contract pricing later.
- Technician. Who did the work, so questions route to the person who was actually standing there.
The reason to capture all seven on site, in the moment, is that the alternative is reconstruction. A tech writing up four accounts at the end of a long day produces entries that are vague where they most need to be specific, and vagueness is exactly what a reviewing manager notices. The IRS's recordkeeping guidance makes the general point that electronic records satisfy the same requirements as paper ones — and in practice they are dramatically easier to retrieve, which is the property that matters when a customer asks what you did on a date four months back.
Mapping devices across a site that takes an hour to walk
Large sites need a device map before they need anything else. Every station, trap, and monitor gets a permanent number tied to a fixed location description — exterior station 14, northeast corner of the dock apron — and those numbers get grouped into zones that match how the building is actually laid out and walked.
Three things fall out of doing this properly:
A substitute technician can run the site. This is the practical payoff and it arrives the first time your regular tech is out. Numbered devices in a stable sequence turn tribal knowledge into a route anyone on the crew can follow.
Activity becomes a trend instead of an impression. Repeated hits at stations 11 through 14 over three visits is a finding you can bring to the customer with a specific recommendation. "We've been seeing some activity out back" is not.
Coverage is verifiable. If the map says forty-two devices and the visit recorded thirty-nine, that gap is visible before the customer finds it.
Attach the map to the property record itself, not to a technician's notebook or phone. Commercial sites change — a zone gets added, a building comes online, stations get relocated during a remodel — and the map has to be a living part of the account that anyone can update.
The visit where you found nothing
New commercial techs consistently under-record clean visits. Nothing happened, so there is nothing to write. It is the exact opposite: the clean visit is the product.
A run of complete entries showing devices checked, areas covered, and no activity observed is the documentary evidence that the program is working — and it is what a manager points to when their district office asks. A blank entry, or a missing month, reads as either a skipped visit or sloppy work, and it is one of the most common reasons a manager starts quietly taking bids.
Make the no-activity visit as structured as the eventful one. Same device round, same areas list, same conditions section, and an explicit note that no activity was observed rather than empty fields. When the account comes up for renewal, an unbroken twelve-month history does more of the selling than anything you can say in the meeting. That is the same logic behind tracking termite and warranty renewals properly on the residential side — the record, not the memory, is what carries a long-cycle commitment forward.
Many sites, one bill
Multi-site accounts are where residential-shaped software tends to break. A property management company with eleven buildings, or a restaurant group with six locations, needs two things that pull in opposite directions: a service history specific to each building, and a single predictable invoice.
Set it up as a parent billing entity with child site records underneath. Each site keeps its own address, contacts, access instructions, device map, schedule, and visit history. Charges accumulate against the sites and roll up into one monthly statement to accounts payable, with each location itemized so the customer can allocate costs internally.
That structure is what makes on-account billing workable at scale. The site manager gets a record about their building; the corporate controller gets one invoice with a purchase order number on it. Split those roles onto separate invoices per site and you create eleven chances a month for something to go unapproved.
Two operational details matter more than they sound:
- The purchase order number belongs on the record, not in someone's memory. Many corporate customers will not pay an invoice that lacks one, and chasing it after the fact is the most avoidable delay in the entire cycle.
- The statement should arrive on the same day every month. Predictability is what gets you into an AP run rather than a pile. Setting the whole thing up as recurring invoices removes the human step that otherwise slips during a busy week.
Scheduling around their operation
Commercial service happens on the customer's clock. A restaurant wants you between close and prep. A warehouse wants you outside its receiving window. A food processing plant may only permit certain work during a sanitation shift. A multi-family property needs notice periods for interior units.
Those constraints belong on the site record as hard scheduling attributes — service window, access method, who to call at the door, escort required or not, blackout dates — not in a dispatcher's head. When they live on the record, recurring treatment scheduling can generate the year's visits in the right windows automatically instead of being reassembled monthly.
The escort requirement is the one operators underestimate. A site where a manager must walk with you can easily consume twenty minutes before any work starts, and if that manager is busy at your arrival time, the whole visit slides. Sites like that are more expensive to serve than their square footage suggests, which is precisely the sort of thing that should show up in pricing rather than in a technician's frustration.
Pricing the contract against the time it really takes
Here is the comparison that decides whether commercial work makes you money:
| Residential route stop | Single-site commercial | Multi-site commercial account | |
|---|---|---|---|
| Typical time on site | 15-30 minutes | 45-120 minutes | Varies per site; often several visits per month across locations |
| Non-service time per visit | Drive between nearby stops | Check-in, escort, write-up | Check-in and write-up at every site, plus account-level review |
| Record required | Brief visit note | Full device round, products, conditions, recommendations | The same per site, plus a rollup the customer can review as one program |
| Billing | Card or link at the visit | Monthly invoice, sometimes net-30 | One statement to a billing entity, itemized by site, purchase order required |
| Cash timing | Same day | 15-45 days | 30-60 days, dependent on the AP cycle |
| Revenue per hour of total time | High if the route is dense | Moderate; drops sharply if escort time is unpriced | Highest ceiling, but only when non-service time is priced in |
| What drives renewal | No visible pests | Consistent, complete site record | Complete records across every site plus a reliable single invoice |
The failure mode is pricing a commercial contract on the treatment and discovering later that the account eats four hours a month you never counted. Price it on total annual hours consumed: drive, check-in and escort, the device round, the write-up, unscheduled callbacks between visits, and the annual review. Divide the contract value by that number and compare it against what the same hours earn on a dense residential route — the honest version of the route density and profitability math.
Do that and a few things become clear fast. Callback-heavy accounts are often underpriced by a wide margin, and a single site that generates monthly emergency visits can be worth less per hour than a residential day. Sites clustered geographically are worth more than their revenue suggests because the drive amortizes. And an account whose manager insists on a full escort every visit deserves either a higher price or an access arrangement that removes the escort.
Slow payment is the other margin killer. Net-30 that behaves like net-55 is a real cost, and per Intuit's small-business cash-flow research, late and unpaid invoices are among the most common cash-flow problems owners report. Watch days-to-pay per account the same way you watch profitability, and handle the drift early rather than letting it compound into an awkward collections conversation with a customer you want to keep.
Give the customer their own record
The last piece is access. A commercial customer who can pull up their own site history — visits, findings, recommendations, invoices — stops calling your office to ask for copies, and stops worrying about whether anyone came in July. A customer portal turns your documentation from something you produce on demand into something the customer can self-serve, which is both less work for you and a genuine reason to stay.
It also reframes the annual review. Instead of a conversation about price, you are walking through twelve months of complete records, the conditions you flagged and whether they were addressed, and the trend at specific stations. Salesforce's State of Service research consistently finds that connected, real-time tools separate high-performing service organizations from the rest — and in commercial pest control the mechanism is not mysterious. The operator whose records are instantly retrievable looks like the professional in the room.
The bottom line
Commercial accounts are not bigger residential jobs. They are records businesses with a service component, sold to a buyer who has to justify the line item to somebody upstairs. Build the account structure first: every physical site as its own record with its own device map and history, rolled up to one billing entity that gets one predictable monthly statement.
Then document everything, especially the visits where you found nothing. Then price the contract against the hours the account genuinely consumes, escort time and callbacks included, rather than against the minutes spent applying product. The operators who hold commercial work for a decade are not usually the cheapest bid. They are the ones who can produce any visit from any site in about ten seconds.
Related reading: Recurring treatment scheduling for pest control · Chemical and product usage tracking · On-account billing for service businesses. For a complete machine-readable feature and pricing reference, see our LLM reference page.