Published by
Throne of Profit EditorialReviewed by
William Hassell
Founder & Chief Editor, Throne of Profit
Ask two pest control owners how many stops a tech should run in a day and you'll get two very different answers — one says fourteen, the other says nine, and both are sure they're right. The truth is that the number itself isn't the point. A stop count that looks great on a spreadsheet can quietly mean rushed treatments, skipped inspections, and callbacks that eat the very revenue the extra stops were supposed to earn. The right daily target isn't the most stops a tech can physically reach — it's the most stops they can complete at full quality without cutting corners.
Most owners never set that number deliberately. It drifts. A busy season pushes routes fuller, nobody pulls them back, and "normal" slowly becomes whatever the schedule happened to hold last July. Meanwhile the tech who's overloaded starts shaving minutes off each stop, and the one who's underloaded costs you a full salary for two-thirds of a day's work.
ONE TECH'S DAY
too few ░░░░▇▇▇▇░░░░ idle time, salary burns, low output
right ▇▇▇▇▇▇▇▇░░░░ full quality, sustainable pace
too many ▇▇▇▇▇▇▇▇▇▇▇▇ rushed work → callbacks → hidden cost
└─ throughput ceiling is quality, not hoursOwner symptoms
You have no target stop count per tech — the schedule just fills up until the day is full.
Callbacks and re-treats climb during busy stretches, then quietly fade when routes thin out.
One tech clears fourteen stops and another struggles with nine, and you don't know which pace is right.
Why this happens
Stops-per-day drifts because nobody owns the number. Route density gets attention — how tight the geography is — but the individual tech's throughput usually doesn't. Owners assume a full day equals a productive day, so they keep loading stops until the tech runs out of daylight. The problem is that different jobs take different time: a quick residential re-service and a full commercial inspection aren't interchangeable units, but a raw stop count treats them as if they are. Without a deliberate target that accounts for job type and quality, the schedule optimizes for looking full rather than for finishing well.
Common mistakes
Setting no target at all, so the pace is whatever the calendar happened to fill.
Counting stops as equal units, ignoring that a commercial account eats three residentials' worth of time.
Chasing the highest number, treating maximum stops as the goal instead of maximum quality-completed stops.
Never revisiting the target by season, so a summer pace bleeds into a slow winter and vice versa.
Judging techs by raw count without looking at callbacks, which rewards the corner-cutter and punishes the thorough tech.
Business consequences
An unmanaged stop target costs money at both ends. Overload a tech and the treatments get rushed — missed harborage, skipped perimeter, a hurried note — and those show up weeks later as callbacks, re-treats, and the occasional lost account, each one wiping out the margin the extra stop earned. Underload a tech and you're paying a full day's wage for two-thirds of a day's production. The owner who sets a deliberate target lands in the middle: techs run a full, sustainable day, the work holds up, callbacks stay low, and capacity planning finally rests on a real number instead of a guess.
How experienced operators think about it
They treat the daily stop count as a throughput ceiling set by quality, not a quota to maximize. The mental question isn't "how many stops can this tech physically reach?" — it's "how many stops can this tech complete to standard, day after day, without burning out?" They weight stops by job type rather than counting them flat, so a route packed with commercial accounts carries fewer stops than one full of quick residentials. And they watch callbacks as the honest signal: if the count goes up and callbacks go up with it, the target was set too high, no matter how good the day looked on paper.
Practical actions
Set a target range, not a single number — for example, a residential-heavy day might aim for a band of stops, adjusted down for commercial-heavy routes.
Weight stops by job type. Give inspections and large accounts a heavier "time value" so the count reflects real work, not just entries on a schedule.
Pair the count with a quality signal. Track callbacks and re-treats per tech alongside stops, so throughput and quality are read together, never separately.
Adjust the target by season. Set a fuller pace for peak months and a leaner one for the slow stretch, rather than letting one number rule the whole year.
Review outliers, don't just rank them. When a tech runs high or low, ask why before you act — geography, job mix, and skill all move the number.
Questions every owner should ask
Do I have an actual target stops-per-day, or does the schedule just fill until it's full?
When I look at my fastest tech, is the work holding up — or am I rewarding speed that comes back as callbacks?
Does my stop count account for the difference between a five-minute re-service and a full commercial inspection?
Frequently asked questions
Isn't more stops per day always better for revenue?
Only up to the point where quality holds. Past that ceiling, each extra stop tends to cost you more than it earns — a rushed treatment becomes a callback, and a callback is a second trip with no new revenue plus a customer who now trusts you less. The goal isn't the highest raw count; it's the highest number of stops completed to standard. A slightly lower target that eliminates re-treats often nets more than a packed schedule that generates them.
How is this different from route density?
Route density is about the geography — how close your stops are and how little windshield time sits between them. Stops-per-day is about the individual tech's throughput and pacing: how much work one person can complete well in a day, regardless of how tight the map is. Tight routes help you hit a stop target, but they don't set it. You can have dense routes and still overload a tech, or loose routes and still pace a tech sustainably. They're related levers, not the same one.
Related articles
Running a Profitable Pest Control Company — the pillar.
Surviving the Winter Slowdown When Summer Pests Pay the Bills — pacing capacity across the season.
Stop Guessing at Chemical Costs: Tracking Product Use Per Job — another per-job number worth managing.
Why Jobs Take Longer Than You Quoted — the general time problem.
Where Time Leaks on a Typical Job — where the hours actually go.
Every business has more decisions than time
Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.
Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.