How do you set sales quotas in 2027 when AI generates a large share of the pipeline?

👁 0 views📖 2,245 words⏱ 10 min read5/28/2026

Direct Answer

Build quotas bottom-up from rep capacity (ramped reps multiplied by productivity, ASP, and win rate), then weight pipeline by source — discount AI-sourced pipeline 0.6 to 0.8x because it converts worse than inbound or warm referrals. Target 60 to 70 percent of reps hitting quota; if AI inflates raw pipeline volume, resist raising the number until the conversion data justifies it.

In 2027 a mid-market SaaS AE quota runs 5 to 6x on-target earnings, so a $250K OTE rep carries roughly $1.25M to $1.5M in annual quota. The mistake to avoid is treating an AI-generated meeting as equal to a referral-generated one. Tools like Clari, Gong, Xactly, QuotaPath, and CaptivateIQ now segment pipeline by origin and let RevOps apply a conversion multiplier before the quota math ever begins.

Set the company revenue target first, build a capacity model second, apply a coverage ratio third, weight pipeline by source fourth, distribute with ramp and attrition buffers fifth, and stress-test the attainment curve last. A quota plan that ignores source quality looks aggressive on paper and collapses by Q2 when AI-sourced deals stall in the funnel.

1. The three quota-setting methods

Every quota model descends from one of three approaches, and most strong 2027 plans blend them.

Top-down starts with the board-approved revenue number and divides it across the sales team: revenue target divided by number of reps, adjusted for ramp, attrition, and seasonality. It is fast and aligns to investor expectations, but it ignores whether reps can physically carry the load.

A $30M target split across 20 AEs implies $1.5M each — fine if capacity supports it, reckless if it does not.

Bottom-up (capacity-based) starts from what each rep can realistically produce given territory, segment, average selling price, and historical win rate, then sums upward to see whether the total clears the company target. Bottom-up is the honest method. It surfaces the gap between ambition and capacity before the year starts rather than in the Q3 board deck.

Hybrid is what disciplined RevOps teams actually run: build bottom-up to establish a credible capacity ceiling, compare it to the top-down target, and negotiate the delta through hiring, productivity programs, or a target reset. Salesforce, HubSpot, and Pavilion member operators all describe the same loop — the two numbers rarely match on the first pass, and the reconciliation is the real work.

1.1 When each method fits

Early-stage companies with thin historical data lean top-down because they have no reliable capacity baseline yet. Companies with two-plus years of clean pipeline history in Clari or Gong should anchor on bottom-up, because the win-rate and ASP inputs are trustworthy. Anyone scaling a new segment — adding enterprise on top of an SMB motion, for example — must build a separate capacity model per segment rather than averaging them, because the win rates and sales cycles differ too much to blend.

2. Building a capacity-based quota model

The capacity model is the spine of any defensible quota. The formula in plain terms: ramped AE capacity multiplied by productivity multiplied by ASP multiplied by win rate, then layered with a coverage ratio to derive the pipeline a rep needs to generate that bookings number.

Start with ramped AE capacity — the count of reps available, adjusted for where each sits on the ramp curve. A rep in month two is not a full producer. Multiply each rep's nominal capacity by their ramp factor (more on this in section five).

Layer in productivity: how many deals a fully-ramped rep closes per quarter at the segment's typical ASP and win rate. If a mid-market rep works 40 qualified opportunities a quarter, wins 25 percent, and the ASP is $40K, that is 10 wins worth $400K per quarter, or $1.6M annualized before ramp and attrition haircuts.

Then apply the coverage ratio. Pipeline divided by quota typically lands at 3 to 4x in 2027 — meaning a rep carrying $1.5M in quota needs roughly $4.5M to $6M in generated pipeline to hit it at normal win rates. Coverage is where the AI-pipeline question becomes unavoidable, because not all of that $6M converts at the same rate.

