How should comp scale across territories with vastly different TAM in 2027?

The outcome you should expect when comp is tied to opportunity

The first thing that changes when you move from equal quotas to TAM-weighted quotas is not the payout — it is the conversation. Reps stop arguing about whether their patch is fair and start arguing about whether the score that produced their patch is right. That is a strictly better argument to be having, because the second one is auditable and the first one is not.

Concretely, here is the shape of the outcome you should plan for in the first four quarters after a re-cut. Voluntary attrition among quota-carrying reps typically compresses, because the reps most likely to leave under a flat plan are the ones in thin patches who were structurally incapable of clearing plan — and, more painfully, the top reps in dense patches who noticed that their 180% was mostly geography and concluded the company could not tell the difference between them and a territory. Both groups are expensive. The thin-territory rep costs you a re-hire and a nine-month ramp. The dense-territory rep costs you the account relationships and, often, a competitor's best quarter.

The percentage of reps at or above 100% should rise, and this is the number that confuses executives most. It rises not because you lowered the bar but because you moved the bar to where the opportunity actually is. If your attainment distribution is bimodal — a cluster around 140% and a cluster around 55%, with a hollow middle — that is the signature of unequal TAM under equal quotas, and it is diagnosable from a spreadsheet before you touch a single plan document. Healthy plans produce a distribution with a fat middle: most reps between 80% and 130%, with tails on both sides, and roughly 55-65% of reps clearing 100%.

Total variable comp cost should stay close to flat. This is the part that CFOs do not believe until they see the stress test. Adding a 3.0x accelerator for thin-territory overperformance sounds like an expense until you notice that thin-territory overperformance is rare by construction — that is what makes the territory thin — while the offsetting decelerator in dense territories applies to a bucket where windfall attainment is common. In most models the two roughly cancel, landing within a couple of points of the prior year's variable spend. Run the stress test against last year's actuals before you argue about it: recompute what every rep would have earned under the new plan, sum it, and compare. If the delta is more than about five points of total variable, your tier multipliers are wrong, not your concept.

Two second-order effects are worth naming because they show up in month three and surprise people. First, pipeline hygiene improves in thin territories, because a rep carrying 0.7x baseline quota with a real chance of hitting it starts working the whole account list instead of camping on two whales. Second, forecast accuracy in dense territories often gets worse for a quarter, because reps who were previously sandbagging against an easy number stop needing to. Both are transient. Neither is a reason to revert.

What drives that outcome — the mechanics underneath the plan

The outcome above comes from six interlocking components. They are not a menu; removing one usually breaks another.

TAM-weighted quota. This is the load-bearing piece. Quota is derived, not negotiated: a territory's dollar-weighted opportunity score maps through a fixed formula to a quota number. The formula should include OTE, variable mix, an assumed pipe-coverage ratio, and a blended win rate for the segment composition of that specific patch. When the CFO asks why one rep carries 2.7 million and another carries 1.8 million for identical OTE, the answer is a score divided through an equation — not a judgment call, not seniority, not who negotiated hardest at offer stage.

A floor accelerator. Below roughly 60% attainment, most plans either pay nothing (a cliff) or pay a flat rate. In a genuinely thin patch both are corrosive. A floor rate — something under 1.0x, paid from dollar one — says: we know the ground is hard, we are not pretending otherwise, and we are also not paying full freight for under-attainment. The cost is small because few reps live there for long; the retention effect is large because it removes the "why am I even trying" moment in month five.

A decelerator above roughly 150%. Windfalls are real: a private-equity rollup, a compliance mandate, a single Fortune 500 consolidation, a renewal flood that happened to land in one patch. None of those are a skill demonstration equal to 130% built from a dozen net-new logos. A decelerating rate in the 150-200% band, plus an explicit windfall clause above that, protects plan economics without capping genuine overperformance. Get this board-approved in advance and written into the plan document. Removing a decelerator mid-year because one rep complained publicly is the single fastest way to destroy the credibility of everything else on this list.

Strategic-logo SPIFFs. No quota multiplier fully closes the absolute-dollar gap between a dense metro and a rural patch. What closes the *emotional* gap is prestige. A named-logo bonus that a thin-territory rep can realistically win makes that patch a place ambitious people volunteer for rather than a place people are sentenced to.

A quarterly true-up against TAM realization. Most plans measure attainment only. Measure a second number: what fraction of the identified opportunity in the patch the rep actually engaged. A rep at 85% attainment and 45% realization is fragile — riding two accounts, ignoring the bench. A rep at 78% attainment and 72% realization is healthy and got hit by cycle slippage. These two people need opposite management, and attainment alone cannot tell them apart.

