# Headcount Planning: How to Build a Hiring and Payroll Forecast

*Alex Tapio · 2026-08-08 · 13 min · FP&A*

Canonical: https://finamodel.com/blog/headcount-planning-model

Learn how to build a headcount planning model in Excel: department-level hiring plans, attrition, fully-loaded comp, and payroll forecasting, with a full worked example.

**A headcount plan turns a hiring intention ("we're adding 20 people this year") into a monthly, department-level forecast of who joins, who leaves, and what it all costs on a fully-loaded basis. This guide walks through the full build: the hires-minus-attrition mechanics, fully-loaded comp, a department-level worked example, how payroll forecasting extends the same plan into gross wages and employer tax, and the mistakes that make headcount plans wrong in ways nobody notices until the budget blows through.**

Headcount is usually the largest line item on a growth-stage company's P&L - often 60-70% of opex for a software business. Yet it's frequently the least rigorously modeled: a single growth rate applied to last year's payroll, or a hiring number picked to hit a board target with no bottom-up build underneath it. A proper headcount model fixes that by working department by department, month by month, from a starting headcount through planned hires and expected attrition to a fully-loaded cost that ties directly into the P&L.

```mermaid
flowchart TD
    A["Starting Headcount by Department"] --> B["+ Planned New Hires"]
    B --> C["- Attrition (Prior HC x Attrition %)"]
    C --> D["Ending Headcount"]
    D --> E["x Fully-Loaded Comp Rate (Base x Benefits Multiplier)"]
    E --> F["Monthly Department Payroll Cost"]
    F --> G["Roll Up to Annual Headcount Budget"]
    G --> H["Feed Into P&L / Opex Forecast"]
```

*From a department-level hiring plan to a fully-loaded payroll budget that feeds the P&L.*

---

## Structuring the Model

A headcount model built for actual use - not just a board slide - needs three linked layers:

1. **Hires sheet:** New hires, attrition, and ending headcount per department, per month.
2. **Compensation sheet:** Fully-loaded monthly comp expense per department, built off base salary and a benefits load multiplier.
3. **Summary / rollup:** A Y1 view per department - starting HC, total hires, total attrition, ending HC, and total comp - that a CFO can put in front of a board in one screen.

Some models add a fourth layer for revenue-generating functions: a **productivity sheet** that converts sales headcount into revenue capacity, since a newly hired rep isn't immediately as productive as a tenured one.

As with any FP&A model, every rate - attrition %, benefits load, hires per month - belongs on an assumptions block, not hardcoded into formulas. That's what lets you flex the plan ("what if we slow Engineering hiring by 2 heads a quarter?") in seconds instead of rebuilding rows.

<!-- template:hiring-model -->

---

## The Core Mechanic: Hires, Attrition, Ending Headcount

Every department row runs the same formula each month:

```
Ending HC = Prior Ending HC + New Hires - Attrition
Attrition = Prior Ending HC x Monthly Attrition %
```

Month 1 uses the starting headcount as the prior-period base. The subtlety that trips people up: **don't round headcount every month.** Attrition on 11.8 people is a real, if fractional, quantity - 0.2 or 0.3 of a person - and if you round to a whole number each month before carrying it forward, small rounding errors compound over 12 months and your year-end headcount will drift from what the formula actually implies. Carry the decimal through the year and round only when you report a whole-number headcount.

### Worked Example: Sales Headcount, Six Months

Assume the Sales department starts the year at 10 reps, the plan calls for 2 new hires every month, and the department carries a 2% monthly attrition rate (roughly 24% annualized, typical for a sales org). Each month's attrition is rounded to one decimal for readability, and that rounded ending headcount carries forward as next month's starting point:

| Month | Starting HC | New Hires | Attrition (2% of Starting) | Ending HC |
| :--- | :---: | :---: | :---: | :---: |
| 1 | 10.0 | 2 | 0.2 | 11.8 |
| 2 | 11.8 | 2 | 0.2 | 13.6 |
| 3 | 13.6 | 2 | 0.3 | 15.3 |
| 4 | 15.3 | 2 | 0.3 | 17.0 |
| 5 | 17.0 | 2 | 0.3 | 18.7 |
| 6 | 18.7 | 2 | 0.4 | 20.3 |

