Headcount planning: a hiring plan your cash can survive

Headcount planning means keeping a plan for every current and planned role, with its start date, fully loaded cost, owner and the driver or milestone that justifies it, and feeding that plan into the cash forecast month by month. Most startup hiring plans instead start as a list of roles the team wants; the cash forecast comes later, if at all, and the two rarely agree. Then a raise takes longer than expected, or bookings come in below plan, and the hiring list becomes the first thing to cut, often after offers are already out.

This playbook is for founders of seed to Series B software companies.

Why headcount is the plan

In most software companies, payroll and the costs that come with it are the largest cash cost by a wide margin. That makes headcount planning the biggest lever on runway, and the one a founder controls most directly.

It is also the lever that is hardest to reverse. Cancelling a vendor contract is a phone call. Reversing a hire costs severance, morale and months of lost momentum. The cheapest moment to change a hiring decision is before the offer goes out, which is why the plan needs to be tested against cash before recruiting starts, not after.

A good headcount plan answers four questions for every role: why this role, when it starts, what it really costs, and what has to be true before the company hires it.

The fully loaded cost of an employee

The fully loaded cost is everything the company pays because a person is on the team, and salary is only part of it:

• Base salary. The starting point, paid monthly or semi-monthly.
• Employer payroll taxes. The employer's share of social security and Medicare, plus federal and state unemployment taxes. Social security and federal unemployment tax apply only up to an annual wage limit, while Medicare has no limit, so the employer's tax cost for a well-paid employee is often heavier early in the year.
• Benefits. Health, dental and vision premiums, retirement plan contributions and any other benefits. These vary widely by plan design and by whether the employee covers a family.
• Equipment. A laptop, monitors and accessories, usually a one-time cost in the start month.
• Software seats. Every tool priced per user adds a monthly cost per hire: email, collaboration, design, engineering and sales tools.
• Recruiting fees. If an agency fills the role, the fee is a one-time cash cost, often paid when the hire starts or soon after.
• Commissions and bonuses. For sales roles, variable pay can be a large share of total compensation. It should be tied to the bookings forecast, not left out because it is variable.

Stock options matter to the employee but do not use cash, so they sit outside the cash forecast. Track them in the cap table and the equity pool plan.

A common shortcut is to multiply salary by a loading factor to cover taxes and benefits. That works for a first pass, as long as the factor reflects the company's actual benefits and payroll data. It is not a universal number, and one-time costs such as equipment and recruiting fees should be modeled separately in the month they are paid.

Start dates and ramp time

A hire does not cost money the day the plan says it does, and it does not produce results on day one either. Both sides need dates.

Start dates

A start date is the end of a chain: approval, job description, sourcing, interviews, offer, acceptance and notice period. Each step takes time, and plans tend to assume it all happens faster than it does. Model the start month as the month the person actually joins payroll, and set it realistically. If recruiting has not started, a start date next month is not a plan.

Ramp time

New hires take time to become productive, whether that means learning the codebase or learning the accounts. The ramp matters most for sales:

• Account executives ramp to quota. A new rep usually carries a reduced quota for the first several months while building pipeline. Bookings from that rep start low and build, and then the sales cycle and collection terms delay the cash further.
• Cost is immediate, output is delayed. The full monthly cost hits from the start month. The revenue the hire supports arrives months later.

A plan that assumes a new rep closes at full quota in month one overstates near-term bookings and makes the hiring plan look self-funding when it is not. Use a ramp schedule based on the company's own history where it exists, and be conservative where it does not.

Linking hires to drivers and milestones

Every role in the plan should connect to something the business needs to do. There are two kinds of link.

• Driver-based roles scale with a measurable volume. Support and customer success roles scale with customers or accounts. Sales roles scale with the bookings target and quota capacity. Implementation roles scale with new customers onboarding.
• Milestone-based roles unlock a specific outcome. A senior engineer to ship a product the roadmap depends on. A first finance hire before an audit. A security lead before an enterprise sales push.

Writing the link down forces a useful question: if the driver does not grow, or the milestone moves, does the company still need this role on this date? If the answer is no, the role should have a trigger rather than a fixed date.

Building the hiring plan

A practical hiring plan fits on one tab. For each role, record:

