Territory performance analysis

Territory performance analysis is the practice of comparing sales results across territories to find where the team is winning, where it is losing, and where the opportunity is being left on the table. A territory can be a geography, an industry vertical, a customer segment, or a named-account list. The analysis measures each territory against its own quota and against its peers, then looks for the reasons behind the differences.

The core comparison is attainment: bookings divided by quota for each territory. A territory at 130% of quota and a territory at 60% of quota both contribute to the same national number, but they need opposite interventions. Averaging them hides the signal. Territory performance analysis keeps the territories separate so the pattern stays visible.

The analysis only becomes useful when it explains the gap. A territory can miss quota because it has too few accounts, because the accounts are low value, because pipeline coverage is thin, because win rates are low, or because the quota itself was set too high. Each of these points to a different fix owned by a different person, which is why a flat ranking of territories is rarely enough on its own.

There is no single number that captures territory performance. The analysis is a set of inputs measured per territory, then compared across the set. Start with attainment, then layer in the drivers that explain it.

1. 1

   Territory attainment

   Bookings divided by quota for each territory. This is the headline. A territory at 0.6 attainment is at 60% of target. Rank every territory by this figure to see the spread.

2. 2

   Coverage ratio

   Open pipeline value divided by remaining quota. A territory needs roughly three to four times its remaining quota in pipeline to hit target. A territory below that is short on opportunity, not execution.

3. 3

   Account potential

   Total addressable revenue across the accounts assigned to the territory. A territory can run perfectly and still miss if the accounts simply cannot buy enough. This separates a coverage problem from an execution problem.

4. 4

   Win rate by territory

   Closed-won opportunities divided by all closed opportunities in the territory. A low local win rate points to a sales-skill, competitive, or product-fit issue specific to that territory.

5. 5

   Rep capacity

   Number of active accounts per rep against a sensible ceiling. An over-loaded territory leaves accounts uncovered. An under-loaded one wastes quota-carrying headcount.

Reading these together turns a ranking into a diagnosis. A territory at 60% attainment with a coverage ratio of 5 and a low win rate has plenty of pipeline and is losing deals it should win, which is a selling problem. The same 60% with a coverage ratio of 1.5 has a pipeline problem, which is a demand problem. The two need different owners and different actions.

A metric tree decomposes territory performance into the drivers that produce it, so a missed number resolves to a specific cause rather than a vague underperformance. This is where territory analysis moves from a leaderboard to a decision tool.

The first level splits each territory into the things that build bookings: the accounts available, the pipeline generated, the rate at which deals convert, and the size of those deals. Each of these then decomposes further. Pipeline generation breaks into inbound demand, outbound activity, and marketing-sourced opportunities. Conversion breaks into win rate and sales-cycle length. Account quality breaks into the count of accounts and their average potential value.

This structure lets you compare two territories on the same branches. If one is behind only on pipeline generation, the fix sits with demand generation and the rep activity owner. If it is behind only on win rate, the fix sits with sales enablement and the territory manager. The tree makes the difference legible instead of leaving it buried in a national total.

There is no universal benchmark for a single territory, because quotas are set locally. The useful benchmarks describe the spread across territories and the coverage that supports a number. A healthy organisation has a tight spread and most territories carrying enough pipeline.

A common rule of thumb is that around 60% to 70% of territories should land within the on-track band in a well-balanced organisation. If most territories cluster at the extremes, the issue is usually quota setting or territory design rather than selling. A coverage ratio below two in any territory is an early warning that attainment will fall regardless of effort.

Improving territory performance is rarely about asking reps to work harder. It is about diagnosing why each territory sits where it does and matching the intervention to the cause. The same gap can demand four different actions depending on which branch of the tree is short.

The decomposition approach starts by finding which branch of the tree explains the largest part of the gap, then acting only there. A territory short on pipeline does not need more enablement, and a territory short on win rate does not need more leads.

KPI Tree lets you connect each branch of the territory tree to the person accountable for it. The territory manager owns coverage and execution, demand generation owns pipeline supply, sales operations owns territory design and quota setting. With RACI ownership on every node, a missed territory routes straight to the right owner instead of becoming a line item in a national review. When the number moves, the accountable owner is notified, and the verified impact loop checks whether the action taken actually closed the gap.

1. 1

   Comparing attainment without comparing potential

   Ranking territories purely on attainment rewards whoever got the richest accounts. Always read attainment next to account potential, or the analysis punishes the wrong reps.

2. 2

   Averaging territories into a national number

   A national figure hides the spread that matters. A 100% national number can sit on top of half the territories failing and half over-delivering, which needs two different responses.

3. 3

   Treating every miss as an execution problem

   Most under-performance below 70% is structural, driven by coverage or design, not effort. Adding pressure to a territory with no pipeline does not create pipeline.

4. 4

   Ignoring quota quality

   A territory can look strong only because its quota was soft. Without checking how each quota was set, the analysis flatters poor territory design and conceals real risk.

5. 5

   Looking at a single point in time

   A snapshot misses momentum. A territory at 80% and rising is in a different position to one at 80% and falling. Trend the numbers across periods, not just the latest figure.