Startup Headcount Planning for the Next Year

Hiring is usually the biggest decision in a startup's plan for the year ahead, and the hardest one to undo. Startup headcount planning means deciding which roles you need, when you need them and what they will cost, then linking each hire to a goal and to your runway. This guide gives you a simple process and a template you can finish before your plan goes to the board.

A man standing beside a dry-erase board in an office, talking through a plan written on the board
A headcount plan starts on the whiteboard: goals first, then the people needed to reach them.

Key takeaways

  • Start from next year's goals and work back to the roles, not from a wish list of hires.
  • Cost each role fully: salary plus employer taxes, benefits, equipment, software and recruiting.
  • Give every planned hire a start month and a trigger, so you hire when the evidence says yes.
  • Model at least two scenarios and check your runway under each before you commit.
  • Review the plan every month or quarter and adjust hires up or down.

Late October is when many founders sit down with next year's plan. The revenue forecast gets most of the attention, but the headcount plan drives most of the spending. For most startups, people are the largest cost line, and each hire adds a monthly commitment that continues long after the excitement of the offer letter.

A good headcount plan does not need complex software. It needs clear thinking about what the company must achieve, honest numbers about what people cost and a few rules about when to pull the trigger. Let's build one.

A quick note: this article is general information, not legal, tax or employment advice. Employment law, payroll taxes and benefits rules vary by country and state, so check the details with an accountant or employment lawyer before you make offers.

Start with goals, not job titles

The most common headcount plan is a list of roles each manager would like. That list is almost always too long, and it rarely matches what the company needs most. Turn it around.

  1. Write down next year's top goals. Keep it to three to five. If you use OKRs (Objectives and Key Results, typically set quarterly), start with the objectives you expect for the first half of the year.
  2. Ask what work each goal requires. For example, "launch in a second market" might need sales coverage, local support and some product changes.
  3. Check who can do that work today. Some of it fits existing people. Some of it needs a new skill. Some of it can wait.
  4. Name the gaps. Each real gap becomes a candidate role. Note which goal it serves.
  5. Consider alternatives. Could a contractor, an agency, a tool or a change in process cover the gap for now?

When every role is linked to a goal, prioritizing becomes much easier. If the goal is dropped or delayed, the role moves with it.

Common mistake

Planning hires to match last year's growth rate. If revenue rose fast this year, it is tempting to assume the team should grow at the same pace. Growth in the past does not guarantee growth next year. Tie each hire to a specific goal and a trigger instead.

Work out the true cost of each role

Salary is only part of what a hire costs. When you add the rest, the total can be noticeably higher than the number in the offer letter. Build a cost for each role that includes:

  • Base pay and any bonus or commission.
  • Employer payroll taxes and contributions. In the US this includes employer payroll taxes and possibly state taxes. In the UK it includes employer National Insurance and workplace pension contributions. Rates change, so check the current figures.
  • Benefits, such as health insurance in the US or private medical insurance in the UK if you offer it.
  • Equipment and software: laptop, monitors, licenses and any role-specific tools.
  • Recruiting costs: job ads, recruiter fees and the time your team spends interviewing.
  • Ramp time. New people take time to reach full speed, so do not count on full output from day one.

Many founders use a "loaded cost" for each role: the full yearly cost including all of the above. Your accountant or payroll provider can help you estimate the employer costs for each country where you hire.

Equity is a cost too

Option grants do not hit your bank balance, but they use up your option pool. In the US, options are usually priced at fair market value based on a 409A valuation, and the difference between ISOs and NSOs affects how employees are taxed. In the UK, EMI options are the main tax-advantaged scheme for small companies. Add a column for planned grants and check that your pool can cover next year's hires plus refresh grants for existing staff.

Pro tip

Plan by start month, not just by count. Three hires in January cost far more over the year than three hires in October. Showing start months in your plan makes the cash impact clear and helps you spread hiring across the year.

A headcount plan template

Copy this table into a spreadsheet and add one row per planned role. The amounts below are made up for illustration only, so replace them with your own estimates.

RoleTeamGoal it servesStart monthLoaded yearly cost (example)Hiring triggerPriority
Senior backend engineerEngineeringShip team featuresFebruary$160,000Plan approved and fundedMust have
Account executiveSalesGrow mid-market revenueApril$140,000Pipeline reaches agreed level for two monthsShould have
Customer support specialistSupportKeep response times steadyJune$65,000Tickets per agent stay above target for six weeksShould have
Marketing managerMarketingLaunch second marketSeptember$110,000Second market pilot hits goalsNice to have

Add two summary rows at the bottom: total new cost for the year (counting only the months each person is employed) and the cost of the full team at year-end run rate. The second number shows what you are committing to for the following year.

A person writing notes and lines with a marker on a whiteboard during a planning session
Write triggers next to every role, so hiring follows evidence rather than optimism.

