Sales route planning decides which accounts a rep visits, in what order and how often. Good routes start from account value and fixed appointments, then fill the gaps with nearby accounts, and every visit ends up logged in the CRM.
- Tier accounts first, then map them; the shortest route is rarely the best one
- Lock anchor appointments, then backfill nearby A and B accounts
- Plan realistic visit times and keep an hour of slack each day
- Measure miles, visits per day and revenue per visit, not just distance
Sales route planning is the work of choosing which customers and prospects a field rep sees each day, in which order and how often, so more of the week goes to selling and less to driving. People tend to treat it as a mapping job. Most of the real work, though, is deciding who deserves the visit; the map comes after.
Most outside reps already know their territory. What they lack is a repeatable way to turn a list of 150 accounts into a sensible Tuesday. Without one, days get built around whoever called last, the same friendly customers get visited too often, and a big account two towns over goes quiet for a quarter.
This guide walks through a method that works with any toolset: tier the accounts, set visit frequencies, fix anchor appointments, then let software sequence the rest. It also covers when a CRM mapping add-on is enough and when teams with complex visits are better served by a custom mobile app for their field team that combines routing with order capture, photos and offline work.
What is sales route planning?
Sales route planning is a daily and weekly schedule of customer visits built from three inputs: who matters most, how often they need to be seen and where they are. Distance is only the last of the three.
That is the key difference from delivery routing. A courier has to reach every address on the manifest and wants the cheapest sequence. A sales rep doesn't have to visit everyone. The rep is choosing which stops are worth making at all, which ones have fixed times, and which nearby accounts can fill the gaps between them.
A complete route plan therefore answers four questions:
- Who: which accounts are due a visit this week, based on tier and last contact date.
- When: which visits are fixed appointments and which are flexible drop-ins.
- In what order: the sequence that keeps driving low while respecting opening hours.
- What happens at each stop: the goal of the visit and where the notes go afterwards.
Under the hood, the sequencing part is a known optimisation problem: the vehicle routing problem with time windows. Commercial engines such as the Google Maps Platform Route Optimization API solve it with constraints like visit windows and working hours. You don't need the maths. It does explain why a planner can beat a human at ordering twelve stops: the number of possible orders grows faster than anyone can check by hand.
Why does route planning matter for field sales?
Route planning matters because selling time is the scarcest resource a field team has. In Salesforce's fifth State of Sales survey of more than 7,700 sales professionals, reps said they spend just 28% of their week actually selling (Salesforce research). For outside reps, a large share of the rest is spent behind the wheel, parking and waiting.
Better routes attack that share directly. The payoffs show up in four places:
- More visits per day. Cutting a few backtracks often frees room for one or two extra calls.
- Better coverage of key accounts. A frequency rule stops high-value customers from slipping through because they are slightly out of the way.
- Lower cost. Fewer miles mean less fuel, lower mileage reimbursement and less vehicle wear.
- Cleaner data. When the route lives in the CRM, every visit is logged against an account, so managers can see coverage instead of guessing it.
Why isn't Google Maps enough for sales routes?
Google Maps is great at getting a rep from one stop to the next, and plenty of reps use it for exactly that. Ask it to plan the whole day and it runs out of road quickly:
- Stop limit. A multi-stop route tops out at ten points, which is less than a busy day for many reps.
- No reordering. It keeps stops in the order you type them, so you do the optimisation in your head.
- No account context. It doesn't know which stop is a top-ten customer, which one closes at 3 p.m. or which one you saw yesterday.
- No logging. Nothing flows back to the CRM, so the visit history lives in a rep's memory.
The usual pattern is to plan in a dedicated tool or CRM mapping view, then hand off each leg to Google Maps or Waze for turn-by-turn directions. That split plays to each tool's strength.
How do you plan sales routes, step by step?
The method below takes about two hours to set up for a territory and around fifteen minutes a week to maintain. It works whether you use a spreadsheet, a CRM map view or a dedicated route planner.
1. Clean the account addresses
Routing is only as good as the location data behind it. Export every account in the territory and fix missing postcodes, PO boxes used as visit addresses and duplicates of the same site. If a company has several branches, each branch the rep visits needs its own address record. Our guide to structuring a CRM database covers how to keep companies and locations separate.
2. Tier every account by value
Give each account an A, B or C tier based on current revenue and realistic potential. A simple rule: A accounts are the top 15 to 20% that drive most of your revenue, B accounts are steady mid-sized customers and promising prospects, and C accounts are small or dormant. Store the tier as a picklist field so maps and reports can filter on it.
3. Set a visit frequency for each tier
Decide how often each tier should see a rep in person. The next section suggests starting values. Once frequencies exist, the weekly question becomes "who is due?" rather than "who do I feel like seeing?".
4. Plot the accounts and spot clusters
Put all accounts on a map coloured by tier. Clusters appear immediately: a business park with six customers, a high street with four prospects, a corridor along a main road. Many teams split the territory into four or five zones, one per weekday, so each day stays geographically tight.
5. Lock the anchor appointments first
Anchor appointments are the fixed-time meetings: demos, quarterly reviews, negotiations. Put these in the calendar first. They decide which zone the rep works in that day.
6. Backfill with nearby due accounts
Around each anchor, add the A and B accounts in the same zone that are due a visit, then C accounts if time allows. This "anchor and backfill" approach is where most of the gain comes from. A rep who drives forty minutes to one meeting and back has wasted the trip; a rep who adds three nearby check-ins has turned it into a productive half day.
7. Let software sequence the stops
Now hand the list to the optimiser. Enter the visit duration for each stop and any opening-hour windows, and let it order them. Check the result against common sense, such as school-run traffic or a customer who prefers mornings, and adjust.
8. Log each visit before the next drive
The last step happens in the field. Before leaving the car park, the rep logs a one-line outcome and the next step against the account. On a phone this needs to take under a minute, which is why a good mobile CRM matters as much as the routing engine.
How often should each account be visited?
Visit frequency should follow account value and buying cycle, not habit. These starting values suit most B2B field teams; adjust them after a quarter of real data.
| Tier | Typical share of accounts | In-person visit | Between visits |
|---|---|---|---|
| A: key accounts | 15 to 20% | Every 2 to 4 weeks | Call or email weekly |
| B: steady customers and hot prospects | 30 to 40% | Every 6 to 8 weeks | Call or email every 2 weeks |
| C: small or dormant accounts | 40 to 50% | Quarterly or less | Automated email nurture |
| New prospects | Varies | When qualified or when passing nearby | Sequence of 3 to 5 touches |
Two rules keep the system honest. First, any A account with no visit in twice its target interval goes on a weekly exception list. Second, C accounts should not get in-person time unless they sit on the way to something more important. Marketing automation can keep them warm far more cheaply than a car journey.
A worked example: one rep, eight stops
To make the method concrete, here is an illustrative day for a rep selling supplies to dental practices in a mid-sized metro area. The figures are rounded and the setting is hypothetical, but the pattern is typical of what teams see when they move from calendar-driven days to planned routes.
Before planning: the day was built as calls came in. The rep had a 9:00 demo in the north, a 13:00 review in the south and filled the rest with practices that had asked for a visit, scattered across the city. The day ran to about 112 miles and six visits.
After planning: the 13:00 review moved to Thursday, the south-zone day. Tuesday became a north-zone day around the 9:00 demo. The rep backfilled with two A accounts and three B accounts within fifteen minutes of the demo, plus two C practices on the route back. The day ran to about 74 miles and eight visits.
| Measure | Before | After | Change |
|---|---|---|---|
| Miles driven | 112 | 74 | -38 |
| Visits completed | 6 | 8 | +2 |
| A and B accounts seen | 3 | 5 | +2 |
| Time driving (approx.) | 3 h 40 min | 2 h 25 min | -75 min |
The rep sold the same way on both days. The gain came from grouping the day by zone, deciding which meeting set the zone and filling the gaps with accounts that were due anyway.
How do you measure the payoff of route planning?
Measure route planning by its effect on selling capacity and coverage, with mileage as a supporting number. A simple monthly scorecard per rep covers it:
- Visits per field day, and the share of them with A or B accounts.
- Miles per visit, which falls as clustering improves.
- Coverage of A accounts: the share visited within their target interval.
- Revenue or pipeline per visit, which shows whether the extra visits are the right ones.
For a quick cost estimate, multiply miles saved per day by the mileage rate you reimburse, then by field days per year. Using the example above, 38 fewer miles a day at the 2025 IRS standard rate of 70 cents a mile is about $26 a day, or roughly $4,800 a year over 184 field days. The 75 minutes of driving saved each day is usually worth more than the mileage, because it converts into one or two more conversations.
Compare the same months year on year where you can. Field sales is seasonal, and a quiet August will flatter any change made in July.
Which features should a sales route planner have?
A sales route planner needs to understand accounts, not just addresses. Use this checklist when comparing tools:
- Stop optimisation for at least 20 to 30 stops a day, with visit durations and time windows.
- Two-way CRM sync, so tiers, last visit dates and notes flow in and visit outcomes flow back.
- Map filters by tier, owner, last visit date and open opportunities.
- Territory tools to draw zones and rebalance them between reps.
- Mobile check-in with one-tap visit logging and photo capture.
- Offline mode for basements, rural areas and industrial sites with weak signal.
- Handoff to navigation apps such as Google Maps or Waze for each leg.
- Manager reporting on coverage, visits and miles per rep.
CRM sync deserves the most scrutiny. A planner that keeps its own copy of the account list will drift out of date within weeks. Our CRM integration guide explains what to check in a sync before you sign.
Which route planning tool fits your team?
Most small teams should start with what their CRM already offers and move to a dedicated planner once reps regularly have more than eight stops a day. Beyond that, the right tool depends on how much happens at each stop and how tightly the route has to tie into your CRM and other systems.
| Option | Best for | Strengths | Limits |
|---|---|---|---|
| Spreadsheet plus Google Maps | One or two reps, few stops | Free, familiar | Manual ordering, no visit history, 10-stop cap |
| CRM map view or add-on | Small teams already on a CRM | Uses live account data, simple | Basic optimisation, few territory tools |
| Dedicated sales route planner | Field teams of 5 to 100 reps | Strong optimisation, territories, check-ins | Another subscription, sync quality varies |
| Custom field app | Teams whose visits include orders, audits or inventory | Fits your exact visit flow, works offline, connects to ERP | Build and maintenance cost, needs a clear spec |
A custom app makes sense when the visit itself is the complex part: a rep who takes orders against live stock, records shelf audits or collects signatures needs those steps and the route in one place. We cover that scenario in more depth in our pieces on order-taking apps for sales reps and door-to-door sales apps.
What are the most common route planning mistakes?
Most route planning failures come from planning the map before the priorities. Watch for these:
- Optimising for distance alone. The shortest route that skips your best customer is a bad route.
- Unrealistic visit times. Planning 20 minutes for a visit that always takes 45 wrecks the afternoon. Use averages from logged visits.
- Stale data. Closed sites, moved offices and wrong pins send reps to empty buildings. Review addresses quarterly.
- No flexibility. A plan with no buffer collapses at the first overrun. Keep slack and a short list of nearby fallback accounts.
- Territories that never change. Accounts grow, churn and move. Rebalance territories at least quarterly, and immediately when a rep leaves or a large account changes hands.
- Skipping the log. If visits aren't recorded, next week's plan is built on guesswork and managers cannot see coverage.
A one-week rollout plan
You can move a field team onto planned routes in five working days without stopping sales:
- Day 1: export accounts, clean addresses and remove duplicates.
- Day 2: agree tier rules with sales leadership and tag every account A, B or C.
- Day 3: set visit frequencies and build the "due this week" view in your CRM.
- Day 4: map accounts, draw weekday zones per rep and pick a sequencing tool.
- Day 5: each rep plans next week using anchor and backfill, and the manager reviews the plans in a 30-minute session.
After a month, compare visits per day, miles per visit and A-account coverage with the month before. Adjust tiers and frequencies, then repeat the review quarterly.
Sales route planning FAQ
What is sales route planning?
Sales route planning is deciding which accounts a field rep visits, in what order and how often, so that driving time goes down and time with high-value customers goes up. It combines account priority, visit frequency and geography, not just the shortest drive.
Can I plan sales routes with Google Maps?
For a handful of stops, yes. Google Maps limits a route to ten points, keeps them in the order you enter and knows nothing about account value, opening hours or visit history. Once a rep has more than a few stops a day, a planner that reorders stops and reads CRM data saves real time.
How many visits a day should a field sales rep plan?
It depends on visit length and territory density. A rep with 30-minute visits in a dense city can manage eight to ten; a rep with hour-long demos across a rural territory may manage four. Plan from realistic visit time plus drive time, and leave a buffer of about an hour.
How often should sales territories be replanned?
Review routes weekly and territories at least quarterly, or sooner when a rep leaves, a large account is won or lost, or one rep's calendar is consistently overloaded compared with others.
How is sales routing different from delivery routing?
Delivery routing tries to drop every package as cheaply as possible. Sales routing chooses which stops are worth making at all, weighs them by revenue potential and fixes appointment times first, then fills the gaps with nearby accounts.
Do I need special hardware for route planning?
No. A smartphone with a route planning app or a CRM mobile app is enough. What matters more is clean account addresses, a visit-frequency rule for each account tier and the habit of logging each visit before driving to the next one.



