How to build a sales territory plan

Segment the account base

Start with a clean account list, not a map. Pull every account you could sell to, including current customers, closed-lost accounts and untouched prospects, and strip duplicates before anything else. A territory plan built on a list with 8% duplicates will produce books that look balanced and are not. Then segment. The useful segmentation cuts are the ones that change how a rep sells: company size band, industry, existing customer versus new logo, and buying motion (self-serve, inside sales, field). Geography is a segmentation cut only when travel or language actually matters. For a fully remote inside sales team, splitting by US state adds a constraint without adding value, and it is the single most common reason books end up lopsided. Assign every account a tier at this stage. Three tiers is enough for most teams: strategic accounts that get a named plan, core accounts that get a standard cadence, and long-tail accounts that get campaigns rather than individual attention. Write the tier rules down as thresholds, not adjectives, so a new account can be tiered by anyone without a meeting. Our account tiering model gives you the scoring sheet and thresholds to copy. Expect 10% to 20% of accounts to be unclassifiable on the first pass because of missing firmographics. Park those in a holding bucket and fix the data rather than guessing, because a mis-tiered account distorts both the coverage math and the quota that follows it.

Size potential per account

Balance means nothing until you have a number per account. Account count is a bad proxy because 40 enterprise accounts and 40 small businesses are not the same book. The usable measure is potential annual contract value: what this account could spend with you at full adoption, not what it spends today. Build it from something you can defend. Employee count times a per-seat price is crude but repeatable. Better inputs are the number of seats in the buying department, the number of sites, or spend on the incumbent you replace. Take the median of your closed-won deals in each segment over the last four quarters and use it as the base, then adjust for size band. Do not hand-tune individual accounts at this stage, because that is where sandbagging enters the plan. For existing customers, potential is expansion headroom: total potential minus current spend. A customer already at 90% adoption belongs in a lower workload tier than its logo suggests, and treating it as a whitespace account is how account managers end up with unreachable numbers. Record two columns against every account: potential ACV and current ACV. The gap between them is what territory design is actually distributing. Cross-check the total. If your whole addressable list sums to a potential ten times your company target, either the potential model is inflated or your segmentation is too loose. Sizing at the account level also feeds sales capacity planning later, so use the same numbers in both exercises rather than building two models that disagree.

Set balance criteria

Decide what balanced means before you draw a single territory, and write it as a rule with a tolerance band. Three criteria cover most teams. First, potential: each book should hold roughly equal potential ACV, usually within plus or minus 10%. Second, workload: accounts carry different servicing costs, so weight them. A common weighting is three units for a tier one account, 1.5 for tier two and 0.5 for tier three, then equalise total units per rep. Third, disruption: how many accounts change hands compared with last year. A plan that is perfectly balanced on paper and moves 70% of accounts will cost you more in lost relationships than it gains in fairness. Cap churn at 20% to 30% of accounts per rep unless you are deliberately resetting the model. These three criteria fight each other. You cannot get equal potential, equal workload and low disruption at the same time, so rank them and say so out loud. Most growth-stage teams should rank potential first, workload second, disruption third in a year they are adding headcount, and reverse the order in a flat year. Also set your constraints: minimum accounts per rep, maximum travel radius for field roles, named accounts that cannot move for contractual or relationship reasons, and any language or timezone requirements. Feed those into the territory balancing worksheet so the tolerance checks run automatically rather than by eye. The terminology here is worth agreeing on across sales, finance and RevOps before you present anything, because territory planning means different things to a CFO and a regional VP.

A worked example

Take 1,200 accounts and eight account executives. Tiering puts 120 accounts in tier one at $60,000 potential ACV each, 380 in tier two at $25,000, and 700 in tier three at $8,000. Potential totals $7.2M, $9.5M and $5.6M, so $22.3M across the list. Divide by eight reps and the target per book is $2.79M of potential. Now the workload check. At three units for tier one, 1.5 for tier two and 0.5 for tier three, the list carries 360 plus 570 plus 350, which is 1,280 workload units, or 160 units per rep. A book of 15 tier-one, 48 tier-two and 86 tier-three accounts scores 45 plus 72 plus 43, exactly 160 units, and carries $900,000 plus $1.2M plus $688,000, which is $2.788M of potential. That book passes both tests. A book with 22 tier-one accounts and few others would hit the potential target at $2.8M but score 66 units on tier one alone and finish well under 160, which means that rep is under-loaded and someone else is carrying their servicing hours. Then sanity-check quota coverage. If the company target is $9.4M of new ARR, each rep carries $1.175M against $2.79M of potential, a ratio of 2.37 to one. Set a floor, say two to one, and any book below it is not a quota problem, it is a territory problem. In this example a rep at $2.1M of potential lands at 1.79 and needs accounts moved in before quotas are published, not a carve-out after the year starts.

