Sales Territory Plan Sample for 2026

A practical guide for operators responsible for a finished sales territory plan, with the decisions, evidence, controls, examples, and operating rules needed to make it work.

By Kevin Davis, Co-Founder & CEO

A complete worked plan for a fifty-rep SaaS team, with the numbers filled in and the tradeoffs named. That position is useful only when the planning team can translate it into inputs, decisions, controls, and a result the field can understand.

BoogieBoard treats a finished sales territory plan as part of a governed change process. The model must connect market strategy with account-level evidence, productive capacity, explicit decision rights, and controlled activation. The objective is not to remove judgment. It is to make judgment visible and repeatable.

The central position is: Lock before you model. The sections below turn that position into definitions, alternatives, procedures, examples, controls, and an operating decision.

Working Definitions

• Balance Goal: a measurable objective for healthy opportunity, quality, workload, or continuity.
• Account Locking Criteria: the published rules for assignments that should not move.
• Territory Logic: the rules that determine where accounts and roles belong.
• Scenario: one complete current-state or proposed territory design.
• Territory Health: the measured condition of a complete territory against its published goals.

BoogieBoard's observed prospect books range from 1 to 15 accounts for strategic AEs to roughly 250 to 1,000 for SMB AEs. Those ranges are context, not quotas: role, segment definition, service model, and account quality determine whether a book is workable. For a finished sales territory plan, use that observation only for the claim and population it directly supports.

Independent evidence provides a separate check for a finished sales territory plan: Research in Psychology & Marketing examined how adjustments for territory difficulty affect perceptions of performance-evaluation fairness and usefulness.

Core Components: A Finished Sales Territory Plan

A finished territory plan contains the business objective, 50-rep roster, role structure, segment logic, Balance Goals, locks, scenarios, decision record, activation plan, and governance. Document inputs and outputs separately. Inputs include account attributes, hierarchy, current assignments, opportunities, customer obligations, capacity, and quota. Outputs include the territory roster, summary health measures, account-level changes, exception records, and activation instructions. That separation lets reviewers challenge an assumption without rebuilding the entire design. In a finished sales territory plan, test the choice against Account Locking Criteria, then record any accepted exception in the decision log.

A complete model needs a population, a measurable objective, a source of truth, an owner, an acceptable range, and an effective date. Balance Goal describes one part of the decision; Account Locking Criteria and Territory Logic keep it connected to capacity and execution. Missing any one of these components pushes the unresolved choice downstream, where it usually appears as an account-level exception. The a finished sales territory plan review is complete only when Territory Logic and the affected account roster tell the same story.

Common Models and Variations: A Finished Sales Territory Plan

Worked numbers make assumptions inspectable but are examples, not benchmarks for every SaaS company. The model in this subsection is useful only when its organizing rule matches the selling motion. Compare options by opportunity, workload, continuity, explainability, and maintenance burden. A structure that looks simple at launch can create expensive exceptions when accounts change segment, sellers leave, or related companies need coordinated coverage. The a finished sales territory plan review is complete only when Territory Logic and the affected account roster tell the same story.

No model removes judgment. Geographic, named-account, segment, industry, customer, and hybrid structures each solve a different constraint. Use the fewest logical layers that express the strategy, then state where a deliberate override is allowed. Complexity should correspond to a real customer or operating need, not inherited convention. Use one current-state baseline to keep every a finished sales territory plan scenario comparable.

Balance Goal: The Decision Test

A plan that ends with a roster but omits rules, evidence, transition, and review is only an assignment file. A practical test is to pick one surprising account and trace it end to end. Explain why it is in the segment, why it belongs in the territory, whether it is locked, which goals it affects, and what happens when the seller changes. If the answer requires several private spreadsheets, the model is not yet governed. Use one current-state baseline to keep every a finished sales territory plan scenario comparable.

Account Locking Criteria: The Decision Test

Use this module to make the hidden decision explicit. State the role, population, evidence, rule, exception path, and operating consequence. The objective is not a perfectly clean model; it is a model whose compromises are visible enough to approve, communicate, and improve. For a finished sales territory plan, name the approver, the permitted evidence, and the condition that would justify a departure from the rule.

Territory Logic: The Decision Test

A practical test is to pick one surprising account and trace it end to end. Explain why it is in the segment, why it belongs in the territory, whether it is locked, which goals it affects, and what happens when the seller changes. If the answer requires several private spreadsheets, the model is not yet governed. Keep account-level results beside the a finished sales territory plan summary so Account Locking Criteria remains inspectable after approval.

Scenario: The Decision Test

