SDR Quota Design by ACV Tier (with Math)

SDR quotas set wrong are one of the most expensive operational mistakes in outbound-led SaaS growth. Set too high, and you burn out SDRs and see attrition spike. Set too low, and you underutilize expensive headcount and create false pipeline confidence. Set them to the wrong metric entirely — activities rather than pipeline output — and you build a theater of motion that looks productive in dashboards while starving the AE team of real pipeline.

Getting SDR quota design right requires starting from the revenue math, not from benchmarks. What quota does the business need this SDR role to contribute? Work backward from that number to define the right output metric, then layer activity benchmarks on top as leading indicators.

The Math That Should Drive Every SDR Quota

Starting Point: AE Pipeline Demand

Every SDR quota exists to serve an AE quota. The first question in SDR quota design is not "how many calls should an SDR make" — it's "how much pipeline does each AE need, and how much of that pipeline should come from outbound SDR activity?"

AE Pipeline Demand Formula:

AE Pipeline Required = (AE Quota / Average ACV) × Pipeline Coverage Ratio

Example for a mid-market AE with $1.2M annual quota, $60K ACV, and 3x coverage requirement:

AE Pipeline Required = ($1,200,000 / $60,000) × 3 = 60 opportunities per year = 15 per quarter

If outbound SDR activity is expected to source 50% of AE pipeline (with the rest from inbound and AE self-generated), the SDR contribution per AE is 7–8 qualified opportunities per quarter.

Pipeline Coverage Ratio by ACV Tier

Pipeline coverage ratio — the multiple of quota in open pipeline — varies by ACV and sales cycle length. Higher ACV deals have longer sales cycles and higher variance per deal, requiring higher coverage to hit forecast with confidence.

These ratios are grounded in Gartner's 2025 B2B Sales benchmarks, which show that enterprise deals close at 20–25% from qualified stage versus 35–45% for SMB, necessitating larger pipeline buffers.

SDR Quota Benchmarks by ACV Tier

SMB Tier (ACV <$15K)

Characteristics: High-volume, high-velocity. Qualification criteria are light. Decision-making is often single-threaded. Sales cycles run 14–45 days.

Output quota benchmark: 15–25 qualified meetings (SQLs) per month, or 45–75 per quarter.

Activity benchmarks (leading indicators):

• 60–90 cold calls per day
• 40–60 cold emails per day (across sequences)
• 10–15 LinkedIn touches per day

SDR-to-AE ratio: Typically 1:1 to 1:2 (one SDR supports one to two AEs).

At this ACV tier, SDR throughput is the constraint. The qualification bar should be efficient — do not apply enterprise-grade MEDDIC criteria to a $8K ARR deal. A confirmed pain point, a decision-maker engaged, and a meeting on calendar is a qualified opportunity for SMB.

Mid-Market Tier (ACV $15K–$75K)

Characteristics: Multi-threaded buying, moderate discovery required. Sales cycles run 45–90 days. Champion identification matters more than at SMB.

Output quota benchmark: 10–15 SQLs per month, or 30–45 per quarter.

Activity benchmarks:

• 40–60 cold calls per day
• 30–50 cold emails per day
• 15–20 LinkedIn touches per day (heavier research per account)

SDR-to-AE ratio: Typically 1:1 to 2:3 (two SDRs supporting three AEs).

Quality begins mattering more than quantity at this tier. An SDR who books 10 meetings per month with proper champion identification and confirmed budget awareness is more valuable than one booking 20 meetings with thin qualification.

Enterprise Tier (ACV >$75K)

Characteristics: Complex, multi-stakeholder, long-cycle. Research depth per account matters significantly. Qualification must meet MEDDIC or equivalent criteria.

Output quota benchmark: 4–8 qualified opportunities per month, or 12–25 per quarter.

Activity benchmarks:

• 20–35 cold calls per day (more research time required)
• 20–30 cold emails per day (higher personalization, lower volume)
• 20–30 LinkedIn research and engagement actions per day

SDR-to-AE ratio: Typically 2:1 or 3:1 (multiple SDRs per AE), because AE bandwidth is expensive and AE capacity should not be wasted on thin pipeline.

RAIN Group's 2025 outbound benchmarks show that enterprise SDRs spending more than 40% of their time on account research and personalization (versus raw activity) generate 35% more pipeline per hire than those optimized purely for activity volume.

Working the Math: Three Worked Examples

Example 1: SMB SaaS, 5-SDR Team

Inputs:

• ACV: $8,000
• AE Quota: $600,000/year
• Pipeline Coverage Required: 2.5x
• SDR-sourced pipeline: 40% of total
• SDRs on team: 5

AE Pipeline Math:

Total AE pipeline needed = ($600,000 / $8,000) × 2.5 = 187.5 opportunities/year
SDR-sourced opportunities needed = 187.5 × 0.40 = 75 opportunities/year per AE
SDR monthly quota = 75 / 12 = 6.25 → round to 6–7 SQLs/month per SDR

Team output check: 5 SDRs × 6.5 SQLs/month = 32.5 SQLs/month = 390/year At $8K ACV × 2.5x coverage = $3.12M in annual pipeline contribution from SDR team.

Example 2: Mid-Market SaaS, 3-SDR Team

Inputs:

• ACV: $45,000
• AE Quota: $1,800,000/year
• Pipeline Coverage Required: 3.5x
• SDR-sourced pipeline: 50%
• SDRs on team: 3

AE Pipeline Math:

Total pipeline needed = ($1,800,000 / $45,000) × 3.5 = 140 opportunities/year
SDR-sourced = 140 × 0.50 = 70 opportunities/year
SDR monthly quota = 70 / 12 = 5.8 → round to 6 SQLs/month per SDR

