Rep headcount and ramp planning

Plan outbound headcount from productive output by period. Start with the revenue or qualified pipeline the team must create, translate that need into usable capacity, and schedule hiring early enough for ramp and backfills. Headcount alone can mislead: a new hire, an overloaded territory, or meetings nobody can hold can leave the team with activity that does not produce usable output.¹ Capacity also has to account for ramp, attrition, time off, territory coverage, and other constraints.²

Start with the output gap

Use the gap between required and current output to give every role a clear job in the output model.

For outbound, capacity planning asks how many productive SDRs are needed to create enough qualified conversations for the AEs you have or plan to hire.³ Keep headcount, productivity and capacity separate. Headcount is the number of people employed or budgeted for a role.⁴ Productivity is the output a fully ramped rep actually produces according to historical data.⁵

Answer three questions: What qualified pipeline or revenue must the team create in each period? Which part of that output is missing? If you cannot say what output a proposed hire adds and when it adds it, the request is still a seat count.

Build the ramp model

A hire contributes as part of a cohort. Put its start date in the period when its output arrives, and show the gap between employment date and productive contribution.

Model ramp as percentages of steady-state productivity across the first, second, third and fourth quarters.⁶ Set the ramp assumption to the expected sales percentage of steady-state productivity as tenure increases.⁷ Use prior performance data when estimating ramp time.⁸ Align the ramp cycle with the sales cycle.⁹

An SDR hired in January is not fully productive until April, while an AE hired in January does not close first deals until June or July.¹⁰ Test whether the output arrives in the period where the plan needs it.

For each cohort, ask when a new hire can first count toward the target, what the rep produces before that point, and which assumption changes if the sales cycle gets longer.

Place hiring dates backward

Show when capacity is required before opening seats. Starting with open seats hides the cost of ramp.

Plan hires backward from revenue impact goals while considering ramp times.¹¹ Use a first or hired quarter row to represent the annual hiring plan.¹² Measure hiring plans in new hires per quarter and keep them realistic against the ability to recruit and close reps.¹³

Managers should have planned headcount hired before the target increases.¹⁴ Put the requisition, recruiting path and expected contribution in the plan before the period that needs the output.

Check when the output must be live and how early the cohort must start. Also check whether the recruiting team can close the hiring plan at the pace the model assumes.

Add attrition and operating limits

The plan has to account for people leaving and for output changing while the team is being built. Treat departures as schedule inputs instead of surprises.

Use predicted departures to start recruiting backfills and build them into the annual plan.¹⁵ Capacity models should include ramp curves, hiring start dates and expected attrition.¹⁶ Call volume fluctuates substantially depending on how many people are being ramped.¹⁷

Review the model whenever a departure becomes likely, a start date slips or a cohort ramps differently from the assumption. Then change the period output, the backfill date or the hiring sequence. Do not leave the original capacity figure in place after one of its inputs has changed.

Identify which departures could remove productive output before the next cohort contributes, how much recruiting time each backfill needs, and which period becomes exposed if a start date moves.

Sequence the roles

Use readiness gates to decide when to add capacity and where. Add the role that removes the bottleneck shown by the model.

Once a repeatable sales process exists, hire an SDR as quickly as you can.¹⁸ Before approving the role, determine whether the shortfall is more AEs or more BDRs and plan accordingly.¹⁹ When pipeline creation is the constraint, hire SDRs first, verify pipeline surplus, then scale AEs.²⁰

A proposed trigger for additional headcount is getting 80 percent of the team to 80 percent attainment.²¹ Use that as a checkpoint for whether the current team is producing close to the assumed level before adding another layer of capacity. If the model shows a pipeline shortage, the role sequence may differ from a plan built around closing capacity.

Before adding the next role, identify whether the constraint is qualified pipeline, closing capacity or ramp support. Then define what must be true before that role can use the output created by the previous one.

What not to do

A model goes wrong when targets or start dates stand in for productive output. Keep these failure modes visible during approval.

• Do not use quota as proof that capacity exists; quota is a management and compensation number.²²
• Do not treat adding five SDRs as adding five fully productive SDR equivalents on their start dates.²³
• Do not hire SDRs for capacity before validating total addressable market.²⁴
• Do not hire before the company is ready for the added capacity.²⁵
• Do not treat hiring four AEs and four SDRs simultaneously as a typical starting pattern.²⁶

Use the model when a requisition is proposed and before its start date is approved. Make the decision only when the expected period output and the constraint it removes are visible. If either is missing, change the assumption or hold the request.