Setting Sales Quota in SaaS

The backbone article on quota-setting covers the four methods — historical, top-down, market-based, activity-based — and the attainment distribution you're targeting. SaaS adds a specific complication: the metric isn't revenue, it's ARR. And ARR has variants — new ARR, expansion ARR, net new ARR — that each behave differently in a quota model.

Most SaaS companies set quota top-down from the board plan. The CEO commits to $40M in new ARR. Sales leadership divides by headcount, adjusts for ramp, and calls it done. The result: quotas that reflect what the company needs, not what the territories can produce. QuotaPath's 2024 data — 91% of organizations missing quota expectations — is disproportionately a SaaS number.

ARR is the metric, but which ARR

A SaaS AE might carry quota on new logo ARR, expansion ARR, or total net new ARR. Each creates a different quota dynamic.

New logo ARR is the cleanest to quota against. The rep sources and closes new customers. The territory's opportunity is estimable from account lists and market sizing. Historical close rates apply. This is where the standard quota-setting methods work best.

Expansion ARR is harder. The opportunity is a function of the installed base — how many customers are in the territory, what they're currently paying, and how much headroom exists. An expansion rep with 200 accounts at 60% product penetration has a fundamentally different opportunity than one with 50 accounts at 90% penetration. Setting equal expansion quotas across unequal books is the territory variance problem from the backbone, magnified.

Net new ARR (new logo + expansion - churn) is the most honest metric but the hardest to quota. The rep controls acquisition and expansion but has limited control over churn. Penalizing a rep for churn they couldn't prevent is the same problem as holding a rep accountable for a market disruption — it breaks the link between effort and outcome.

If you quota on net new ARR, separate the churn component. Set the quota on gross additions (new + expansion) and handle retention through a separate modifier or gate — not by burying churn inside the quota number where it silently punishes the rep.

Product-line splits create hidden quota problems

Multi-product SaaS companies often split quota by product line: $600K in Platform ARR, $200K in Analytics ARR, $100K in Security ARR. The intent is to drive balanced selling across the portfolio. The effect is three quotas masquerading as one.

The rep now has to hit three targets, and the commission math changes depending on which product they sell. If Platform deals are easier to close but Analytics has a higher attach rate, the rep will over-index on Platform and neglect Analytics — exactly the opposite of what the split was designed to do.

Two approaches that work better. First: set a single ARR quota with a product-mix modifier. If the rep hits $900K total ARR but less than 15% comes from Analytics, they earn at base rate. If the mix is balanced, they earn at an elevated rate. This preserves a single quota while incentivizing portfolio breadth. Second: separate the roles. If the product lines are different enough to need independent quotas, they're different enough to need independent sellers.

Usage-based pricing breaks traditional quota models

Consumption-based SaaS — where the customer commits to a platform but usage determines the bill — creates a quota problem that traditional ARR models don't handle. The rep closes a $100K committed contract, but actual consumption might land at $60K or $180K depending on the customer's adoption.

Quota on committed value rewards the rep for the deal they closed. Quota on consumption rewards the rep for outcomes they may not control. Neither is fully correct.

The emerging pattern: quota on committed value for the initial sale, with a consumption modifier that adjusts payout based on actual usage within a defined band. If consumption lands between 80% and 120% of committed value, no adjustment. Below 80%, payout is reduced (the deal was oversold). Above 120%, the rep earns a bonus (the deal was undersold or adoption exceeded expectations). This keeps quota anchored to what the rep can control — the deal — while creating a feedback loop on deal quality.

Territory sizing in SaaS is measurable — use it

SaaS has better territory data than almost any other industry. You know your ICP. You have firmographic data on every account. You can count the number of companies in each territory that match your buyer profile, estimate deal size by segment, and apply historical conversion rates.

This means the market-based quota method — the most rigorous and hardest to execute — is more feasible in SaaS than anywhere else. Use it. Not as the sole input, but as the primary sanity check on whatever quota your top-down model produces.

If your top-down quota for a territory implies capturing 35% of the addressable opportunity and your best territories historically convert at 15%, the quota is fiction. The territory data will tell you, if you look.

Pull total addressable accounts by segment, multiply by average deal size, apply your historical stage-to-close conversion rate, and compare the result to the quota you're about to assign. If the quota exceeds what the data says is achievable, either the territory needs more accounts or the quota needs to come down.

Ramp quota calibration from cohort data

The backbone covers ramp schedules in general. In SaaS, you have the data to calibrate them precisely. Pull every AE hired in the last two years. Plot their monthly new ARR bookings as a percentage of full quota by month of tenure. The median curve across the cohort is your ramp schedule.

Most SaaS companies discover their actual ramp is 5–7 months to consistent full-quota performance — not the 3–4 months their ramp comp plan assumes. Setting ramp quotas from actual cohort data instead of assumptions eliminates the structural gap between what the plan expects and what the rep can deliver.

What to check before finalizing

• Quota metric is clearly defined — new logo ARR, expansion ARR, or gross additions — not net new ARR with churn buried inside
• Product-line quotas are either consolidated into a single target with a mix modifier, or assigned to separate roles
• Usage-based pricing is handled with a consumption modifier, not a pure committed-value or pure consumption quota
• Territory quotas are validated against addressable market data, not just divided equally from the top-down target
• Ramp quotas are derived from actual AE cohort performance data, not from a generic 25/50/75/100 schedule
• Attainment distribution from last year is calculated — if fewer than 50% of reps hit quota, the quota is too high regardless of what the board plan says

For the full framework on quota-setting methods, attainment targets, and mid-year adjustments, see the backbone guide on how to set sales quota.

More on SaaS sales compensation

• Accelerators in SaaS Sales — Accelerator thresholds depend on quota accuracy
• Draws in SaaS Sales — How quota levels drive draw amounts and recovery timelines
• Ramp Compensation in SaaS Sales — Reduced quotas during ramp are a quota-setting decision