An $800K Territory Cannot Carry a $1.2M Quota

Average quota attainment fell to 42.7% in the second quarter of 2025, and 57.3% of reps missed (RepVue, Q2 2025 sales benchmarks). When that number lands on a board slide the first move is always the same: coach the reps, tighten the pipeline, run a call blitz. I have watched that reflex play out on teams where the reps were fine and the map was broken. An $800K territory cannot carry a $1.2M quota no matter how well the person in it sells. Before you audit the rep, audit the patch you handed them.

The old way blames the seller for the miss. The honest version blames the carve, because uneven account distribution is the most overlooked cause of a missed number and it stays invisible until someone measures opportunity instead of counting logos. The angriest Slack thread I ever set off proved the other half of this. My spreadsheet was clean, every territory within a few points of the median, and the revolt still came, because a rep opened his new patch and found two accounts gone, both of which he had worked for two quarters. He was not reacting to my math. He was reacting to the edge case I never wrote down. Territory carving fails on two things: opportunity you did not balance, and rules you did not publish.

Here is what a defensible carve looks like when it settles. A raw pool of accounts, balanced on logo count, reads as fair and hides a wide spread of real opportunity. Weight each account by what predicts revenue and the spread shows itself. Carve to a tight band around the median and the plan that survives an argument settles out of the noise. Scroll it, then I will show you the formula and the query under each stage.

3,000Raw account pool3,000 accounts split evenly on logo count. Every rep got the same number of names, so the plan looks fair on the surface.

←

→

Locate yourself on those three stages. Most plans ship at the first one, balanced on logo count and quietly hiding a spread wide enough to hand one rep a lottery ticket and another a resignation letter. The middle stage is the audit almost nobody runs before the year starts. The last stage is a carve you can defend line by line, because you can show the weighted opportunity behind every boundary. The framework at the end of this piece is the sequence that gets you from the first stage to the last without a mutiny.

The miss is a map problem before it is a motivation problem

Start by separating two numbers the room routinely blends. Average attainment is not participation. RepVue put average attainment at 42.7% in Q2 2025, but Hyperbound found only 28% of reps hit 100% of quota in 2023, down from 44% in 2022 (Hyperbound, 2025 sales report). Those describe different failures. A low average can hide a team where most reps land near target and a handful crater; a low participation rate means the plan itself is set past what the map can produce. If you are redesigning territories, watch participation, because that is the number a broken carve moves.

Then check whether the book each rep carries is even sizeable enough to work. TOPO and Gartner benchmarks put a workable enterprise book at 75 to 125 accounts with 400 to 500 named contacts (TOPO/Gartner). Hand a rep 400 accounts and the coverage problem is not effort, it is arithmetic: nobody multi-threads 400 accounts in a quarter. Account count per rep is the first thing I check when attainment craters, because a book that is too thin or too fat both produce the same miss.

The largest hidden overstatement, though, is ramp. Finance sees twelve new hires and a full quota each and books the sum as capacity. Half of them start the year mid-ramp, and AE ramp runs about six months (Bridge Group), so a rep at month three produces close to half a ramped rep. The nominal plan and the real plan diverge by millions.

Rep cohort	Reps	Nominal quota each	Ramp factor	Real capacity each	Cohort real
Fully ramped	6	$1.2M	1.0	$1.2M	$7.2M
Mid-ramp (month 3 of a 6-month ramp)	6	$1.2M	0.5	$600K	$3.6M
Total	12	$14.4M nominal			$10.8M real

Fair-share balancing, then capacity-based quota

Start with fair-share balancing. Every territory should hold roughly equal opportunity, measured by whatever predicts revenue for your business: total addressable pipeline, account count weighted by segment, or historical spend. Never balance on raw logo count. One hundred enterprise logos and one hundred SMB logos are not the same territory, and a rep can see that in ten seconds.

