Stop Optimizing for Miles: Route Your Reps by Revenue Per Hour

Here's a number that should bother you: for a typical outside-sales rep, only 35–40% of the workday is actually spent in front of customers. The rest evaporates into driving, parking, waiting, and re-planning on the fly. That's an illustrative figure, not a lab result — but run the math on your own team and you'll land somewhere uncomfortably close.

Now here's the part most managers get wrong: they try to fix this by minimizing miles. They buy a route optimizer, it draws the shortest loop between eight stops, everyone feels efficient, and revenue doesn't move.

Shortest isn't the goal. Revenue per selling hour is the goal. Let me show you the difference.

The shortest route is often the least profitable

A distance-minimizing algorithm treats every stop as equal weight. Visit A, B, C, D — just don't backtrack. Tidy on a map. Terrible for the P&L.

Because your accounts are not equal. A 45-minute detour to see a €120k renewal that's wobbling is worth ten perfectly-sequenced drop-ins on accounts that buy a case of product a quarter. The classic optimizer can't see that. It's colour-blind to value.

So the first shift is philosophical: you're not routing locations, you're routing opportunities.

Practically, that means every account needs a weight before it ever hits a map:

• Revenue tier — actual or realistic potential, not vanity size
• Cadence requirement — how often this account genuinely needs a face
• Urgency signals — an open quote, a churn risk, a competitor sniffing around
• Conversion probability — is this a visit that moves money, or a courtesy call?

Once stops carry weight, "the best route" changes completely. It stops being the tightest loop and becomes the day that produces the most weighted contact per hour on the road.

Run a windshield-time audit first

Before you touch cadence or territory, measure the leak. You can't improve what you're guessing about.

For two weeks, capture three things per rep, per day:

1. Time in front of customers (start of meeting to end)
2. Time driving (door to door)
3. Number of productive stops (a real conversation, not a drop-and-go)

Then compute one brutal metric: selling hours ÷ total working hours. Most teams are shocked. I've seen managers assume 60% and discover 33%.

Watch for these patterns in the data:

• The starburst rep — lives central, radiates out to a far account, comes back, goes out again. Pure waste.
• The Friday cliff — great Monday-Thursday density, then Friday is one meeting 90 minutes away.
• The loyalty loop — the same friendly, low-value accounts visited weekly because the rep likes them.

That last one is the quiet killer. Cadence should follow value, not comfort.

Redesign cadence around value, not habit

Most visit rhythms are inherited, not designed. "We always see them monthly." Says who? Based on what?

Build a simple cadence matrix. Two axes: account value and relationship risk or momentum. Four boxes:

• High value / high momentum — frequent, planned, agenda-driven visits. Protect these slots first.
• High value / stable — regular but lighter touch; a call can replace a drive.
• Low value / high momentum — a genuine growth bet; visit while it's hot, then reassess.
• Low value / stable — the danger zone. These are eating your windshield time. Move most to phone, email, or a quarterly swing.

The uncomfortable truth: cutting drive time is mostly about deciding who not to visit in person. The route math is downstream of that decision.

A useful rule of thumb — treat it as a starting point, not gospel: if an account can't justify the fully-loaded cost of a visit (rep time + drive time + fuel + opportunity cost of the stop you didn't make), it doesn't get a windshield visit by default.

Fix territory design before you fix routes

You cannot route your way out of a badly drawn territory. If a rep's patch is a 300km smear with three clusters and a lonely outlier, no algorithm saves them.

Good territory design balances three things at once, which is exactly why humans do it badly and software does it well:

• Workload — total required visits and hours, not just account count
• Value — even revenue potential so comp stays fair
• Geography — compact, drivable clusters with sane travel between them

The outlier problem

Every territory has orphan accounts — one big customer stranded 90 minutes from everyone else. Options that actually work:

• Batch them. Never visit an outlier alone. Pair the trip with prospecting or a second nearby account, even a small one.
• Trade them. If a neighbouring rep drives past that account weekly, reassign it and rebalance value with a swap.
• Downgrade the channel. If it's high-value but geographically brutal, a hybrid of quarterly visits plus monthly video may beat monthly drives.

Where the software earns its keep

Here's my opinion, stated plainly: manual route planning in a spreadsheet is a false economy. A rep spending 30 minutes each evening replanning tomorrow is losing 2.5 hours a week — over two full working weeks a year — to a task a computer does in seconds and does better.

The real value of a modern planner isn't the pretty map. It's three things working together:

• Weighted optimization — sequencing stops by value and urgency, not just proximity
• Cadence enforcement — flagging when a high-value account is overdue and when a low-value one is being over-visited
• Live re-routing — when a meeting cancels at 9am, instantly rebuilding the day around the best remaining opportunity instead of the rep defaulting to "drive home"

This is exactly the seam SalesFleet is built for — route optimization and cadence living inside the CRM, so the plan reflects the pipeline, not a separate map that's out of date by lunch. When the tour planner knows which deals are open and which accounts are at risk, "efficient" finally means profitable, not just short.

The 90-day rollout that actually sticks

Don't boil the ocean. Sequence it:

1. Weeks 1–2: Run the windshield-time audit. Get a real baseline number.
2. Weeks 3–4: Tier and weight every account. Build the cadence matrix.
3. Weeks 5–6: Redesign territories around clusters and balanced workload. Handle outliers deliberately.
4. Weeks 7–12: Turn on weighted routing, then coach to the new numbers weekly.

Track one headline metric throughout: revenue per selling hour. Not miles saved, not fuel — those are nice side effects and they'll improve on their own. The number that tells you it's working is more money produced per hour a rep is actually with a customer.

The bottom line

Cutting drive time and fuel is a worthy goal, but it's the symptom you fix, not the disease you diagnose. Reps waste windshield time because their territories are lumpy, their cadence is habitual, and their routes are optimized for distance instead of dollars.

Fix the weighting, fix the cadence, fix the territory — and the shorter routes, lower fuel bills, and happier reps arrive as a bonus. Optimize for revenue per hour, and everything else follows.