Four weeks into the new fiscal year, the Head of Sales calls me. The plan he signed off in December is already cracking. Two of his eight AEs are at 40 percent of quarterly quota. Three are sandbagging because they got a fat patch and the math is too easy. The remaining three are quietly working accounts that were officially assigned to someone else. The CRO wants a fix by the next forecast call.
This is the script for almost every Q2 conversation I have. The plan was not bad. The plan was a spreadsheet exercise that ignored four things that decide whether a territory map survives contact with the real world.
I have built or fixed sales territory plans for about 30 B2B companies between Series A and Series C in the last decade. The pattern is boring. Companies build territories by ZIP code, headcount band, or a quick split of the customer list. They run it through a comp model, ship it on January 2, and discover by April that half the patches are unworkable.
This piece is what I would do instead. It is opinionated. It will not flatter your VP of Sales if his current plan is built in Excel. Read it anyway.
Share of B2B sales teams that redraw territories mid-year because the original plan stopped working. Source: my own audit data across 30 SMB and Series A-C companies, 2022-2025.
What sales territory planning actually is
Sales territory planning is the process of deciding which accounts go to which seller, how many accounts each seller can work, and what the quota and comp look like at that load. It is not a list of cities. It is not a vertical split. Those are inputs. The output is a coverage model that ties quota, capacity, and the addressable market together.
A real plan answers four questions:
- How many accounts in our addressable market are worth working this year?
- How much pipeline can one seller generate from a fixed number of accounts?
- How many accounts can one seller actually touch in a quarter without dropping balls?
- What does that map look like across the team, and where does it break?
If your current territory document does not answer all four, it is a seating chart, not a plan.
Why most B2B territory plans break by Q2
I see the same four mistakes every time.
Mistake one: the plan is based on geography or headcount band only. Geography made sense when reps drove to meetings. For a SaaS or services business in 2026, ZIP code is a weak proxy for fit. A 200-person logistics company in Indianapolis and a 200-person AI startup in Berlin are not the same buyer.
Mistake two: the plan ignores propensity to buy. Two patches with the same total account count can have wildly different intent signals. One AE inherits 800 accounts with 12 percent showing fresh hiring or funding signals. The other inherits 800 accounts that have been stale for 18 months. They get the same quota. Guess who quits in May.
Mistake three: capacity is set by gut. "Each AE should carry 150 accounts" is a number people inherit from a previous job and never recheck. The right number is a calculation, not a tradition.
Mistake four: nobody validates the plan against win rate and cycle length. If your average cycle is 90 days and your AE has 200 active accounts, the math says she needs to start a new opportunity every 11 working days just to keep pipeline coverage at 3x. That is fine if she has SDR support and clean data. It is impossible if she does not.
A territory plan is a coverage math problem dressed up as a map.
Stop arguing about who gets New York. Argue about how many fit-and-intent accounts one seller can actually work in a quarter, and back into the headcount from there.
The four-input model I use
The plan I build for every client is the same shape. Four inputs, two outputs. It fits on one slide and you can run it in HubSpot or Salesforce with a CSV export.
Input one: total addressable market with ICP fit scoring
Start with your ideal customer profile. If you do not have one written down with named firmographic ranges, stop here and write a real ICP document first. Going further without one is guesswork.
With an ICP, pull the universe of companies in your serviceable market. For most of my clients this is between 5,000 and 80,000 accounts. Score each account on ICP fit. I use a four-band model: A (perfect fit), B (close fit), C (edge case), D (out of scope). The bands are deterministic. Same company should always get the same band.
A practical rule: if your A and B bands together hold fewer than 1,500 accounts, your problem is not territory planning. It is market size. Different conversation.
Input two: intent and timing signals
Static fit is not enough. A B2B account is worth working when fit overlaps with a real buying window. The window is signaled by hiring, funding, leadership change, tech adoption, RFP language, or product usage if you have a freemium motion.
I run waterfall enrichment on the A and B accounts using Clay, then tag accounts with one of three intent tiers:
- Hot: signal in the last 30 days, fit band A or B.
- Warm: signal in the last 90 days, fit band A or B.
- Cold: no fresh signal, fit band A or B.
The hot and warm pools are the working universe for the year. The cold pool is a watchlist. You do not assign cold accounts to a quota-carrying AE in January because they will not get worked. They will sit and rot and make your CRM look like a graveyard.
Input three: per-seller capacity
This is the input most companies skip. Capacity is the number of accounts one seller can meaningfully touch in a quarter. "Meaningfully touch" means at least three outbound attempts per account, a manual review of news and signals, and a real follow-up cycle.
The math I use:
- Working days per quarter: ~60
- Hours per day on account work: 5 (the rest is meetings, admin, calls in flight)
- Minutes per account per quarter for a healthy touch pattern: 45 (research, three sequence sends, one manual edit, a LinkedIn touch)
- Account capacity per quarter per AE: (60 × 5 × 60) / 45 = 400 accounts
400 is a ceiling, not a target. Add new opportunity management on top and the real number is closer to 220 to 280 for an AE running their own outbound. For a hybrid model where SDRs source the top of funnel, AEs can carry 350 to 400 because the touch pattern shifts.
If your current model has each AE assigned 600 plus accounts, the seller is silently triaging. Most are working the 50 they like and ignoring the rest. You are not getting territory coverage. You are getting cherry-picking with extra steps.
Input four: pipeline math from cycle length and win rate
The last input ties it all together. Take last 12 months of closed-won data and compute:
- Average sales cycle in days
- Average win rate (won / created opportunities)
- Average deal size
From quota and cycle, you get required pipeline. From win rate, you get required opportunities. From opportunities and account-to-opp conversion rate, you get required active accounts.
Example: AE has a $1.2M annual quota, $40k average deal size, 25 percent win rate, 90-day cycle, 8 percent account-to-opportunity conversion. Math:
- Closed deals needed: 30 per year
- Opportunities needed: 120
- Active accounts needed at any time to feed the 120: ~150 in a 90-day window
- Annual account universe needed for the AE: ~600 working accounts
If your capacity per AE is 280 per quarter, you can hit 600 over the year by rotating focus quarterly. That works. If your capacity is 150, the plan does not pencil and you either lower the quota or raise the AE count.
The two outputs
With the four inputs locked, you produce two things.
Output one: the coverage map. A table that shows each AE name, their assigned account count by tier (hot, warm, cold-watchlist), their quota, the implied pipeline, and the implied close rate needed. One slide. Anyone in the company can read it.
Output two: the gap analysis. Where coverage is thin or impossible. Maybe you have 4,200 hot and warm accounts in band A and B, eight AEs, and a per-AE capacity of 280 per quarter. That means 280 × 8 = 2,240 accounts get real coverage in any quarter. The remaining 1,960 accounts are uncovered. The gap analysis tells leadership where to invest: more AEs, more SDRs, narrower ICP, or a partner motion.
The gap analysis is the document that justifies headcount. Without it, hiring decisions become political.
How to build this in HubSpot in two weeks
Most of my clients run on HubSpot. Here is the sequence I follow when I get hired to fix a broken territory plan.
Two notes on this:
First, you need to run CRM data hygiene before any of this. Scoring on decayed data produces fake bands. If your last enrichment run was 12 months ago, 27 to 35 percent of your records are wrong. The plan you build on top will be wrong by the same amount.
Second, the assignment rule needs to be deterministic and auditable. "Round robin" is fine for inbound leads but it is a terrible way to split a finite addressable market. Use a documented rule: vertical, deal size band, account fit band, geography as a tiebreaker. Write the rule down. When an AE asks why an account is not theirs, you should be able to point at one row of a sheet.
Old way vs what actually works
The 90-day review cadence
A territory plan is not a yearly document. It is a quarterly document with a yearly framing. I bake the review into the same operating rhythm as the sales QBR. Three questions to answer each quarter:
- Did the actual account work match the assigned plan? (Pull HubSpot activity by company owner. Compare to the assigned list.)
- Did the intent tagging predict opportunity creation? (If hot accounts had 3x the opp creation of cold ones, the model works. If not, the signal mix is wrong.)
- Where did pipeline come from versus where it was expected? (If half the pipeline came from accounts that were supposed to be in another AE's patch, your assignment rule is broken or your reps are working off-script.)
I keep a simple HubSpot dashboard for this with four widgets: account activity by owner, opportunity creation by intent tier, pipeline by assigned vs actual owner, win rate by fit band. Half an hour to build, pays back the first time a CRO asks why Q1 missed.
Common pitfalls I keep running into
Pitfall one: the plan assumes 100 percent AE retention. A territory plan that breaks the moment one AE leaves was not a plan. Build the rule, not the assignment. If you can rerun the assignment in a day when someone quits, you are fine.
Pitfall two: treating named accounts as immovable. Strategic accounts are real and deserve special handling. But "I have always owned Microsoft" is not strategy. Set a rule for named accounts (revenue threshold, named by exec sign-off, time-bound assignment) and apply it.
Pitfall three: forgetting to model SDR coverage. If SDRs source half your opportunities, their territory has to match the AE territory. I have seen companies where the SDR books a meeting for an AE who does not own the account. Then it gets reassigned, the prospect gets confused, and the deal stalls. Match the maps or kill the SDR layer. Do not run them out of sync.
Pitfall four: not factoring in deal cycle length and multithreading. If your cycle is 120 days with 6+ stakeholders per deal, you cannot stack 400 active accounts on one AE and expect anything other than ghosted deals. Capacity is a function of complexity, not just count.
Pitfall five: ignoring the comp plan. Territory and comp are the same lever. If two AEs have unequal addressable revenue but the same quota, one of them is being set up to fail. I get into this in detail in the B2B sales comp playbook.
A real example
A 22-person B2B SaaS team I worked with last year had eight AEs and 4,800 named accounts split alphabetically. Yes, alphabetically. The CRO inherited it from a prior CRO and never questioned it.
We ran the four-input model. Findings:
- 4,800 accounts but only 1,840 in fit bands A and B
- 312 accounts in band A or B with hot signals in the last 30 days
- Average AE capacity at current activity load: 240 accounts per quarter
- Quota assumed 580 working accounts per AE
- Gap: 340 accounts per AE were assumed but not worked
We rebuilt the map. Eight AEs split 1,840 fit-A-and-B accounts into 230-account patches with intent rebalancing every quarter. The remaining 2,960 accounts moved to a watchlist worked by the SDR team only when a fresh signal hit.
Three months later, opportunity creation per AE was up 41 percent. Win rate went up 6 points because reps were working accounts they actually had a real chance with. The CRO stopped asking why pipeline was thin. He started asking when we could hire the next AE because the gap analysis showed real coverage room.
Not magic. Just doing the math.
When to build this yourself vs hire help
Honest answer: if you have a RevOps person with bandwidth and clean data, build it yourself. The math is not complicated. The hard parts are the enrichment plumbing, the assignment rule design, and getting the VP Sales to agree to capacity numbers instead of vibes.
If you do not have RevOps in-house and your last territory exercise was a meeting where everyone argued about named accounts, you are better off bringing someone in for a six-week sprint. The output is a one-page plan, a HubSpot configuration, a Clay table, and a refresh cadence. You can run it yourself after that.
Running into the same wall?
Book a free 30-minute audit and I will show you the three gaps I would fix first in your current territory plan.
Book an audit →Frequently asked questions
How often should we redo sales territory planning?
The full TAM scoring exercise happens once a year, usually in November for a January start. The intent refresh and rebalance happens quarterly inside the QBR. If you redo the whole plan more than once a year, you have a planning problem, not a territory problem.
What is the right number of accounts per AE?
For a hybrid model with SDR support, 280 to 400 working accounts per quarter is workable. For a full-cycle AE doing their own outbound, 220 to 280 is the cap. These are not opinions, they come from the capacity math: working days × focus hours × minutes per account.
Should we split by geography, vertical, or account size?
By fit band and intent first, then by vertical or size as a tiebreaker. Geography only matters if you have an in-person motion or strict data residency rules. For SaaS sold remotely, ZIP code is a weak signal.
How does territory planning differ for Series A vs Series B?
At Series A you usually have 2 to 4 AEs and the right move is a flat named-account split with quarterly rebalance. At Series B with 8 to 20 AEs, you need the full four-input model because the gap analysis is what justifies your next round of hiring. The math gets more important as the team gets bigger.
How do we handle existing customer accounts in the plan?
Separate map. Customer accounts go to account managers or customer success, not new-business AEs. Mixing them in the same territory plan is how renewals get dropped and new logo motion gets diluted. I cover the handoff in the sales to CS playbook.
What tools do we actually need to do this well?
A CRM (HubSpot or Salesforce), an enrichment tool (Clay is what I use), and a sheet or BI tool for the planning math. That is it. You do not need a dedicated territory planning platform until you have 50+ sellers. Before that, a clean HubSpot configuration plus a Clay table plus a Google Sheet is enough.
The bottom line
Sales territory planning is coverage math, not a seating chart. If your current plan does not start with TAM, intent, and capacity, it is going to break by Q2 and you are going to spend the next quarter rebuilding it in the dark. Build the math once, refresh quarterly, and the plan stops being a year-end fight and starts being a routine operating decision. That is the work.