flowchart TD A[Company Revenue Target] --> B[Count Ramped AE Capacity] B --> C[Multiply by Productivity per Rep] C --> D[Apply ASP and Win Rate] D --> E[Derive Bookings Capacity] E --> F[Apply Coverage Ratio 3-4x] F --> G[Required Pipeline by Rep] G --> H{Pipeline Sources} H --> I[Inbound 1.0x] H --> J[Outbound-Human 0.8x] H --> K[AI-Sourced 0.6-0.8x] I --> L[Source-Weighted Pipeline] J --> L K --> L L --> M[Final Quota per Rep]

The model output is a per-rep bookings number that rolls up to a team total. If that total falls short of the top-down target, the gap is a hiring problem, a productivity problem, or a target problem — not something to paper over by raising individual quotas past what capacity supports.

3. Why AI-sourced pipeline needs a conversion discount

This is the 2027 wrinkle. When AI agents and automated outbound generate a large share of meetings, raw pipeline volume balloons, and the naive reaction is to raise quota proportionally. That is the central error of AI-era quota setting.

The data does not support equal treatment. Across 2027 benchmarks compiled by groups like Bridge Group, ICONIQ Growth, and the Bessemer State of Cloud report, AI-outbound meetings convert 30 to 50 percent worse than warm referrals and meaningfully worse than inbound demo requests.

The lead is colder, the intent is weaker, and the qualification is thinner. A meeting an AI agent booked from a cold sequence is not the same asset as a meeting a customer requested.

The fix is a source-weighted pipeline. Segment generated pipeline into inbound, outbound-human, and AI-sourced buckets, then apply a conversion multiplier before computing coverage: inbound at roughly 1.0x, outbound-human around 0.8x, and AI-sourced pipeline discounted to a 0.6 to 0.8x multiplier depending on your own observed conversion delta.

Mediafly, BoostUp, and Gong all support source-tagging that makes this measurable rather than a guess.

Practically: if a rep generates $6M in raw pipeline but $3M of it is AI-sourced at a 0.7x weight, the effective coverage is $3M inbound/human plus $2.1M weighted AI, or $5.1M against a $1.5M quota — a 3.4x effective ratio, not the 4x the raw number implied. Quota should be set against the weighted pipeline, never the raw volume. Otherwise the plan assumes conversions that the AI-sourced deals will not deliver, and attainment cracks mid-year.

4. 2027 quota and attainment benchmarks

Concrete numbers anchor the model. The 2027 ranges that RevOps Co-op operators, Winning by Design, and SaaStr data converge on:

Mid-market SaaS AE quota: 5 to 6x OTE. A $250K OTE rep carries $1.25M to $1.5M.
Enterprise AE quota: 4 to 5x OTE. Longer cycles and higher ASPs lower the multiple.
SMB AE quota: 6 to 8x OTE. Higher velocity supports a richer multiple.
Pipeline coverage: 3 to 4x of quota at normal win rates.
Win rate: 15 to 25 percent enterprise, 20 to 30 percent mid-market.
AI-sourced pipeline conversion discount: 0.6 to 0.8x versus inbound.

The attainment distribution is the health check most teams skip. A healthy plan has 60 to 70 percent of reps hitting quota. That band is the signal that quota is challenging but achievable. If fewer than 40 percent hit, the quota is too high — reps disengage, attrition climbs, and the forecast becomes fiction.

If more than 80 percent hit, the quota is too low, which means either sandbagging or money left on the table because targets were under-set. Xactly and CaptivateIQ attainment dashboards make this curve visible per segment, and it should be reviewed every quarter, not just at annual planning.

5. Distributing quota across ramped and new reps

A single uniform quota across a team with reps at different tenures guarantees failure for the new hires and complacency for the veterans. Quota distribution must respect the ramp curve.

The standard 2027 ramp schedule: 0 percent of full quota in month one, then 25, 50, 75, and 100 percent across months two through five. A rep hired in month one is learning the product and building pipeline, not closing; charging them full quota immediately is a setup for early attrition.

