Optimize Sales Territories: Pick the Right Model

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

By George James, Co-Founder & CPO

Reconsider geo-led models unless you sell a physical product. Most software companies inherit geography and never revisit it. 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 sales territory model selection 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: Reconsider geo-led models unless you sell a physical product. The sections below turn that position into definitions, alternatives, procedures, examples, controls, and an operating decision.

Working Definitions

• geographic territory: a defined input used when evaluating sales territory model selection.
• named account: a defined input used when evaluating sales territory model selection.
• hybrid territory: a defined input used when evaluating sales territory model selection.
• Segmentation Logic: a defined input used when evaluating sales territory model selection.
• coverage model: a defined input used when evaluating sales territory model selection.

Across BoogieBoard's observed designs, geographic models appear in roughly 25% to 50% of 25- and 100-rep companies, 35% to 60% of 250-plus-rep companies, and 50% to 75% of 1,000-plus-rep organizations. For sales territory model selection, use that observation only for the claim and population it directly supports.

Independent evidence provides a separate check for sales territory model selection: The U.S. Census Bureau publishes business counts by geography, industry, and enterprise size and identifies the data as useful for market research and territory management.

What Is Sales Territory Model Selection?

Territory model selection chooses the organizing rule that best reflects how customers buy and how sellers cover them: geography, named accounts, segment, industry, customer status, or a hybrid. The useful distinction is between data, policy, and judgment. Data describes the accounts and roles. Policy states the repeatable rule. Judgment chooses among legitimate tradeoffs. When those layers are blended in a spreadsheet formula or a private manager request, sales territory model selection becomes difficult to explain and impossible to audit consistently. In sales territory model selection, test the choice against named account, then record any accepted exception in the decision log.

Sales territory model selection is a governed coverage decision, not a label applied after accounts have already moved. It connects geographic territory, named account, and hybrid territory to a defined role and market. The output should tell stakeholders what is being decided, which evidence is allowed, who approves exceptions, and how the result will be operated after launch. The sales territory model selection review is complete only when hybrid territory and the affected account roster tell the same story.

Common Models and Variations: Sales Territory Model Selection

Geography is useful when travel, regulation, language, or local relationships matter. Otherwise it often adds boundaries without improving the buying motion. 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 sales territory model selection review is complete only when hybrid territory 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 sales territory model selection scenario comparable.

geographic territory: The Decision Test

Inherited geography becomes self-justifying: leaders preserve it because it exists, then add exceptions to solve every problem it creates. 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 sales territory model selection scenario comparable.

named account: 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 sales territory model selection, name the approver, the permitted evidence, and the condition that would justify a departure from the rule.

hybrid territory: 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 sales territory model selection summary so named account remains inspectable after approval.

Segmentation 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. Before activating sales territory model selection, show managers the effect on hybrid territory and every downstream rule that depends on it.

coverage model: 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 sales territory model selection, document the effect on geographic territory before the model advances.

Advanced Considerations: Sales Territory Model Selection

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. In sales territory model selection, test the choice against named account, then record any accepted exception in the decision log.

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. The sales territory model selection review is complete only when hybrid territory and the affected account roster tell the same story.

geographic territory: The Decision Test: Review 10

Evaluate each model against service constraints, specialization, account hierarchy, hiring pool, explainability, data quality, and maintenance burden. The strategic question is what the company believes creates a healthy path to market. Translate that belief into measurable Balance Goals, then test it through scenarios. The model is a hypothesis: it should be specific enough to guide a decision and humble enough to be revised when evidence changes. The sales territory model selection review is complete only when hybrid territory and the affected account roster tell the same story.

See Balance in the Planning Workflow

The relevant product workflow is Balance Hybrid Territories by Type. BoogieBoard Scenario Planning keeps the account-level assumptions, tradeoffs, and proposed assignments visible while the team completes that work.

Scenario Results show customer and prospect mix, prospect grade, quarterly ARR, account locks, and rep capacity in one review surface.

hybrid territory: 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 sales territory model selection, name the approver, the permitted evidence, and the condition that would justify a departure from the rule.

Segmentation Logic: The Decision Test 2

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 sales territory model selection summary so named account remains inspectable after approval.

Operating and Governing the Model: Sales Territory Model Selection

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 sales territory model selection decision a source date, an owner, and a condition that would trigger revision.

After activation, monitor assignment gaps, source-data changes, capacity events, and Territory Health. Use defined triggers and review windows instead of constant reshuffling. A territory model should absorb ordinary hiring, departure, and account changes without becoming a new annual reconstruction project. Before activating sales territory model selection, show managers the effect on hybrid territory and every downstream rule that depends on it.

named account: The Decision Test: Review 15

After activation, monitor assignment gaps, source-data changes, capacity events, and Territory Health. Use defined triggers and review windows instead of constant reshuffling. A territory model should absorb ordinary hiring, departure, and account changes without becoming a new annual reconstruction project. Before activating sales territory model selection, show managers the effect on hybrid territory and every downstream rule that depends on it.

geographic territory: The Decision Test: Review 16

Technology should preserve the model, not only the final owner field. Test version control, current-to-future comparison, account-level inspection, locks, scenario assumptions, approvals, effective dates, CRM deployment, and audit history. A faster spreadsheet export is not the same as a governed planning system. For sales territory model selection, document the effect on geographic territory before the model advances.

geographic territory: The Decision Test: Review 18

Measure the components before combining them. Report distributions for geographic territory, named account, and hybrid territory, then show the spread, median, outliers, and acceptable range. A composite score can support comparison, but it should never hide the account attributes and assumptions that produced it. The sales territory model selection review is complete only when hybrid territory and the affected account roster tell the same story.

Use both current-state and future-state views. Report account movement, locked accounts, unassigned records, family splits, vacancies, and quota differences beside Territory Health. Monitor outcomes later, but avoid claiming that attainment alone proves the design was correct; product, market, timing, execution, and quota also affect performance. Use one current-state baseline to keep every sales territory model selection scenario comparable.

Decision Worksheet

Decision	Evidence to inspect	Control
Define the population	geographic territory and comparable roles	Named data owner
Measure the current state	named account and hybrid territory	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

Which sales territory model should we use?

Territory model selection chooses the organizing rule that best reflects how customers buy and how sellers cover them: geography, named accounts, segment, industry, customer status, or a hybrid. Geography is useful when travel, regulation, language, or local relationships matter. Otherwise it often adds boundaries without improving the buying motion. Use the published definitions and complete-territory result instead of relying on one universal benchmark.

When should you change territory models?

Evaluate each model against service constraints, specialization, account hierarchy, hiring pool, explainability, data quality, and maintenance burden. A remote SaaS team replaces state boundaries with segment and time-zone logic. It preserves working-hour coverage without forcing uneven state populations or local hiring. Publish the assumptions so another reviewer can reproduce the answer.

What data is required for sales territory model selection?

For sales territory model selection, assemble governed account data, current assignments, role capacity, and decision evidence for geographic territory, named account, and hybrid territory. 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 sales territory model selection be reviewed?

Review sales territory model selection on the formal planning cadence and whenever the inputs behind geographic territory, named account, and hybrid territory 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 sales territory model selection, define Balance Goals tied to geographic territory, named account, and hybrid territory 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 sales territory model selection, a spreadsheet remains adequate while one owner can preserve geographic territory, named account, and hybrid territory, 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

Reconsider geo-led models unless you sell a physical product. Most software companies inherit geography and never revisit it. 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 sales territory model selection, compare scenarios, and make the account-level tradeoffs visible before activation.