Every outside sales organisation has one cost that never appears on a P&L as its own line: the hours reps spend driving between stops. It is paid for in salary, and it produces nothing. Reducing it is the cheapest available increase in selling capacity, because it does not require hiring, better closing, or more leads.
The trap is that "route optimisation" sounds like a dispatch problem. Sales is not delivery. A courier's stops are fixed and interchangeable; a rep's stops are chosen, and the choice is a judgment about which relationships are worth time this week. A method that ignores that gets rejected by reps, correctly.
Start by measuring, not optimising
Before changing anything, find out where the time actually goes for one typical week. Three numbers are enough:
- Stops per day. Completed visits, not attempts.
- Drive time per day. Wheels moving, door to door.
- Face time per stop. Minutes actually in front of the customer.
Most teams that have never looked are surprised by the ratio. If drive time is larger than face time, routing is the highest-leverage fix available and nothing else you do to the sales process will matter as much.
Getting these numbers without turning it into a paperwork exercise is exactly what geofence check-ins are for: arrival and departure get recorded automatically when the rep enters and leaves a customer's location, so the measurement costs the rep nothing.
Cluster the territory before you sequence the day
The common mistake is optimising the order of stops that should never have been on the same day. Sequencing is a small win; clustering is a large one.
Divide the territory into geographic zones — four or five for a typical metro patch — and assign each zone a day. Monday is the north zone, Tuesday the east, and so on. Accounts get visited on their zone's day unless there is a reason to override.
This does several useful things at once:
- Drive legs get shorter because every stop is already near the last one.
- Scheduling gets easier, because "I'm in your area Thursday" is a true and persuasive sentence.
- Coverage gaps become visible — if a zone keeps getting skipped, that is now obvious rather than hidden in a list.
- Reps build route knowledge: parking, receiving hours, which door to use.
Zones need rebalancing when accounts grow unevenly. Once a quarter is usually enough.
Sequence around fixed points and traffic
Within a day, work outward from the constraints rather than trying to solve the whole thing at once:
- Place appointments first. Anything with a committed time anchors the day; everything else fits around it.
- Respect the customer's clock. Receiving windows, shift changes, and lunch rushes decide when a stop is even possible. A perfectly short route that arrives during the lunch rush is a wasted trip.
- Drive against the flow. Start at the far end of the zone in the morning and work back toward home. Outbound against inbound commuter traffic, and the last leg of the day is the shortest.
- Fill gaps with nearby prospects. A cancellation is thirty minutes of found time. It is only usable if the rep can see, on a map, who else is within five minutes right now.
Leave room for judgment
A route plan that cannot be overridden will be ignored. The largest account in the territory asking for a Friday visit outranks the routing model, always. The plan's job is to make the default sensible so that deviations are deliberate and rare, not to remove the decision.
This is also where mandated routing tends to fail culturally. Reps read a locked route as a statement that their judgment is not trusted, and adoption collapses. Present the route as the starting proposal it actually is.
Make the tooling invisible
Whatever the method, it dies if it requires a separate app, copy-pasting addresses, or planning the next day at 9pm. The workflow has to be: open the CRM, see today's stops on a map in a sensible order, tap the first one, navigation starts. Arrival logs itself. Notes take a few seconds at the door.
If a rep has to retype an address into a maps app, you have added work in order to save work, and the arithmetic usually comes out negative.
A useful test: can a rep replan their afternoon, from the cab of a truck, in under a minute? If not, they will improvise instead — and improvisation is what you were trying to improve on.
What to expect
Teams that go from ad-hoc visiting to zone-based planning generally find capacity for at least one more stop a day, which compounds fast across a team and a year. The gain comes mostly from clustering, not clever sequencing — which is good news, because clustering is the part you can do with a map and an afternoon.
Track the same three numbers after a month. If drive time per stop has not moved, the zones are probably too large or too many accounts are being visited off-day.
The Light plots your accounts on a map, plans multi-stop routes, hands off to turn-by-turn navigation, and logs visits automatically with geofence check-ins — inside the same app that holds the customer record. See how it works, or read what makes a field sales CRM different.