Assign accounts to reps

Assignment is where politics arrive. Run it in two passes. The first pass is mechanical: let the rule set or the tool allocate every account against your criteria with no names attached, so you see what a balanced structure looks like before anyone defends their book. The second pass is human: apply the named exceptions you agreed in the constraints list, then rebalance the remainder to bring every book back inside tolerance. Keep the exception list short and documented. Every exception you grant has to be absorbed by someone else. Match reps to books on evidence rather than seniority. Look at win rate by segment, average deal size and cycle length per rep over the last four quarters. A rep who closes 34% in mid-market and 11% in enterprise should not receive the enterprise-heavy book because they have been there longest. Where two reps are close, prefer continuity and leave relationships intact. Publish the assignment with the numbers attached. Every rep should see their own potential ACV, workload units and account count next to the team average, and the criteria used. Books handed out without the math behind them get relitigated for a quarter. Then decide how new accounts entering the database get assigned, because a static plan decays within weeks. That rule belongs in your lead routing setup, not in a manager's head, and it should follow the same tier and segment logic the plan uses. Write the whole assignment down in a sales territory plan template so the structure, criteria and exceptions live in one document that survives the person who built it.

Write rules of engagement

Rules of engagement are what stop territory disputes from reaching a VP. They answer the questions the assignment map cannot. Who owns an account when a buyer from a different division at a different site raises their hand? What happens when a prospect in one rep's book gets acquired by a company in another rep's book? Who owns an inbound lead that matches an account nobody has touched in nine months? How long does a rep hold an unworked named account before it returns to the pool? Set explicit answers with dates and thresholds. A common structure: the account owner at the parent domain owns all subsidiaries unless the subsidiary is separately tiered; acquisitions transfer at the next quarter boundary with the in-flight deal staying with the originating rep; inbound leads route to the account owner regardless of persona; and named accounts with no logged activity for two quarters return to the unassigned pool. Then define the split rules. If two reps genuinely worked a deal, decide in advance whether credit splits 50-50, follows the account owner, or follows the opportunity creator, and make sure the compensation system can actually process whatever you choose. Rules that the comp tool cannot execute become manual adjustments and manual adjustments become disputes. Name the arbiter. One person, usually the RevOps lead, decides contested cases within a fixed window, say five business days, and the decision is final for the fiscal year. Our rules of engagement template covers the standard cases, and the sales compensation software category is where to look if your current system cannot handle splits cleanly.

Handle in-flight pipeline

The step that breaks most rollouts is what happens to open opportunities on the day the map changes. Get it wrong and reps spend January arguing about deals instead of working them. Pull every open opportunity and sort it by stage and close date before the plan goes live. The default that works for most teams: opportunities past the point of a confirmed buying process stay with the originating rep through close, with the new owner added as a collaborator on the account. Earlier-stage opportunities transfer with the account, because there is little relationship equity to lose and the new owner needs pipeline. Draw the line at a specific opportunity stage instead of a vague sense of momentum, so the rule can be applied by query rather than by judgement. Set an outer boundary. An inherited deal that has not closed within one full sales cycle past the transition date transfers anyway, otherwise reps hold stale deals to protect commission. Commission needs its own decision made at the same time. If a deal stays with the old owner, the new owner usually gets no credit, which means their quota should reflect the pipeline they did not receive. Adjust the ramp or the first-quarter number rather than pretending the gap does not exist. Finally, plan the handover mechanics. Every transferring opportunity needs a short written handoff covering the contacts, the current stage, next steps and any commitments made, plus a joint call with the buyer where the relationship is worth keeping. Check pipeline coverage per rep after the transfers, not before, because the transfer rules can leave one book well short even when the account math balanced.

Lock the plan before quota

