Cut fair territories, settled before the disputes start.
“How do I cut territories so no rep gets a dead patch and nobody fights over inbound?”
The segmentation, the account distribution, a balance check across every rep, and the rules for disputes and inbound.
What this skill does
Takes your account universe and cuts it into territories that are balanced on the thing that matters, usually potential, not just account count. It picks the segmentation axis, distributes accounts across reps, runs a fairness check so no rep is handed a dead patch, and writes the dispute and inbound rules up front so ownership is decided before the deal, not during it.
Inputs
- Works today with: a list of accounts with a size or potential signal (employees, revenue, tier), region or segment, and current owner if any. Paste it or upload a CSV.
- More powerful connected to a CRM: it reads owners, open pipeline, and won history so balance accounts for work already in flight.
- Sharper with an enrichment or firmographic source: it fills missing size and industry so the segmentation is not guesswork.
- Sharper with a data warehouse: it weights territories by modeled potential, not a single raw field.
How it works
- 1The segmentation
Pick the axis that matches how you actually sell. Geography suits high-volume field motions. Named accounts suit enterprise. Industry suits a vertical play. State the axis, then hold it consistent, because a book that is half geo and half named is a book nobody can be measured on.
- 2The account distribution
Assign accounts to reps against the axis, then sort by POTENTIAL so the strong and weak accounts are spread, not clumped. A territory that is all logos and no potential is a punishment. Keep each book under MAX_ACCOUNTS so coverage is real, not a name on a list.
- 3The balance check across reps
Sum POTENTIAL per rep and compare to the mean. Flag any book outside TOLERANCE. Balance on potential, not on account count, because 60 strong accounts and 60 dead ones are not the same job. Show the spread so the split survives the room.
- 4The rules for disputes and inbound
Write these before go-live. Inbound: a new lead routes by INBOUND_RULE, usually domain match to an owned account first, then territory. Disputes: name the tie-breaker, usually first meaningful activity, and the escalation path. Held and no-owner accounts go to a house pool with a claim rule. The point is that ownership is decided by policy, not by whoever shouts first.
Output format
TERRITORY DESIGN · 6 reps · illustrative
Rep Accounts Potential idx vs mean Flag
North 52 104 +4% ok
South 48 98 -2% ok
East 61 131 +31% over, rebalance
West 39 71 -29% thin, add accounts
Central 50 100 0% ok
House 44 - - round-robin pool
Rules set:
1. Inbound routes on domain match, then territory. No manual grabs.
2. Contested account goes to first meaningful activity, RevOps breaks ties.
3. East is 31% over the mean. Move ~8 accounts to West before launch.
Tips
- Balance is checked on potential, never on raw account count alone.
- Every rep book is shown against the mean with the spread named, not asserted "fair."
- Inbound and dispute rules are written and dated before assignments go live.
- No account is left with two owners or none, the overlap and orphan lists are shown.
Walk into the forecast call with a number you can defend.
Sorts each deal into commit, best-case, or pipeline by evidence, flags one risk, and scripts what to press each rep on.
Run a pipeline review that finds problems, not recites them.
Coverage vs target, stage aging, week-over-week movement, stuck deals, and the question to ask per deal.