The basis you pick for splitting a customer base decides what your team optimizes for all year, and it usually gets chosen in an afternoon.
Two models dominate the conversation. Geographic mapping assigns reps to places. Account-based mapping assigns reps to customers, grouped by industry, size, product line, or whatever dimension actually predicts how the selling goes.
Most comparisons treat this as a preference. For a field team it is closer to a constraint problem, because one of the two models has a cost the other does not: someone has to drive.
What each model actually allocates
Geographic territories allocate travel. Draw them well and a rep spends less of the week moving and more of it in front of customers. Draw them badly and you have built a commuting job with a quota attached.
Account-based territories allocate relationships and expertise. A rep who covers hospital systems learns how hospital systems buy (the committee, the procurement cycle, the objections) and carries that across every account in the book, wherever those accounts sit.
The models are answering different questions. Geography asks how to cover ground efficiently. Account-based asks how to match the right seller to the right buyer. Both are legitimate, and they conflict as soon as your best-matched rep is four hours away.
| Geographic | Account-based | |
|---|---|---|
| Allocates | Travel | Relationships and expertise |
| Main question | How do we cover ground efficiently? | How do we match the right seller to the right buyer? |
| Works best when | Accounts are similar and revenue is spread across many of them | Accounts differ by industry, size, or buying process |
| Main cost | Reps sell to buyers they do not specialize in | Drive time across a wider area |
Before choosing, write down which variable explains more of your win rate: where an account is, or what kind of account it is.
Geography is a constraint before it is a model
Map My Customers’ territory planning guide says that if your reps spend almost no time in physical meetings and work mostly by phone and email, you probably do not need to work geographically at all.
Field teams live with the inverse. When reps sell to contractors, architects, and distributors spread across hundreds of miles, geography becomes a tax on every other choice you make.
That is why a purely account-based model is harder to run in the field than it looks on a slide. Assigning your medical-device specialist every hospital in three states is coherent on paper and produces a rep who spends more time on the interstate than in the building.
So the practical question for a field org is how much geographic inefficiency the account match is worth.
When account-based allocation earns the overhead
It earns it when accounts differ more from each other than from their neighbors.
A distributor selling the same catalogue to every hardware store in a region gains little from specialization. The sale is broadly the same one repeated, and proximity wins. A company selling into hospitals, veterinary practices, and manufacturing plants is running three different sales motions, and asking one rep to hold all three because they share a zip code costs more than the drive time saves.
Deal size and cycle length push the same way. Where a single account can carry a quarter, matching your strongest rep to it is worth several hours of driving. Where revenue is spread thinly across hundreds of accounts on a reorder cadence, the visit count matters more than the match, and geography should lead.
The tiering question sits underneath this. Map My Customers’ guide splits customers three ways: those that take the least effort to serve, those that need work but are worth it, and those that might need more than they are worth. That third group is usually the one an account-based model quietly over-serves.
The hybrid, and where it breaks
The clean version of either model rarely survives contact with a real book, and one resolution is to run both at once.
Named or strategic accounts get assigned by fit: the rep with the right expertise owns them wherever they sit, and the travel is accepted as a cost of the relationship. Everything else is allocated geographically, in patches drawn to be drivable, with visit cadence set by tier rather than by rep preference.
That hybrid is also where territory design usually goes wrong, because the two systems compete for the same hours. A rep holding four named accounts across a region plus a geographic patch has two jobs, and the named accounts usually win the conflict. If you run this model, the named-account commitment has to come out of the capacity calculation before the geographic patch is drawn, not after.
The same discipline applies to whitespace. Uncovered areas on the map are easy to see and easy to postpone, and they tend to sit in whichever half of the hybrid nobody owns outright.
The mapping decision is smaller than the execution one
Whichever basis you choose, the lines are drawn once or twice a year, and the outcome is decided by what happens inside them every week.
Research Map My Customers ran with Jasper Engines found that rep behavior affected results more than territory size did. Two reps in comparable markets produced different outcomes depending on how they planned their days. The top cohort held slightly fewer accounts than their peers and visited them 2.5 times more often, logging three times the activity. The detail is in what makes top field sales reps tick.
That finding does not make territory design irrelevant. It does mean a redesign is the smaller lever, and that a team choosing between models while nobody can see which accounts are actually being visited is optimizing the wrong layer.
Territory mapping software draws the boundaries and shows you the map. A system of execution decides who gets seen inside those boundaries this week, captures whether the visit happened, and tells you which parts of the territory have gone quiet. You need the second one to know whether the first one worked.
Choosing, in practice
Run three checks before you commit to a model.
Look at your last four quarters and ask whether the wins cluster by geography or by account type. Then calculate, for each rep, the visits their book requires against the visits their week allows. That number tells you how much travel inefficiency you can actually absorb. Finally, decide who owns whitespace, because neither model assigns it by default.
Write the answers down before the next planning cycle. A model chosen on evidence is also one you can defend to the rep who ends up with the harder patch.
FAQs
What is sales territory mapping?
Sales territory mapping is the process of dividing a customer base among reps and representing those divisions on a map. It covers how the boundaries are drawn, which accounts fall inside each one, and how coverage is reviewed. The mapping itself is allocation; whether the accounts inside a territory actually get visited is a separate question.
What is an account-based sales territory?
An account-based territory groups accounts by something other than location (industry, company size, product line, or named-account status) and assigns each group to the rep best matched to it. The aim is expertise: a rep who sells to one kind of buyer repeatedly learns that buyer’s cycle, committee, and objections.
What data do you need to map sales territories?
At minimum: account locations, an account tier or value indicator, and a realistic visit cadence per tier. Adding recent visit history is what turns the exercise from a redraw into a diagnosis, because it shows which accounts are already being under-covered. Without it you are balancing a plan rather than the work.
Is territory mapping the same as route planning?
No. Territory mapping decides which accounts a rep owns; route planning decides the order they visit them in on a given day. Teams often buy one expecting the other. Mapping without daily planning leaves reps to sequence the week themselves, which is where a lot of drive time goes.