Plan outbound headcount from productive capacity, then work backward from the revenue or qualified pipeline the business needs. A person on the org chart does not contribute the same output as a fully ramped rep, and a booked meeting is useless capacity if nobody can hold it.1 Hiring people on a start date does not create fully productive capacity on that date.2 The plan should show when output appears, what limits it, and which assumptions can change the hiring decision. Build it around the output each hire can create in the period.
Set the output target
Set the result the team must produce before deciding how many people to hire. Keep the target in the unit the business will use to judge capacity.
Start with the revenue or qualified pipeline the team must produce. In an outbound motion, translate that target into the number of productive SDRs needed to create enough qualified conversations for the AEs already in place or planned.3 Connect the operating constraints to the revenue target, then show what the team can produce and which assumption needs to change.4
Ask:
- What revenue or qualified pipeline must the team create in the planning period?
- How many qualified conversations can the downstream team absorb?
- What constraint currently keeps output below target?
- Which assumption would change the hiring decision?
Move on when the target is explicit and the model has a defined output measure.
Separate headcount from usable capacity
Keep headcount and capacity on separate lines. Headcount tells you what you plan to employ or budget. Capacity tells you what that group can produce after ramp, attrition, time off, territory coverage, and other constraints.
Capacity is the total productive output available during a defined period after adjusting for ramp, attrition, time off, territory coverage, and other constraints.5 Quota is the target assigned to a representative or team, and it does not prove that the matching capacity exists.6
Build a row for each hiring wave and show its expected productive output for each period. Treat the start date as an input and show the output date in the capacity view. Keep both visible so a request for more headcount can be tested against the work the team can absorb and the output the business needs.
Build the ramp curve
The ramp curve turns a hiring date into a realistic production date. Use it to decide when a hire must start and to see whether the plan depends on output that has not arrived yet.
Use prior performance data when estimating ramp time.7 Add ramp curves, hiring start dates, and expected attrition to the capacity model.8 With a five-month ramp, a company targeting July productivity must hire by January.9
Model the productivity curve for each ramping rep so the forecast does not treat a recent hire as fully productive.10 Ask what a new hire produces in each period, when that output becomes dependable, and what training or territory condition moves the curve. If a long ramp comes with high early attrition, treat that as a hiring or expectation-setting problem.11
Do not finalize the plan while ramp assumptions exist only as a blanket percentage. Replace them with a curve grounded in prior performance, then test the effect of a slower ramp on the target date.
Place hiring and backfills against the target
Once the output curve exists, place each hire against the date when the business needs the capacity. Show the gap before the hire contributes and the gap that remains if the start date slips.
Plan hires backward from the revenue impact goal while accounting for ramp time.12 Have the hire in place before the planned headcount target increases.13 When a departure is predictable, start the backfill recruiting path and include it in the annual plan.14
Ask:
- By what date must the hire produce useful output?
- How much capacity is missing before that date?
- Which departure needs a backfill path now?
- What happens to the target if the start date moves?
A useful hiring calendar shows the start date, expected productivity date, capacity gap, and action that closes it. The person approving headcount can then inspect more than the total number of hires.
Check market and territory supply
Headcount can exceed the work available to support it. Check the account pool before the model turns a revenue target into a hiring request.
Hiring SDRs without validating total addressable market means hiring for capacity the company does not have.15 Ask which accounts each hire can work, how many accounts a workable territory contains, and how much of that pool is reachable in the planning period. Separate accounts that exist on paper from accounts that can support the expected activity.
Move on when every proposed hire has a clear account pool and the territory can support the output assigned to that hire. If the pool cannot support the plan, change the target, coverage design, or hiring timing before adding capacity.
Review the plan as a set of assumptions
A headcount plan earns approval when someone can see what would make it succeed or fail. Put the assumptions where they can be changed without rebuilding the whole model.
For each hiring wave, record the target output, start date, ramp curve, expected attrition, territory supply, and resulting productive capacity. Run the plan again when one of those assumptions changes. If a small change in ramp or attrition removes the expected output, surface that gap before the hire is approved.
Use the review to decide which constraint deserves attention first. A hiring request can be sound while the model shows that timing, territory supply, or ramp is the actual limit.
What not to do
These errors turn a headcount plan into a count of people without a credible output path.