Blog
Published Aug. 6, 2026 by Kevin Davis ยท Updated August 6, 2026
A practical guide for operators responsible for territory potential, with the decisions, evidence, controls, examples, and operating rules needed to make it work.
![]()
A practical guide for operators responsible for territory potential, with the decisions, evidence, controls, examples, and operating rules needed to make it work.
By Kevin Davis, Co-Founder & CEO
5 Key Takeaways
Territory design is hypothesis testing. Potential is the variable you are hypothesising about, so how you define it determines everything downstream. 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 territory potential 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: Territory design is hypothesis testing; Balance Goals are the hypothesis. The sections below turn that position into definitions, alternatives, procedures, examples, controls, and an operating decision.
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 territory potential, use that observation only for the claim and population it directly supports.
Independent evidence provides a separate check for territory potential: Research on commercial territory design treated multiple balance requirements, compactness, contiguity, and feasibility as simultaneous planning criteria.
Point estimates simplify planning but overstate certainty. Ranges and component measures are more honest when data is sparse. The right answer depends on the role and market. Fair does not mean equal across unlike jobs. It means comparable roles are measured by the same published standard, while legitimate differences in motion, capacity, and responsibility receive their own standard. In territory potential, test the choice against Territory Viability, then record any accepted exception in the decision log.
Compare alternatives against the same population and definitions. One option may improve Total Account Potential, another may protect Territory Viability, and a third may reduce disruption. Do not let each option use a different denominator or source date; that turns scenario review into a presentation contest. The territory potential review is complete only when Balance Goal and the affected account roster tell the same story.
Calling every company in TAM potential gives the seller a large number with no usable account path behind it. 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 territory potential review is complete only when Balance Goal and the affected account roster tell the same story.
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 territory potential scenario comparable.
Territory potential estimates the serviceable opportunity available in a defined book over a defined horizon. It is narrower than TAM and should reflect fit, reachability, product relevance, and capacity. 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. For territory potential, name the approver, the permitted evidence, and the condition that would justify a departure from the rule.
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. Keep account-level results beside the territory potential summary so Territory Viability remains inspectable after approval.
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 territory potential summary so Territory Viability remains inspectable after approval.
Decision Note: whitespace
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 territory potential decision a source date, an owner, and a condition that would trigger revision.
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 territory potential, show managers the effect on Balance Goal and every downstream rule that depends on it.
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. For territory potential, document the effect on Total Account Potential before the model advances.
The relevant product workflow is Design Territories with Quota Relativity. BoogieBoard Scenario Planning keeps the account-level assumptions, tradeoffs, and proposed assignments visible while the team completes that work.
A scenario result compares quota-relative territory measures across reps before the proposed design goes live.
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 territory potential, test the choice against Territory Viability, 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 territory potential review is complete only when Balance Goal and the affected account roster tell the same story.
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 territory potential review is complete only when Balance Goal and the affected account roster tell the same story.
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 territory potential scenario comparable.
Compare alternatives against the same population and definitions. One option may improve Total Account Potential, another may protect Territory Viability, and a third may reduce disruption. Do not let each option use a different denominator or source date; that turns scenario review into a presentation contest. For territory potential, name the approver, the permitted evidence, and the condition that would justify a departure from the rule.
The right answer depends on the role and market. Fair does not mean equal across unlike jobs. It means comparable roles are measured by the same published standard, while legitimate differences in motion, capacity, and responsibility receive their own standard. Keep account-level results beside the territory potential summary so Territory Viability remains inspectable after approval.
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 territory potential summary so Territory Viability remains inspectable after approval.
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 territory potential decision a source date, an owner, and a condition that would trigger revision.
Decision Note: SAM 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. Give the territory potential decision a source date, an owner, and a condition that would trigger revision.
Define the serviceable population, choose account-level potential inputs, calculate ranges, sum to the territory, and compare the result with quota and workload.
A $10M theoretical market becomes $6M serviceable after fit and geography filters and $4M realistically coverable after seller-capacity constraints.
| Decision | Evidence to inspect | Control |
|---|---|---|
| Define the population | Total Account Potential and comparable roles | Named data owner |
| Measure the current state | Territory Viability and Balance Goal | 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 |
Review territory potential at three levels. At the company level, reconcile market coverage, capacity, quota, and disruption. At the territory level, compare the published goals, locked-account burden, vacancies, and workload. At the account level, inspect hierarchy, fit, ownership, open work, and the reason for every exception. These views should use the same scenario and source date.
This review pass emphasizes Total Account Potential. Require reviewers to state whether feedback is a data correction, a policy challenge, or a preference. Corrections update the evidence. Policy challenges go to the named approver. Preferences remain visible but do not silently change the model. This discipline keeps Total Account Potential, Territory Viability, and Balance Goal coherent through approval and activation.
Review territory potential at three levels. At the company level, reconcile market coverage, capacity, quota, and disruption. At the territory level, compare the published goals, locked-account burden, vacancies, and workload. At the account level, inspect hierarchy, fit, ownership, open work, and the reason for every exception. These views should use the same scenario and source date.
This review pass emphasizes Territory Viability. Require reviewers to state whether feedback is a data correction, a policy challenge, or a preference. Corrections update the evidence. Policy challenges go to the named approver. Preferences remain visible but do not silently change the model. This discipline keeps Total Account Potential, Territory Viability, and Balance Goal coherent through approval and activation.
Review territory potential at three levels. At the company level, reconcile market coverage, capacity, quota, and disruption. At the territory level, compare the published goals, locked-account burden, vacancies, and workload. At the account level, inspect hierarchy, fit, ownership, open work, and the reason for every exception. These views should use the same scenario and source date.
This review pass emphasizes Balance Goal. Require reviewers to state whether feedback is a data correction, a policy challenge, or a preference. Corrections update the evidence. Policy challenges go to the named approver. Preferences remain visible but do not silently change the model. This discipline keeps Total Account Potential, Territory Viability, and Balance Goal coherent through approval and activation.
Territory potential estimates the serviceable opportunity available in a defined book over a defined horizon. It is narrower than TAM and should reflect fit, reachability, product relevance, and capacity. Point estimates simplify planning but overstate certainty. Ranges and component measures are more honest when data is sparse. Use the published definitions and complete-territory result instead of relying on one universal benchmark.
Define the serviceable population, choose account-level potential inputs, calculate ranges, sum to the territory, and compare the result with quota and workload. A $10M theoretical market becomes $6M serviceable after fit and geography filters and $4M realistically coverable after seller-capacity constraints. Publish the assumptions so another reviewer can reproduce the answer.
For territory potential, assemble governed account data, current assignments, role capacity, and decision evidence for Total Account Potential, Territory Viability, and Balance Goal. Date the sources and publish the definitions so another reviewer can reproduce the result and separate a factual correction from a policy exception.
Review territory potential on the formal planning cadence and whenever the inputs behind Total Account Potential, Territory Viability, and Balance Goal 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.
For territory potential, define Balance Goals tied to Total Account Potential, Territory Viability, and Balance Goal 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.
For territory potential, a spreadsheet remains adequate while one owner can preserve Total Account Potential, Territory Viability, and Balance Goal, 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.
Territory design is hypothesis testing. Potential is the variable you are hypothesising about, so how you define it determines everything downstream. Use the sequence above to keep the decision governed, evidence-based, and inspectable at both the account and territory levels.
Watch practical territory-design workflows on the BoogieBoard YouTube channel.
Schedule a Live Demo to model territory potential, compare scenarios, and make the account-level tradeoffs visible before activation.