Headcount planning is one of the highest-leverage activities an engineering leader undertakes — and one of the least well-taught. Most CTOs and VPs of Engineering learn by doing, often making costly mistakes before developing a reliable process.
This guide is a practical, opinionated framework for engineering headcount planning: how to model what you need, how to build the business case, and how to survive the budget cycle with your hiring plan intact.
Why does engineering headcount planning fail?
Engineering headcount planning fails for a predictable set of reasons:
- Plans are built on intuition ("we feel stretched") rather than capacity data
- Requests arrive without modelled cost implications
- Engineering and finance speak different languages — one talks in people, the other in fully-loaded cost
- Plans don't account for ramp time, attrition, or the cost of vacancies
- The link between headcount and business outcomes is unclear
The best engineering headcount plans solve all of these problems before the conversation with the CFO begins.
How do I calculate how many engineers I need to hire?
The instinct is to think "we need three more engineers." The right starting point is "we have X units of capacity and we need Y." Working backwards from capacity requirements produces more defensible plans.
How to model capacity:
- Define your unit of capacity. For most teams this is engineer-weeks or story points. Sprint velocity is a reasonable proxy.
- Identify your committed roadmap for the next 6–12 months and estimate the engineering work required.
- Subtract known capacity: current team size × available weeks (~46) × utilisation rate (typically 70–80%).
- The gap between required and available capacity is your hiring number.
This framing immediately gives you something quantitative to anchor the conversation on.
How do I structure a headcount plan by role and seniority?
"We need three engineers" is not a headcount plan. Finance needs to model specific costs, and your recruiting team needs a specific brief. Define:
- Role type: backend, frontend, full-stack, platform, ML, mobile, QA, etc.
- Seniority: junior, mid, senior, staff — these are not interchangeable, and the cost differences are significant
- Employment type: permanent, contractor, or offshore — each has a different cost structure and lead time
- Start timing: quarter-by-quarter. A hire in Q1 vs Q4 has dramatically different in-year cost impact.
A well-structured headcount plan looks like a table, not a number.
How do I calculate the fully-loaded cost of planned engineering hires?
Every hire request should come with a cost model attached. Finance will do this anyway — better to do it yourself so you control the assumptions.
For each planned hire, calculate:
- Base salary (benchmarked to current market)
- Employer payroll tax (NIC in the UK; FICA in the US)
- Pension / retirement contributions
- Benefits (health, dental, life insurance)
- Tooling and software licences
- Recruiting cost (agency fee or internal cost allocation)
- Management overhead allocation
Quick reference multipliers:
| Scenario | Multiplier on Base | |---|---| | UK permanent employee | 1.3x–1.5x | | US permanent employee | 1.5x–1.8x | | UK contractor (via agency) | 1.0x–1.1x (all-in day rate) | | Offshore (LATAM / Eastern Europe) | 0.4x–0.7x of UK/US equivalent |
How long does it take to hire a senior software engineer?
A headcount plan that ignores hiring timelines is a fantasy. Build these into your model:
- Time to hire: Senior engineers take 8–16 weeks to hire from kick-off to offer acceptance.
- Notice periods: Most senior engineers in the UK serve a 1–3 month notice period.
- Ramp time: A new engineer is not fully productive on day one. Expect 4–8 weeks of reduced output while they get up to speed.
In practice, if you need capacity by Q3, you should be recruiting in Q1.
How should I account for attrition in my headcount plan?
Most headcount plans model hiring-in without modelling attrition. Average voluntary attrition in the UK tech sector runs at 10–15% per year. For a team of 20 engineers, that's 2–3 leavers per year — which must be replaced just to maintain current capacity, let alone grow.
Build attrition into your model as a baseline backfill number, separate from growth hires.
How do I present a headcount plan to get budget approved?
The CFO doesn't approve headcount because you feel stretched. They approve it because the cost is justified by the business outcome. For every headcount request, be able to articulate:
- What will this person work on? Be specific about the roadmap items, products, or systems.
- What is the business impact? Revenue enabled, cost reduced, technical debt eliminated, risk mitigated.
- What is the cost of not hiring? Delayed launches, accumulated technical debt, team burnout and attrition.
- What is the payback period? If a new engineer enables £200k of additional ARR, a £130k fully-loaded hire pays back in under a year.
Engineering leaders who frame requests in these terms win budget. Those who frame them as "we're overwhelmed" don't.
What are common headcount planning mistakes to avoid?
Hiring ahead of process: Headcount without a clear team structure leads to underutilised engineers and management chaos.
Ignoring dependencies: Hiring engineers without hiring the product managers or designers they need to work with is a common trap.
Underestimating the hiring manager's time: Recruiting is a 15–25% overhead on the hiring manager's time during active search. If your EMs are already stretched, this matters.
Treating headcount as permanent: Some capacity needs are temporary. Contractors, staff augmentation, or outsourced workstreams are valid tools — and often faster and more flexible than permanent hires.
How TeamCalc Supports Headcount Planning
TeamCalc is built around exactly this workflow. You model your team — roles, seniorities, locations, employment types, and start dates — and TeamCalc calculates:
- Fully-loaded cost per hire and for the team overall
- In-year vs annualised cost based on planned start dates
- Salary benchmarking against current market data
- Scenario comparisons (e.g., "what if we hire three seniors vs five mids?")
- Exportable outputs ready for board packs and finance reviews