Sign in Start free

Sales route planning is a frequency problem before it is a distance problem.

The shortest drive between the wrong accounts is still a wasted week. What decides a plan is which customers are due, and that decision is made before anyone opens a map. Five vendors' own documentation, the six inputs a plan is built from, and the arithmetic nobody publishes.

The short answer

Sales route planning is choosing which customers to see in a period, then sequencing them into drivable days. The choosing comes first and carries almost all of the value. It runs off the account record: how often this customer is due to be seen, what it is worth, what happened last time. The sequencing, the part every product demo shows, is the last step.

Of the five vendor documentation sets we read in July 2026, three name visit frequency as a planning input, four name fixed calendar meetings, and one names live business hours.

The six inputs of a planWhat it answersNamed by
Visit frequency per accountWho is due this week3 of 5
Fixed calendar meetingsWhat cannot move4 of 5
Account filters (tier, stage, last activity)Who is worth the day3 of 5
Saved or recurring routesWhat repeats next cycle3 of 5
Start and end pointWhere the driving begins3 of 5
Live business hoursWhether they are open1 of 5

Counted across the public documentation of Badger Maps, Leadbeam, Map My Customers, RepMove and SPOTIO, read between 19 and 29 July 2026. "Named by" means the vendor's own help centre, FAQ, feature page or published plan table uses the input as something you plan with. A vendor not naming an input is not evidence that the product lacks it; it is evidence about the documentation we could read. We build a competing product and have left ourselves out of the count for that reason.

Where this comes from

Every quote below was read on the vendor's own help centre, FAQ, feature page or public review profile, with the access date noted. Model figures are labelled as models, with their assumptions printed beside them. We build Lead Mapper, a competitor, which is why nothing here is characterised from memory. Tool by tool: sales route planner. Wider category: sales routing software.

What is sales route planning?

Sales route planning turns a book of accounts into a sequence of days. It has two unequal halves. The first selects: of the several hundred customers a rep is responsible for, which belong in the next five working days. The second sequences: in what order they are driven.

Almost everything published about this subject covers the second half, because that is what a screen recording can show. A list goes in, a tidy line comes out, the mileage drops. Map My Customers describes it in one FAQ sentence: "Map My Customers will sort them into the optimal order by drive time and distance" (read 29 July 2026). The assumption is visible: them has already been chosen. Something decided the list before the software touched it.

That something is the plan. If the selection is wrong, optimizing it well produces an efficient drive past customers who did not need seeing, while the ones who did wait another fortnight. It is why a rep with a perfectly optimized week can still lose an account.

The vocabulary blurs the two halves on purpose. The second half compared tool by tool, with prices and published capacity, is the sales route planner page; the whole category including the map layer is sales routing software. This page is about the first half.

The input that decides the plan: how often each account is due

Ask a field manager how their reps decide where to go and the usual answer is a mixture of habit, the loudest customer, and whatever is on the way. Ask the same question of a well run book and you get a number: this customer is a fortnightly call, that one is quarterly.

That number is the interval, the one input from which a plan can be derived rather than argued about. Map My Customers publishes the mechanism in its own FAQ, with the example intervals included: "Frequencies tell Map My Customers how often each account should be visited. Set a frequency at the account level (e.g., every 14 days for Tier 1, every 30 days for Tier 2) and the platform will flag accounts that have fallen behind cadence" (read 29 July 2026). Badger Maps builds routes from the same idea and says so in the title of a knowledge base article, "How to Create a Route Based on Visit Frequency" (read 29 July 2026). Leadbeam approaches it from the management side, describing its Studio module as surfacing "Cadence gaps, stalling deals, accounts going cold, follow-ups that didn't happen" (read 29 July 2026).

The clearest evidence that the interval is load-bearing comes from a tool built without it. In Route4Me's review corpus, a district manager wrote in November 2017: "Could use route editing tool for accounts not seen on a regular basis. Some accounts I see every 3 to 4 weeks where others I may only want to see 2-3 times a year. I would like to be able to set that up automatically within the software." That is a competent user of a competent optimizer describing the gap between a delivery plan and a sales plan. The stops were fine; the schedule behind them had nowhere to live.