By Month 6, Sales has grown from 10 to just over 20 reps - 12 gross hires against roughly 1.7 heads of cumulative attrition. In Excel, this is three formulas dragged down: attrition references the prior row's ending HC, and ending HC sums starting HC, hires, and subtracts attrition.

```excel
// Attrition (Month N)
= EndingHC_PriorMonth * Assumptions!$B$Sales_Attrition

// Ending HC (Month N)
= EndingHC_PriorMonth + NewHires_ThisMonth - Attrition_ThisMonth
```

---

## Fully-Loaded Compensation

A hiring plan alone doesn't tell you what it costs. The bridge from headcount to dollars is the **fully-loaded cost per employee**:

```
Fully-Loaded Annual Cost = Base Salary x Benefits Load Multiplier
```

The benefits load multiplier bundles employer payroll tax, healthcare premiums, retirement match, and general overhead into a single number applied on top of base salary. US tech companies typically run **1.20x-1.35x**; European employers run **1.30x-1.50x** because of heavier mandatory social charges. A $145,000 Engineering base salary at a 1.28x load costs the company $185,600 a year - not $145,000. Miss that multiplier and your comp budget will consistently understate reality by 20-35%.

### Y1 Department Summary: A Worked Example

Here's a full-company Y1 rollup for a mid-stage startup across five departments, showing the hires-minus-attrition mechanic from the section above already carried through the full year, plus the fully-loaded comp math:

| Department | Start HC | Y1 Hires | Y1 Attrition | End HC | Avg Base Salary | Benefits Load | Fully-Loaded Cost/Head |
| :--- | :---: | :---: | :---: | :---: | :---: | :---: | :---: |
| Engineering | 20 | 8 | 3 | 25 | $145,000 | 1.28x | $185,600 |
| Sales | 10 | 6 | 2 | 14 | $110,000 | 1.25x | $137,500 |
| Marketing | 5 | 2 | 1 | 6 | $100,000 | 1.22x | $122,000 |
| G&A | 4 | 1 | 0 | 5 | $95,000 | 1.20x | $114,000 |
| Customer Success | 6 | 3 | 1 | 8 | $85,000 | 1.24x | $105,400 |
| **Total** | **45** | **20** | **7** | **58** | - | - | - |

Check the headcount roll-forward first: 45 starting + 20 hires - 7 attrition = 58 ending. That identity has to hold on every summary tab, or a formula is broken somewhere upstream.

Because headcount grows through the year rather than jumping to its ending level on day one, a reasonable approximation for the average headcount carrying cost during the year is the simple average of starting and ending HC per department:

| Department | Avg HC (Start+End)/2 | Fully-Loaded Cost/Head | Y1 Fully-Loaded Comp |
| :--- | :---: | :---: | :---: |
| Engineering | 22.5 | $185,600 | $4,176,000 |
| Sales | 12.0 | $137,500 | $1,650,000 |
| Marketing | 5.5 | $122,000 | $671,000 |
| G&A | 4.5 | $114,000 | $513,000 |
| Customer Success | 7.0 | $105,400 | $737,800 |
| **Total** | **51.5** | - | **$7,747,800** |

A company growing from 45 to 58 heads over the year lands at roughly **$7.75M** in fully-loaded Y1 comp expense - the single number that drops into the opex section of the P&L. Note this average-HC approach is a planning simplification; the actual template builds the cost month by month off ending HC, which is more precise but not necessary to sanity-check the order of magnitude.

<!-- template:payroll-forecast -->

---

## Payroll Forecasting: One Level Deeper

Headcount planning tells you how many people and roughly what they cost. **Payroll forecasting** breaks the fully-loaded number into the actual components a payroll system will charge, which matters for cash planning and for reconciling the model against ADP, Gusto, or Rippling output.

