Startup Headcount Planner: How to Model Team Costs and Hiring Timelines
Headcount is typically 60-80% of startup burn. Getting it wrong breaks your unit economics and runway calculations. Multiply salaries by 1.25-1.35 in the US (or country-specific rate) to get loaded cost. Hire by stage: seed is 70% engineers, Series A is 40-50% engineers and 30% sales/marketing, Series B is more balanced. Track revenue per employee (should be $150-250K ARR per employee at Series A). Account for ramp time when hiring so you don't model hockey stick productivity. Plan headcount explicitly: who, when, why, how much.
Why Headcount Kills Most Startup Burn Models
The most expensive thing at a startup is people. Headcount typically represents 60-80% of burn in the early stages (pre-profitability). Yet I see founders underestimate headcount costs constantly.
They think of salary as the cost. Engineer at $120K per year? That's what goes in the model. Wrong. The fully-loaded cost is salary plus taxes, health insurance, benefits, 401K match, recruiting fees for replacement staff, equipment, office allocation, and admin. In the US, that multiplier is typically 1.25 to 1.35. So that $120K engineer costs the company $150-160K per year all-in.
I've seen countless financial models where the founder underestimated team costs by 30-40% because they didn't include the loaded cost. You build your revenue projections and hire plan based on this model. Six months later, payroll is 40% higher than you expected, runway shrinks from 18 months to 12 months, and you're suddenly in a panic fundraising mode.
Getting headcount costs right is foundational to an accurate financial model.
Calculating Loaded Salary Cost
In the US: Take base salary and multiply by 1.25-1.35. For a $120K engineer, that's $150-162K. This multiplier includes:
- Payroll taxes: ~7.65% (Social Security and Medicare)
- Health insurance: $500-800/month per employee ($6-10K annually)
- Other benefits (dental, vision, FSA, life insurance): $1-2K annually
- 401K match: 3-4% of salary ($3.6-4.8K for $120K salary)
- Recruiting fees for replacement: ~20% of salary (amortized across 3-4 year tenure)
- Equipment and setup: $2-5K per employee amortized
If you're including office space, that adds another 10-15%. A 10-person team in San Francisco headquarters with good office space can add $1-2K per person per month in rent and utilities.
In the UK: Multiply by 1.15-1.25. The multiplier is lower because while employer National Insurance (13.8%) is higher than US payroll tax, benefits and health insurance costs are lower (NHS is public). Typical loaded cost for a £85K engineer: £100-106K.
In France: Multiply by 1.40-1.50. French payroll taxes are high (42% of gross salary as employer contribution). This makes French hires significantly more expensive. A EUR 90K engineer costs the company EUR 126-135K fully loaded.
Remote/distributed teams: Multiply by 1.20-1.30. You save office space but add complexity. Distributed teams often have higher recruiting costs, tool costs, and timezone coordination overhead.
Build a simple calculator: base salary × multiplier by geography = loaded cost. Use this for all headcount planning.
| Country | Base Multiplier | Example ($120K base) |
|---|---|---|
| US (Bay Area) | 1.30-1.35x | $156K-162K |
| US (Other) | 1.25-1.30x | $150K-156K |
| UK | 1.15-1.25x | €138K-150K |
| Remote | 1.20-1.30x | $144K-156K |
Headcount by Stage: What's Typical
Seed Stage (5-10 people): Typically 70% engineering, 20% sales/marketing, 10% operations/admin. You're still building the product. Sales is a founder doing customer development, maybe one junior salesperson. Operations is likely the founder CEO managing cash and admin work. At seed stage, you cannot afford much headcount, so every hire needs to move the needle on product or revenue.
| Stage | Engineering | Sales | Ops | G&A | Total |
|---|---|---|---|---|---|
| Seed | 70% | 15% | 5% | 10% | 5-10 |
| Series A | 45% | 30% | 10% | 15% | 15-30 |
| Series B | 38% | 37% | 12% | 13% | 50-100+ |
Engineering team at seed stage includes the technical founder plus 1-3 additional engineers. These are not yet senior people (you can't afford them). They're mid-level engineers who can execute on technical roadmap but still need some direction.
Series A (15-30 people): Composition shifts to 40-50% engineering, 30-35% sales/marketing, 15-20% operations/finance. You've proven product-market fit. Now you're scaling sales and marketing. Operations grows because you need finance, HR, and admin infrastructure to support 25 people.
Sales team at Series A now includes a VP Sales or Head of Sales (usually $150-200K base + commission), 2-4 sales development reps (SDRs) at $50-70K + commission, and often an account executive starting at $100K+ base + commission. These are real salespeople who will carry your company through Series A and beyond.
Engineering is bigger but also includes more specialization. Frontend engineers, backend engineers, infrastructure/DevOps engineer, maybe a tech lead who manages other engineers.
Series B (50-100+ people): More balanced: 35-40% engineering, 35-40% sales/marketing, 20-25% operations/finance/HR. At this stage you need a CFO or VP Finance, a head of people/HR, a head of operations. These are not cheap hires (typically $150-200K base for director roles), but they're critical to managing a growing organization.
Sales team expands. You might have a VP Sales plus multiple account executives, customer success managers (often 1 per 15-20 customers), and a marketing team that includes content, paid acquisition, and brand roles.
Salary Benchmarks by Role and Geography
Engineers (base salary, not including equity or bonus):
| Role | US (Bay Area) | US (Other) | UK | Remote |
|---|---|---|---|---|
| Junior | $80-110K | $60-80K | £50-65K | $65-85K |
| Mid-Level | $120-160K | $90-120K | £75-95K | $100-130K |
| Senior | $160-200K | $120-150K | £100-130K | $130-170K |
| Staff/Principal | $200-250K+ | Rare | Rare | $170-200K |
Sales roles (base + commission):
- Sales Development Rep (SDR): $50-70K base + $15-30K commission (US)
- Account Executive: $100-150K base + $50-150K commission (US), varies widely by deal size
- VP Sales: $150-250K base + commission/bonus (US), higher in Bay Area
Marketing roles:
- Content/Growth marketer: $80-120K (US), £50-75K (London)
- Paid acquisition specialist: $100-150K (US)
- VP Marketing: $150-200K+ (US), especially if also responsible for brand
Operations/Finance:
- Finance analyst/bookkeeper: $60-90K (US), £40-60K (London)
- Controller/VP Finance: $150-200K (US), £90-130K (London)
- Operations Manager: $80-130K (US)
These are 2025-2026 ranges and they vary significantly by company stage, location, and market competition. Remote companies often pay between San Francisco and Midwest rates.
Revenue Per Employee: Your Efficiency Metric
Revenue per employee tells you if you're being efficient with headcount. Calculate it as: Annual Revenue / Number of Employees (in FTE).
Typical benchmarks:
- Seed stage: $100-150K ARR per employee
- Series A: $150-250K ARR per employee
- Series B: $250-400K ARR per employee
- Mature SaaS companies: $300-500K+ ARR per employee
A company at Series A with $2M ARR and 12 employees has $167K ARR per employee, which is reasonable. A company at Series A with $2M ARR and 20 employees has $100K ARR per employee, which suggests you've hired faster than you've grown revenue. This isn't necessarily bad---maybe you just closed a funding round and you're about to scale sales---but it's a red flag to monitor.
As you scale, revenue per employee should improve because you're not hiring proportionally with revenue growth. You're building leverage.
Hiring Plans: Who, When, Why
The best headcount models don't just list headcount. They detail each hire: who, when, why, and what impact they'll have.
Instead of "Add 3 engineers in Q3," the model should say: "Hire frontend engineer in Month 7 (currently bottleneck on web app), hire backend engineer in Month 9 (data processing performance), hire DevOps in Month 11 (infrastructure complexity)." Each hire has a rationale.
Similarly for sales: "Hire VP Sales in Month 6 (need experienced sales leader), hire SDR in Month 7 (process leads from product-led trial), hire AE in Month 10 (close larger deals from VP Sales relationships)."
This approach accomplishes three things. First, it forces you to think about hiring order and dependencies. Can't hire an AE before you have an SDR pipeline. Second, it lets you model the impact of each hire. When you hire the SDR, you increase pipeline. When you hire the AE, you increase close rate. Third, it surfaces when you're being unrealistic. If you're planning to hire 10 engineers in 4 months, you probably can't recruit and onboard that fast.
Accounting for Ramp Time
New employees don't reach full productivity immediately. Account for this in your model or you'll be surprised when hiring doesn't immediately solve your problems.
Engineering: Takes 1-2 months to ramp. A new engineer in month 1 is 30-40% productive. Month 2 is 60-70% productive. Month 3 onwards is 100% productive. Model this explicitly so you don't expect 100% contribution month 1.
Sales: Takes 3-4 months to ramp. Month 1: 20% productive (learning the product and pitch). Month 2: 40% productive (initial meetings). Month 3: 60% productive (starting to close deals). Month 4-5: 80-90% productive. Month 6 onwards: 100% productive. A new salesperson who costs $120K fully loaded will generate minimal revenue for the first 3 months. Budget for that or you'll miss cash flow targets.
Operations/Admin roles: Can ramp quickly, often 60-70% productive from day 1. These roles are less dependent on company-specific knowledge and more on execution.
The Hiring Budget vs. Revenue Growth Relationship
One of the most useful exercises is comparing your hiring plan to your revenue growth plan. If you're planning 15% MoM revenue growth but adding headcount that only costs 5% more per month, you're becoming more efficient (good). If you're planning 10% MoM growth but adding 20% more headcount cost, you're becoming less efficient (needs justification).
Most founders go through phases: first phase is underhiring (bottlenecked by capacity), second phase is overhiring (excited about growth, hire too many people). The overhead of managing a larger team reduces productivity. Smart hiring plans account for both the benefit (more people can do more work) and the cost (more people means more management overhead).
Try It Yourself: Calculate Your Headcount Costs
The Headcount & Salary Planner at /tools/#headcount lets you build your hiring plan by department. Input the number of people in engineering, sales/marketing, operations, and leadership for each month. Input salary by department. The tool calculates your fully-loaded cost (you select your geography or provide a multiplier), shows you total team cost over time, and tracks revenue per employee as you grow. You'll see how hiring impacts your burn and when new hires should improve your ratio.
Frequently Asked Questions
What's a realistic fully-loaded cost multiplier for salary?
In the US, multiply base salary by 1.25-1.35. This includes taxes, benefits, payroll processing, and recruiting fees for replacement staff. In the UK, multiply by 1.15-1.25. In France, multiply by 1.40-1.50 (much higher payroll tax). These are conservative. If you include office space allocation and equipment, the multiplier gets higher.
When should I hire engineers vs. sales vs. operations?
Early stage: hire engineers first. You need a product. Mid-stage: add sales and product. Late stage: add finance, operations, and specialized roles. Seed stage: 70% engineering, 20% sales/marketing, 10% operations. Series A: 40-50% engineering, 30-35% sales/marketing, 15-20% operations. Series B: more balanced across all three.
How do you account for ramp time when hiring?
A new engineer takes 1-2 months to ramp. A new salesperson takes 3-4 months to reach full productivity. Account for this by including only 30-40% of their contribution in month 1, 60-70% in month 2, 100% month 3+. This prevents you from modeling hockey stick growth immediately after hiring.
What's revenue per employee by stage?
Seed stage: $100-150K ARR per employee. Series A: $150-250K ARR per employee. Series B: $250-400K ARR per employee. These are rules of thumb. Companies that are engineering-heavy or have efficient GTM reach $300-400K per employee at Series A. Companies that are sales-heavy might only reach $100-150K.
Should I include contractors and part-time in headcount?
Yes, but clearly. Calculate FTE (full-time equivalent). Two part-time people at 50% each = 1 FTE. Contractors should be in your expense model but they do increase your cost of team.
Summary
Headcount is your largest expense and your most important resource. Get it right and you can scale efficiently. Get it wrong and runway collapses. Calculate loaded costs accurately by geography. Hire according to stage and need. Track revenue per employee to monitor efficiency. Plan hiring explicitly with rationale for each position. Account for ramp time so projections are realistic. The founders who raise capital most efficiently are not those who hire cheaply. They're those who hire strategically---the right people at the right time---and who track the efficiency of their hiring decisions. A CFO hire at Series A costs $180K fully loaded but might save you a bridge round because you fix financial management early. That's a good hire. Hiring a mid-level engineer when you need a staff engineer is a bad hire regardless of cost. Be strategic about headcount. It's the largest line item in your financial model and your biggest lever for building profitably.
Get the complete guide with all 16 chapters, exercises, and model templates.
Get Raise Ready - $9.99