What a startup hiring plan is, and why it drives burn rate
A startup hiring plan is a month-by-month schedule of which roles you will add, when, and at what fully loaded cost, set against the cash you have left. Because payroll is usually 60–80% of an early-stage startup's monthly spend, the hiring plan is the single biggest lever on burn rate — and therefore on runway.
Most founders plan hires by need ("we need a second engineer"). Survivors plan them by runway ("we can afford a second engineer only if it still leaves us 18 months"). That shift in question is the whole discipline.
The true cost of a hire is more than the salary
The number on the offer letter understates what a hire costs. Add employer payroll taxes and social contributions, benefits, equipment, software seats, recruiting fees and management time. A common rule of thumb is a fully loaded multiplier of roughly 1.2x to 1.4x base salary, and higher where employer contributions are heavy.
A hire also costs money before they produce anything: recruiting runs for weeks, onboarding takes one to three months, and a mis-hire is paid for twice — once in salary, once in the replacement search.
$6,000
Base salary per month
≈ $7,800
Fully loaded at 1.3x
≈ $93,600
Cost over 12 months
How one hire changes runway: a worked example
Runway equals cash divided by net monthly burn. Take a startup with $600,000 in the bank, $40,000 in monthly costs and $10,000 in monthly revenue — net burn of $30,000 and 20 months of runway.
Now add two engineers at $7,800 fully loaded each. Net burn rises to $45,600, and runway falls to about 13 months. Two hires removed seven months of life, without a single dollar of revenue added. Unless those hires lift revenue enough to offset the cost, you have traded time for capacity.
| Before hiring | After 2 engineers | |
|---|---|---|
| Cash | $600,000 | $600,000 |
| Net monthly burn | $30,000 | $45,600 |
| Runway | 20 months | ≈ 13 months |
How to sequence hires so you do not outrun your cash
Hire in the order that unlocks revenue or removes your biggest bottleneck, not in the order of org-chart tradition. A practical sequence for a seed-stage product company:
1. Founders cover product, sales and operations first. 2. The first hire removes the founder's biggest time sink — often engineering or sales. 3. A customer-facing hire comes once there is a repeatable sale. 4. Management layers, HR and specialist roles come last, and only after the first three are productive.
Test each hire with a simple gate: does this role pay for itself within two quarters, or does it protect something that would otherwise break? If neither answer is yes, wait.
Five hiring mistakes that quietly shorten runway
Most hiring damage is not one big decision; it is a handful of small, repeatable errors. Watch for these:
1. Hiring ahead of revenue: adding sales or support staff before there is a repeatable sale. 2. Ignoring the lag: a hire's cost starts on day one, but their output takes one to three months to show. 3. Hiring seniority you cannot yet use: an expensive executive with no team to lead. 4. Forgetting non-salary costs: tools, equipment and recruiting fees. 5. Treating headcount as progress: a bigger team feels like momentum, but only revenue, retention and learning count as momentum.
Every one of these shows up in net burn within a quarter. The fix is a monthly review: compare the plan, actual payroll and remaining runway, and pause open roles if runway slips under your floor.
A pre-hire checklist you can run in ten minutes
Before any offer goes out, answer five questions in writing: What specific problem does this role solve? What is the fully loaded monthly cost? How many months of runway remain after the hire? Which milestone should this person help reach within two quarters? What is the cheapest reversible alternative, such as a contractor?
If you cannot answer the first and fourth questions in one sentence each, the role is not ready to be opened. Founders who write these answers down tend to hire fewer people, later, and keep more cash for the moments that matter, such as a delayed customer payment or a slow fundraise.
Guardrails: runway floors and cost-per-hire triggers
Set two rules before you open a job post. First, a runway floor: never approve a hire that pushes projected runway below 12–18 months, because a fundraise typically takes three to six months to close. Second, a trigger: tie each hire to a milestone, such as reaching a monthly revenue level or closing a pilot.
Contractors, part-time roles and fixed-term contracts keep optionality when revenue is uncertain. They cost more per hour but are far cheaper to reverse, and reversibility is worth real money when your runway is short.
Practising hiring trade-offs in Founder Runway
Founder Runway is a startup simulation where hiring and spending choices have consequences. A run lasts 20 rounds, each decision has 4 options, and you can start at Pre-Seed, Seed, Pre-Series A or Series A across B2B, B2C and B2G business models, including sectors such as Health-Tech, Green-Tech and Edu-Tech.
Play one run where you staff up early and another where you stay lean, and watch cash, burn and runway respond turn by turn. The endings are failure, promising, EBITDA positive and high-value exit potential.
Frequently asked questions
What is a startup hiring plan?
A startup hiring plan is a schedule of the roles you will add, when you will add them and what each will cost fully loaded, compared against your cash and runway. It keeps headcount growth from outpacing the money available.
How much does it really cost to hire an employee?
The fully loaded cost is typically 1.2x to 1.4x base salary once you add payroll taxes, benefits, equipment, software and recruiting. Heavy employer contributions in some countries push the multiplier higher.
How do hires affect burn rate?
Payroll is often 60–80% of early-stage costs, so each hire raises monthly burn by its fully loaded cost. Burn rises immediately, while the revenue a hire enables usually arrives months later.
When should a startup make its first hire?
When a founder's biggest bottleneck is clear and the hire can pay for itself or protect the business within about two quarters, and runway stays above 12–18 months after the hire.
How much runway should remain after a new hire?
Aim to keep at least 12–18 months of projected runway after any hire, since raising a round commonly takes three to six months and needs a buffer.
Test this decision in the game.
Apply the same assumption across one run and see which metric weakened three turns later.