The 2027 Headcount Plan: A Hiring Ramp That Fits the Runway

Why Headcount Is the Lever

For most growth-stage companies, payroll is the largest cost line by far, and the headcount plan is therefore the largest single input to the next year's cost base. It is also the input the company controls most directly. Revenue is a forecast; the roadmap is an intention; but hiring is a decision — the company chooses whether and when to bring each person on. That makes the headcount plan the primary lever for shaping the runway, and getting it right is the highest-leverage cost-planning work of the year.

The headcount plan also sits at the centre of the 2027 budget. As covered in the budget-build framework, the cost side of a driver-based budget is built from the headcount plan — each hire a line with a start date and a fully-loaded cost. The headcount plan and the budget are therefore inseparable, and building the headcount plan well is most of building the cost side of the budget well.

The Fully-Loaded Cost

The most common headcount-planning error is to model salaries rather than fully-loaded costs. The true cost of a hire is not the salary — it is the salary plus employer National Insurance (currently around 13.8 per cent above the secondary threshold, subject to any Budget change), pension contributions, benefits, equipment, software licences, and the allocated overhead the person consumes. The fully-loaded cost can be 20 to 30 per cent above the base salary, and a plan built on salaries alone understates the cost base materially.

The discipline is to model every hire at fully-loaded cost, with the on-costs percentage as an explicit driver so that a Budget change to employer NI — one of the scenarios worth pre-positioning — flows through the plan in a single input. This connects directly to the driver-based forecast, where the payroll driver carries the on-costs percentage.

Sequencing the Ramp

The headcount plan is not a headline number — it is a sequence of dated hires, and the sequencing is where it becomes a runway tool. Ten hires across 2027 have a very different cash impact depending on whether they land in Q1 or are spread through the year. Front-loading the hires spends the cash sooner and shortens the runway; back-loading preserves runway but delays the capacity. The sequencing is a deliberate choice the CFO and the board make against the runway, not an afterthought.

The discipline is to build the ramp as dated hires and to make the sequencing visible: here is the cash impact of hiring on this schedule, here is the runway that results, here is what delaying a cohort by a quarter does. This turns the headcount plan from a cost total into a set of decisions the board can adjust — the essence of a driver-based plan.

The Productivity Lag

A hire is a cost from day one but a contributor only after a ramp — the time to hire, onboard, and reach productivity. For many roles this lag is one to two quarters, and for senior or specialist roles it can be longer. A headcount plan that assumes a hire contributes immediately overstates the near-term benefit and can lead to over-hiring on the expectation of capacity that has not yet arrived.

The discipline is to model the cost from the start date but the contribution from the productive date, and to reflect this in both the cost plan and any revenue or capacity the hire is expected to drive. For revenue-generating roles like sales, this is the ramp already built into the driver-based forecast; for other roles, it is a reminder that the capacity a hire adds lags the cost by a quarter or two.

Headcount Scenarios

Because the headcount plan is a set of dated decisions, it supports scenarios naturally — and the headcount scenarios are among the most useful the board sees, because they translate directly into runway. Build three: the base plan, a conservative plan that delays or removes some hires to extend runway, and an investment plan that adds hires to accelerate growth, funded by additional capital or stronger performance.

The value is that the board can see the runway consequence of each hiring posture directly. "The base plan runs the runway to here; delaying the Q2 engineering cohort extends it by this much; the investment plan requires a raise by this date." That is a concrete, decision-ready conversation, far more useful than an abstract debate about headcount growth.

Making It a Board Decision

The headcount plan should reach the board as a decision, not a fait accompli. Present the dated, fully-loaded ramp, the resulting runway, and the scenarios, and let the board engage with the actual choices: which hires, when, and the runway trade-off of each. This is where the headcount plan earns its place as the centrepiece of the cost side of the 2027 budget — it is the set of decisions with the largest impact on next year's outcome, and the board should own them explicitly.

The practical timing is to have the headcount plan built and scenario-modelled as part of the September-to-November budget-build cycle, so it goes to the board with the 2027 budget rather than being decided piecemeal through the year. A headcount plan agreed as a whole, against the runway, is far more coherent than one assembled from individual hiring approvals.

Key Takeaways

• The 2027 headcount plan is the largest driver of next year's cost base and the lever most within the CFO's control — hiring is a decision, not a forecast.
• Model every hire at fully-loaded cost (salary plus ~20–30% on-costs), with the on-costs percentage as an explicit driver so a Budget NI change flows through in one input.
• Build the ramp as a sequence of dated hires and make the sequencing visible — front-loading shortens the runway, back-loading preserves it; the choice is deliberate.
• Model cost from the start date but contribution from the productive date — the one-to-two-quarter productivity lag prevents over-hiring on capacity that has not arrived.
• Build three headcount scenarios — base, conservative, investment — because they translate directly into runway and make a concrete board conversation.
• Take the dated, scenario-modelled plan to the board as a decision, built into the September-to-November budget cycle rather than assembled from piecemeal approvals.