Most B2B SaaS sales cycles mean a new rep's first real closes land in months four to six anyway, so the ramp aligns quota to reality.

Two more adjustments belong in distribution:

Attrition buffer. If you distribute 100 percent of the company target across current headcount, any departure leaves the target uncovered. Plan to over-hire capacity slightly or distribute quota to roughly 105 to 110 percent of target so that expected attrition still leaves the company on plan.

Over-distributing quota to exactly 100 percent of target with no buffer is a common and avoidable miss.

Seasonality and territory. A rep in a seasonally strong territory or one inheriting an installed base should not carry the same number as a rep opening a greenfield region. The capacity model already captures some of this; distribution is where you finalize it.

flowchart TD A[Total Company Quota Need] --> B{Rep Tenure?} B -->|Month 1| C[0% Ramp Quota] B -->|Months 2-5| D[25 / 50 / 75 / 100% Ramp] B -->|Fully Ramped| E[100% Capacity Quota] C --> F[Sum Ramped Capacity] D --> F E --> F F --> G{Covers Target<br/>plus Attrition Buffer?} G -->|No| H[Hire / Reset Target / Lift Productivity] G -->|Yes| I{Attainment 60-70%?} I -->|Under 40% hit| J[Quota Too High - Lower] I -->|Over 80% hit| K[Quota Too Low - Raise] I -->|60-70% hit| L[Publish Quota Plan]

6. Stress-testing the attainment distribution

Before publishing, back-test the proposed quota against last year's actual performance and the source-weighted pipeline forecast. Take each rep's modeled capacity, apply the new quota, and ask: given their historical win rate and the weighted pipeline they realistically generate, what percentage would have hit?

If the back-test shows only 35 percent clearing the bar, the quota is too aggressive regardless of how good the top-down target looks. Lower the quota or fund more pipeline — do not publish a plan that fails the attainment test. Conversely, if 85 percent would have cleared it easily, raise the number; the team is being under-asked.

Run the stress test specifically against the AI-sourced segment. If a large share of forecasted pipeline is AI-sourced and you used too generous a conversion multiplier, the back-test will overstate attainment. Pressure-test the multiplier itself by comparing AI-sourced cohort conversion to inbound cohort conversion in Gong or Clari over the trailing four quarters, and adjust before the quota locks.

7. Common quota-setting mistakes in the AI era

The recurring failures of 2027 quota planning cluster around AI pipeline and ramp:

Setting quota on raw AI pipeline volume. The headline error — treating a flood of AI-generated meetings as equal to inbound and inflating quota to match. The volume is real; the conversion is not.
Uniform quota across ramped and new reps. Charging a month-two hire the same as a tenured rep, which burns out new hires and inflates early attrition.
No attrition buffer. Distributing exactly 100 percent of target across headcount so any departure puts the company behind plan instantly.
Year-over-year quota inflation without capacity justification. Raising every rep's number 20 percent because last year worked, with no change in productivity, ASP, or coverage to support it. Quota should rise when capacity rises, not by default.
Ignoring source segmentation entirely. Running one undifferentiated pipeline number when inbound, outbound-human, and AI-sourced deals convert at materially different rates.

Avoiding these is mostly discipline: build bottom-up, weight by source, buffer for attrition, and let the attainment distribution — not optimism — set the final number.

Frequently Asked Questions

Should quota go up just because AI generates more pipeline?

Not automatically. More raw pipeline does not mean more bookings if the AI-sourced share converts worse. Raise quota only when the source-weighted pipeline and observed conversion data justify it. Resist proportional increases tied to raw volume alone.

What conversion discount should I apply to AI-sourced pipeline?

Start with a 0.6 to 0.8x multiplier versus inbound and refine it using your own data. Compare AI-sourced cohort conversion to inbound conversion in Gong or Clari over the trailing four quarters and set the multiplier to the observed delta rather than a guess.

What percentage of reps should hit quota in a healthy plan?

