Sales Capacity Planning: How Many Reps Do You Need?

Leah Clapper

Summarize this article with your favorite LLM
Table of contents

Summarize article with your LLM

Sales capacity planning converts a revenue target into the number of quota-carrying reps needed to hit it.

This guide gives the headcount formula, a worked example and the adjustments that make the plan realistic. All numbers are illustrative. Replace them with your own data.

What is sales capacity planning?

Sales capacity planning is the process of estimating how much revenue a sales team can produce and how many reps it needs to meet a target. Capacity is the expected output of the team after accounting for quota, attainment, ramp time and attrition.

It differs from setting quotas. Quota setting divides a target among reps. Capacity planning asks whether the team has enough reps to reach the target at realistic attainment.

The quota attainment guide covers quota setting and attainment. The quota math guide covers activity targets.

Which inputs does the capacity model need?

The model needs the revenue target, quota per ramped rep, expected attainment, ramp time and attrition.

Each input has an owner and a source.

Input

Definition

Source

Revenue target

New bookings goal for the period

Finance plan

Quota per ramped rep

Annual quota for a fully ramped rep

Sales leadership

Expected attainment

Average share of quota reps actually achieve

Historical CRM data

Ramp time

Months until a new rep carries full quota

Past hires

Ramp productivity

Share of quota a new rep produces during ramp

Past hires

Attrition

Share of reps expected to leave

HR data

Hiring lead time

Months from approval to start date

Recruiting

Use the last four to eight quarters of your own data. A planning figure from another company reflects its market, deal size and process.

What is the headcount formula?

Required ramped reps equal the revenue target divided by the quota per ramped rep multiplied by expected attainment.

Required ramped reps = Revenue target / (Quota per rep x Expected attainment)

Worked example (illustrative):

Item

Value

Revenue target

$12,000,000

Quota per ramped rep

$1,000,000

Expected attainment

75%

Productive output per rep

$750,000

Required ramped reps

12,000,000 / 750,000 = 16

If the team has 12 ramped reps, it is 4 short before ramp and attrition. The difference between quota and attainment is the main reason plans that assume 100% attainment fall short.

How do ramp and attrition change the number?

Ramp lowers the output of new hires, and attrition removes reps mid-year. Adjust the plan for both.

Continue the example. Suppose a new rep produces 25% of quota in each of the first two quarters and 100% afterward, and one of the 16 reps is expected to leave at mid-year.

Adjustment (illustrative)

Effect

New rep hired at start of year

Produces about 62.5% of a ramped rep's annual quota in year one

One departure at mid-year

Loses about half a year of that rep's output

Hiring lead time of three months

New rep starts after the plan period begins

The point is the method, not the numbers. Each hire starts producing later than its approval date, and each departure removes output before a backfill is productive. Model both by quarter, not by year.

See the onboarding guide for ramp measures.

How do you plan by quarter?

Build a quarterly table with starting reps, hires, departures and productive capacity. A table shows when capacity arrives, which a single annual figure hides.

Quarter

Starting reps

Hires

Departures

Ramped-equivalent reps

Q1

12

2

0

Starting reps plus ramp share of hires

Q2

14

2

1

Recalculate with ramp share

Q3

15

0

0

Hires from Q1 now ramped

Q4

15

0

0

Hires from Q2 partly ramped

Fill the last column with your own ramp curve. Compare the sum of quarterly capacity with the revenue target for each quarter.

Revenue arrives with sales cycle lag, so check the sales cycle guide before assuming a rep hired in Q2 closes deals in Q2.

How do territories and segments affect capacity?

Capacity must be planned per segment, because quota, attainment and deal size differ across them. A team total can look sufficient while one region is understaffed.

Plan each territory or segment separately, then sum. The territory management guide covers how to divide accounts. Check that each territory has enough qualified accounts to support its reps, using the account prioritization guide.

What happens when capacity is short?

When capacity is short, the options are to hire, raise productivity, lower the target or accept the gap. Each has a cost and a delay.

  1. Hire. Slowest, because of lead time and ramp.

  2. Raise productivity. Coaching, better account selection and automation that removes non-selling time.

  3. Adjust the target. A planning decision for finance and leadership.

  4. Accept a risk-weighted gap. State it openly in the plan.

Do not assume automation fixes the gap. Measure rep time first. Rox agents can take on research and follow-up tasks, and results vary by team and process, so test on a pilot group before changing headcount plans.