Set hiring triggers and priorities

A headcount plan is a set of options, not a list of promises. Triggers turn it into something flexible.

What a good trigger looks like

A trigger is a condition that must be true before you open the role. Good triggers are specific and measurable. Examples include:

  • A funding round closes or the plan is formally approved.
  • Revenue or pipeline reaches an agreed level for a set period.
  • A workload measure, such as support tickets per person, stays above target.
  • A pilot project succeeds and the next stage needs a dedicated owner.

Sort roles into tiers

Label each role "must have," "should have" or "nice to have." Must-have roles are hired as planned. Should-have roles wait for their trigger. Nice-to-have roles only open if the year goes better than plan. When cash gets tight, you already know which roles to pause.

Hypothetical example

Imagine Amara, co-founder of a 20-person B2B startup. Her managers ask for 14 new roles. She links each one to the company's four goals and finds that five roles do not clearly serve any of them. Of the nine left, she labels four as must have, three as should have with triggers and two as nice to have. Her base-case plan includes seven hires, and her cautious case includes four. Both keep her runway above the level her board agreed. When a big deal slips in the spring, she pauses one should-have role without any panic.

Model scenarios and protect your runway

Once you have costs and start months, run the numbers in at least two scenarios.

  1. Base case. The hires you expect to make if the year goes roughly to plan.
  2. Cautious case. Only must-have roles, with later start dates. Use this to see how long your cash lasts if revenue grows more slowly.
  3. Upside case (optional). Extra roles you would add if revenue or funding comes in ahead of plan.

For each scenario, check your monthly burn and runway. Many founders set a minimum runway they will not go below and treat it as a hard line. If a scenario crosses that line, cut or delay roles until it does not.

Forecasting tools such as Fathom, Float, LivePlan, Jirav or Pulse can help you model headcount alongside revenue. A well-organized spreadsheet works fine too. Check current features, pricing and privacy policies before connecting your accounting data.

Common mistake

Forgetting that hires are hard to reverse. Cutting a planned role is easy. Letting someone go after they join is painful for them, for the team and for your reputation. Hire a little later than you think you need to, and use contractors to bridge short gaps where that fits local rules.

Contractors, part-timers and other options

Not every gap needs a full-time employee. Before you add a role, ask whether one of these fits better for the first months:

  • Freelancers or contractors for specialist or project work. Classification rules differ by country, so check that a contractor arrangement is genuine.
  • Agencies for work like design, paid ads or recruiting.
  • Part-time or fractional roles, such as a part-time finance lead.
  • Tools and automation that remove repetitive work from the team.
  • Internal moves, where someone grows into a new role and you backfill a more junior position.

If you plan to hire people in other countries or as remote staff, factor in local employment law, payroll setup and your remote work policy, which should cover hours, equipment, data security and expenses.

Get buy-in and keep the plan alive

A headcount plan only works if managers understand it and the board supports it.

  • Share the logic with managers. Show which goals drove which roles, and explain the triggers. People accept a "not yet" more easily when they see the reasoning.
  • Present it with the budget. Your board will want to see headcount, costs and runway together, usually as part of next year's plan.
  • Review it regularly. Check the plan every month or quarter. Mark which triggers have been hit, which roles are open and which should be paused.
  • Track actuals. Compare planned start dates and costs with what really happened. The gaps teach you how to plan better next year.

Your headcount planning checklist

  • Write down three to five goals for next year
  • List the work each goal requires and the current gaps
  • Turn real gaps into roles, each linked to a goal
  • Estimate the loaded cost of every role
  • Check that your option pool covers planned grants
  • Add start months, triggers and priority tiers
  • Model base and cautious scenarios against your runway
  • Consider contractors, tools or internal moves for each gap
  • Share the plan with managers and the board
  • Set a monthly or quarterly review date

Frequently asked questions

How far ahead should a startup plan headcount?

Most startups plan in detail for the next 12 months and roughly for the year after. Early-stage companies often review the plan every quarter because their goals change quickly.

What is a loaded cost?

It is the full cost of a role, not just the salary. It includes employer taxes and contributions, benefits, equipment, software and recruiting. Your accountant or payroll provider can help you estimate it for each country.

Should we hire ahead of revenue?

Sometimes, for roles that take a long time to pay off, such as engineering for a key product. Use triggers and scenarios so you only hire ahead when your runway can absorb it if revenue arrives later than hoped.

The bottom line

Startup headcount planning works best when it starts with goals, counts the full cost of each role and uses triggers to decide when to hire. Model at least two scenarios, protect your runway and sort roles into must have, should have and nice to have so you can adjust quickly.

Block an afternoon this week, list next year's goals and fill in the template one role at a time. You will walk into budget season with a plan you can defend and change with confidence.

Written by

Our editorial team researches and writes practical, no-fluff guides for founders, entrepreneurs and small business owners. About us