Use this module to make the hidden decision explicit. State the role, population, evidence, rule, exception path, and operating consequence. The objective is not a perfectly clean model; it is a model whose compromises are visible enough to approve, communicate, and improve. Give the a finished sales territory plan decision a source date, an owner, and a condition that would trigger revision.

Territory Health: The Decision Test

A practical test is to pick one surprising account and trace it end to end. Explain why it is in the segment, why it belongs in the territory, whether it is locked, which goals it affects, and what happens when the seller changes. If the answer requires several private spreadsheets, the model is not yet governed. Before activating a finished sales territory plan, show managers the effect on Territory Logic and every downstream rule that depends on it.

Balance Goal: The Decision Test 2

Use this module to make the hidden decision explicit. State the role, population, evidence, rule, exception path, and operating consequence. The objective is not a perfectly clean model; it is a model whose compromises are visible enough to approve, communicate, and improve. For a finished sales territory plan, document the effect on Balance Goal before the model advances.

Calculating and Testing Finished Sales Territory Plan

The sample selects three primary goals, locks 8% of accounts for active work, compares a low-disruption and a higher-equity scenario, and records why leadership chooses the latter. Create three scenarios. Scenario A minimizes movement, Scenario B minimizes variance on the primary goal, and Scenario C protects continuity while improving the two largest outliers. Compare complete territories after qualifying locks return. Select the scenario whose residual imbalance leadership is prepared to explain and operate. In a finished sales territory plan, test the choice against Account Locking Criteria, then record any accepted exception in the decision log.

Assume six comparable territories cover 900 serviceable accounts. A count-only split begins at 150 accounts each. The team then measures Balance Goal, Account Locking Criteria, and Territory Logic; one territory holds 28% of high-potential accounts and another carries twice the near-term workload. The worked answer is not to force identical counts. It is to publish the priority, range, and tradeoff. The a finished sales territory plan review is complete only when Territory Logic and the affected account roster tell the same story.

Worked Example 2: A Decision You Can Reproduce

Use a 30-AE, 10-BDR, and 10-customer-role model; define comparable populations, prebuild vacancies, and approve account and role assignments together. Assume six comparable territories cover 900 serviceable accounts. A count-only split begins at 150 accounts each. The team then measures Balance Goal, Account Locking Criteria, and Territory Logic; one territory holds 28% of high-potential accounts and another carries twice the near-term workload. The worked answer is not to force identical counts. It is to publish the priority, range, and tradeoff. The a finished sales territory plan review is complete only when Territory Logic and the affected account roster tell the same story.

Create three scenarios. Scenario A minimizes movement, Scenario B minimizes variance on the primary goal, and Scenario C protects continuity while improving the two largest outliers. Compare complete territories after qualifying locks return. Select the scenario whose residual imbalance leadership is prepared to explain and operate. Use one current-state baseline to keep every a finished sales territory plan scenario comparable.

Worked Example 3: A Decision You Can Reproduce

Create three scenarios. Scenario A minimizes movement, Scenario B minimizes variance on the primary goal, and Scenario C protects continuity while improving the two largest outliers. Compare complete territories after qualifying locks return. Select the scenario whose residual imbalance leadership is prepared to explain and operate. Use one current-state baseline to keep every a finished sales territory plan scenario comparable.

Assume six comparable territories cover 900 serviceable accounts. A count-only split begins at 150 accounts each. The team then measures Balance Goal, Account Locking Criteria, and Territory Logic; one territory holds 28% of high-potential accounts and another carries twice the near-term workload. The worked answer is not to force identical counts. It is to publish the priority, range, and tradeoff. For a finished sales territory plan, name the approver, the permitted evidence, and the condition that would justify a departure from the rule.

See Scenario Planning in the Planning Workflow

The relevant product workflow is Manage Territory Scenarios in BoogieBoard. BoogieBoard Scenario Planning keeps the account-level assumptions, tradeoffs, and proposed assignments visible while the team completes that work.

BoogieBoard keeps current and future territory scenarios separate so teams can model changes before activation.

Worked Example 4: A Decision You Can Reproduce

Create three scenarios. Scenario A minimizes movement, Scenario B minimizes variance on the primary goal, and Scenario C protects continuity while improving the two largest outliers. Compare complete territories after qualifying locks return. Select the scenario whose residual imbalance leadership is prepared to explain and operate. Keep account-level results beside the a finished sales territory plan summary so Account Locking Criteria remains inspectable after approval.

Operating and Governing the Model: A Finished Sales Territory Plan

