Sales Quota Setting: How to Set Realistic B2B Rep Targets That Drive Growth Without Burning Out Your Team
By Rick Elmore ·
Most quota misses are decided before the quarter starts. Not by the reps, and not by the market—by the person who typed a number into a spreadsheet without doing the math underneath it. If your team hit 62% of quota last year and you responded by raising the number, you didn't set a target. You set a trap.
Sales quota setting is the process of translating your revenue goal into per-rep targets that are grounded in capacity, territory potential, and real attainment history—not just divided evenly from a board slide. Done right, quotas pull growth forward. Done wrong, they inflate pipeline theater, drive your best reps out the door, and leave you guessing why forecast and reality never agree.
This post is about the math and the method. Not comp plans, not territory design—those are separate decisions. Here we're answering one question: what number should each rep carry, and how do you defend it?
Top-down vs. bottom-up quota setting: which actually works?
There are two ways to arrive at a quota, and most companies use the wrong one because it's faster.
Top-down starts with a company goal—say, $12M in new revenue—and divides it by headcount. Twelve reps, a million each. Clean, fast, and almost always disconnected from what any individual rep can realistically produce. Top-down answers "what do we need?" and ignores "what can we actually do?"
Bottom-up starts from the rep. How many accounts can one person work? What's the conversion rate at each stage? What does the territory contain? You build each rep's achievable number from their inputs, sum it up, and compare that total against the company goal. When there's a gap—and there usually is—you've found a real problem to solve instead of papering over it with an aggressive number.
| Dimension | Top-down | Bottom-up |
|---|---|---|
| Starting point | Company revenue goal | Individual rep capacity and territory |
| Speed to set | Fast | Slower, requires data |
| Rep buy-in | Low—feels imposed | High—grounded in their reality |
| Forecast accuracy | Poor | Strong |
| Surfaces hiring/coverage gaps | No | Yes |
| Risk of burnout | High | Low |
The honest answer: you need both, in that order. Build bottom-up to find what's achievable, then use the top-down goal as a stress test. If bottom-up says the team can produce $9M and leadership wants $12M, the difference isn't a quota increase. It's a decision about headcount, pipeline investment, or expectations. The quota should never be the place where that gap gets hidden.
How to calculate rep capacity before you set a single number
Capacity is the ceiling. A rep can only touch so many accounts, run so many meetings, and close so many deals in a quarter. If your quota assumes more than their capacity allows, it's fiction from day one.
Work it out in steps:
- Start with selling time. A rep does not sell 40 hours a week. Pull out internal meetings, admin, ramp, and dead time. Most reps have roughly 25–30 genuinely productive selling hours. Use your own data, not the gross number.
- Find your average deal cycle and touch load. How many meetings, calls, and follow-ups does one closed deal require from first contact to signature? Count the whole motion, not just the demo.
- Calculate how many active opportunities a rep can carry. Divide available selling time by the time each live opportunity demands. This gives you a realistic concurrent pipeline count—often lower than managers assume.
- Apply your true win rate. Not the aspirational one. The win rate your CRM actually shows over the last four quarters, segmented by lead source if the numbers differ enough to matter.
- Multiply by average deal size. Capacity in opportunities × win rate × average contract value = the revenue one rep can plausibly produce in the period.
Here's where most teams slip: they skip the capacity math entirely and reverse-engineer activity from the quota. "You need $1M, so you need 40 deals, so make 100 calls a day." That's backwards. It assumes the number is correct and treats the rep as the variable. Capacity-first flips it. The rep's realistic output is the input, and the quota has to respect it.
If the capacity math produces a number well below your goal, you've learned something valuable before the quarter started: you don't have a performance problem yet, you have a capacity problem. Fix it with more reps, better lead flow, or a shorter sales cycle—not with a bigger number on the same person.
Using historical attainment to pressure-test your targets
Capacity tells you the ceiling. History tells you the pattern. You need both, because capacity is theoretical and attainment is what actually happened under real conditions.
Pull at least four quarters of attainment data, per rep where you can. The single most useful chart you can build is the distribution of attainment across the team. Not the average—the spread. Here's why the average lies: if half your team hits 130% and half hits 40%, the average looks like 85% and everything seems fine. In reality you have two different problems wearing one number.
What to look for in the distribution:
- Where does the middle of the pack land? If the median rep hits 70% of quota consistently, the quota is set about 40% too high, not the team underperforming by 30%.
- What percentage of reps hit 100%? A healthy quota has most of the team between roughly 80% and 120%, with top performers stretching higher. If only two of twelve reps clear quota, the number is broken.
- Is the spread about talent or about territory? If the top attainers all sit in mature territories, the gap is structural, not personal—and the quota should reflect territory potential, not a flat per-head figure.
A quota that almost nobody hits doesn't motivate. It teaches the team to stop believing the number, and once reps stop believing it, they stop managing to it. They sandbag, they disengage, and your forecast becomes noise. The goal is a target that most of the team can reach with strong effort and that the best can beat—tension, not fantasy.
Adjusting for territory and ramp so the math is fair
A flat quota across unequal territories isn't simple, it's lazy. Two reps with identical skill will post wildly different numbers if one works a dense, mature book and the other works a greenfield region with no brand awareness. Charging them the same quota punishes the rep you assigned the harder job.
You don't need a perfect model. You need to weight quotas against the factors that genuinely move outcomes:
- Account potential: total addressable spend in the territory, not just account count.
- Existing penetration: how much of that potential is already won versus open.
- Pipeline inheritance: a rep walking into live, qualified opportunities starts ahead of one starting cold.
- Lead support: territories fed by consistent inbound or outbound flow carry more; starved territories carry less.
Ramp deserves its own treatment. A rep in their first two quarters cannot carry a full quota, and pretending otherwise just manufactures an early miss that poisons their confidence. Set ramped quotas that step up over the first two to three quarters based on your actual average time-to-productivity. If your data says reps reach full output in month five, don't hand them a full number in month two. A new hire who misses an impossible ramp quota often reads it as "I'm failing" and leaves right before they would have become productive.
Building the quota model and keeping it alive
Put the pieces together in one defensible model. The sequence matters:
- Calculate bottom-up capacity for each rep or role.
- Overlay historical attainment to sanity-check what capacity predicts against what actually happens.
- Adjust for territory weight and ramp stage so individual numbers reflect the actual job.
- Sum the team total and compare it to the company goal.
- Resolve the gap honestly—through headcount, pipeline investment, or revised expectations, never by silently inflating individual numbers.
The piece most teams skip entirely: quota setting is not an annual event. Territories shift, reps ramp, win rates move, and the market changes. A quota set in January against last year's conversion data can be meaningfully wrong by Q3. Review attainment distribution every quarter. If the pattern breaks—say a segment's win rate drops because of a new competitor—your quota math is now feeding you bad targets, and you'll see it in the distribution before you see it in the forecast.
This is where connected systems earn their keep. When your CRM, pipeline data, and attainment reporting live in one place instead of three disconnected tools and a spreadsheet, the inputs to your quota model stay current automatically. You can see capacity, win rate, and attainment move in real time instead of reconstructing them once a year from memory. That's the difference between a quota you set and forget and one that actually steers the business. If you want help wiring that together, it's part of how we think about building a revenue engine across our packages.
Where this fits
Quota setting sits at the center of RevOps because it's where strategy meets reality. Get it right and everything downstream—forecasting, comp, hiring plans, coaching priorities—runs on solid ground. Get it wrong and every other system inherits the error. The discipline is simple to state and easy to skip: build from the bottom up, respect capacity, pressure-test against history, weight for territory and ramp, and revisit the math as conditions change. The reward is a team that trusts its numbers and chases them, instead of one that quietly writes them off in week two. Quota, comp design, and territory planning work as a system; this post covered the target math, but the real gains come when all three are built together and fed by connected data.
Want a second set of eyes on how your targets, pipeline, and systems line up? Book a Revenue Systems Audit and we'll pressure-test your quota math against your real capacity and attainment data.