Which planning inputs each vendor's own documentation names, read July 2026 A six by five matrix. Visit frequency is named by Badger Maps, Leadbeam and Map My Customers. Fixed calendar meetings are named by Badger Maps, Leadbeam, Map My Customers and RepMove. Account filters are named by Badger Maps, Map My Customers and SPOTIO. Saved or recurring routes are named by Badger Maps, RepMove and SPOTIO. A start and end point is named by Map My Customers, RepMove and SPOTIO. Live business hours are named by Leadbeam alone. Seventeen of thirty cells are filled. What each vendor's documentation lets you plan from Filled cell: the vendor's own help centre, FAQ, feature page or plan table names this input. Read 19 to 29 July 2026. Badger Leadbeam MMC RepMove SPOTIO Visit frequency per account Fixed calendar meetings Account filters (tier, stage, activity) Saved or recurring routes Start and end point Live business hours Sources: each vendor's own help centre, FAQ, feature page and published plan table. 17 of 30 cells filled. Absence is a fact about the documents, not about the product.
The input that answers "is this customer even open right now" is named by one vendor of five. The input that answers "where does the driving start" is named by three.

Fixed calendar meetings are the most widely documented input, which fits: an appointment is the one constraint nobody argues with. Leadbeam's Compass module is described entirely in those terms, sequencing "up to 50 stops a day around the things that actually matter - your calendar's fixed meetings, live business hours from Atlas, real-time traffic. Reps never knock on one that's closed" (read 29 July 2026). Live business hours, by contrast, appear once in five, which is worth asking about in any trial.

The five decisions behind a week of sales route planning

A plan is not a list of stops. It is five decisions taken in an order that matters, because each one narrows the next. Reversing them is the most common way a week goes wrong: teams draw a route, then justify the accounts on it.

  • Set an interval per tier, not per account. Two or three tiers is enough to start. Map My Customers uses 14 days and 30 days as its published example. Per-account exceptions can be added later; starting per account guarantees the exercise never finishes.
  • Pull the due list, not the whole book. Due means last visit plus interval falls inside the period. This is the step that decides the week, and it is arithmetic rather than judgement.
  • Anchor what cannot move. Confirmed appointments are fixed points; everything else is planned around them. Four of the five documentation sets we read name calendar meetings as a planning input, which is the highest agreement of any input in the grid above.
  • Group the due accounts geographically before sequencing them. A due list scattered over a whole territory is not a week. Clustering turns it into candidate days, and this is the step a spreadsheet genuinely cannot do.
  • Sequence each day last. This is the part the software is best at and the part that matters least. It is also the only step that is fully automatic in every tool in the category.

The order is the argument. Steps one and two decide whether the week was worth driving; step five decides how long it takes. Most buying conversations spend their time on step five, and most of the disappointment afterwards traces back to steps one and two never being made explicit.

How many accounts a rep can hold, and why the interval decides it

The interval is not a preference. It is a budget, and it can be spent only once. Once you write down how often each tier is due, the size of a workable book stops being a matter of opinion.

The arithmetic is simple enough to do on paper. A rep who completes 8 visits on a field day, works 4 field days a week and 46 weeks a year makes about 1,472 visits a year. An account on a 14-day interval consumes 26 of those; an account on a 90-day interval consumes 4. Divide and you have the ceiling.

Model: how many accounts one rep can hold at a given visit interval At a modelled 1,472 visits a year, a 7-day interval supports 28 accounts, a 14-day interval 56, a 21-day interval 85, a 30-day interval 121, a 60-day interval 242 and a 90-day interval 363. The interval is a budget: accounts one rep can hold Model, not measurement. Assumes 8 visits per field day, 4 field days per week, 46 working weeks, so 1,472 visits a year. Every 7 days 28 Every 14 days 56 Every 21 days 85 Every 30 days 121 Every 60 days 242 Every 90 days 363 Read as: at a 14-day interval, the 57th account cannot be served without breaking the interval on one of the other 56. The 14-day and 30-day rows use the example intervals Map My Customers publishes in its own FAQ, read 29 July 2026. Every other figure is our own arithmetic from the assumptions in the subtitle. Change the visit rate and every bar moves proportionally.
Six intervals, one visit budget. The numbers are a model, and the assumptions behind them are printed above so you can substitute your own.

Use it as a sanity check. A rep carrying 200 named accounts on a promise of monthly contact is being asked for roughly 2,400 visits a year against a realistic 1,472, and no optimizer closes a gap of that size. Run the same arithmetic backwards and it becomes territory design, covered on sales territory mapping.

Why a correct cadence still produces an impossible week

Intervals that are individually reasonable collide when they land on the calendar together, and planning one week at a time hides the collision until the week arrives.

Take the book that the model allows: 20 accounts on a 14-day interval and 78 on a 30-day interval, 98 accounts in total, comfortably inside the ceiling at 113 visits per four weeks against a capacity of 128. Now schedule it the obvious way, with the fortnightly accounts all falling in the same weeks.