60 to 70 percent. Below 40 percent means the quota is too high and attrition risk rises; above 80 percent means it is too low, signaling sandbagging or under-set targets. Review the distribution quarterly, not just at annual planning.

What is a typical AE quota multiple of OTE in 2027?

Mid-market SaaS AEs run 5 to 6x OTE, enterprise AEs 4 to 5x, and SMB AEs 6 to 8x. A $250K OTE mid-market rep carries roughly $1.25M to $1.5M in annual quota.

Should new reps carry full quota immediately?

No. Use a ramp schedule — typically 0 percent in month one, then 25, 50, 75, and 100 percent across months two through five. Full quota from day one ignores ramp reality and drives early attrition.

How much pipeline coverage do reps need?

Three to four times quota at normal win rates, measured against source-weighted pipeline rather than raw volume. A rep carrying $1.5M needs roughly $4.5M to $6M in effective, source-weighted pipeline to hit the number reliably.

Sources

Salesforce State of Sales — quota and capacity planning benchmarks, 2027
HubSpot Sales Benchmarks — AE quota and attainment data, 2026-2027
Clari — pipeline coverage and forecasting source-segmentation guidance
Gong Labs — AI-outbound vs. Inbound conversion analysis, 2027
Xactly Insights — quota attainment distribution benchmarks
QuotaPath and CaptivateIQ — commission and quota distribution practices
Bridge Group SaaS AE Metrics Report — ramp schedules and quota multiples
ICONIQ Growth and Bessemer State of Cloud — coverage ratios and win-rate benchmarks
Pavilion, SaaStr, RevOps Co-op, Winning by Design — operator quota-setting practices
Mediafly and BoostUp — pipeline source-tagging and weighted-coverage tooling

Download:

### Direct Answer

Build quotas bottom-up from rep capacity (ramped reps multiplied by productivity, ASP, and win rate), then weight pipeline by source — discount AI-sourced pipeline 0.6 to 0.8x because it converts worse than inbound or warm referrals. Target 60 to 70 percent of reps hitting quota; if AI inflates raw pipeline volume, resist raising the number until the conversion data justifies it. In 2027 a mid-market SaaS AE quota runs 5 to 6x on-target earnings, so a $250K OTE rep carries roughly $1.25M to $1.5M in annual quota. The mistake to avoid is treating an AI-generated meeting as equal to a referral-generated one. Tools like Clari, Gong, Xactly, QuotaPath, and CaptivateIQ now segment pipeline by origin and let RevOps apply a conversion multiplier before the quota math ever begins. Set the company revenue target first, build a capacity model second, apply a coverage ratio third, weight pipeline by source fourth, distribute with ramp and attrition buffers fifth, and stress-test the attainment curve last. A quota plan that ignores source quality looks aggressive on paper and collapses by Q2 when AI-sourced deals stall in the funnel.

## 1. The three quota-setting methods

Every quota model descends from one of three approaches, and most strong 2027 plans blend them.

**Top-down** starts with the board-approved revenue number and divides it across the sales team: revenue target divided by number of reps, adjusted for ramp, attrition, and seasonality. It is fast and aligns to investor expectations, but it ignores whether reps can physically carry the load. A $30M target split across 20 AEs implies $1.5M each — fine if capacity supports it, reckless if it does not.

**Bottom-up** (capacity-based) starts from what each rep can realistically produce given territory, segment, average selling price, and historical win rate, then sums upward to see whether the total clears the company target. Bottom-up is the honest method. It surfaces the gap between ambition and capacity before the year starts rather than in the Q3 board deck.

**Hybrid** is what disciplined RevOps teams actually run: build bottom-up to establish a credible capacity ceiling, compare it to the top-down target, and negotiate the delta through hiring, productivity programs, or a target reset. Salesforce, HubSpot, and Pavilion member operators all describe the same loop — the two numbers rarely match on the first pass, and the reconciliation is the real work.

### 1.1 When each method fits

