Hiring Plan and Runway: Modeling Headcount Against the Cash You Actually Have

What does a planned seat actually cost per month?

Base salary is the number people quote and it is rarely more than three quarters of the real figure. Add employer contributions and statutory costs, which vary substantially by country and sometimes by region within a country, so use the rates that apply where the person will be employed rather than a blended assumption. Add benefits, insurance, and any allowances you provide.

Then add the costs that attach to a person regardless of role: equipment, software seats, workspace if you have one, and any recurring travel the role implies. Individually these look small and collectively they move the figure meaningfully, particularly for roles carrying several expensive tool licenses.

Finally add the one-time costs at the front: any recruiting fee or advertising spend, relocation or signing payments, and the productivity ramp. Ramp is not a cash cost, so keep it out of the burn model and hold it in the output model, but do not forget it exists when you are deciding whether a hire made in month nine helps you hit a milestone in month twelve.

Why does offer-to-start lag break most hiring plans?

Plans are usually written against the month a role is approved, and cash leaves against the month a person starts. Between those two points sits the search itself and then a notice period that is set by the candidate's existing contract and by local convention, and in some markets that notice runs to several months. A plan that ignores the gap systematically overstates how much capacity you will have in any given quarter.

The consequence runs both ways and founders usually only model one. On the optimistic side, you plan output from a person who will not be at their desk for four months. On the pessimistic side, you plan burn that does not begin when you thought, which means an early-year plan looks more expensive than the cash actually shows, and founders then approve additional seats against a surplus that is really just a timing artifact.

Model each seat with two dates: approved and started. Put the cost against the started date and the output against started plus a ramp period appropriate to the role. Revenue-carrying roles typically carry the longest ramp because a sales cycle has to run its full length before the first result appears, and modeling them as productive on day one is the most common source of an over-optimistic plan.

How do I connect the hiring plan to runway?

Compute your current cash-out month from your existing burn, then add each planned seat at its fully loaded monthly cost from its expected start month, and recompute. What you are looking for is not a single number but a curve: how the cash-out month moves as each hire is added in sequence. That curve tells you which specific hire is the one that crosses the line.

Set a floor and treat it as inviolable. Many founders work to a rule of keeping some minimum number of months of runway at all times, on the reasoning that a fundraise takes longer than expected and that negotiating from a position of scarcity is expensive. Whatever floor you choose, choose it while calm and write it down, because the decision is much harder to make in the month you approach it.

Then check the plan against the milestone rather than against the calendar. Runway is only meaningful relative to what you need to prove before you next raise or reach profitability. A plan that keeps twelve months of cash but does not deliver the evidence a next round requires is worse than a plan that spends to ten months and produces the proof.

How do I run scenarios without building a complicated model?

Three columns are enough. Build a base case with the hires you are confident about, a downside case with only the seats you would defend if revenue came in materially below plan, and an upside case that you would only execute after a specific event such as a closed round or a revenue threshold. Each column produces its own cash-out month.

The discipline is in defining the trigger, not the scenario. Write the condition that moves you from base to downside as something observable and dated: if a stated revenue or cash figure is not met by a stated month, these named seats do not open. Without the trigger the downside case is a document nobody ever executes, because in the moment there is always a reason to believe the next month will be better.

Keep the upside case genuinely conditional. The most common failure is a founder who mentally commits to upside hires, describes them to candidates, and then cannot execute when the triggering event slips. Those conversations damage your reputation with people you will want to hire later.

What are the practical alternatives to adding permanent headcount?

Contract and project-based arrangements convert a fixed cost into one you can stop, which suits work with a defined endpoint and a clear deliverable. The trade-offs are real: worker classification rules differ by jurisdiction and misclassification carries penalties, so structure these with local advice, and accept that contractors accumulate less shared context than employees.

Deferring a hire while buying a tool that removes part of the work is worth pricing seriously. The comparison is not tool cost against salary, it is tool cost plus the residual hours someone still spends against the fully loaded seat. Sometimes the tool wins clearly and sometimes it moves the work rather than removing it, and the difference is visible if you count the residual hours honestly.

Reordering the plan is the cheapest lever and the least used. If two seats are planned for the same quarter and only one is on the critical path to your next milestone, sequencing them three months apart changes your cash-out month without removing anything from the plan. Do this before considering anything more drastic.

How should a hiring freeze work if I need one?

Define its scope precisely, because an ambiguous freeze is worse than either alternative. State whether it applies to approved but unopened roles, roles currently in process, backfills for people who leave, and any offer already extended. An unclear freeze produces a month of paralysis in which nobody knows whether to continue a search and candidates in process are left without an answer.

Handle in-flight candidates immediately and directly. Someone in your final round has probably declined other conversations to be there. Telling them promptly, with a plain explanation, preserves the relationship for when conditions change. Going quiet is the option that costs nothing today and closes the door permanently.

Set the review date and the conditions for lifting it at the same time you impose it. A freeze with no stated end is read internally as a signal about the company's health, and that reading spreads faster and further than the facts warrant. Naming the conditions turns an indefinite worry into a defined situation.

How does the funding stage change the calculus?

Before an institutional round, the plan is usually constrained by absolute cash and every seat is weighed against months of survival. The relevant question for each hire is whether it materially increases the probability of reaching the evidence a next round requires, and hires that merely improve operations rarely clear that bar at this stage.

Immediately after a round, the risk inverts. There is cash, there is pressure to deploy it, and the plan tends to expand to fill the balance. The discipline that matters here is start-date sequencing rather than total headcount, because hiring the whole plan in one quarter overwhelms your ability to onboard anyone well and front-loads the burn against output that has not started.

Equity has its own arithmetic that runs alongside cash and is easy to underweight. Every grant to a new hire has a dilutive effect on existing holders, the pool needs to last until the next financing, and both the mechanics and the tax treatment differ by jurisdiction and company structure. Model the pool consumption alongside the cash plan and take specialist advice locally rather than assuming a general rule applies.

What to take away

• ▸Model fully loaded cost per seat: base, employer contributions, benefits, tooling, workspace, and one-time costs.
• ▸Place each seat on the calendar at its realistic start date, not its approval date, and model ramp separately.
• ▸Recompute the cash-out month hire by hire to find which specific seat crosses your runway floor.
• ▸Write the trigger, not just the downside scenario, as an observable condition with a date attached.
• ▸Reorder the plan before cutting it; sequencing two seats a quarter apart moves the cash-out month for free.
• ▸Define a freeze precisely, tell in-flight candidates promptly, and state the conditions for lifting it.