An annual re-cut with grandfathering. Once per year, never quarterly. When a patch shrinks materially, hold the affected rep's prior quota through the first half of the new year while the transition happens. The cost is a rounding error. The alternative is watching your best people do the accelerator math on their shrunken patch and update their résumé the same afternoon.

The feedback loop in that diagram is the part people skip. The true-up feeds tiering, but only at the annual re-cut — a patch that overperforms all year gets re-tiered upward next January, not next quarter. Mid-year re-tiering converts the model from a plan into a negotiation, and once reps learn that performance triggers a harder quota within the same year, they will manage their attainment to just under the trigger. You will have built a sandbagging machine.

Benchmarks and realistic ranges to design against

Treat every number here as a starting range to calibrate against your own actuals, not a target to copy. The point of publishing ranges is to give you a sanity check, not a shortcut.

Quota coverage as a multiple of OTE. The multiple falls as deal size rises, because velocity falls faster than price. SMB motions typically carry the highest multiples, mid-market sits in a middle band, enterprise lower, strategic lowest of all. The multiple is not a preference — it is roughly the inverse product of your win rate and your qualification rate, plus a slippage buffer. Derive it. If your qualified-opportunity-to-closed-won rate is 25% and your sourced-pipe-to-qualified rate is 80%, throughput is 20%, implying 5x pipe coverage before buffer and around 6x after. A team running 8x coverage and still missing is not short on pipe; it is generating pipe that does not match the territory math.

Quota spread across tiers. In a four-tier model, the dense tier commonly carries something like 1.4-1.6x the baseline quota, the strong tier 1.1-1.3x, the moderate tier at baseline, and the thin tier 0.6-0.8x. The spread between the top and bottom tier lands roughly 2x. If your underlying TAM genuinely varies more than that — and in some businesses territories are *vastly* different, five or ten to one — do not try to absorb the entire spread in the quota multiplier. Beyond about 2.5x, split the patch, add a rep to the dense side, or move that segment to a named-account model. A single rep cannot work five times the opportunity, so a five-times quota is not a quota; it is a resignation letter with a signature line.

Accelerator rates by tier. Rates should move inversely to tier density. A dense-tier rep might see roughly 1.5-1.7x in the first accelerator band and a hard cap above 200%. A thin-tier rep should see the richest rates — 2.0-2.5x in the first band and 2.5-3.0x above — because rare overperformance in a sparse market needs to be financially meaningful or it will not motivate anyone. The design intent is convergence at 100% (every tier earns the same variable at target, by construction) and deliberate divergence in the tails.

Floor rates. Below-60% rates in the 0.7-0.85x range are typical, scaled slightly richer as tier density drops. Keep them modest. The floor is a retention device, not a hammock.

Tier distribution. Force something close to 20/30/30/20 across the four tiers. Left unconstrained, sales leadership will upgrade nearly every patch to avoid the uncomfortable conversation, the distribution bloats toward the top, and the model quietly reverts to a flat plan wearing a tier costume. If you genuinely cannot defend a thin tier, you have too many territories, not better ones.

Dispute volume as a health metric. Comp disputes running above about 5% of eligible deals indicate a plan or territory problem. Disputes under about 1% are not a triumph — they usually mean reps have given up on the process, which is worse than noisy engagement.

Grandfathering cost. Budget a small single-digit percentage of variable cost in re-cut years. It is one of the cheapest retention instruments available and it buys you the political room to actually re-cut, which is worth far more than the line item.

Ramp interaction. A new rep in a thin patch cannot hit even the reduced tier quota in the first three quarters. Use quarterly ramp fractions — something like a quarter, half, three-quarters, then near-full of the tier quota — and leave the floor accelerator active throughout. Stacking a standard ramp on top of an already-thin patch compounds the problem instead of solving it, and it is the most common reason a well-designed tier model still bleeds new hires.

Risks, edge cases, and the failure modes that actually kill this

The stolen account. A rep nurtures an account for eighteen months, and at re-cut it moves to another patch under a headquarters-assignment rule. Pay a residual override — a reduced rate on opportunities sourced before the re-cut, running twelve to twenty-four months — with full credit to the new owner. It is inexpensive and it removes the single most cited reason reps quit after a territory change.

The multi-territory logo. A strategic account touching three patches. Decide the split before the deal starts, not at close. A primary owner carrying the majority credit with minority splits to the others during the cycle, converting to full primary ownership at renewal, works. Litigating splits after the money lands is the most expensive form of internal politics there is.

Partner-sourced deals. A channel partner does most of the work and the deal closes in a rep's patch. Pay the rep a reduced rate rather than zero. They still hold the relationship, the renewal, and the expansion. Zeroing them out teaches the field to fight the channel, and you will spend years undoing that.