Early-stage companies with thin historical data lean top-down because they have no reliable capacity baseline yet. Companies with two-plus years of clean pipeline history in Clari or Gong should anchor on bottom-up, because the win-rate and ASP inputs are trustworthy. Anyone scaling a new segment — adding enterprise on top of an SMB motion, for example — must build a separate capacity model per segment rather than averaging them, because the win rates and sales cycles differ too much to blend.

## 2. Building a capacity-based quota model

The capacity model is the spine of any defensible quota. The formula in plain terms: ramped AE capacity multiplied by productivity multiplied by ASP multiplied by win rate, then layered with a coverage ratio to derive the pipeline a rep needs to generate that bookings number.

Start with **ramped AE capacity** — the count of reps available, adjusted for where each sits on the ramp curve. A rep in month two is not a full producer. Multiply each rep's nominal capacity by their ramp factor (more on this in section five).

Layer in **productivity**: how many deals a fully-ramped rep closes per quarter at the segment's typical ASP and win rate. If a mid-market rep works 40 qualified opportunities a quarter, wins 25 percent, and the ASP is $40K, that is 10 wins worth $400K per quarter, or $1.6M annualized before ramp and attrition haircuts.

Then apply the **coverage ratio**. Pipeline divided by quota typically lands at 3 to 4x in 2027 — meaning a rep carrying $1.5M in quota needs roughly $4.5M to $6M in generated pipeline to hit it at normal win rates. Coverage is where the AI-pipeline question becomes unavoidable, because not all of that $6M converts at the same rate.

```mermaid
flowchart TD
    A[Company Revenue Target] --> B[Count Ramped AE Capacity]
    B --> C[Multiply by Productivity per Rep]
    C --> D[Apply ASP and Win Rate]
    D --> E[Derive Bookings Capacity]
    E --> F[Apply Coverage Ratio 3-4x]
    F --> G[Required Pipeline by Rep]
    G --> H{Pipeline Sources}
    H --> I[Inbound 1.0x]
    H --> J[Outbound-Human 0.8x]
    H --> K[AI-Sourced 0.6-0.8x]
    I --> L[Source-Weighted Pipeline]
    J --> L
    K --> L
    L --> M[Final Quota per Rep]
```

The model output is a per-rep bookings number that rolls up to a team total. If that total falls short of the top-down target, the gap is a hiring problem, a productivity problem, or a target problem — not something to paper over by raising individual quotas past what capacity supports.

## 3. Why AI-sourced pipeline needs a conversion discount

This is the 2027 wrinkle. When AI agents and automated outbound generate a large share of meetings, raw pipeline volume balloons, and the naive reaction is to raise quota proportionally. That is the central error of AI-era quota setting.

The data does not support equal treatment. Across 2027 benchmarks compiled by groups like Bridge Group, ICONIQ Growth, and the Bessemer State of Cloud report, **AI-outbound meetings convert 30 to 50 percent worse than warm referrals** and meaningfully worse than inbound demo requests. The lead is colder, the intent is weaker, and the qualification is thinner. A meeting an AI agent booked from a cold sequence is not the same asset as a meeting a customer requested.

The fix is a **source-weighted pipeline**. Segment generated pipeline into inbound, outbound-human, and AI-sourced buckets, then apply a conversion multiplier before computing coverage: inbound at roughly 1.0x, outbound-human around 0.8x, and **AI-sourced pipeline discounted to a 0.6 to 0.8x multiplier** depending on your own observed conversion delta. Mediafly, BoostUp, and Gong all support source-tagging that makes this measurable rather than a guess.

Practically: if a rep generates $6M in raw pipeline but $3M of it is AI-sourced at a 0.7x weight, the effective coverage is $3M inbound/human plus $2.1M weighted AI, or $5.1M against a $1.5M quota — a 3.4x effective ratio, not the 4x the raw number implied. **Quota should be set against the weighted pipeline, never the raw volume.** Otherwise the plan assumes conversions that the AI-sourced deals will not deliver, and attainment cracks mid-year.