Team output check: 3 SDRs × 6 SQLs/month = 18 SQLs/month = 216/year At $45K ACV × 3.5x = $3.43M annual SDR pipeline contribution.

Example 3: Enterprise SaaS, 4-SDR Team

Inputs:

• ACV: $180,000
• AE Quota: $4,500,000/year
• Pipeline Coverage Required: 5x
• SDR-sourced pipeline: 35%
• SDRs on team: 4

AE Pipeline Math:

Total pipeline needed = ($4,500,000 / $180,000) × 5 = 125 opportunities/year
SDR-sourced = 125 × 0.35 = 43.75 opportunities/year
SDR monthly quota = 43.75 / 12 = 3.6 → round to 4 qualified opportunities/month per SDR

Team output check: 4 SDRs × 4 qualified opps/month = 16/month = 192/year At $180K ACV × 5x coverage = $8.6M annual SDR pipeline contribution.

The Ramp Period: Adjusting Expectations for New SDRs

New SDRs do not hit full productivity on day one. A realistic ramp schedule:

For enterprise SDRs with longer account research requirements, ramp typically extends to month 5–6 before full quota expectations are appropriate.

Ramp adjustment has a material impact on SDR team planning. If the business needs to generate $X in SDR pipeline starting in Q3, a new SDR hired in Q2 will not be at full productivity until Q4. Revenue operations teams that ignore ramp when modeling SDR headcount needs consistently end up pipeline-short relative to plan.

Activity Quotas as Leading Indicators

Activity quotas — calls per day, emails per day, LinkedIn touches per day — are forecasting tools and coaching levers, not the primary accountability metric.

The right way to set activity quotas is to work backward from pipeline output targets:

Target SQLs per month = 8
Average conversion from connect to SQL = 20%
Connects needed per month = 40
Average connect rate from cold calls = 8%
Cold calls needed per month = 500
Working days = 22
Daily call quota = 23 calls/day

This math gives the SDR a clear line of sight from daily activity to monthly output. It also gives the manager a diagnostic tool: if an SDR hits activity quotas but misses pipeline quotas, the problem is conversion rate (targeting, messaging, qualification). If an SDR hits pipeline quotas but not activity quotas, they're working efficiently — that's worth understanding, not penalizing.

For deeper context on how pass criteria and qualification standards connect to SDR output quality, see SDR-to-AE Pass Criteria. The methodology for building the content and playbooks that support SDR conversations is covered in the SaaS sales enablement content library.

Quota Attainment Benchmarks and What They Signal

Tracking quota attainment distribution across the SDR team reveals system-level problems that individual attainment hides.

Healthy attainment distribution (target):

• <70% attainment: fewer than 20% of SDRs
• 70–100% attainment: 50–60% of SDRs
• >100% attainment: 20–30% of SDRs

If more than 40% of SDRs are below 70% attainment, the quota is likely set too high, the ICP is too narrow, the tooling is insufficient, or the ramp program is too short. All four should be investigated.

If more than 50% of SDRs consistently exceed 100% attainment, the quota is set too low — and the organization is likely leaving pipeline on the table by not pushing harder on outbound investment.

SalesLoft's 2025 SDR operations report found that organizations with proper quota calibration (defined as 20–30% over-attainment) showed 40% lower SDR attrition than those with either very high or very low average attainment — suggesting that achievable-but-stretching quotas are a retention lever as much as a performance lever.

Connecting SDR Quota to the Broader Revenue Model

SDR quota does not exist in isolation. It's one lever in the expansion revenue forecasting model and the broader outbound vs inbound allocation decision framework.

The quota design exercise should be revisited every six months in a growing SaaS business — as ACV shifts, win rates change, and pipeline coverage empirics develop, the math that drove last year's quota may no longer reflect current reality. Treat SDR quota design as a living model, not an annual HR exercise.

Frequently Asked Questions

What happens when SDR quota design is misaligned with AE quota?

The most common failure mode is SDR quotas designed too high relative to AE pipeline capacity. SDRs generate meetings that AEs cannot absorb, causing meeting no-shows (prospects who waited too long to connect with an AE lose interest) and AE perception of poor SQL quality. The fix is to verify that SDR pipeline output × conversion rate to close matches AE quota at the team level — if they don't reconcile, one of the numbers is wrong.

Should SDR compensation be tied entirely to quota attainment?

Compensation design should weight toward pipeline output (SQLs, qualified meetings) rather than activities. A common structure is 60–70% base, 30–40% variable, with variable tied primarily to SQL attainment and secondarily to opportunity-to-AE advancement rate. Tying compensation entirely to activities creates gaming risk — SDRs optimize for the counted metric, not the downstream revenue outcome.

How do you handle quota for SDRs in multiple territory or segment assignments?

SDRs with split territory assignments should carry quotas that reflect the productivity profile of each segment, weighted by the share of time allocated. A SDR spending 60% on enterprise and 40% on mid-market should carry a blended quota: 0.6 × enterprise benchmark + 0.4 × mid-market benchmark. Applying a single benchmark across mixed assignments creates systematic under- or over-quotation depending on which segment is harder.

Conclusion

SDR quota design is revenue operations work, not HR work. The correct starting point is the AE revenue model: what pipeline does the business need, what fraction comes from outbound, and how many qualified opportunities must each SDR generate to support that math?

From that starting point, work backward to a pipeline-based output quota. From that quota, work forward to the activity benchmarks that predict attainment. Monitor attainment distribution at the team level, not just average attainment, to diagnose whether the quota is calibrated correctly.

ACV tier drives almost everything in this model — qualification standards, activity-to-pipeline conversion rates, ramp time, and SDR-to-AE ratios all scale with deal size. Build the math for your specific tier, revisit it every six months, and treat it as the operational foundation for every other outbound investment decision.