Module 4 · The Operations Disciplines · Chapter 15 of 32
Territory and Quota Design
Turn coverage-as-capacity into a design input: carve the account universe into balanced books, set quota as capacity times productivity with the Growth Formula as the capacity input, and never let a free-text owner field corrupt the map.
9 min read
I was halfway through a territory-to-rep alignment sheet, pulling every territory out of production and rolling accounts up to whoever owned the most of them, when the top two reps in one region turned out to be the same man. Roughly 28,000 accounts sat under one spelling of his name, another 12,000 under a second spelling one letter off. The system had cheerfully treated a typo as two separate humans. If I had built next year’s capacity plan off that sheet, I would have staffed a rep who did not exist and shorted a real one by two-thirds of his book. The map was wrong before anyone set a single quota, and it was wrong in a way no amount of coaching or pipeline review would ever surface.
That is the trap this chapter is about. In Forecasting we used coverage equals one over win rate as a capacity check: given a number, how much qualified pipeline does it demand. Territory and quota design runs the same arithmetic in the other direction. Before the quarter, before anyone commits to anything, you decide the number itself from what the map can physically produce. Do it from capacity and the forecast has a floor it can trust. Do it from gut, or from last year plus whatever growth percentage the board wants, and you have manufactured a miss you will spend three quarters explaining.
The number is a capacity decision, not a growth wish
A quota is not a motivational target you reverse-engineer from what finance needs. It is the output of a physical system, the same recurring-revenue factory this course has been building since the first chapter. So it obeys a factory equation.
quota (plannable) = capacity × productivity
where a seat’s capacity = territory opportunities × win rate (CR4) × ACV
Capacity is what your ramped, quota-carrying seats can physically produce from the books they cover. Productivity is the fraction a real rep converts of that: ramp state, on-task discipline, the assumed attainment. Set quota above capacity times productivity and you have set it above what the map can yield, no matter how the plan is written.
Read the second line closely, because it is the whole discipline. A single rep is a production line, and a production line has a throughput you can compute. Multiply the qualified opportunities their territory can feed them by their win rate and by the average deal size, and you have the most that seat can produce in a year at benchmark conversion. That is not a target you negotiate. It is a ceiling the territory sets. Productivity is the honest discount you apply on top: reps ramp, reps miss, and the plan I worked on assumed 85% attainment across the team with 5% attrition baked in. Plan every seat at 100% of its ceiling and the aggregate is guaranteed to fall short, which is why you assign somewhat above the target and let the productivity factor bring it back to earth.
Capacity is the Growth Formula, scoped to one book
That seat-level ceiling is not a new idea. It is the Growth Formula from The Mathematical Model, pointed at one territory instead of one motion. The book wrote a motion’s production capacity as visitors times the product of every conversion rate times list price. Scope that to a single rep and it collapses to opportunities the book can generate, times CR4 (the win rate), times ACV. Coverage is the inverse of the win rate, so it tells you how much pipeline the quota you just wrote will demand the territory to contain.
Carve on potential, not on account count
Capacity math is only as good as the carve underneath it, and the carve starts with segmentation. In the org I audited, territory did not live in native Salesforce Territory Management at all. It lived in one field on the account, about 89 distinct values in a US - REGION - SUBREGION - SEGMENT shape, covering roughly 165,000 accounts. Segment is baked right into the string, and that is deliberate: segment sets the base quota, because a mid-market book and an enterprise book have different ceilings for the exact reasons The Go-To-Market Model laid out. Higher ACV funds a higher number per seat. It does not mean the enterprise rep works harder.
| Segment (seat) | Base annual quota | Assumed attainment | Motion it maps to |
|---|---|---|---|
| Inside / Commercial | ~$770K | 85% | Low / Medium Touch |
| Sr. Commercial | ~$990K | 85% | Medium Touch |
| Mid-Market | ~$1.21M | 85% | High Touch |
| Enterprise | ~$1.8M | 85% | High Touch (+ SE) |
| Strategic / Named | ~$2.2M | 85% | Dedicated Touch |
Quota anchors from a revenue plan I built, rounded; attainment and the 5% attrition assumption are the plan’s own. Each row is quota = capacity × productivity collapsed into a planning default. The Enterprise seat carries more than the Commercial seat because its book yields more per deal, not because anyone expects heroics, and remember the warning from the GTM Model chapter: segment describes who the buyer is, motion describes what it costs you to win them, and the two are not the same axis.
Within a segment, the fairness rule is that a territory is a container of opportunity, so you balance the containers, not the account counts. Two hundred dead accounts and forty live ones are not equal books, and scoring on last year’s bookings just rewards whoever inherited the good territory. The full mechanics of that balancing, the potential-scoring query, the flat-versus-weighted worked example, the ramp table, and reading attainment as participation rather than average, live in the territory and quota reference. This chapter’s job is the design logic that sits above it: quota is capacity times productivity, capacity is the Growth Formula run forward, and an unbalanced carve breaks the equation before you ever compute it.
The map is a data artifact, and a shaky one
Here is the part every capacity model quietly assumes and almost no one checks: that the field linking accounts to reps is trustworthy. Mine was not, and yours may not be either.
This is why territory and quota design belongs to operations and not to a spreadsheet a sales leader keeps in a tab. The number that lands on a rep’s plan is the last step in a chain that runs through the CRM data model, the ownership field, the segmentation, and the capacity math, and any weak link corrupts everything downstream of it without throwing an error. Governing that field is not clerical hygiene. It is the difference between a quota that describes reality and one that describes a typo.
Hand off to compensation
You now have an earnable number, sized from capacity and balanced across the team so a miss reads as a rep signal and not a map defect. What the number does not yet tell you is which behavior earns the money. A rep handed a $1.8M enterprise quota can chase one whale and coast, or grind out fifteen mid-size lands, and everything to this point is indifferent between them. The quota-to-OTE ratio you just implied (four to six times pay, per the reference) is the first hint that the target and the payout are one system, not two.
Compensation and Incentive Design is where you make the plan care. Accelerators, the split between paying for acquisition and paying for expansion, the governance that keeps the plan pointed at whichever growth engine the business actually needs at its stage. Set the number from capacity here. Decide what the number rewards next.