Skip to content

Blog

Balance sales territories by opportunity and workload

Equal account counts can create very unequal jobs.

4 min read
Balance potential against coverage work. Four unequal territory parcels have different opportunity density, beside a workload gauge. No real geography or account data is shown.

Two territories each contain 120 accounts and carry the same target. One is a compact group of established buyers with clear ownership. The other contains subsidiaries, uncertain fits and several resource-intensive evaluations. The territory sheet looks balanced because it counts the thing that is easiest to count.

Balance territories by the opportunity they can plausibly support and the work required to cover them. Account count, historical revenue and estimated potential each reveal part of the picture. None is sufficient alone. RevOps should make those dimensions visible, then help leadership decide whether the imbalance calls for reassignment, different support or a more realistic expectation.

Keep potential and workload on separate axes

Potential asks what relevant business could exist in the territory. Workload asks what the team must do to investigate, win and serve it. A territory can score high on both. Combining them into one weighted score too early can hide the fact that an attractive market exceeds the assigned team’s capacity.

Use potential estimates that fit the available evidence. Distinguish known commercial opportunities from accounts that merely resemble previous buyers. Show the basis for any estimated opportunity amount, including what is unknown. A large employer is not automatically a large attainable deal, and last year’s bookings may reflect a seller’s work or a one-time purchase rather than a repeatable territory advantage.

For workload, identify the meaningful service units: active evaluations, account-development work, renewal coordination and travel or specialist requirements where relevant. Avoid treating every CRM account as an equally demanding unit. The purpose is to understand the job, not to create an elaborate model that cannot survive a manager’s questions.

Compare two fictional territories

Imagine North has 120 named accounts, including 20 active opportunities that usually require one seller-led working session each month. South also has 120 accounts, but 12 of its active opportunities require two working sessions plus specialist coordination. For this example, North’s direct monthly session load is 20; South’s is 24 before coordination time. These are illustrative inputs, not productivity standards.

North also has 40 accounts with credible fit evidence and no current buying project. South has 70 that have not been researched sufficiently to establish fit. Calling South’s larger unworked pool “more potential” would reward uncertainty. Classify the research gap separately and estimate the effort needed to resolve it.

The operating response need not be a territory swap. Leadership might give South temporary research support, reduce simultaneous evaluations or narrow the target list. If the underlying potential is genuinely greater and capacity remains inadequate, a split may make sense. The analysis should expose the choice rather than predetermine it.

Ask whether a boundary change solves the actual problem

A territory can underperform because its opportunity is weak, coverage is insufficient, the offer does not fit, or the team is executing poorly. Moving accounts addresses only some of those conditions. It can also disrupt relationships and consume transition capacity.

Before redrawing boundaries, identify the constraint with frontline managers. If specialist availability limits progress across both territories, redistributing sellers may simply relocate the queue. If customer ownership is unclear across subsidiaries, an account-hierarchy policy may be the prerequisite. If the issue is a concentrated cluster of active deals, temporary support may be less disruptive than a permanent redesign.

Use a small set of alternative allocations. For each, show opportunity evidence, expected work, seller availability and affected live commitments. Include a “keep boundaries, change support” option. A comparison that only offers different ways to move accounts assumes the answer before the review begins.

Explain fairness without promising identical outcomes

A defensible territory plan gives sellers a credible opportunity to perform under the business’s strategy. It cannot make markets, timing and buyer behavior identical. Be explicit about which differences the company intends to compensate for through capacity, coverage or target-setting decisions.

Keep territory design separate from compensation interpretation. The appropriate leaders own any target or credit decisions. RevOps should preserve the plan version and effective date so later performance analysis can distinguish the assignment people worked from the one currently visible in the CRM.

After a redesign, monitor the assumptions that justified it. Did the research reveal the expected fit? Did the support remove the bottleneck? Were live commitments transferred successfully? Early booking differences alone are an incomplete verdict when buying cycles span several months.

Use the current context, then plan the transition

RevTech’s Customer Context can help assemble connected account, ownership and opportunity information for review. Its Quotas and Territories experience is currently presented as Coming Soon. This article’s allocation framework is a management method, not an automated territory-design capability.

Once leadership chooses an allocation, use the existing account-reassignment guidance to protect customer continuity. Design and transfer are separate decisions. The territory becomes useful when the assigned team understands both the opportunity it is expected to pursue and the work it has the capacity to carry.

Put the framework to work

Demo

See how the work gets done.

Explore how agents prepare work across your revenue teams, and how people review it, guide it and decide what happens next. Fictional data. Real product.

Explore the demo