Building PestRouting: What We Are Working On Right Now
A short, honest update on what we are building right now — route audit logic, simulation, FieldRoutes-aware workflows, and the things we deliberately are not building yet.
Most software vendors share roadmap updates through carefully-curated marketing pages. We would rather just write what we are building, what we are not, and what we have learned that changed our priorities.
The Inside PestRouting category is the channel for that. Periodic, honest, no committee-approved language. The point is to keep the operational thinking visible to the industry, not to manufacture excitement about features we have not shipped yet.
Here is what we are working on right now, what we are deliberately holding off on, and how owners can shape what comes next.
Why we publish roadmap updates in the open
Two reasons.
The first is practical. Pest control owners we talk to have been promised the same set of features by the same set of vendors for years. The promises are easy to make, harder to ship, and almost never accompanied by a clear view of what is being deliberately not built. Open roadmap updates are the way to break that pattern — show the work, name the trade-offs, and let the industry hold us accountable.
The second is strategic. PestRouting is not trying to be the everything-tool. We are trying to be the audit-and-operations layer that sits cleanly alongside FieldRoutes. The roadmap should make that scope visible — not because we cannot do more later, but because the discipline of staying narrow now is what makes the work valuable.
The roadmap principle: What we are building matters less than what we are deliberately not building. The first list grows quickly through enthusiasm. The second list is what keeps the product honest.
Where we are right now
We are roughly one quarter into shipping the production audit framework. The audit takes a pest control operator's FieldRoutes data, runs the structured diagnostic across the five operational layers, and produces a prioritized findings document the owner can act on without any further commitment.
The audit work has been the right starting point. It has produced the pattern recognition that makes everything else we are building useful, and it has surfaced the questions that pest control owners actually need answered — not the questions we expected to find.
The biggest learning has been about the cost of audit-only deliverables. A findings document is valuable, but it is also one step removed from the operational change it implies. The operations team that reads the audit needs tooling to act on it — and that is what the next phase of the build is about.
What is shipping next: route audit logic improvements
The first build priority is making the audit itself more comprehensive and faster to deliver. Three specific work streams are active.
The first is broader pattern coverage — adding diagnostics for symptoms we have seen across audits but did not initially capture in the framework, like exception-protocol entrenchment and tech-consistency drift on recurring accounts.
The second is faster data ingestion — reducing the time from "send us your FieldRoutes export" to "here are the findings" from weeks to days. Most of this work is unglamorous data engineering that pays back in audit throughput.
The third is sharper benchmarking — comparing each audit's findings against the structural patterns we have observed across operations, so the owner gets context for how their numbers compare without us claiming false precision.
What is shipping next: route simulation
The second priority and the one we are putting the most engineering effort into. Route simulation answers the question that audits raise but cannot fully answer: what would the operation look like if the recommendations were implemented?
The simulation works by taking the operation's existing FieldRoutes data, applying the recommended changes (territory cleanup, recurring re-anchoring, dispatch rule enforcement), and modeling the resulting route quality, productivity, and capacity changes over a defined window. The output is a side-by-side view of the current operation and the simulated post-cleanup operation.
According to the U.S. Bureau of Labor Statistics (May 2024 OES data), the financial stakes of operational change in pest control are large enough — fully loaded technician compensation around $30 per hour — that owners deserve a quantified preview before they commit to the disruption. Simulation is how we deliver that preview.
What is shipping next: FieldRoutes-aware workflows
The third priority is the operational layer. Audit findings and simulation outputs are useful but require the operations team to translate them into FieldRoutes configuration changes. That translation work is where most cleanup initiatives stall.
The FieldRoutes-aware workflows close that gap. They take the audit recommendations and the simulated targets, and produce specific configuration changes the operations team can implement directly in FieldRoutes — territory boundary updates, recurring schedule re-anchoring, dispatch rule templates, exception tracking configuration.
This is the layer that turns insight into operational change. The National Pest Management Association's ongoing industry research consistently identifies operational discipline as the lever most correlated with margin and retention in residential pest control. Our job is to make that lever easier to pull, not to add another dashboard nobody reads.
Audit alone
Findings document. Owner reads it. Operations team interprets it. Implementation requires translating recommendations into FieldRoutes configuration. Cleanup stalls in the gap.
Audit + simulation + workflows
Findings document. Quantified preview of post-cleanup operation. Specific FieldRoutes configuration changes ready to apply. Cleanup runs without the implementation gap.
What we are deliberately not building yet
Three things we have decided not to build in the current phase, and why.
1. A FieldRoutes replacement. We are not building an alternative to FieldRoutes. The platform is the operational system of record for most of our target customers, and replacing it would be the wrong fight. PestRouting sits alongside FieldRoutes, not against it.
2. A standalone routing optimizer. Optimization without the upstream operational cleanup produces marginal improvement and customer disappointment. We are not adding an optimization button until the operations underneath are clean enough to make optimization actually work.
3. A self-serve audit product. Audits depend on judgment that takes time to develop. A self-serve version would underdeliver on both the analysis and the recommendations. The audit will be a guided product for the foreseeable future, with the audit framework documented openly so operators can run their own diagnostic if they prefer.
How to influence what comes next
The fastest way to shape the roadmap is to talk to us directly. The audits we run produce the patterns that change our build priorities, and the operators we work with influence which features land first.
Less directly, the questions, objections, and feedback that come through the blog and through industry conversations all feed into the same prioritization process. Fleetio's fleet performance research (2024) and other field-service operational research consistently informs how we frame the audit findings; pest-control-specific feedback consistently informs what we build next.
For the founders' rationale on why we started with audits, the deep dive on why we started with route audits covers the original decision. Our pattern update on what we learned from early audits covers the structural findings that have shaped the roadmap. And the framework breakdown in our route audit scorecard covers the diagnostic itself.
Frequently asked questions
When will route simulation be available to customers?
Active development this quarter, with limited customer access targeted in the following quarter. Full availability depends on the simulation matching audit findings reliably across enough operations to trust the outputs in customer hands.
How does PestRouting integrate with FieldRoutes today?
Today, integration is via FieldRoutes data exports — operators send us their export, we run the audit, and we deliver findings. The next phase will reduce that friction through more direct data flow as the FieldRoutes-aware workflows ship.
Why are you not building a routing optimizer first?
Because optimization on top of unstructured operations produces marginal improvement at best and disappointment at worst. We saw enough vendors fail with that pattern in pest control that we deliberately chose to start with the operational cleanup layer instead. Optimization comes after, not first.
Will PestRouting ever offer a self-serve audit?
Possibly, eventually. The current judgment is that the audit value depends on interpretation that does not translate well to a self-serve format yet. The audit framework itself is documented openly so operators can run their own diagnostic if they prefer — and we may package that into a guided self-serve experience once the patterns are robust enough across operations.
How can I get on the early-access list for new features?
The cleanest path is to engage with us through a route audit. Audit customers get the earliest access to new features because the simulation and workflows are designed against the patterns surfaced by their data. Reach out through the standard discovery channels.
What metrics does PestRouting use to know whether the build is working?
Three: audits delivered per month, findings adoption rate (do customers act on the recommendations), and post-cleanup operational improvement (does the simulation match what actually happens). All three need to be moving in the right direction for us to consider the product strategy validated.
Written by
PestRouting Team
Practical guidance on pest control route optimization, scheduling, and operational efficiency.
Liked this? Get the same analysis on your routes.
30 minutes. We listen first. Then you decide if a real audit makes sense. No pitch, no pressure.