Sales Territory Aside—Quota Setting: How to Build B2B Sales Quotas That Are Achievable and Still Drive Growth
By Rick Elmore ·
Every January I watch the same movie play out. A revenue leader opens a spreadsheet, takes last year's number, multiplies by 1.3 because the board wants 30% growth, divides by headcount, and ships it to the field. By March, half the team is already behind, the best reps are quietly updating their LinkedIn, and the forecast is a work of fiction. The quota wasn't wrong because the growth target was greedy. It was wrong because nobody connected the number anyone was carrying to what the territory, the rep, and the pipeline could actually produce.
Quota setting is one of the highest-leverage decisions RevOps makes all year, and it's routinely done in an afternoon. This is a walkthrough of how I build quotas that people believe in without sandbagging the company's growth. One thing up front: this is about calculating and allocating the number, not about pay. Commission rates, accelerators, and clawbacks are compensation design. Keep those conversations separate or you'll end up negotiating the target instead of engineering it.
- Reconcile top-down and bottom-up before you commit. The board's growth number and the field's capacity rarely match on the first pass. The gap is the real work.
- Ramp is a line item, not a footnote. New and recently hired reps cannot carry a full number, and pretending otherwise inflates your plan.
- Allocate by territory potential, not equal division. Two reps with identical quotas and wildly different territories is how you lose the one in the weaker patch.
- Stress-test coverage. If quota times attainment assumptions doesn't clear the company target with margin, the plan breaks the moment anyone underperforms.
- Separate the number from the pay. Set the quota first on capacity logic, then design comp around it.
Start with the gap between top-down and bottom-up
There are two legitimate ways to arrive at a quota number, and both are incomplete on their own.
The top-down method starts with what the business needs. The board wants a certain ARR, finance has a burn plan, and sales is responsible for some share of that growth. You work backward: company target, minus expected renewals and expansion that the sales team isn't closing new, equals the new business the field has to generate. That's your top-down sales quota requirement in aggregate.
The bottom-up method starts with what the team can actually do. You look at each rep, their ramp status, their territory, their historical attainment, and the pipeline available to them, then you sum it up. That's your realistic capacity.
The number almost never matches on the first pass. When top-down says the team needs to produce $12M in new business and bottom-up capacity says $9M, you have a $3M gap staring at you. This is the most useful moment in the entire process, because now you have a real decision instead of a wish. You can close that gap four honest ways: hire more reps, raise per-rep productivity with better pipeline or enablement, extend ramp expectations, or lower the growth target. What you cannot do is paper over it by writing a bigger number on each rep's plan and hoping. The gap doesn't disappear because you ignored it. It just shows up later as a missed forecast.
I treat the top-down number as the goal and the bottom-up number as the reality, and I spend most of my time engineering the bridge between them. That bridge is usually some mix of a hiring plan with realistic start dates, a pipeline generation commitment from marketing and SDRs, and an honest conversation with leadership about what's genuinely achievable this year versus what's a two-year build.
Build capacity from the rep up, not the headcount down
Dividing the company target by headcount is the original sin of quota setting. It assumes every rep is identical, fully ramped, and sitting on equivalent territory. None of that is true.
Bottom-up capacity starts with a productivity assumption per fully-ramped rep in a given segment. If a mid-market AE closing at your average deal size and win rate can realistically produce a certain amount of new ARR in a year when they're running at full speed, that's your baseline unit. You derive that from your own history, not from a benchmark deck. Pull your actuals: average deal size, sales cycle length, win rate, and how many qualified opportunities a rep can genuinely work at once. Those four numbers tell you what one healthy rep produces.
Then you adjust that baseline rep by rep. A rep in their fourth year who knows the product and sits on a mature book is not the same unit as someone you hired in Q4. Segment matters too: enterprise reps carry fewer, larger deals with longer cycles; SMB reps carry volume. Build your capacity model by segment first, then by individual within each segment.
When teams run this exercise honestly for the first time, the number that comes out is usually lower than the top-down ask. That's not a failure of the model. That's the model doing its job, surfacing the gap early enough to actually do something about it.
Treat ramp as real math, not a courtesy
The fastest way to blow up a quota plan is to assign full numbers to reps who aren't fully ramped. If a new AE takes, say, two quarters to reach full productivity, a rep who starts in April is not going to deliver an annual rep's worth of new business this year. That's not a performance problem. It's physics.
I build ramp directly into the quota. A rep's annual number should reflect their expected productivity across each quarter based on where they are in their ramp curve. Someone hired mid-year carries a prorated, ramp-adjusted quota, not a full one with a mental asterisk. The asterisk never survives contact with the comp plan, and a rep who's set up to miss from day one disengages fast.
Here's a simplified view of how ramp changes a rep's contribution within a year:
| Rep status | Start point | Expected % of full capacity (year 1) | Planning implication |
|---|---|---|---|
| Fully ramped | Day 1 of plan year | ~100% | Carries full capacity number |
| Mid-ramp | Hired prior Q3–Q4 | ~70–85% | Discount for remaining ramp quarters |
| New hire, Q1 start | Start of plan year | ~40–60% | Ramp-adjusted quota, grows quarterly |
| New hire, mid-year start | Q3 or later | ~15–30% | Prorated and ramp-adjusted; minimal year-1 load |
Treat those percentages as placeholders for your own ramp data, not gospel. The point is that a planned headcount number is not a planned capacity number. Ten reps on the roster where four are still ramping do not produce ten reps' worth of quota. Finance needs to understand this, because it's the difference between a forecast that holds and one that quietly erodes every quarter as new hires miss targets they were never positioned to hit.
Allocate by territory potential, not equal shares
Once you know aggregate capacity, you have to split it across the field. Equal division feels fair and is almost always wrong, because territories are not equal. One rep's patch might have 400 target accounts with strong fit and active buying signals. Another's might have 120 accounts, half of which already churned once. Giving them the same quota punishes the second rep for geography and lets the first one coast.
Allocate against territory potential instead. Potential is some function of the number of addressable accounts, their fit and size, existing penetration, and pipeline already in motion. You don't need a perfect model. Even a rough scoring of each territory on account count, average account value, and current coverage gets you far closer to fair than dividing by headcount. A rep sitting on a dense, high-fit territory should carry more than a rep opening a thin or new region, and both should feel the number matches their patch.
This is where quota setting and territory design feed each other. If you can't make the quotas balance across territories, that's often a signal the territories themselves need to be redrawn, not that someone's number needs a nudge. Good RevOps treats these as one connected system rather than two separate spreadsheets. If you want help wiring territory data, capacity models, and pipeline signals into a single system that updates as reality changes, that's a core part of what we build into a revenue engine, and you can see how we scope it in our packages.
Stress-test coverage before you ship it
The last step before anyone sees their number: check that the plan survives imperfection. Total quota across the team should exceed the company target, not just equal it. That buffer, often called coverage or over-assignment, exists because not every rep hits plan. If you assign exactly the company number across the field and anyone comes in under, you miss by definition.
I model this directly. Take total assigned quota, multiply by a realistic blended attainment rate drawn from your own history, and see what lands. If your team historically attains 85% of quota on average and you want to clear the company target with confidence, your total assigned quota needs enough cushion to absorb that. When the math says attainment times assigned quota falls short of the target, the plan is already broken and you haven't even launched. Fix it now by adjusting coverage, hiring, or pipeline assumptions, not in Q3 when the hole is undeniable.
One caution: there's a difference between healthy coverage and silent sandbagging the other direction. Pile too much over-assignment on top of ramp discounts and thin territories and you've recreated the exact impossible number you were trying to avoid. The coverage buffer protects the company against variance. It's not a license to inflate individual quotas past what capacity supports.
Where the number ends and the pay begins
Everything above produces one output: a defensible quota number for each rep, built from capacity, ramp, and territory, stress-tested for coverage. That's the end of quota setting. What happens to a rep financially when they hit 80% or 120% of that number is a separate discipline. Commission rates, accelerators above target, draws during ramp, and SPIFs all belong to compensation design, and they should be built on top of a quota you already trust.
The reason to keep them separate is practical. The moment you design the number and the pay in the same conversation, people start reverse-engineering the quota to protect their earnings, and you lose the objective capacity logic that made the number credible. Set the quota on the merits. Then design comp to reward the behavior and outcomes you want against that quota. Two steps, two conversations, in that order.
Frequently asked questions
How often should we revisit sales quotas during the year?
Review the inputs quarterly, even if you hold annual quotas steady. Ramp status changes, territories shift, reps leave, and pipeline moves. A mid-year check catches a plan drifting away from reality before the gap becomes unrecoverable. I'd avoid changing an individual's number mid-year except for structural changes like a territory split, because moving the target erodes trust fast.
What's the right quota coverage ratio?
There's no universal figure, and anyone quoting you a precise one across all companies is guessing. Derive it from your own blended attainment. If your team reliably attains most of quota, you need less over-assignment; if attainment is volatile, you need more buffer to protect the company number. The ratio is an output of your historical data, not an industry constant.
Should new reps get a reduced quota or a draw instead?
Both, and they solve different problems. A ramp-adjusted quota keeps the plan honest about what a new rep can produce, which protects your forecast. A guaranteed draw protects the rep's income while they build pipeline, which is a comp decision. Use the reduced quota for planning accuracy and the draw for retention. They work together.
If your quota plan is built on last year's number times a growth multiple divided by headcount, it's worth pressure-testing before the year gets away from you. Book a Revenue Systems Audit and we'll walk through your capacity model, territory data, and coverage math together.