Governance begins with explicit decision rights. One Driver runs the process, one Approver chooses the final tradeoff, Contributors supply evidence, and Informed stakeholders receive the result. Publish the review cadence, correction path, exception authority, and source of truth with the approved roster. Give the a finished sales territory plan decision a source date, an owner, and a condition that would trigger revision.

Start With the Business Objective

The control at this stage is a decision log. Separate factual corrections from policy exceptions, preserve rejected alternatives, and attach an effective date. For the planning team, the practical test is whether another informed person could reproduce the result from the same data and rules without relying on private context. Before activating a finished sales territory plan, show managers the effect on Territory Logic and every downstream rule that depends on it.

Define Roles and Comparable Populations

Define Roles and Comparable Populations means producing one inspectable decision before advancing. Name the input, owner, output, and approval. Keep the current state as a baseline, and record assumptions that could change the result. This dependency order prevents a late preference from rewriting earlier definitions without anyone seeing the cost. For a finished sales territory plan, document the effect on Balance Goal before the model advances.

Validate Account and Capacity Data

The control at this stage is a decision log. Separate factual corrections from policy exceptions, preserve rejected alternatives, and attach an effective date. For the planning team, the practical test is whether another informed person could reproduce the result from the same data and rules without relying on private context. In a finished sales territory plan, test the choice against Account Locking Criteria, then record any accepted exception in the decision log.

Set Balance Goals and Acceptable Variance

Set Balance Goals and Acceptable Variance means producing one inspectable decision before advancing. Name the input, owner, output, and approval. Keep the current state as a baseline, and record assumptions that could change the result. This dependency order prevents a late preference from rewriting earlier definitions without anyone seeing the cost. The a finished sales territory plan review is complete only when Territory Logic and the affected account roster tell the same story.

Decision Worksheet

Decision	Evidence to inspect	Control
Define the population	Balance Goal and comparable roles	Named data owner
Measure the current state	Account Locking Criteria and Territory Logic	Source date and baseline
Choose the tradeoff	Scenario comparison and complete Territory Health	Recorded approver
Activate the result	Account roster, changes, quota, and transition rules	Effective date and correction path

Frequently Asked Questions

What does a finished territory plan look like?

A finished territory plan contains the business objective, 50-rep roster, role structure, segment logic, Balance Goals, locks, scenarios, decision record, activation plan, and governance. Worked numbers make assumptions inspectable but are examples, not benchmarks for every SaaS company. Use the published definitions and complete-territory result instead of relying on one universal benchmark.

Can I see a territory plan example?

Use a 30-AE, 10-BDR, and 10-customer-role model; define comparable populations, prebuild vacancies, and approve account and role assignments together. The sample selects three primary goals, locks 8% of accounts for active work, compares a low-disruption and a higher-equity scenario, and records why leadership chooses the latter. Publish the assumptions so another reviewer can reproduce the answer.

What data is required for a finished sales territory plan?

For a finished sales territory plan, assemble governed account data, current assignments, role capacity, and decision evidence for Balance Goal, Account Locking Criteria, and Territory Logic. Date the sources and publish the definitions so another reviewer can reproduce the result and separate a factual correction from a policy exception.

How often should a finished sales territory plan be reviewed?

Review a finished sales territory plan on the formal planning cadence and whenever the inputs behind Balance Goal, Account Locking Criteria, and Territory Logic change materially. Keep customer and pipeline ownership stable between reviews; reopen the model when strategy or new evidence changes the decision, not merely because a manager prefers a different assignment.

How should Balance Goals and account locks work together?

For a finished sales territory plan, define Balance Goals tied to Balance Goal, Account Locking Criteria, and Territory Logic before applying locks. Then publish Account Locking Criteria, lock only qualifying accounts, optimize the movable book, and score the complete territory so locked burden and residual imbalance remain visible.

When should a spreadsheet be replaced with a planning system?

For a finished sales territory plan, a spreadsheet remains adequate while one owner can preserve Balance Goal, Account Locking Criteria, and Territory Logic, plus versions, account detail, approvals, and deployment without manual reconciliation obscuring the rule. Move to a planning system when scenario volume, collaboration, or audit work overwhelms the decision itself.

In Summary

A complete worked plan for a fifty-rep SaaS team, with the numbers filled in and the tradeoffs named. Use the sequence above to keep the decision governed, evidence-based, and inspectable at both the account and territory levels.

See Territory Planning in Practice

Related Content

• Balance Goals: The Complete Guide to Territory Equity
• Designing Books of Business: The Complete Guide
• How to Communicate a New Territory Plan Effectively

Schedule a Live Demo to model a finished sales territory plan, compare scenarios, and make the account-level tradeoffs visible before activation.