Model: visits per week from a 98-account book, planned naively and planned staggered Planned naively the four weeks carry 38, 18, 38 and 19 visits, and weeks one and three exceed the 32-visit weekly capacity. With the fortnightly accounts split into two staggered halves the same book carries 28, 28, 28 and 29 visits, every week inside capacity. The same book, planned two ways Model. 20 accounts at a 14-day interval plus 78 at a 30-day interval. Capacity line at 32 visits a week (8 a day, 4 field days). capacity 32 Naive: week 1 38 Naive: week 2 18 Naive: week 3 38 Naive: week 4 19 capacity 32 Staggered: week 1 28 Staggered: week 2 28 Staggered: week 3 28 Staggered: week 4 29 Both plans contain 113 visits over 28 days. Only the staggered one is executable. Our own arithmetic; intervals from Map My Customers' published example, read 29 July 2026.
Same accounts, same intervals, same total work. Splitting the fortnightly accounts into two alternating halves is the whole fix, and it is invisible if you plan a week at a time.

The fix is one line long: split the fortnightly accounts into two halves and start them a week apart. What makes it worth writing down is that no amount of route optimization finds it, because it is not a routing decision. It is a scheduling decision taken a level above the map, and it is the reason a four-week view beats a one-week view. Twenty-eight days is the shortest window in which a 14-day and a 30-day interval both repeat.

Sales route mapping software: what the tools ask you for first

The request a product makes before it will do anything reveals the model underneath.

RepMove states the driving-first model most clearly: "The Optimize button will be available only after you add a start and end" (read 29 July 2026). It will not begin until it knows where the car is. SPOTIO is similar, with stops added by keyword search, by clicking records on the map, or by lassoing pins, after which "you can edit any specific stops on the route, change the order of stops, set a starting/ending location" (read 29 July 2026).

Map My Customers asks a different first question. Its planning view stacks filters "by tier, last activity date, deal stage, custom field, territory, or distance from your current location", kept as a Saved Filter (read 29 July 2026), and every field except the last comes from the account record rather than the map. Badger Maps sits in the same place, with articles titled "How to Build Filters" and "How to Route Filtered Accounts (Web App)" (read 29 July 2026). Filter first, route second.

Neither model is wrong; they answer different questions. If your stops arrive as a list from someone else, the driving-first model is the shorter path. If they have to be chosen from several hundred candidates every week, the filter-first model is doing the harder half for you.

Route planning for sales reps and route planning for a manager are different jobs

The same plan is two documents depending on who is holding it. A rep needs to know what today is. A manager needs to know whether the book is being covered, which is a question about the accounts that are not on any route.

That second question is the one most tooling answers weakly, and the documentation shows where it is answered at all. Map My Customers states that the platform "will flag accounts that have fallen behind cadence" (read 29 July 2026). Leadbeam's Studio module is described as surfacing "Cadence gaps, stalling deals, accounts going cold, follow-ups that didn't happen, deal stages that don't match the conversation" and routing "each signal to the right manager" (read 29 July 2026). Both sentences are about absence rather than activity, and absence is the manager's real subject.

For a rep the useful output is narrower: today's sequence, the context behind each stop, and fast logging. For a manager it is coverage, measured against the intervals set in decision one. Without those intervals there is no definition of a covered territory and nothing for a report to be right or wrong about. Territory side: sales territory mapping. Tool side: sales route planner.

How to plan a sales route in one sitting

A first pass on a real book takes about an hour, and it is worth doing on paper before any software is bought, because the output is exactly what a trial should be tested against.

  • Write three tiers and three intervals. Ten minutes. Argue about the boundary cases later; the boundary cases are never what breaks a plan.
  • Multiply and compare. Accounts in each tier, times visits per year at that interval, against a realistic annual visit count. If the total exceeds capacity, the plan is fiction and the tiers have to change before anything else does.
  • Lay four weeks side by side. Not one. The collisions between a fortnightly and a monthly interval only appear over 28 days, and staggering the shorter interval is usually the entire fix.
  • Cluster the due list by area, then cut it into days. This is where a map earns its place, and it is the one step that does not survive being done in a spreadsheet.
  • Test the plan, not the demo. Take one real week from the exercise into any trial and rebuild it. If the tool cannot express your intervals, it will not hold your plan, however well it optimizes the drive.

The last point is worth insisting on. A trial that consists of importing a spreadsheet and pressing Optimize tests the easiest thing the software does. A trial that starts from a due list tests what you are buying.