Territories come first, quotas second. Setting quota before the map is final guarantees a renegotiation, because every accepted territory change alters the potential behind somebody's number. Publish a freeze date, communicate it, and hold it. A workable sequence for a January fiscal year: draft territories in October, review with regional leaders through early November, freeze the map by 1 December, publish quotas mid-December, and open the year with plan documents signed. That leaves a real window for appeals while keeping quota publication late enough to reflect the final map. Run a formal appeal window of one to two weeks against the frozen draft. Require every appeal to name the criterion it fails, potential, workload or an agreed constraint, with the numbers attached. Appeals phrased as preference get no hearing. Expect to accept a handful and reject most, and publish the outcomes so the process looks the same to everyone. Before you sign off, run the coverage test again on the final map. Every book should sit inside your tolerance on potential and workload, and every rep's quota should sit under your coverage floor against their book's potential. If one book fails, fix that book rather than lowering everyone's number. Then set a review cadence. Quarterly reviews catch drift from new logos, churn and headcount changes without reopening the whole plan, and an annual redesign resets the structure. Publish both dates with the plan so reps know a mid-year carve-out is not on the table. Comparing the tooling that supports this cycle is worth doing before the next annual plan, and the sales planning software category covers the platforms that model capacity and coverage together.

Tools worth paying for

Spreadsheets handle a first territory plan well. They stop working when the rebalance takes longer than the window you have to run it, when three people maintain conflicting copies, or when assignment rules have to execute continuously in the CRM rather than once a year. Named options and what they cost, as of September 2026. Xactly AlignStar quotes every deal and publishes no list price, so ask for the standalone figure and the bundled figure alongside Xactly Plan or Incent. Salesforce Enterprise Territory Management carries no separate fee on qualifying Sales Cloud editions, and Salesforce lists the Sales Planning add-on at $75 per user per month billed annually. Salesforce's own documentation puts Enterprise edition at up to 1,000 territories per model, with Performance and Unlimited reaching 20,000 through support. Anaplan and Pigment both quote custom, and Anaplan buyers should note that Vendr puts implementation services at 50% to 150% of the first-year subscription. For CRM-native setups, Zoho lists Enterprise at $40 per user per month billed annually with territory management unavailable below that tier, HubSpot lists Sales Hub Professional at $90 per seat per month annually plus a required $1,500 onboarding fee, and Microsoft lists Dynamics 365 Sales Enterprise at $105 per user per month paid yearly. Field teams have published prices: Badger Maps is $58 per user per month on annual billing, with Lead Routing at $16 per territory and Align at $20 per territory on a five-territory minimum, while SPOTIO quotes custom on plans that start at five users. The full territory management software category lists the rest with the same pricing detail.

When not to buy

Skip the software if your account data is not ready. Every planning platform assigns accounts using the fields already in your CRM, so missing industry codes, unresolved parent-child hierarchies and duplicate accounts produce a confident-looking plan built on bad inputs. Fix the data first and the spreadsheet plan will already improve. Skip it if you have fewer than about ten reps and one selling motion. At that size a balanced plan takes an afternoon and the annual licence buys a problem you do not have. Skip it if nobody owns the model after purchase. These tools need a person who maintains hierarchies, assignment rules and the balance criteria every quarter. Bought without that owner, they decay into an expensive record of last year's map. What to test in a demo, using your own account file, not the vendor's: load 500 of your accounts and ask the vendor to build one balanced book live. Ask what happens when an account's tier changes mid-quarter, whether the change propagates to ownership automatically or waits for a run. Ask how the tool handles overlays, where a specialist and a generalist both touch the same account. Ask how assignments write back to the CRM, whether that write-back is one-way or two-way, and what happens when someone edits an owner field directly in the CRM. Ask to see the audit trail for a single account's ownership history. Then ask for two references at your headcount and selling motion, and ask those references how long their last rebalance took start to finish. That number tells you more than any feature list.

Buyer checklist

• Deduplicate the account list and resolve parent-child hierarchies before any segmentation work starts.
• Assign every account a tier using written numeric thresholds, not judgement calls.
• Record potential ACV and current ACV as separate columns against every account.
• Rank your balance criteria (potential, workload, disruption) and publish the ranking with the plan.
• Run a mechanical assignment pass with no rep names attached before applying any exceptions.
• Cap account churn per rep at 20% to 30% unless you are deliberately resetting the model.
• Set the in-flight pipeline rule at a named opportunity stage, with an outer transfer deadline.
• Freeze the map on a published date and publish quotas only after the freeze.
• Check every book against the quota coverage floor and fix the failing book, not the company number.
• Book the quarterly review and annual redesign dates before the plan goes live.

Related