Short answer: headcount planning has exactly two drivers – growth (new seats the plan requires) and backfill (seats attrition will empty) – and one timing rule that trips up every fast-growing team: open the requisition one time-to-fill ahead of the need, not when the need arrives. The model below is a quarterly spreadsheet you can copy, sized from demand drivers rather than gut feel, with the attrition and fill-time numbers wired in.
The two-driver formula
For any team, next period’s hiring need is:
New hires = Growth hires + Backfill hires
Growth hires = current headcount × growth rate
Backfill hires = current headcount × attrition rate
That’s the entire engine (it’s exactly what the Headcount Planning Calculator computes per department). The sophistication isn’t in the formula – it’s in sizing the two rates from evidence instead of optimism.
Step 1 – Size growth from demand drivers, not vibes
“We’ll grow the team 20%” is a wish. Tie each team’s size to the thing that actually creates its work:
| Team | Demand driver | Sizing ratio |
|---|---|---|
| Customer support | Tickets / active customers | Agents = monthly tickets ÷ tickets-per-agent capacity |
| Sales | Pipeline / quota | Reps = revenue target ÷ quota per rep |
| Delivery / services | Billable demand | People = forecast billable hours ÷ hours per head (revenue-per-employee sanity-checks this) |
| Engineering | Roadmap scope | Hardest to ratio – size from committed roadmap, not headcount envy |
| Ops / G&A | Total company size | Ratio to total headcount (e.g. 1 ops per 25 staff) |
Now “20% growth” becomes “support handles 4,000 tickets/month next quarter at 800 tickets/agent capacity → 5 agents needed → we have 4 → +1 growth hire.” That’s a number you can defend, and it self-corrects: if the ticket forecast is wrong, the headcount ask is visibly wrong too.
Step 2 – Size backfill from your real attrition rate
Backfill is the seat you’ll refill because someone left – invisible in optimistic plans and the reason teams that “only planned to grow by 6” end up hiring 11. Use your actual turnover rate, not a benchmark, and segment it: a support team at 25% attrition and an ops team at 8% need very different backfill provisions even at the same headcount.
Two refinements:
- Use regrettable + non-regrettable both for backfill (the seat empties either way), but plan the replacement quality differently.
- Front-load known departures – a notice already given, a maternity leave, a fixed-term end – into the specific quarter, rather than smearing the annual rate evenly.
Step 3 – The worked model: 40-person company, one year
Current headcount 40, split across departments. Blended growth target ~15%, blended attrition ~13%. Partial hires are rounded up – you can’t half-staff a need, and under-planning a seat is more expensive than over-planning one.
| Department | Current | Growth rate | Growth hires | Attrition | Backfill hires | Total hires | End headcount |
|---|---|---|---|---|---|---|---|
| Support | 12 | 20% | 2.4 → 3 | 25% | 3.0 → 3 | 6 | 15 |
| Sales | 8 | 25% | 2.0 → 2 | 20% | 1.6 → 2 | 4 | 10 |
| Delivery | 10 | 10% | 1.0 → 1 | 12% | 1.2 → 2 | 3 | 11 |
| Engineering | 6 | 15% | 0.9 → 1 | 8% | 0.5 → 1 | 2 | 7 |
| Ops / G&A | 4 | 0% | 0 | 10% | 0.4 → 1 | 1 | 4 |
| Total | 40 | 7 | 9 | 16 | 47 |
The headline every founder should sit with: to grow net +7 (40→47), you must hire 16 – because backfill more than doubles the recruiting workload. Plan, budget, and staff recruiting for the gross number, not the net. (At a cost per hire of ~$4,500, that’s a ~$72,000 recruiting spend line the “we’re adding 7 people” framing completely hides.)
Step 4 – The timing rule (where plans meet reality)
A headcount plan that says what to hire but not when to start is half a plan. The rule:
Open the requisition (time-to-fill) before the seat is needed.
If your time to fill for an engineer is 55 days and you need them productive for a Q3 project launch on 1 July, the req opens in early May, not July. Build a quarterly roadmap that back-dates every hire by its role’s fill time:
| Need-productive date | Role | Fill time | Open req by | Ramp buffer |
|---|---|---|---|---|
| 1 Jul | Senior engineer | 55 days | ~1 May | +90 days to full productivity |
| 1 Aug | Support agent ×2 | 25 days | ~5 Jul | +30 days ramp |
Add the ramp period on top for anything where “productive” matters (see the 90-day onboarding curve) – a role needed productive in July that also needs 90 days to ramp really has an April req date. This is why fast-growing teams feel permanently behind on hiring: they plan headcount by quarter but forget that each hire’s clock started a quarter earlier.
Step 5 – Stress-test before you commit
Three checks before the plan goes to the board:
- Recruiter capacity: 16 hires ÷ your recruiter’s throughput – can they actually run that many searches? If not, the plan needs a recruiter before it needs anyone else (Recruiter Capacity Calculator).
- Revenue per head: does the end-state 47 still clear your revenue-per-employee floor, or are you hiring ahead of revenue? A dropping ratio across the plan is the early-warning that you’re over-hiring.
- The downside case: re-run with growth halved and attrition +5 points. If that scenario breaks cash, the plan is too aggressive – build in requisition “trigger dates” that only fire if the demand driver actually materialises.
FAQ
Quarterly or annual planning? Plan the year, revise quarterly. The demand drivers (pipeline, tickets, roadmap) move every quarter, and a fixed annual plan is stale by Q2 in a growing company.
How do I handle a hiring freeze mid-plan? Freeze growth hires; think hard before freezing backfill, because an unfilled backfill seat quietly overloads the remaining team and accelerates the next departure – the freeze that saves one salary can trigger two exits.
What attrition rate should I assume for a brand-new team with no history? Start from your industry benchmark (the tool page lists them), then correct toward your actual number as soon as you have two quarters of data. New teams often run higher early attrition (fit mismatches surface fast).
Does this work below 20 people? Yes, and the timing rule matters more – at 12 people one unplanned departure is 8% of the company, and a two-month fill gap is genuinely painful. Small teams should hold a slightly larger backfill buffer, not a smaller one.
Calculators referenced: Headcount Planning · Employee Turnover · Recruiter Capacity · Time to Fill · Revenue Per Employee · Cost Per Hire. Size the drivers from your own data; benchmarks are only the starting estimate before your numbers exist.
