Headcount Planning by Stage: From Pre-Seed to Series A, What is Realistic
Every hire must map to a milestone. Fully-loaded cost is 1.25-1.50x base salary. Payroll should not exceed 70% of monthly burn. Plan for 18-24 months between raises. Cross-border hiring adds significant complexity through different burden rates, currency risk, and termination costs.
Author: Yanni Papoutsi · Fractional VP of Finance and Strategy for early-stage startups · Author, Raise Ready
Published: 2025-06-15 · Last updated: 2025-06-15
Reading time: ~10 min
The Headcount Trap
One of the most common mistakes in startup financial models is unrealistic headcount planning. Founders either hire too fast and burn through capital, or they're too conservative and can't execute on their vision. The right answer depends on your stage, your capital, and what milestones you need to hit.
Most investor-backed startups plan for 18-24 months of runway between raises. If you're raising a Series A at $2 million and planning to last 24 months, your monthly burn can't exceed $83,000. If payroll is 65% of burn (which is typical), that's about $54,000 per month for headcount costs. That buys you roughly 2-3 full-time employees at market rates, plus a founder salary. This constraint is where most financial models break down.
Five Rules for Every Stage
Rule 1: Map Every Hire to a Specific Milestone
Never add headcount just because you have cash. Every hire should directly support a near-term milestone. If your milestone is "launch product beta by month 6," you need a developer. If your milestone is "close first 10 customers," you need a salesperson. If you're hiring a CFO when you have $500K in runway and haven't closed a Series A yet, something is wrong.
Document this for every hire: "Hire [role] in month [X] to support milestone [Y]." This forces you to be specific about why you need someone and when.
Rule 2: Founders Do Everything First
You don't hire a VP of Sales in month 2. You do sales in month 2. You don't hire a product manager in month 1. You define the product in month 1. Founders are generalists. Lean into that. Hire specialists only when you've proven the function works and you're bottlenecked.
The exception: if you're hiring a technical co-founder to balance a non-technical founder, that's appropriate early. But hiring a head of engineering when you're a solo engineer is premature.
Rule 3: Budget 1.25-1.50x Base Salary as Fully-Loaded Cost
This is the most commonly missed cost. If you hire a developer at $120,000 base salary, your actual cost is $150,000-180,000. The additional 25-50% covers taxes, benefits, equipment, office space, and recruiting/hiring costs amortized across the hire.
For international hires, the multiplier is often higher (1.3-1.6x) due to employer payroll taxes in some countries, visa sponsorship, and accounting complexity. Build this into your model explicitly.
Rule 4: Keep Payroll Under 70% of Monthly Burn
If you're burning $100,000 per month, payroll should not exceed $70,000. This gives you room for rent, software, infrastructure, and other operating costs. If payroll creeps above 70%, you're making it impossible to operate.
Founders are notorious for underpaying themselves and overpaying others, which distorts this metric. Be disciplined. If you're burning $100K/month, you can afford roughly three employees at $80K total fully-loaded (including founder salary) or two employees at market rate.
Rule 5: Plan for 18-24 Month Runway
This is the north star. If you're raising $2 million with a monthly burn of $100,000, you have a 20-month runway. That's right in the middle of the 18-24 month window. If you're running a 12-month burn plan, you're taking on too much risk. If you're conservatively planning for 24 months, you have more flexibility.
Headcount decisions ripple across this entire runway. Hiring someone in month 3 costs you roughly 18 months of salary if you maintain that position until the next raise. That's a $250,000+ commitment hidden in a single decision.
The $500K Pre-Seed Scenario
Runway: 20 months at $25K/month burn
Payroll budget: $17,500/month
Typical headcount: 2-3 people total (including founders)
At pre-seed, you should be largely bootstrapped founders with one junior hire. If you have two founders, neither is taking salary, and you hire a developer at $80K (fully-loaded), that's roughly $6,600/month for the first employee and headcount stays within budget. You're not hiring sales, operations, or product people yet.
The $1.5M Seed Scenario
Runway: 20 months at $75K/month burn
Payroll budget: ~$52,500/month
Typical headcount: 4-5 people (founders + 2-3 employees)
At seed stage, you can afford two solid employees. Typical hires: a senior developer and a customer success person. You might have one founder still taking partial salary. You still don't hire an operations person or CFO.
The $2.5M Series A Scenario
Runway: 20 months at $125K/month burn
Payroll budget: ~$87,500/month
Typical headcount: 6-8 people (founders + 4-6 employees)
At Series A, you have room to build a small team. Typical hires: developer(s), designer, operations person, customer success, and potentially a sales hire. This is where you start bringing in functional expertise. Founders are still hands-on but not doing everything.
The $5M Series A Scenario
Runway: 20 months at $250K/month burn
Payroll budget: ~$175K/month
Typical headcount: 12-15 people (founders + 10-13 employees)
At a larger Series A, you can build real functional teams. Engineering (4-5 people), product/design (2-3), operations/finance (2), sales/customer success (2-3), marketing (1-2). This is where organizations start forming and you hire functional heads.
The Hiring Timeline Problem
Most founders model hiring as happening in month 1. Reality is messier. In month 1, you decide to hire. In month 2, you recruit and interview. In month 3, the person starts and ramps. So that person isn't productive until month 4. Meanwhile, you're paying them from month 3 on. This creates a lag in payroll versus productivity.
More importantly, it compresses your runway. If you plan for 20 months of runway and frontload hiring to months 1-6, you might burn through cash faster than modeled because you're paying for people who aren't yet productive.
Practical solution: model hiring as happening 2-3 months before you need productivity. If you need someone to be productive in month 6, hire them in month 3 or 4.
The International Hiring Complexity
Many startups hire engineers remotely from cheaper labor markets. This seems like a money-saver (you pay $60K instead of $120K), but the fully-loaded cost is often higher than expected due to:
- Employer payroll taxes: Some countries have 30-40% employer social contributions. A $60K employee becomes $78-84K fully-loaded.
- Currency risk: If you hire a developer in India at 50 lakhs INR (~$6,000/month), you're exposed to INR depreciation. Over two years, this could add 10-15% to actual costs.
- Time zone coordination: You lose synchronous working time. This tax is real but hard to quantify in the model.
- Visa sponsorship: If you ever want to bring someone to your office, visa sponsorship costs $5-10K per person.
- Termination complexity: Firing someone in a different country is legally complex and expensive.
International hiring can still make sense, but use a 1.4-1.6x multiplier instead of assuming dramatic savings.
Building Your Headcount Model
Start with revenue milestones and work backward. If your target is $1 million ARR by month 24 (typical Series A goal), what team do you need to build that? If each salesperson can generate $300K in ARR and you need 3-4 salespeople, you need a VP Sales (or founder doing sales) plus salespeople. That's 4-5 sales-related roles. Add engineering, product, operations, and you're at 12-15 people.
Then check: can your $2.5M raise support this team for 24 months? If not, your revenue model is too aggressive or you need to raise more. This constraint forces honesty into your financial model.
Frequently Asked Questions
Contractors cost 25-30% more on a per-hour basis but have no benefits or commitment. They make sense for specific projects (design, legal, accounting) but are expensive for core team members who are full-time. For a series A startup, you should be mostly employees. Contractors + employees typically costs 1.5-2x what employees-only costs.
Yes, but it's painful. Most founders delay cuts too long because they're optimistic about fundraising. Best practice: if you're 60% through your runway and only 40% to next milestone, make cuts now instead of waiting. Cutting two people removes 25-30% of burn and extends runway by 8-10 months. It's better than running out of cash.
Founders should take a salary proportional to market rate for their role, adjusted for stage. At pre-seed, $60-80K. At seed, $80-100K. At Series A, $100-120K. Taking no salary looks good initially but creates problems: you lose financial credibility (can't borrow money), you drain personal savings, and you're misaligning founder incentives (pay me or I leave). Model founder salaries explicitly.
Yes. You'll eliminate lease costs but still have equipment, internet stipends, and occasional team offsite costs (add $5-10K per year for this). Remote hiring also lets you access cheaper labor markets, but adds the complexity mentioned above. Net savings are roughly 20-30% on location costs, but don't assume you can reduce the 1.25-1.50x salary multiplier significantly.
Get the complete guide with all 16 chapters, exercises, and model templates.
Get Raise Ready - $9.99