See the sales and operations planning guide.

Which mistakes distort capacity plans?

  • Assuming 100% attainment. Use observed attainment.

  • Ignoring ramp. New hires do not produce at full quota at once.

  • Ignoring hiring lead time. Approval is not a start date.

  • Planning only at team level. Segments differ.

  • Using a stale ramp curve. Refresh it every year.

  • Forgetting backfills. Departures cost output before the replacement is productive.

Conclusion

Capacity planning turns a target into a hiring plan by dividing the target by realistic output per rep. The two inputs that most often cause misses are expected attainment and ramp time. Plans that use full quota for every rep overstate capacity.

Model by quarter and by segment. A quarterly table shows when each hire becomes productive and when each departure removes output. It also shows when revenue, which lags activity by the sales cycle, can arrive.

Begin with the formula and your last four quarters of attainment data. Add ramp and attrition next, then segment the plan. Review it each quarter and update the ramp curve with real hires.

Results vary with data quality, deal mix and market conditions. Rox does not guarantee specific revenue outcomes.

Frequently asked questions

How do I calculate how many reps I need?

Divide the revenue target by quota per rep multiplied by expected attainment.

What attainment should I assume?

Use your own average from recent periods, not a benchmark from another company.

How long does ramp take?

It depends on deal size and cycle length. Measure it from your last several hires.

How often should I update the plan?

Quarterly, or when attainment, attrition or the target changes.

Should I include managers in capacity?

Only if they carry quota. Count them separately otherwise.

Summarize this article with your favorite LLM

Rox is committed to the privacy and security of its users. Customer data processed through the Rox platform is encrypted in transit and at rest using AES-256 encryption and is never used to train generalized machine learning models. Rox maintains SOC 2 Type II compliance and undergoes independent third-party security audits on an annual basis. All AI-generated outputs, including but not limited to prospect recommendations, message drafts, meeting summaries, and pipeline scoring, are provided for informational purposes and should be reviewed by authorized personnel before any action is taken. Performance metrics referenced on this website, including pipeline generation figures, response rates, and revenue impact, reflect results reported by individual customers under specific configurations and may not be representative of all deployments. Actual results will vary based on factors including but not limited to data quality, CRM configuration, outreach volume, market conditions, and target audience. Rox does not guarantee specific revenue outcomes. The Rox platform integrates with third-party services including Salesforce, HubSpot, Gmail, Microsoft Outlook, Slack, and others; availability and functionality of third-party integrations are subject to the respective providers' terms of service and may change without notice. Features described as "autopilot," "autonomous," or "automated" operate within user-defined parameters and require initial configuration and ongoing oversight. Rox, the Rox logo, and "Revenue on Autopilot" are trademarks of Rox Data Corp. All other trademarks are the property of their respective owners. Service availability is subject to the terms outlined in your enterprise agreement. For questions regarding data processing, compliance certifications, or platform capabilities, contact security@rox.com.

Rox is committed to the privacy and security of its users. Customer data processed through the Rox platform is encrypted in transit and at rest using AES-256 encryption and is never used to train generalized machine learning models. Rox maintains SOC 2 Type II compliance and undergoes independent third-party security audits on an annual basis. All AI-generated outputs, including but not limited to prospect recommendations, message drafts, meeting summaries, and pipeline scoring, are provided for informational purposes and should be reviewed by authorized personnel before any action is taken. Performance metrics referenced on this website, including pipeline generation figures, response rates, and revenue impact, reflect results reported by individual customers under specific configurations and may not be representative of all deployments. Actual results will vary based on factors including but not limited to data quality, CRM configuration, outreach volume, market conditions, and target audience. Rox does not guarantee specific revenue outcomes. The Rox platform integrates with third-party services including Salesforce, HubSpot, Gmail, Microsoft Outlook, Slack, and others; availability and functionality of third-party integrations are subject to the respective providers' terms of service and may change without notice. Features described as "autopilot," "autonomous," or "automated" operate within user-defined parameters and require initial configuration and ongoing oversight. Rox, the Rox logo, and "Revenue on Autopilot" are trademarks of Rox Data Corp. All other trademarks are the property of their respective owners. Service availability is subject to the terms outlined in your enterprise agreement. For questions regarding data processing, compliance certifications, or platform capabilities, contact security@rox.com.