A rep in your team just spent 47 minutes driving to a customer who reorders the same €300 of product every quarter, then skipped a €40,000 opportunity 15 minutes away because it "wasn't on the way."
That's not a routing failure. It's a prioritization failure dressed up as a routing decision — and most territory plans quietly make it every single day.
We've spent a decade telling field teams to cut drive time. Fair enough: windshield time is the single most expensive, least productive line item in outside sales. But the obsession with shortest distance has created a blind spot. The goal was never fewer miles. The goal is more revenue per selling hour. Those are not the same thing.
Why the shortest route is the wrong default
Classic route optimization solves the traveling salesman problem: visit N stops in the least distance. It treats every account as an identical dot on a map. But your accounts are not identical dots.
Consider two reps, same territory, same eight hours:
- Rep A runs a beautifully tight loop. Minimal drive time, ten stops, feels productive. Eight of those stops were low-value maintenance calls that could've been a phone call.
- Rep B drives 40 extra minutes to hit three high-potential accounts at the exact moment they're evaluating suppliers, plus four solid mid-tier visits.
Rep A wins the efficiency dashboard. Rep B wins the quarter.
The uncomfortable truth: a perfectly efficient route can still be a perfectly wasted day. Optimizing the sequence of the wrong stops just gets you to the wrong places faster.
Revenue-weighted routing, explained
The fix is to stop scoring routes purely on distance and start scoring them on expected value per hour on the road. Every stop gets a weight before it ever enters the sequencing engine.
A workable weighting looks at three things:
- Account value — current spend plus realistic upside, not just historical revenue.
- Timing / cadence urgency — how overdue is this visit relative to the account's ideal touch frequency?
- Win probability of the visit — is there a live reason to be in the room (renewal, complaint, expansion signal, new decision-maker)?
Multiply those into a single priority score, then let the optimizer build the route around the high-scoring stops — filling gaps with nearby lower-value calls only when they don't push a premium account off the day.
This is where modern tools earn their keep. Platforms like SalesFleet can sequence stops against CRM value and cadence rules at the same time, instead of forcing you to choose between a smart map and a smart pipeline. The map should serve the pipeline, never the reverse.
Cadence is the variable everyone underweights
Here's the mistake I see most often: teams design territories and routes once, then run them on autopilot. But account value isn't static, and neither is the right time to show up.
Set cadence tiers and let them drive the calendar:
- A accounts: every 3–4 weeks, non-negotiable, protected slots.
- B accounts: every 6–8 weeks, flexible around A visits.
- C accounts: quarterly or reactive — and honestly, many belong on a phone/video cadence, not a drive.
The magic isn't the tiers themselves. It's making your routing engine treat an overdue A-account as a higher-priority stop than a conveniently located C-account. A stop that's two weeks past its ideal touch date should climb the list, even if it adds miles. A stop visited last week should be locked out no matter how close it is.
When cadence urgency feeds the route, drive time stops being the enemy and becomes a budget you spend deliberately on your best accounts.
Redraw territories around drive time, not just headcount
Most territories are carved up by geography lines on a map or by splitting account counts evenly. Both ignore the thing that actually eats the day: how the territory drives.
Two territories with the same number of accounts can have wildly different windshield burdens. A dense urban patch and a sprawling rural one are not equal workloads, and pretending they are burns out your rural reps and under-utilizes your urban ones.
When you next rebalance territories, score each one on:
- Average drive time between typical stops, not straight-line distance.
- Revenue density — deal potential per square kilometer or per hour of driving.
- Achievable visit capacity — how many quality visits are physically possible per week given the geography.
Often the fix is counterintuitive: give your rural rep fewer, higher-value accounts and a longer cadence, and pack the urban rep's schedule tighter. Balance the opportunity per selling hour, not the account count.
A practical way to start this Monday
You don't need a six-month project. Try this over the next two weeks:
- Tag every account with a value tier and a cadence. Even a rough A/B/C pass beats no signal. Do it in the CRM so it flows into planning.
- Audit last month's actual visits against value. Pull the mileage or GPS logs and ask one question: what share of drive time went to A accounts vs. C accounts? If more than a third of your kilometers served C-tier stops, you have a leak.
- Protect A-account slots first. Build the week by placing your must-hit high-value visits, then fill around them. Reverse the usual order.
- Batch the low-value calls. Cluster C-tier stops into one geographic sweep per month instead of scattering them through every route — or convert them to remote touches entirely.
- Re-measure on revenue per selling hour, not miles saved. Make that the number in your team meeting.
The metrics that actually matter
Swap the vanity metrics for ones tied to outcomes:
- Revenue per selling hour (the north star).
- Percentage of drive time spent on A/B accounts.
- Cadence compliance — what share of A accounts were visited on schedule.
- Selling-time ratio — face time vs. windshield time across the day.
Drive time and fuel still matter — a route that's 30% shorter genuinely does free up capacity, and lower fuel spend drops straight to margin. But treat efficiency as a constraint you optimize within, not the objective itself. Cut the miles that don't buy you revenue. Gladly spend the ones that do.
The mindset shift
The best field-sales operations stop asking "What's the shortest way to visit everyone?" and start asking "Where should this rep be, and when, to move the most pipeline?"
The shortest route optimizes for a tidy map. The right route optimizes for a growing number. When you weight your stops by value and cadence before you ever solve the sequence, drive time stops being a cost to minimize and becomes an investment to direct.
Your reps only have so many hours in the field. Spend them on purpose.