Take a single $100,000-base-salary employee and build the employer burden line by line:

| Component | Rate | Monthly Amount |
| :--- | :---: | :---: |
| Gross wages | - | $8,333.33 |
| FICA Social Security | 6.2% | $516.67 |
| FICA Medicare | 1.45% | $120.83 |
| FUTA (net, first $7,000/yr) | 0.6% | $3.50 |
| SUTA (illustrative, first $9,000/yr) | 3.0% | $22.50 |
| Healthcare benefit (fixed) | - | $650.00 |
| 401(k) match | 4.0% | $333.33 |
| **Total employer burden** | - | **$1,646.83** |
| **Fully-loaded monthly cost** | - | **$9,980.16** |

```
Effective Load Multiplier = ($8,333.33 + $1,646.83) / $8,333.33 = 1.20x
```

That 1.20x sits right at the low end of the typical US tech range cited above (1.20x-1.35x) - which is exactly the check to run when you're picking a benefits load assumption for the headcount model: build it up from the actual components once, confirm it's in a sane range, then use the single multiplier everywhere else. FICA Social Security and FUTA/SUTA are wage-base-capped, so a high earner's effective multiplier drops slightly later in the year once they cross the cap - a detail that matters for individual payroll reconciliation but washes out at the department-average level used in a headcount model.

---

## Sales Productivity: Converting Headcount Into Revenue Capacity

For revenue-generating headcount, the ending-HC number overstates near-term output, because a rep hired in Month 1 isn't fully ramped in Month 1. The standard fix is a blended productivity factor:

```
Productive HC = Ending HC x Productivity Factor
Revenue Capacity = Productive HC x Quota per Rep
```

Using the Sales build from above - 20.3 reps by Month 6 - and a blended productivity factor of 0.75 (typical for a SaaS org with a 3-4 month ramp):

```
Productive HC = 20.3 x 0.75 = 15.2 reps
```

If each fully-ramped rep carries a $600,000 annual quota ($50,000/month), Month 6 revenue capacity is:

```
Revenue Capacity = 15.2 x $50,000 = $760,000/month
```

Compare that to naively multiplying the full 20.3 nominal reps by quota - $1,015,000/month - a 34% overstatement. This is the single most common way a hiring plan quietly inflates a revenue forecast: treating headcount and revenue capacity as the same number when they aren't.

<!-- tool:startup-runway-calculator -->

Headcount is usually the biggest driver of burn, so once the comp build above is done, running it through a [startup runway and burn-rate](/blog/startup-runway-burn-rate) view shows how fast the hiring plan eats into cash - and where the plan needs to flex if runway gets tight.

---

## Common Mistakes to Avoid

1. **Forgetting the benefits load multiplier entirely.** Budgeting off base salary alone understates true cost by 20-50%, and the gap compounds as headcount scales.
2. **Applying one blended attrition rate company-wide.** Sales and customer-facing attrition typically runs 1.5-2x higher than engineering or G&A. A single rate either overstates stable-department turnover or understates high-churn department turnover.
3. **Treating sales headcount as immediately productive.** Skipping a ramp/productivity adjustment overstates near-term revenue capacity, which cascades into an overstated revenue forecast built on a hiring plan that hasn't actually delivered yet.
4. **Rounding headcount every month instead of at reporting time.** Compounding monthly rounding errors across 12 months can shift year-end headcount by a full head or more versus what the underlying rates actually imply.
5. **Not reconciling the plan against actual payroll runs.** A headcount model that never gets checked against ADP/Gusto output drifts silently - start-date timing slips, contractors get miscategorized as FTEs, and backfills for attrited roles get missed.
6. **Modeling headcount and comp on separate, unlinked tabs.** If the hires sheet and the compensation sheet don't reference the same ending-HC cells, they will eventually disagree, and nobody will notice until finance and the department head are looking at two different numbers.

---

## Key Takeaways

