How do you design sales territories that scale as you hire?

Every sales leader I know has lived the same week. You hire two reps. Now you have to redraw the map.

Someone loses their best account. Someone else gets a patch of nothing. The Slack messages start. A month later the new reps are still waiting for a territory that feels fair, and your best seller is updating their resume.

Territories should not be redrawn every time you hire. They should be built so that hiring is just another split.

Why does the usual volume-based territory model break?

It breaks because it cuts the map by counts and totals, and counts do not describe the work. At TVEyes, the first model divided accounts by volume. It missed hundreds of accounts altogether, and reps felt it was unfair, which was fair of them.

Two territories with the same number of accounts can have very different potential, and very different effort. A patch full of small, fast deals and a patch full of large, slow ones are not the same job. As a public guide from Spotio puts it, equal account counts are not enough: balance workload, opportunity and whether a rep can actually cover the ground.

The second problem is that a volume model is hard to change. When you add a rep, you have to move a pile of accounts from several people, and every move is a negotiation.

So the question to ask is not "how do we divide this fairly today?" It is "what happens to this design when we hire again?"

What does a territory model that keeps splitting look like?

It starts from a unit you can divide again. At TVEyes we moved to a DMA model. A DMA is a designated market area, the region a local media market covers. The point is that a DMA is, in the words we used on the project, infinitely divisible. When a market gets too big for one rep, you split it. Nothing else has to move.

The same idea handled the hardest case. Federal accounts do not follow a map, so we split them into about 20 sub-pockets, each with its own owner. A new hire takes a sub-pocket. Nobody else loses anything.

You do not have to use DMAs. Any unit works if it has three properties:

• It is small enough to hand to one person.
• It can be split again when it grows.
• Everyone can see where the boundary is. Reps should be able to look up who owns an account and why.

Pick the unit that fits how your team sells. Geography works for field and regional selling. Industry or product line can work for specialists. Strategic and national accounts usually need their own list, off the map.

How many accounts should one rep own?

Set a cap, and make it small enough that the rep can actually work every account. At DealRoom, each AE and each BDR owns at most 300 accounts.

A cap does something a map cannot. It tells you when to hire. If your territories are full and the pipeline is still bigger than the team can handle, that is a hiring decision with numbers behind it. It also tells you when a territory is too small: a rep with a handful of accounts and nothing to do should be given more.

Choose the cap from the work, not from a ratio you read somewhere. Ask how many accounts a rep can touch in a quarter with real attention. Start there. Adjust with data.

How do you keep reps from taking accounts they should not?

Lock the owner field, and give people one clean way to ask for a change. DealRoom learned this the hard way. One BDR claimed signal accounts out of a shared pool, which is exactly what you would do if you were measured on pipeline. So the owner field is now locked.

Here is what replaced it:

1. A weekly swap form. Normal changes go through one form, reviewed once a week.
2. An ad hoc path for urgent signals. When a buying signal shows up on an account, the team can swap it right away.
3. Reclaim after silence. Accounts nobody has touched for 90 days go back to the pool.

The same kind of rule helped TVEyes. SDRs can own companies for prospecting, under strict territory rules. And at go-live there was a 30-day use it or lose it rule, so a new owner either worked an account or released it.

Reclaiming idle accounts is the part leaders skip. It is the part that keeps a fixed cap from locking up your market. It also fixes a quieter problem we saw at DealRoom: 40 marketing-qualified leads came in on a group of accounts and only 5 were touched.

What data do you need before you cut territories?

You need to know the whole market, not just what is already in the CRM. At TVEyes, the addressable market was about 92,000 companies. Only 31,686 were in the CRM. The other 60,400 were net-new.

If we had cut territories on the CRM alone, reps would have been handed a third of their market and told it was the whole thing.

So we enriched in stages, company data first. Then, with a real list, we could cut territories by potential and by workload instead of by whatever was loaded.

If you are not sure what your market is, start there. Our revenue operations work begins with the account list because every other decision depends on it.

Do territories fix a transactional sales team?

No. This is the thing nobody wants to hear. TVEyes had a territory problem, and fixing it mattered. But territories alone do not change how reps sell.

If reps are chasing one quick deal at a time and never learn the account, a better map gives them a better place to chase quick deals. Territories decide who owns what. They do not decide how the work gets done.

Pair the design with a motion that fits it: account plans for large accounts, signals for timing, and a clear split between what a person does and what an AI agent does. The map is the first step, not the last.

What mistakes should you avoid?

• Redrawing on every hire. If a new rep means a new map, the model does not scale.
• Cutting on the CRM alone. You will miss most of the market.
• Equal counts, unequal potential. Fair means equal opportunity, not equal numbers.
• No owner lock. Reps will claim what looks good.
• No reclaim rule. Idle accounts are the quietest leak in a territory plan.
• Treating the map as the plan. It tells reps where to look. It does not tell them what to do.

What should you do first this month?

1. List every company in your market, not just the ones in the CRM.
2. Choose a unit you can keep splitting and mark where the boundaries are.
3. Set a cap per rep and write it down.
4. Lock the owner field and build the swap form.
5. Decide when idle accounts come back.

Frequently asked questions

Should every rep get the same number of accounts?

Not necessarily. Give every rep a realistic path to their number, and that depends on potential and workload as well as count. A cap is useful as a ceiling, as DealRoom's 300 accounts per AE and BDR shows, but two patches with the same count can still be very different jobs.

How do you handle strategic or national accounts?

Take them off the map. Federal and national accounts do not follow geography, so give them their own list. At TVEyes we split federal accounts into about 20 sub-pockets so each had a clear owner and a new hire could take one without disturbing anyone else.

When should we reclaim accounts from reps?

When nobody has touched them for a set time. DealRoom reclaims accounts untouched for 90 days, and TVEyes used a 30-day use it or lose it rule at go-live. Pick a window that fits your sales cycle, publish it, and make it automatic so it is never personal.

Can SDRs own accounts too?

Yes, with rules. At TVEyes, SDRs can own companies for prospecting under strict territory rules, so the lines between SDR and AE accounts are clear. Without those rules, two people end up working the same account, or neither of them does, and the owner field stops meaning anything.

Do we need to enrich our data before building territories?

Yes. You cannot divide a market you cannot see. TVEyes had 31,686 companies in the CRM out of about 92,000, so we enriched in stages, company data first, so territories could be cut on real information instead of whatever had happened to be loaded.

Sources

• TVEyes territory design, ownership rules and inbound reviews, 2026: the volume model that missed hundreds of accounts, the DMA model, the roughly 20 federal sub-pockets, the 92,000 company market and the 30-day use it or lose it rule.
• DealRoom capacity model, 2026: the 300 account cap per AE and BDR, the locked owner field, the weekly swap form and the 90-day reclaim. See the DealRoom case study.
• Spotio, Sales Territory Design: A Step-by-Step Process: balancing workload, opportunity and geographic feasibility instead of account counts alone.