## 4. 2027 quota and attainment benchmarks

Concrete numbers anchor the model. The 2027 ranges that RevOps Co-op operators, Winning by Design, and SaaStr data converge on:

- **Mid-market SaaS AE quota: 5 to 6x OTE.** A $250K OTE rep carries $1.25M to $1.5M.
- **Enterprise AE quota: 4 to 5x OTE.** Longer cycles and higher ASPs lower the multiple.
- **SMB AE quota: 6 to 8x OTE.** Higher velocity supports a richer multiple.
- **Pipeline coverage: 3 to 4x** of quota at normal win rates.
- **Win rate: 15 to 25 percent enterprise, 20 to 30 percent mid-market.**
- **AI-sourced pipeline conversion discount: 0.6 to 0.8x** versus inbound.

The attainment distribution is the health check most teams skip. **A healthy plan has 60 to 70 percent of reps hitting quota.** That band is the signal that quota is challenging but achievable. If fewer than 40 percent hit, the quota is too high — reps disengage, attrition climbs, and the forecast becomes fiction. If more than 80 percent hit, the quota is too low, which means either sandbagging or money left on the table because targets were under-set. Xactly and CaptivateIQ attainment dashboards make this curve visible per segment, and it should be reviewed every quarter, not just at annual planning.

## 5. Distributing quota across ramped and new reps

A single uniform quota across a team with reps at different tenures guarantees failure for the new hires and complacency for the veterans. Quota distribution must respect the ramp curve.

The standard 2027 ramp schedule: **0 percent of full quota in month one, then 25, 50, 75, and 100 percent across months two through five.** A rep hired in month one is learning the product and building pipeline, not closing; charging them full quota immediately is a setup for early attrition. Most B2B SaaS sales cycles mean a new rep's first real closes land in months four to six anyway, so the ramp aligns quota to reality.

Two more adjustments belong in distribution:

**Attrition buffer.** If you distribute 100 percent of the company target across current headcount, any departure leaves the target uncovered. Plan to over-hire capacity slightly or distribute quota to roughly 105 to 110 percent of target so that expected attrition still leaves the company on plan. Over-distributing quota to exactly 100 percent of target with no buffer is a common and avoidable miss.

**Seasonality and territory.** A rep in a seasonally strong territory or one inheriting an installed base should not carry the same number as a rep opening a greenfield region. The capacity model already captures some of this; distribution is where you finalize it.

```mermaid
flowchart TD
    A[Total Company Quota Need] --> B{Rep Tenure?}
    B -->|Month 1| C[0% Ramp Quota]
    B -->|Months 2-5| D[25 / 50 / 75 / 100% Ramp]
    B -->|Fully Ramped| E[100% Capacity Quota]
    C --> F[Sum Ramped Capacity]
    D --> F
    E --> F
    F --> G{Covers Target<br/>plus Attrition Buffer?}
    G -->|No| H[Hire / Reset Target / Lift Productivity]
    G -->|Yes| I{Attainment 60-70%?}
    I -->|Under 40% hit| J[Quota Too High - Lower]
    I -->|Over 80% hit| K[Quota Too Low - Raise]
    I -->|60-70% hit| L[Publish Quota Plan]
```

## 6. Stress-testing the attainment distribution

Before publishing, back-test the proposed quota against last year's actual performance and the source-weighted pipeline forecast. Take each rep's modeled capacity, apply the new quota, and ask: given their historical win rate and the weighted pipeline they realistically generate, what percentage would have hit?

If the back-test shows only 35 percent clearing the bar, the quota is too aggressive regardless of how good the top-down target looks. **Lower the quota or fund more pipeline — do not publish a plan that fails the attainment test.** Conversely, if 85 percent would have cleared it easily, raise the number; the team is being under-asked.