Sales rep route planning software: what carries over to next cycle

A plan rebuilt from nothing every Monday will be abandoned by the third Monday, so the part of the documentation worth reading before buying is the part about what is saved.

Three of the five documentation sets we read name something re-runnable. Badger Maps lists "Saveable & recurring routes" as a line on both of its published plan tiers (read 29 July 2026). SPOTIO states that "Routes created on the mobile can be run a single time, or given a name and saved as a recurring route" and that mobile-created routes stay visible on the web version (read 29 July 2026). RepMove documents saving "your route as a Route Template under a unique name so you can easily reuse it in the future" (read 29 July 2026).

These are three different objects. A recurring route repeats on a schedule. A template is a starting point you edit. A saved filter, which is what Map My Customers documents, saves the selection rule, so it regenerates a fresh due list each time it opens. For a book that changes, the saved rule ages better: a route saved in March still contains March's accounts.

What breaks a sales route plan

Plans rarely fail on the road. They fail in the gap between the plan and the calendar.

Appointment handling is the recurring theme. A SPOTIO reviewer in renewables wrote in January 2018 that there were "No scheduling follow-ups or reminders in system"; a field agent in May 2022 reported "It does not sync with my Google Calendar. The time for the appointments are usually wrong"; and a Google Play reviewer in September 2025 wrote that "to change your schedule on the calendar is very time-consuming. You cannot move your appointments manually." Three independent voices over seven years, all describing friction between the plan and the diary rather than the road. They are dated reports about specific experiences and we quote them as such.

The second is losing the record of what happened. A plan improves only if last visit dates are accurate, and they are accurate only if logging is fast and works without a signal. Map My Customers publishes an answer worth getting from any vendor in writing: "Everything queues locally and syncs the next time the device gets a signal" (read 29 July 2026). What happens when the plan changes mid-morning is covered on the sales route planner page.

FAQ

What is sales route planning?

Choosing which customers a rep should see in a period, then sequencing them into drivable days. The choosing is driven by how often each account is due, what it is worth and what happened last visit. Sequencing is the final step, not the first.

How do you plan a sales route?

Set an interval per tier, pull the accounts that are due, anchor the appointments that cannot move, cluster the rest geographically into day-sized groups, and sequence each day last.

What is the difference between sales route planning and route optimization?

Optimization sorts a list you have already chosen; planning chooses the list. Map My Customers describes the optimization half plainly: "Map My Customers will sort them into the optimal order by drive time and distance" (read 29 July 2026). The word "them" is where planning has already happened.

What is visit frequency, and which tools use it?

The interval at which an account is due, set per account or per tier. Three of the five documentation sets name it: Map My Customers as Frequencies with 14-day and 30-day example tiers, Badger Maps in an article titled "How to Create a Route Based on Visit Frequency", and Leadbeam as "Cadence gaps" surfaced to managers. All read 29 July 2026.

How many accounts can one sales rep cover?

It follows from the interval. At a modelled 8 visits a day, 4 field days a week and 46 weeks, a rep makes about 1,472 visits a year: roughly 56 accounts at a 14-day interval, 121 at a 30-day interval. Model figures from our own arithmetic.

How far ahead should you plan sales routes?

Four weeks, because 28 days is the shortest window in which a fortnightly and a monthly interval both repeat. In our model of a 98-account book, planning week by week produces weeks of 38, 18, 38 and 19 visits against a capacity of 32, while staggering the fortnightly accounts flattens the same work to 28, 28, 28 and 29.

Can you do sales route planning in a spreadsheet?

The intervals and the due list, yes. What it cannot do is tell you which due accounts sit near each other, and that clustering is what turns a due list into a drivable week.

Does route planning for sales reps require a CRM?

It requires the fields a CRM holds: last visit, value, stage, owner. Map My Customers publishes the filter set behind its planning view, "by tier, last activity date, deal stage, custom field, territory, or distance from your current location" (read 29 July 2026), and only the last of those comes from the map. Our own CRM connections are listed under integrations.

Which tool should I use for sales route planning?

Compare on the planning half, since every tool in the category optimizes. Prices, published capacity and what happens when a day changes are compared on the sales route planner page and across the category in the field sales software guide.

Plan a real week, not a demo route.

Import your accounts or connect your CRM, filter to the ones that are due, cluster them into days and sequence each one. $27 per user per month, free trial, no credit card, no demo call.

Start free trial

Keep reading

Sourced comparisons, pricing breakdowns and the field-sales tooling behind them.