Mid-year relocation. A rep moves between regions. Treat it as a new-hire event for the new patch: base reset to the new market, ramp quotas restarted, prior-year annual credit pro-rated. Carrying old TAM expectations into a *different* market produces a number that nobody believes.

Regulated or legally constrained boundaries. In healthcare, defense, and parts of financial services, patch boundaries may be set by regulation and simply cannot be re-cut for revenue optimization. Here you work within the boundary using named-account overrides and outsized SPIFFs rather than tier accelerators.

Product-led motions. Where reps are primarily expansion-driven against a usage cohort rather than hunting a geography, territory TAM is the wrong unit of analysis entirely. Tie the majority of variable to net revenue retention of the assigned cohort and keep territory scoring as a minor input.

Brand-new product lines. No historical TAM means no defensible tiering. Run twelve months of a flat, quota-light launch plan to generate the data, then tier in year two. Forcing the model onto a product with no history manufactures false precision and punishes the reps who volunteered to sell something unproven.

Small teams. Below roughly eight quota carriers you do not have enough patches to tier without it becoming an individual negotiation with extra steps. Flat plan plus generous SPIFFs. The tier model starts earning its complexity somewhere around fifteen to twenty carriers and becomes close to mandatory past a hundred.

Headquarters concentration. If a majority of revenue concentrates in one metro, no geographic tiering scheme produces equity, because the math is dominated by a single patch. The fix is structural, not compensatory: switch from geographic to vertical alignment so reps compete nationally within an industry.

EMEA enforceability. European labor law in several jurisdictions restricts the enforceability of commission caps and decelerators once employment terms are established. The workaround most teams land on is soft decelerators expressed as SPIFFs that scale down with attainment rather than direct rate reductions. Get local counsel on this before you publish a plan document, not after a rep disputes it.

Currency volatility. In markets with large year-over-year FX swings, a rep can hit 110% in local currency while delivering materially less in reporting currency. Dual-quota measurement — local currency for the rep's variable, reporting currency for revenue recognition, with a bounded quarterly FX adjustment before the company absorbs the remainder — protects retention without leaving the business unhedged.

The secret model. The most common self-inflicted wound: a leader refuses to publish the scoring model because reps will game it. Reps will game it either way. Gaming a published model is vastly less destructive than gaming an imagined one, because at least the published model rewards behavior you chose. Give every rep read access to their own inputs.

The equalization demand. Someone notices that a dense-patch rep out-earned a thin-patch rep by a wide margin and asks for equalization. That gap is the design working. Equal OTE, unequal earnings, because one rep delivered more revenue. Adjusting base pay by patch reintroduces exactly the inequity the model exists to remove. This is a one-time education problem with the People team, and it is worth solving properly once rather than relitigating every year.

A practical rollout plan across a quarter

Rolling this out badly is worse than not rolling it out. The sequence below spreads the work across about ninety days and, critically, front-loads the diagnostic so that you are arguing from data rather than from taste.

Diagnostic, first two weeks. Pull eight quarters of attainment by rep and by patch. Compute the spread between top-quartile and bottom-quartile territories — if it is wide, the current plan is already broken and you have your business case. Pull voluntary attrition by patch and cross-reference it against that spread. Then score the ICP for every named account in the CRM. Be honest that this is the heaviest single workstream; it is usually where the timeline slips, and it is worth staffing properly rather than hurrying.

Model build, weeks three through six. Build the scoring engine in the warehouse or the comp platform. Compute each patch's dollar-weighted opportunity relative to the org median, map scores to tiers, apply forced distribution, and draft the accelerator table. Then stress-test: rerun last fiscal year's actual results through the new plan and see what would have been paid. This is the artifact that gets you through the CFO conversation, and it is also where you will find your own errors.

Socialization, weeks seven through eleven. Brief the CFO on plan economics including the incremental cost of floor accelerators. Brief sales leadership on tier assignments — expect pushback and hold the distribution. Run one-on-one briefings with every rep facing a material comp change in either direction, and hand each of them read access to their own scoring inputs in the same meeting. Get HR sign-off on grandfather clauses and any region-specific labor constraints. Do not skip the one-on-ones to save time; a rep who learns their tier from a spreadsheet in a group meeting starts from a defensive position you will spend a quarter recovering from.

Launch, final two weeks. Launch at the start of a fiscal quarter, never mid-quarter. Publish the audit log. Train the RevOps team on the true-up process and schedule the first realization review ninety days out.

Governance is what keeps the plan alive after launch. Stand up a small standing group — revenue leader, finance leader, RevOps, People, and the segment sales leaders — meeting monthly at the operating level and quarterly for the realization review. That quarterly meeting is the one that matters: it walks every patch's realization against attainment, identifies broken patches, and decides between re-tiering at the next annual cut, re-coaching the rep, or splitting the territory. Log every decision. Two years in, the log is what lets you show a board that tier assignments follow a repeatable process rather than a leader's mood.