My rule: no territory’s weighted opportunity deviates more than 10 to 15% from the median. Hand someone 30% above median and you have handed them a lottery ticket; 30% below and you have handed them a resignation letter. The band matters because reps do the math faster than you think. A rep who suspects their patch is thin will compare notes with a peer over lunch, estimate the gap in their heads, and decide whether the plan is fair long before you finish explaining the methodology. If the real deviation is 12%, that conversation ends in a shrug. If it is 35%, it ends in the thin-territory rep quietly starting to interview, because they have concluded, correctly, that they were handed a harder year for reasons that have nothing to do with effort.

This is a query, not a feel. Pull weighted opportunity per territory from the warehouse and rank every patch by its index against the median, so the balance decision is a report you can hand to the reps rather than a claim they have to trust.

-- Weighted opportunity per territory, indexed to the median.
-- Anything outside 0.85 to 1.15 is a patch to rebalance before the year starts.
WITH terr AS (
  SELECT territory,
         COUNT(*)                                    AS logos,
         SUM(segment_weight * addressable_pipeline)  AS weighted_opp
  FROM accounts
  WHERE account_type = 'prospect'
  GROUP BY territory
)
SELECT territory,
       logos,
       weighted_opp,
       weighted_opp / MEDIAN(weighted_opp) OVER () AS index_vs_median
FROM terr
ORDER BY index_vs_median

Read index_vs_median top to bottom. Every row under 0.85 or over 1.15 is a patch that breaks the band, and it is far cheaper to move accounts between two territories in the planning spreadsheet than to explain a 35% gap to a rep in March. Then set quota from capacity, not from the number finance wishes were true. Capacity-based quota starts from what a fully ramped rep can realistically produce given deal size and cycle length, then adjusts:

territory quota = fully-ramped capacity × ramp factor × territory opportunity index

Skip the opportunity index and you give the same quota to a rep in a rich territory and a rep in a thin one, which means the thin-territory rep is being punished for the map you drew. The formula has three inputs and the diagram below is the whole model. Read it left to right: base capacity gets discounted for ramp, then scaled for how rich the territory is, and only then does it become a defensible number.

Here is a worked split. $12M in new-business quota, eight reps. Naive math says $1.5M each. But two reps are mid-ramp (factor 0.6), two territories carry 20% more weighted opportunity than the median (index 1.2), and two carry 20% less (index 0.8). Distribute by capacity and opportunity and it comes out to ramped reps in rich territories at $1.8M, ramped reps in thin territories at $1.2M, and mid-ramp reps at $1.0M each. Still rolls to $12M. The difference is that every number is now defensible line by line, and “why is my quota higher than hers” has a one-sentence answer.

The naive split and the capacity split roll to the same total. They are not the same plan. The chart makes the gap visible: flat $1.5M for everyone versus a number that traces to ramp and territory.

View as table

Item	Value
Ramped, rich	1.5M
Ramped, thin	1.5M
Mid-ramp	1.5M

Here is the same eight reps as a table, so the roll-up is explicit:

Rep profile	Count	Ramp factor	Opp index	Quota each	Subtotal
Ramped, rich territory	2	1.0	1.2	$1.8M	$3.6M
Ramped, thin territory	2	1.0	0.8	$1.2M	$2.4M
Mid-ramp	2	0.6	1.0	$1.0M	$2.0M
Ramped, median territory	2	1.0	1.0	$2.0M	$4.0M
Total	8				$12.0M

Write the edge cases before the year starts

This is where mutinies get prevented. The balance math is the easy 80%. On the plans I have carved, trust lives in the roughly one in five accounts sitting on a boundary, and those need written rules published before day one, not invented in the heat of a dispute:

• In-flight deals: an open opportunity stays with the original rep through close, even if the account moves territories. Reassigning a deal a rep is about to close is the fastest way to lose the room.
• Named accounts and relationships: a documented active relationship keeps the account, boundary or not. Define “active” with a date threshold so it cannot be argued.
• Splits and parent-child: decide upfront whether a global parent and its subsidiaries stay together or split by geography, and write down which owner wins.
• Mid-year hires and departures: define how a departing rep’s book redistributes and how a new rep’s patch gets carved, including whether donor reps get quota relief for what they give up.