Run the stress test specifically against the AI-sourced segment. If a large share of forecasted pipeline is AI-sourced and you used too generous a conversion multiplier, the back-test will overstate attainment. Pressure-test the multiplier itself by comparing AI-sourced cohort conversion to inbound cohort conversion in Gong or Clari over the trailing four quarters, and adjust before the quota locks.

## 7. Common quota-setting mistakes in the AI era

The recurring failures of 2027 quota planning cluster around AI pipeline and ramp:

- **Setting quota on raw AI pipeline volume.** The headline error — treating a flood of AI-generated meetings as equal to inbound and inflating quota to match. The volume is real; the conversion is not.
- **Uniform quota across ramped and new reps.** Charging a month-two hire the same as a tenured rep, which burns out new hires and inflates early attrition.
- **No attrition buffer.** Distributing exactly 100 percent of target across headcount so any departure puts the company behind plan instantly.
- **Year-over-year quota inflation without capacity justification.** Raising every rep's number 20 percent because last year worked, with no change in productivity, ASP, or coverage to support it. Quota should rise when capacity rises, not by default.
- **Ignoring source segmentation entirely.** Running one undifferentiated pipeline number when inbound, outbound-human, and AI-sourced deals convert at materially different rates.

Avoiding these is mostly discipline: build bottom-up, weight by source, buffer for attrition, and let the attainment distribution — not optimism — set the final number.

## Frequently Asked Questions

**Should quota go up just because AI generates more pipeline?**

Not automatically. More raw pipeline does not mean more bookings if the AI-sourced share converts worse. Raise quota only when the source-weighted pipeline and observed conversion data justify it. Resist proportional increases tied to raw volume alone.

**What conversion discount should I apply to AI-sourced pipeline?**

Start with a 0.6 to 0.8x multiplier versus inbound and refine it using your own data. Compare AI-sourced cohort conversion to inbound conversion in Gong or Clari over the trailing four quarters and set the multiplier to the observed delta rather than a guess.

**What percentage of reps should hit quota in a healthy plan?**

60 to 70 percent. Below 40 percent means the quota is too high and attrition risk rises; above 80 percent means it is too low, signaling sandbagging or under-set targets. Review the distribution quarterly, not just at annual planning.

**What is a typical AE quota multiple of OTE in 2027?**

Mid-market SaaS AEs run 5 to 6x OTE, enterprise AEs 4 to 5x, and SMB AEs 6 to 8x. A $250K OTE mid-market rep carries roughly $1.25M to $1.5M in annual quota.

**Should new reps carry full quota immediately?**

No. Use a ramp schedule — typically 0 percent in month one, then 25, 50, 75, and 100 percent across months two through five. Full quota from day one ignores ramp reality and drives early attrition.

**How much pipeline coverage do reps need?**

Three to four times quota at normal win rates, measured against source-weighted pipeline rather than raw volume. A rep carrying $1.5M needs roughly $4.5M to $6M in effective, source-weighted pipeline to hit the number reliably.

## Sources

- Salesforce State of Sales — quota and capacity planning benchmarks, 2027
- HubSpot Sales Benchmarks — AE quota and attainment data, 2026-2027
- Clari — pipeline coverage and forecasting source-segmentation guidance
- Gong Labs — AI-outbound vs. Inbound conversion analysis, 2027
- Xactly Insights — quota attainment distribution benchmarks
- QuotaPath and CaptivateIQ — commission and quota distribution practices
- Bridge Group SaaS AE Metrics Report — ramp schedules and quota multiples
- ICONIQ Growth and Bessemer State of Cloud — coverage ratios and win-rate benchmarks
- Pavilion, SaaStr, RevOps Co-op, Winning by Design — operator quota-setting practices
- Mediafly and BoostUp — pipeline source-tagging and weighted-coverage tooling

Was this helpful?

⌬ Apply this in PULSE

Pillar · Deal Desk ArchitectureFrom founder override to scaled governance Gross Profit CalculatorModel margin per deal, per rep, per territory Recruiting CalculatorHow many reps you need before you hire

Deep dive · related in the library