The Spreadsheet Exercise That Breaks Your Sales Org

Every January, the same ritual plays out. The board sets a revenue target. Finance divides it by the number of quota-carrying reps. Leadership adds a buffer for attrition and ramp. The result gets called a “stretch target” and pushed down to the field.

This is not quota setting. This is arithmetic disguised as planning.

I have watched this process destroy sales organisations from the inside. Not because the targets were ambitious. Because the targets were disconnected from any structural reality about what each rep could actually produce. The number had nothing to do with territory size, pipeline maturity, deal velocity, or market density. It was a top-down allocation masquerading as a bottoms-up plan.

The problem is not that quotas are hard. Hard quotas are fine. The problem is that most quotas are not hard. They are arbitrary. And arbitrary quotas produce arbitrary behaviour.

The Behaviour Distortion Nobody Models

When a rep receives a quota they believe is unattainable, they do not simply “try harder.” They adapt. And the adaptations are corrosive.

Sandbagging becomes rational. If a rep knows they cannot hit their number regardless of effort, they start managing to the next quarter instead. Deals that could close in Q1 get pushed to Q2 so the rep has a head start. Pipeline gets hidden. Forecasts become fiction.

Discounting accelerates. Reps facing impossible numbers start pulling every lever they can control. The easiest lever is price. Discount approvals spike. Average deal sizes compress. Margin erodes. And because leadership sees the revenue shortfall and pressures reps to close faster, they inadvertently reinforce the discounting behaviour they are trying to prevent.

Attrition follows a pattern. The reps who leave first are not the underperformers. They are the high performers who did the math, realised the quota was structurally broken, and decided to go somewhere with a fairer design. What remains is a team of reps who have learned to game the system rather than sell through it.

This is not a motivation problem. This is a design problem that sits at the intersection of compensation architecture and territory planning. And it compounds every quarter you ignore it.

What Capacity-Based Quota Design Actually Looks Like

A properly designed quota starts from the bottom, not the top. It begins with a capacity model that answers a simple question: given this rep’s territory, ramp status, pipeline, and historical conversion rates, what is a realistic but demanding production target?

The inputs are not complicated. They are just rarely assembled in one place.

Territory potential. How many accounts sit in this rep’s territory? What is the total addressable revenue? What share of wallet is realistic given competitive dynamics and product fit? If you have not done the territory design work to answer these questions, you are guessing at quotas.

Pipeline coverage. What does the rep’s current pipeline look like relative to their target? What is the weighted value at each stage? What are their historical stage-to-stage conversion rates? A rep with 2x coverage and strong conversion rates can absorb a higher quota than a rep with 1.5x coverage and a leaky mid-funnel.

Ramp and tenure. A rep in month three should not carry the same quota as a rep in month eighteen. This seems obvious, but I consistently see organisations apply a flat ramp schedule that bears no relationship to actual productivity curves. Your data tells you how long it takes reps to reach full productivity. Use it.

Capacity constraints. How many opportunities can a rep realistically work at any given time? What is the average sales cycle? How much time gets consumed by non-selling activities? These constraints set a ceiling on production that no amount of motivation can exceed.

When you build quotas from these inputs, you get something powerful: a number that each rep can look at and believe is achievable with strong execution. That belief is not a nice-to-have. It is the foundation of accountability. You cannot hold someone accountable to a number they had no structural path to reach.

Quotas Must Reflect Territory Potential

This is where most quota processes fall apart, even the ones that attempt a bottoms-up approach. They set quotas without first ensuring that territories are balanced.

If Rep A sits on a territory with 200 qualified accounts and Rep B sits on a territory with 80, giving them the same quota is not equitable. It is negligent. Rep A will cruise to attainment while Rep B burns out chasing an impossible number. Both outcomes are bad. Rep A learns that mediocre effort is sufficient. Rep B learns that effort is irrelevant.

Quota setting and territory design are the same conversation. You cannot do one without the other. If your territories are imbalanced, your quotas will be imbalanced, and no amount of “stretch” language will fix it.

This is one of the reasons revenue targets fail at the execution layer. The target itself might be reasonable in aggregate. But the allocation across territories makes it structurally impossible for a portion of the team, which drags down the entire number.

The fix is straightforward but requires discipline. Balance territories first. Then set quotas based on each territory’s potential. If the sum of bottoms-up quotas does not meet the top-down target, you have a capacity problem, not a quota problem. The answer is to hire more reps, expand territories, or adjust the target. The answer is never to inflate individual quotas beyond what the territory can support.

Model Attainability Before You Commit

Before you finalise quotas, run a simple attainability model. Take each rep’s quota and work backwards through their pipeline, conversion rates, and deal velocity. Ask: what would need to be true for this rep to hit this number?

If the answer requires a rep to close at twice their historical win rate, or to generate pipeline at a pace they have never achieved, or to land deals in accounts with no existing relationship, the quota is not a stretch target. It is a fantasy with a commission plan attached.

I recommend modelling three scenarios for every quota: a base case using historical performance, an upside case assuming meaningful improvement, and a downside case assuming some regression. If the quota falls above the upside case for more than 20% of your reps, your plan has a structural problem.

This modelling takes a few hours. The cost of not doing it is a quarter of distorted behaviour, missed forecasts, and incentive structures that drive the wrong outcomes. The math is not hard. The discipline to do it before committing is what separates functional revenue operations from reactive ones.

The Quarterly Review Trap

Many organisations acknowledge that their initial quotas might be imperfect and plan to “adjust at the quarterly review.” This sounds reasonable. In practice, it is a trap.

By the time you adjust quotas mid-year, the behaviour damage is already done. A rep who spent Q1 sandbagging because their quota was unattainable does not suddenly become a high performer when you lower their Q2 number. They have already adapted. The pipeline is already hidden. The discounting patterns are already established. The top performers are already interviewing elsewhere.

Quarterly reviews should be checkpoints, not redesign sessions. If you are making material quota adjustments every quarter, your initial design process is broken. Fix the process, not the symptoms.

The exception is a genuine market shift: a new competitor enters, a product launch gets delayed, a major segment contracts. These are legitimate reasons to revisit quotas mid-cycle. “We set the number too high” is not a market shift. It is a planning failure.

RevOps Must Own Quota Governance

Here is where I will be direct about organisational accountability. Quota governance belongs in RevOps, not in sales leadership and not in finance.

Sales leadership has an inherent conflict of interest. They want quotas low enough to ensure attainment, which protects their team’s earnings and their own credibility. Finance wants quotas high enough to meet the board target, which protects the plan. Neither perspective, in isolation, produces good quota design.

RevOps sits at the intersection. We have the data on territory potential, pipeline health, historical conversion, and capacity constraints. We have the analytical framework to model attainability. And we have the organisational independence to push back when either sales or finance tries to override the model with politics.

This does not mean RevOps sets quotas in a vacuum. It means RevOps owns the methodology, builds the model, and presents a recommendation that sales and finance can pressure-test. The final number is a leadership decision. But it should be an informed leadership decision, grounded in structural analysis rather than negotiation and gut feel.

If your organisation does not have this function in place, that is the first problem to solve. A RevOps team with the right mandate can transform quota setting from a political exercise into an engineering discipline. The result is not just better quotas. It is better forecasts, better retention, and better execution across the entire revenue engine.

Quota setting is not a math problem. It is a design problem. And like all design problems, the quality of the output depends entirely on the rigour of the process. Start with capacity. Ground it in territory reality. Model attainability before you commit. And give governance to the team with the data and the independence to get it right.