One last operational note that gets underestimated: treat the scoring model as versioned code, not as a spreadsheet. Source tables, transformation logic, output tables, and tests — including a test that no rep's score should swing more than about 15% between consecutive quarters without a flagged reason. That test catches data-pipeline breakage before it reaches a paycheck, and a comp error that reaches a paycheck costs more trust than any plan design decision you will make all year.

Related questions

Should base salary ever vary by territory?

Only for cost-of-labor differences across genuinely different labor markets — never for opportunity density. Base tracks the local market rate for the role. Opportunity differences belong in quota and accelerators, where they can be measured, audited, and re-cut annually without touching anyone's contractual base.

How often should territories be re-cut?

Once a year, aligned to the fiscal year, with grandfathering for materially shrunken patches. Quarterly re-cuts destroy account relationships and teach reps that building a territory is pointless. Use the quarterly true-up as a performance-management signal, not as a redesign trigger.

What if a rep's territory is simply too small to support any quota?

Then it is not a territory. Merge it into a neighboring patch, convert the rep to a named-account or overlay role, or move that segment to an inside-sales motion. No accelerator table can fix a patch with insufficient underlying opportunity — you are papering over a coverage decision with a comp mechanism.

Does this apply to customer success and renewals teams?

Partially. The tiering logic transfers, but the input changes from addressable opportunity to book composition — expansion headroom, renewal risk concentration, and account count. The same principle holds: equal target earnings, targets scaled to the book, upside scaled to how hard the book is.

How do you handle a rep who volunteers to take a thin territory?

Make it a deliberate development path. Hold them near their prior variable for a defined period, commit in writing to re-evaluating the tier at the next annual cut based on the opportunity they build, and weight promotion criteria toward realization rather than raw dollars.

FAQ

Doesn't a lower quota in a thin territory just reward weaker reps?

No, because target earnings are identical and performance management is unchanged. A rep who misses a reduced quota is as accountable as anyone else. What changes is that the number reflects what the patch can actually produce, so a miss means something diagnostic instead of being predetermined by geography.

How do we set tiers when we have no clean TAM data?

Start with what you already have — closed-won history by patch, account counts weighted by segment, and a rough ICP fit score from your enrichment vendor. A coarse model applied consistently beats a precise model applied never. Improve the inputs over two or three quarterly cycles and publish each version.

Will publishing the model cause reps to game their territory scores?

Some will try, and that is manageable. Score inputs are largely outside rep control — firmographics, historical win rates, competitive tenure — and the ones reps do influence, like account engagement, are behaviors you want more of. The alternative is reps constructing folk theories about a black box, which erodes trust far faster.

What is the single most common implementation mistake?

Upgrading nearly every territory to the top tiers to avoid uncomfortable conversations. The distribution bloats, the tiers stop differentiating, and within a year you are back to a flat plan with extra administrative overhead. Force the distribution and hold it, even when it is unpopular.

How does this interact with team-based or pooled selling?

Score the pooled patch as one unit and split the resulting quota across the team by role weighting, keeping tiered accelerators at the individual level. Pooled models need explicit split rules documented before deals start; ambiguity in a pool is more corrosive than in individual ownership because there is no default owner to fall back on.

Should RevOps or Finance own the scoring model?

RevOps owns the model and the pipeline that feeds it; Finance owns the cost envelope and signs off on the tier multipliers before publication. Splitting it that way keeps the model close to the territory reality while keeping the plan inside budget, and it gives disputes a clear escalation path.

Sources

• https://www.gartner.com/en/sales
• https://www.alexandergroup.com/insights/
• https://bridgegroupinc.com/research/
• https://www.captivateiq.com/resources
• https://www.xactlycorp.com/resources
• https://www.bain.com/insights/
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights
• https://hbr.org/topic/subject/sales
• https://www.shrm.org/topics-tools/topics/compensation
• https://www.bvp.com/atlas

Related on PULSE

• [What's the modern territory design framework — account clustering vs geographic vs vertical-based?](/knowledge/q386)
• [What accelerator multiples are typical past 100% of quota for SaaS AEs?](/knowledge/q05)
• [What's the difference between top-down and bottom-up quota models, and when should a RevOps leader use each?](/knowledge/q729)
• [How do we handle comp when a rep transfers between territories, and does their old quota still apply?](/knowledge/q266)
• [How do you design a capacity model that accounts for rep tenure, training ramp, and territory variance?](/knowledge/q730)
• [How do you segment your TAM by ICP-fit when you have 50,000 named accounts and only 30 reps?](/knowledge/q1107)