Feed the monthly cost and one-time costs into the cash forecast by month. That link is the point of the exercise, and it is where headcount planning meets the rest of FP&A. A hiring plan kept in a separate spreadsheet from the cash forecast will drift, and nobody will notice until runway is shorter than everyone thought.

Include backfills. People leave, and replacing them costs recruiting fees, overlap and a ramp period even though headcount does not change. A plan with no attrition or backfill assumption understates cost.

Scenarios and hiring triggers

A single hiring plan implies more certainty than any startup has. Build three versions:

• Base. The plan the company expects to run, with realistic start dates.
• Accelerated. What the company would add if bookings or a raise come in ahead of plan.
• Hold. Only the roles that are already committed or essential. This is the plan to fall back to if the downside case arrives.

Triggers connect the scenarios. Instead of "hire two account executives in Q2", the plan says "open the second account executive role once the first reaches a set share of ramped quota" or "start recruiting the next engineering hire once the round closes".

Triggers can be tied to revenue (ARR, bookings, pipeline coverage) or to cash (months of runway in the downside case). Cash triggers are the backstop: if downside runway falls below the level the board has agreed, or cash heads toward a minimum balance set by venture debt covenants, the company moves to the hold plan automatically, without a new debate. Agreeing triggers in advance takes the emotion out of later decisions.

A worked example

A fictional seed stage software company has $4,800K of usable cash and $300K of monthly net burn before any new hires, which gives 16.0 months of runway. It plans three hires: a senior engineer, an account executive and a customer success manager.

For this example only, fully loaded monthly cost is base salary divided by 12, multiplied by 1.25. The 25% uplift for payroll taxes and benefits is an example assumption, not a norm; actual figures depend on location, benefits and pay levels. Each hire also carries an assumed $5K one-time cost for equipment and setup in the start month.

Illustrative figures, not client data.

Now the same three roles under different scenarios. Runway is the month cash runs out, measured from the start of month 1.

Illustrative figures, not client data. Assumes flat pre-hire burn and no revenue from the new hires; the account executive's commissions and bookings are left out to keep the arithmetic simple.

Two points stand out.

• Start dates change the year one budget much more than they change runway. Staggering the starts saves $105K in year one compared with hiring everyone in month 1, but adds only about 0.3 months of runway, because by month 7 all three are on payroll either way. Runway depends on the run rate the company ends up carrying.
• Holding roles changes the run rate. Hiring only the engineer adds about 0.8 months of runway over the base case and keeps $25K a month off the burn for as long as the hold lasts.

In a real plan, the account executive's ramped bookings would partly offset their cost, after a delay. That is exactly why the ramp assumption deserves scrutiny.

Common mistakes

• Budgeting full year cost for mid-year hires. In the example, budgeting all three roles for twelve months would show $555K of year one cost against $450K actually spent. The budget looks safe, but the variance hides whether the plan is on track.
• Treating annual cost as the runway number. The reverse error: a mid-year hire costs little this year but a full year next year.
• Ignoring ramp, salary-only costs or backfills. Each one understates cost or overstates near-term bookings.
• Not updating for slipped start dates. A hire who starts three months late saves cost but delays the work; update both, and do not let the saving quietly fund something else.

How an investor reads your hiring plan

Decipher sets up a company's finance the way an investor or acquirer will read it. On headcount, careful investors tend to check the same things.

• Does it tie to payroll? Current headcount and cost in the plan should match the payroll register. Gaps suggest the plan is not maintained.
• Does it tie to the cash forecast and the raise? The amount being raised should fund the hiring plan to a clear milestone, under a downside case, with room to spare.
• Are costs fully loaded? A plan built on salaries alone will be adjusted, and the runway will shrink in the investor's model.
• Are start dates and ramp realistic? Investors compare planned start dates with how long past hires actually took, and planned rep productivity with how past reps actually ramped.
• What is the mix? The balance of quota-carrying reps to sales support, and of engineering to the rest of the company, says a lot about how the founder thinks the business grows. Revenue per employee is often checked as a sense check on efficiency.
• Is there a hold plan? A founder who can say which hires stop, and when, if bookings slow is showing control of the business, not pessimism.

For help building a hiring plan and cash forecast that hold up in front of investors, see Decipher's fractional CFO and FP&A services.