Territory & quota design

Last planning cycle a manager wanted to put a rep on a PIP. The rep was at 61% attainment, dead last on the board, and the story wrote itself. Then I scored his territory: $800K of real potential against a $1.2M quota. He was converting a higher share of his book than two reps sitting comfortably at 105%. He did not have a performance problem. He had a map problem, and I had handed it to him. Uneven account distribution is the most overlooked cause of missed quota, and it is the first thing I audit before anyone talks about coaching or exits.

The pattern shows up in the aggregate numbers too. Average attainment sat around 42.7% in 2025, roughly 57% of reps missed quota, and only about 28% hit 100%, down from 44% a couple of years earlier (RepVue Q2 2025, Hyperbound 2025). When more than half a team misses, the odds say the model is wrong before the people are. What follows is how I audit the map, ramp-adjust the capacity, and set a quota that is earnable, with the queries and the guardrails.

Balance on opportunity, not account count

A territory is a container of opportunity, so I measure the containers before I set a single number. Two hundred dead accounts and forty live ones are not equal territories, and account count hides that completely. The score I roll up is forward potential, not last year’s bookings, because last year’s bookings reward whoever inherited the good book.

Territory potential

potential = (whitespace TAM × propensity) + open pipeline + renewal/expansion base

Score forward potential, not last year's bookings. Balance so no territory deviates more than about 15% from the median.

That score comes out of the warehouse, not a gut call. The skeleton of the query rolls account-level signals up to a candidate territory:

-- Territory potential = expansion base + open pipeline + weighted whitespace.
-- Run per candidate territory, then compare spread to the median.
SELECT a.Territory__c,
       SUM(a.Current_ARR__c)                                    AS expansion_base,
       SUM(COALESCE(p.open_pipeline, 0))                        AS open_pipeline,
       SUM(a.Whitespace_TAM__c * a.Propensity_Score__c)         AS weighted_whitespace,
       SUM(a.Current_ARR__c + COALESCE(p.open_pipeline, 0)
           + a.Whitespace_TAM__c * a.Propensity_Score__c)       AS total_potential
FROM Account a
LEFT JOIN (
  SELECT AccountId, SUM(Amount) AS open_pipeline
  FROM Opportunity
  WHERE IsClosed = false
  GROUP BY AccountId
) p ON p.AccountId = a.Id
GROUP BY a.Territory__c
ORDER BY total_potential DESC

The chart makes the unfairness impossible to miss. Toggle between the flat split everyone defaults to and the proportional split that equalizes difficulty. Under the flat plan the thin-territory rep is set up to fail before the quarter starts.

Flat $750K quotaPotential-weighted quota

View as table

Stage	Value
$9M potential	8.3%
$6M potential	12.5%
$4.5M potential	16.7%
$3M potential	25%

Ramp-adjust capacity or the plan is fiction

The second thing I got wrong early: planning off nominal quota instead of what ramped reps actually produce. If I have 12 reps starting Q1 on a six-month ramp at 50% productivity, their real Q1 capacity is not 12 times the full quota. Twelve reps at $200K per quarter nominal is $2.4M on paper and about $600K in reality. Hand finance the $2.4M number and you have promised revenue that does not exist yet.

Ramp-adjusted capacity

capacity = Σ (rep × ramped quota × ramp factor × expected attainment)

A body is not a quota-carrier for months. Time-phase every hire by where they sit on the ramp curve.

The gap between the two ways of counting is the difference between a board number you hit and one you miss by 75% in the first quarter. Nobody should file that under rounding error.

A typical enterprise ramp runs longer than most plans assume. Time-phasing by month, not treating every hire as a full carrier on day one, is the whole discipline:

Ramp month	Productivity	Notes
Months 1-2	0%	Onboarding, no carried quota (SDR ramp 3-4 months, Bridge Group)
Months 3-4	50%	Reduced quota, first live deals
Months 5-6	75%	Approaching full book
Month 7+	100%	Full quota carrier

Set the quota, then check who can actually hit it

Here is the model I build in order. Each step feeds the next, and skipping the audit at the top is how you end up PIPing a rep for a map you drew.

1. 1

   1. Pull the account universe

   Enrich with firmographics, product usage, and intent (Salesforce + ZoomInfo/Clay + product signals). No account gets a territory it was never scored into.

2. 2

   2. Score potential and propensity

   Roll account scores up to candidate territories using the query above. Forward potential, never last year's bookings.

3. 3

   3. Balance the territories

   Keep potential spread across reps under about 15% from the median. Rebalance the outliers before setting any number.

4. 4

   4. Over-assign at the company level

   If reps average 85% attainment, assigning exactly the target guarantees a miss. Assign roughly 1.15 to 1.3x so the aggregate clears the number.

5. 5

   5. Allocate quota proportional to potential

   rep quota = total quota × (rep potential / total potential). No rep is punished for the map they drew.

6. 6

   6. Ramp-adjust, then bottom-up sanity check

   Reduced quota for months 1 through N by the ramp table. Then ask the honest question: can this book plausibly reach the number?

7. 7

   7. Lock and publish before the period starts

   A quota that lands in February for a January period is not a quota. Locked, published, signed.

The before-and-after is the whole argument for doing this at all:

	Flat-split plan	Potential-weighted plan
Quota basis	Headcount ÷ target	Rep potential ÷ total potential
$9M-territory rep	$750K (needs 8.3% conversion)	$1.13M (needs 12.5%)
$3M-territory rep	$750K (needs 25% conversion)	$375K (needs 12.5%)
What a miss means	Ambiguous: rep or map?	Clean read on the rep
Rep trust in the number	Low, they can see the imbalance	High, difficulty is equalized

Read attainment as participation, not average

The number that fixes territory arguments is participation: the share of reps hitting 100%, not the average attainment across everyone. In 2025 average attainment sat around 42.7% while roughly 57% of reps missed quota outright, and only about 28% hit 100%, down from 44% a couple of years earlier (RepVue Q2 2025, Hyperbound 2025). Those tell different stories. A healthy average dragged up by three heroes while everyone else drowns is a territory-balance problem, not a talent problem. I never feed cross-stage average attainment into a plan; it launders the imbalance into a single reassuring number.

The distribution is what you act on, not the mean:

Attainment cohort	Read	Action
Participation 60%+ hitting 100%	Healthy, quota is calibrated	Hold the model
Participation 40-60%	Watch, possible top-heavy pull	Audit territory spread
Participation under 40%	Map is broken, not the people	Reset before managing anyone out
Average high, participation low	Heroes masking a distribution problem	Rebalance territories

One more guardrail I hold hard: quota-to-OTE. Standard is 4 to 5x, enterprise stretches to 5.5 to 6x, and anything above 6x is structurally broken (GetGangly 2026, citing Bridge Group/RepVue). If a rep has to sell six times their total pay to hit target, the plan is telling them the accelerators are unreachable, and they will sandbag to next quarter accordingly. This ties straight into how the comp plan pays out, and a broken ratio breaks both at once.

If fewer than roughly half your reps are hitting quota, reset the model before you manage anyone out. The odds say the map is wrong, not the people. Score the book, balance the containers, ramp-adjust the capacity, and set the quota against real potential. Then, and only then, the attainment board is telling you something about the reps instead of about the plan.