How to Build a Dental Sales Territory Map With Provider Data

Most dental-industry sales territories I've seen get built the same way: someone opens a map of the US, splits it into regions that look roughly equal in size, and hands one to each rep. East, West, Midwest, South. It feels fair. It's also usually wrong, and it tends to take about two quarters for that to become obvious - one rep is drowning in accounts, another is making cold calls out of boredom, and nobody can quite explain why the "equal" territories aren't performing equally.

The fix isn't a better map. It's measuring territory size in something other than land.

Square miles don't buy anything

Here's a pair of states that illustrates the problem well: Montana and Nevada. Both are big, both are sparsely populated, both get lumped into "the empty part of the map" when someone's drawing regions by eye. Montana is actually the larger of the two by land area.

But Montana has roughly 1,448 verified dental providers. Nevada has about 3,727 - more than two and a half times as many, packed mostly around Las Vegas and Reno. If you're splitting the Mountain West into two "equal" territories and one rep gets Montana while the other gets Nevada, you haven't split anything evenly. You've given one person two and a half times the opportunity of the other, and from a map, you'd never know it.

This is the core idea, and it's not complicated: a territory's size should be measured in addressable accounts, not square miles. Everything else in this guide is just how to actually get those numbers and act on them.

Start with a real count, not a guess

You need, at minimum, a provider count per state. Ideally also a split between practices (organizations) and individual providers, since those often mean different buying processes depending on what you sell.

Where this trips people up: population isn't a good stand-in for provider count, and neither is "how big does this state feel." Dental provider density tracks more closely with healthcare infrastructure and urbanization than with raw population, which is exactly why Nevada and Montana - similar in most people's mental map - aren't close at all once you actually count.

If you only do one thing differently after reading this, make it this: pull real per-state provider counts before you draw a single territory line. Not estimates. Not "about how many we'd guess." An actual count, specific to your market.

Weight it by specialty if your product needs it

A general territory map (all dental providers, state by state) is fine if you sell something every practice needs - office supplies, scheduling software, general liability insurance. It's the wrong map if you sell something narrower.

Say you sell equipment specific to orthodontic practices. The all-specialty ranking of a state is close to irrelevant to you. What matters is orthodontist count, specifically, and that ranking can look completely different. Arizona has around 496 orthodontists. Nevada - which had more than double Montana's total provider count - has about 287. Montana has roughly 86. The gap between Arizona and Nevada here is smaller in absolute terms than their general-dentist gap, but it's still a real, material difference in how much territory a rep covering "orthodontist accounts" actually has in each state.

The practical rule: filter by the specialty (or specialties) that actually buy your product before you rank states. A general count tells you where the dental market is big. A specialty-filtered count tells you where your market is big, and those are not always the same map.

Split the big states before they break one rep

Some states are just too large for a single territory regardless of how you slice it. California, by itself, has over 58,000 verified dental providers - more than entire multi-state regions elsewhere. Handing one rep "California" as a territory isn't a territory, it's a full-time job with no room to also cover anything else.

The fix is to go one level down, to the city or metro level, inside a state like that. Los Angeles alone has roughly 3,377 providers. San Diego has about 2,179. San Francisco, San Jose, and Sacramento each have well over 1,000. That's already five natural sub-territories inside a single state, each one a reasonable size on its own, well before you even look at the rest of California.

This matters for the shape of the whole exercise: build your territory map at the state level first, but treat any state that's disproportionately large as a flag to drill down to its cities before finalizing anything. A handful of states will usually need this. Most won't.

Putting it together

The actual process, once you have the data, is less complicated than most people expect:

Pull provider counts by state - filtered to your relevant specialty if you have one. Rank states by that number, not by eye. Group them into territories sized by roughly equal opportunity, not equal geography, which will almost never line up with clean regional boundaries like "the Northeast" or "the Southwest." For any state too large to be one territory on its own, break it into its top cities and treat those as separate units in the grouping. Then sanity-check the totals - if one proposed territory has triple the accounts of another, that's not a rounding error, go back and rebalance.

That last step is worth doing before you commit to anything, and it's genuinely faster than it sounds - if you want to test a few state/specialty combinations against each other without pulling raw numbers by hand every time, our TAM calculator does exactly that: pick any states and specialties and it totals up the verified provider count instantly, which is enough to stress-test a proposed split in a few minutes rather than a few spreadsheets.

One more thing: revisit it

A territory map isn't a one-time artifact. Practices open, close, and merge continuously, and a split that was balanced a year ago can drift out of balance without anyone noticing until a rep's pipeline looks thin for reasons that have nothing to do with their performance. Re-running the counts once or twice a year is enough to catch real drift without turning it into a recurring project. The data changes slowly enough that you don't need to watch it constantly - you just can't set it once and assume it holds forever.

← Back to all posts

Chat with us