Publish these as a one-page ruleset next to the map. When a rep escalates, you point at the rule they saw before the year started, and the argument is about the rule, not about whether you play favorites.

The in-flight-deal rule is the one that prevents most mutinies, so make it the sharpest. A rep who spent two quarters working an account and loses it the day the plan ships does not experience a boundary redraw, they experience a robbery. Write it as a hard rule: any opportunity open on the day the plan takes effect stays with its current owner through close or close-lost, and the account moves to the new owner only after that opportunity resolves. That single sentence turns the angriest possible conversation into a non-event, because the rep keeps the thing they were about to close and gives up only the cold accounts they were not working anyway.

The active-relationship rule needs a number attached or it becomes an argument. Everyone believes they have an active relationship with every account they have ever emailed. Define active with a threshold you can query: a logged meeting or a stage-advancing activity in the last 90 days. Now “is this relationship active” is a report, not a debate, and a rep who claims one the CRM cannot see has told you something useful about their hygiene, not about the map.

Here is the difference the written ruleset makes, dispute by dispute:

	No written edge cases	Published ruleset day one
Rep loses an account they worked	Feels personal, escalates loud	Points at the in-flight-deal rule they read
Boundary account with a relationship	Argued case by case in the heat	Active-relationship date threshold decides it
Global parent split across geos	Two reps claim it, you referee	Which-owner-wins rule already published
Mid-year hire carves a patch	Donor reps feel robbed	Quota relief for donors written in advance
The escalation	"You play favorites"	"The rule was published in January"

Here is how I build it: the ramp and capacity aware carve

This is the order I run every territory plan in, and it is the sequence the dissolve field above walks through: raw pool, weighted opportunity, balanced carve, defensible quota. The order matters. Publish the rules before you draw the map, not after, because rules invented mid-dispute always look like favoritism.

1. 1

   Step 1, pick the opportunity measure

   Decide what predicts revenue for your business: addressable pipeline, segment-weighted account count, or historical spend. Write it down. This is the thing every territory gets balanced on, and it is never raw logo count.

2. 2

   Step 2, balance to within 10-15% of median

   Run the weighted-opportunity query, rank every patch by its index against the median, and rebalance anything outside 0.85 to 1.15. Above 30% is a lottery ticket, below 30% is a resignation letter.

3. 3

   Step 3, ramp-adjust capacity before you set quota

   Discount mid-ramp reps to their real first-half capacity so the plan does not book $14.4M when the team can produce $10.8M. Nominal capacity is where the miss hides.

4. 4

   Step 4, set quota from the capacity formula

   Quota = fully-ramped capacity × ramp factor × opportunity index, checked against a 6x OTE ceiling. Compute it per rep so the number traces to inputs, not to a flat division of the company target.

5. 5

   Step 5, publish the edge-case ruleset, then run disputes against the rule

   One page next to the map: in-flight deals, named-account relationships with a date threshold, parent-child splits, mid-year hires with donor quota relief. When a rep escalates, point at the rule everyone saw in January, not at the person.

Where it lands

Territory carving fails on trust, not on math. Balance opportunity to within 10 to 15% of the median, ramp-adjust capacity before you set a single quota, tie the number to a formula so nobody eats a penalty for the map you drew, and write the edge cases down before the plan ships. The 42.7% attainment number that starts every planning cycle is not, for half those reps, a coaching problem. It is a carve that never had the opportunity to carry the quota. Fix the map first.

If you want the mechanics of how ownership moves when accounts change territories, the edge-case rules here pair with a clean handoff process, and the routing-is-latency piece covers the same trust-versus-speed tension on the inbound side. And once the map is fair, the next lie to kill is the coverage ratio you carry into the forecast: the 3x coverage number that lies to you is the pipeline half of the same capacity story.