Route optimization results from real pest control operations.
Case studies from pest control companies on FieldRoutes. What each one wanted from the first call, the rules it kept, and how it got from a free audit to a planned month.
Real operations, described by what they run and the path they took. Names, locations and identifying details are left out to protect our customers. Dates, sessions and figures are real, and each figure says how it was found.
Which one sounds like your office?
- Audit
- a past month planned again
- Live
- a coming month planned on real data
- Measured
- after the new routes ran
- Recurring route book · several techniciansCompleted
Same team, same trucks, 49% more production
Early pilotThe goalMore production from the team already on the payroll.The customer asked for- More work done without hiring
- Every real promise to a customer kept
- Proof in ratios, taken before and after
- +49%
- Production per work time
- −23%
- Miles per stop
- Technicians paid on production · one officeCompleted
Full, fair days for a production-paid team
Since Jul 20266 working sessionsThe goalA full, fair day for every technician, every day.The customer asked for- Every technician working every day
- The same technician for a customer, month after month
- Saturdays only for customers who ask
- ±5%
- Production between technicians
- 1 week
- Locked ahead of every plan
- Salaried technicians · more than one officeIn progress
20% less drive time, and every route kept
Since Sep 20263 working sessionsThe goalShorter drives, without cutting a single route.The customer asked for- Mileage down, not the labour bill
- Every existing route kept
- Customer preferences never forced
- −20%
- Drive time
- Minutes
- To plan a month
- Technicians on commission · across state linesIn progress
33% more per route, every preferred technician kept
Since Aug 20262 working sessionsThe goalFuller routes, with every customer kept by their technician.The customer asked for- More production per route, so more pay per route
- Customers kept with the technician of their zip code
- A technician who works only one state kept there
- +33%
- Production per route
- 2 rules
- Added before the next run
Story log
Running work, not finished write-ups.
The latest from the operations behind these case studies, newest first. When a running month has been measured, its figures move onto the case study with their own label.
- Nov 2026Fair days, production payThe first month planned in PestRouting for real goes out to the techniciansNext
- Oct 2026Fair days, production payNovember planned in one session, after October ran as a dry run
- Oct 2026Fair days, production payOnboarding and setup: calendars, skills, a Saturday crew, the coming week locked, write-back tested
- Sep 2026Fair days, production paySigned up after the audit
- Sep 2026Less driving, every route keptThe coming month planned in minutes. All but 3 visits placed, each of the 3 with its reason
- Sep 2026Less driving, every route keptAudit within days of the first call: 20% less drive time, 17% more stops per route
- Aug 2026More per route, on commissionAudit: 33% more production per route, every preferred technician kept
How a new story starts today
From a free audit to your first planned month
- Within days
1.Free audit
One month you have already run, planned again under your rules. Read-only, nothing written back, walked through in a call.
- One or two sessions
2.Goal and rules
You pick what the planner works toward. Technicians, calendars, areas and locked days go in once.
- This month
3.Dry run
The current month runs in PestRouting next to your own planning, so you see it before it counts.
- Next month
4.Live
Planned in minutes, adopted with one click, written to FieldRoutes. Analytics follows what really ran.
But is it actually better?
What the audit finds when it re-plans a month you have already run.
- 15 to 30%
- fewer miles
- per technician route
- 10 to 25%
- less drive time
- per technician per day
- 15 to 40%
- more production
- typically 2 to 4 more stops per route
Verified ranges from real pest control operations. What they are worth to you depends on the slack in your routes today. That is why the audit runs on a month you have already paid for, and sometimes comes back saying your routes are already tight. How we measure every number we publish
Questions about these results
- What results has PestRouting achieved for pest control companies?
- In a completed pilot, PestRouting measured 49% more production per work time and 23% fewer miles per stop with the same team. In audits that kept every customer rule, it found 20% less drive time for a team of salaried technicians and 33% more production per route for a team on commission, with every preferred technician kept. A month that took two to three hours to plan by hand was planned in minutes. Across operations, the ranges PestRouting publishes are 15 to 30% fewer miles, 10 to 25% less drive time and 15 to 40% more production.
- Why does PestRouting not name the operations in these case studies?
- Our customers have not agreed to be named, and we would rather protect them than decorate a page. Each case study describes what the operation runs, what it wanted from the first call, the rules it kept and the path it took. Dates, sessions and figures are real, and each figure is labelled by how it was found.
- What is the difference between an audit, a live month and a measured result?
- An audit plans a month the operation has already run again, under the same rules, and sets it next to what happened. A live month is a coming month planned in PestRouting on the operation’s own data. A measured result takes the same ratios again after the new routes have run.
- Are these results typical?
- The ranges PestRouting publishes from real operations are 15 to 30% fewer miles, 10 to 25% less drive time and 15 to 40% more production. Single results land above or below them. Some audits come back saying the routes are already tight.
- How fast can my own office get from audit to a planned month?
- The audit takes days. Setting up your goal and rules takes one or two working sessions, the current month can run as a dry run, and the month after can be planned in PestRouting for real.
The next story could be your own month.
30-minute intro call. We connect to FieldRoutes read-only, plan one real month of yours again under your rules and the goal you name, and walk you through the result. Nothing is written back.
Some audits come back saying your routes are already tight. You will hear that too.
PestRouting Blog
FieldRoutes tips, route optimization guides, scheduling playbooks, and case studies built for pest control teams that want denser routes and stronger margins.

Pest Control Peak Season: How to Prepare Your Routes Before the Rush
The rush comes early in some years and stays late in others. Settle these in the quiet months: capacity in hours, seasonal calendars, wider buffers and who waits when a week is full.

Route Optimization ROI for Pest Control: A Worked Example
An 8-technician branch, BLS wages, the IRS mileage rate and the published savings bands, worked through line by line, plus the three ways a saved hour actually turns into money.

How to Build Weekly Route Stability in Pest Control
Route stability means the same customers see the same technician on a predictable day, week after week. How to build it in FieldRoutes, cover vacations without breaking it, and measure it.
Get Your Free Route Audit
A 30-minute intro call, a written report on what your routes are leaving on the table, and zero pressure to sign anything. We only follow up if you ask.
Book Your Free Analysis
Free analysis with no obligation
We'll analyze your current routes and show you the savings potential.
First call within 24 to 48 hours
Full analysis and written report typically ready within about a week.
Real people, start to finish
The people who build PestRouting run your audit and walk you through the results.
Risk-Free Opportunity
See exactly how much you could save before spending a dime.