- **The core mechanic is simple, the discipline is not:** Ending HC = Prior HC + Hires - Attrition, applied consistently department by department, month by month, off assumptions that live in one place.
- **Fully-loaded cost, not base salary, is the real number.** Apply a benefits load multiplier (1.20x-1.35x is typical for US tech) before the comp figure goes anywhere near the P&L.
- **Carry decimals through the build; round only at reporting time.** Rounding headcount every month compounds error across a 12-month forecast.
- **Payroll forecasting is the next layer down**, breaking fully-loaded cost into gross wages, employer payroll tax, healthcare, and retirement match - the components a payroll provider actually charges.
- **Adjust revenue-generating headcount for ramp.** A blended productivity factor keeps the revenue forecast honest about what newly hired reps can actually deliver in their first few months.
- **Reconcile the model against actual payroll runs periodically.** A headcount plan that never gets checked against real payroll data will drift, and the drift compounds the longer it goes unchecked.

For the broader forecasting context this plugs into, see our guide to [financial forecasting methods](/blog/financial-forecasting-methods). Once the plan is set, track it against actuals with a [budget vs. actual analysis](/blog/budget-vs-actual-analysis) to catch drift early.


## Frequently asked questions

### What is headcount planning?

Headcount planning is the process of forecasting how many people a company will employ, by department and by month, along with the fully-loaded cost of employing them. It combines a hiring plan (new hires by role and start date), an attrition assumption (expected departures), and a compensation build (base salary plus the employer-side cost of benefits, payroll tax, and equity) into a single forecast. The output feeds directly into the opex line of the P&L and is usually the single largest cost driver in an early-stage or growth-stage company's budget.

### How do you calculate attrition in a headcount model?

Monthly attrition is typically calculated as the prior month's ending headcount multiplied by a monthly attrition rate: Attrition = Prior Ending HC x Monthly Attrition %. Ending headcount then equals prior ending headcount plus new hires minus attrition. Most models carry headcount as a decimal internally (e.g., 15.3 people) rather than rounding every month, because rounding at each step compounds error over a 12-month build. Round only at the point you report the number, such as a Y1 summary.

### What is a fully-loaded cost per employee?

Fully-loaded cost is base salary multiplied by a benefits load multiplier that captures the employer-side cost of employing someone beyond their paycheck: payroll tax (FICA Social Security and Medicare, FUTA, SUTA), healthcare premiums, retirement match, and general overhead. US tech companies typically run a 1.20x-1.35x multiplier on base salary; European employers often run 1.30x-1.50x because of higher mandatory social charges. A $120,000 base salary at a 1.25x load costs the company $150,000 per year, not $120,000.

### How is headcount planning different from a payroll forecast?

Headcount planning answers 'how many people, in which roles, starting when' and rolls that into a top-line comp budget, usually monthly, by department. Payroll forecasting goes one level deeper: it breaks the same headcount plan into the actual payroll components a finance team has to fund and reconcile against a payroll provider, such as gross wages, employer payroll tax by category, healthcare premiums, 401(k) match, and bonus accrual. In practice, a headcount plan is the input; a payroll forecast is the output used for cash planning and payroll-system reconciliation.

### How do you handle sales headcount differently from other departments?

Sales headcount usually needs a productivity or ramp adjustment on top of the standard hires-minus-attrition build, because a rep hired this month is not fully productive this month. A common approach is to apply a single blended productivity factor (e.g., 0.7-0.8 for a SaaS org with a typical ramp period) to convert nominal headcount into 'productive headcount,' which is what you multiply against quota or average deal size to get a realistic revenue-capacity forecast. Without this adjustment, a hiring plan will overstate near-term sales output.

### What's a realistic monthly attrition rate to assume?

It depends heavily on department, seniority, and company stage, but 1-2.5% monthly (roughly 12-25% annualized) is a common range for growth-stage tech companies, with sales and customer-facing roles typically running at the higher end and engineering and G&A at the lower end. Rather than guessing, pull your company's trailing-12-month attrition by department from HR data if you have more than a year of history; for a first model, 1.5-2% per month per department is a defensible starting assumption to sensitize later.