Headcount Planning Calculator
Plan up to 25 hires across 12 quarters, see fully-loaded cost per role, the runway-cliff month, and a per-hire affordability verdict — plus a startup org chart of the plan. No signup.
Last reviewed: May 2026
18+ months of runway after the plan. Disciplined trajectory — focus on growth.
Planned hires (3/25)
Startup org chart (planned)
SVG view of the planned roles grouped by function. Reporting lines inferred from role title.
What-if simulator
Reverse calculator
Scenarios — save & compare
No saved scenarios. Save the current plan, modify, save another, then compare.
Advisor read
- • Weakest dimension: Sequencing (F). 0 revenue-generating hires before month 12 vs 3 cost-only. Healthy sequencing keeps the ratio at 0.5 or better so revenue catches up to burn.
- • No cliff inside the 48-month horizon — focus on growth, not cuts.
- • All hires fit the target — keep the discipline and revisit after the next milestone.
Export
What is headcount planning?
Headcount planning is the discipline of mapping the next 12–24 months of hires against cash, MRR, and a runway target — turning a wishlist into a model that says how many of the planned roles you can actually afford. The unit of work is a row: role, region, base salary, start month, and employment type. The unit of output is a number: months of runway after every planned hire is on the payroll.
Done well, headcount planning catches the hire that breaks the plan three quarters before it would have. Done badly, it produces a six-page deck and a bridge round. The calculator above runs the model live: every row mutates the runway-cliff chart and updates a 6-dimension report card so the plan is never a static document.
How to build a startup hiring plan in 6 steps
The six steps below are the same ones the calculator runs in the background — except you can lean on the engine to do the arithmetic. They form a workable headcount planning template, useful as the input to a board headcount slide or a startup hiring plan calculator session before fundraise. The same flow answers how to plan startup headcount whether you ship one hire per quarter on a bootstrap hiring plan or 25 hires across 24 months on a hypergrowth plan.
- Establish the cash baseline. Cash on hand, current MRR, monthly MRR growth, gross margin, and a runway target. 12 months is the conventional minimum for early stage; 18 months is the post-2022 default for Series A+ plans.
- List intended hires by quarter. Most plans break above 10 hires inside 4 quarters because the spreadsheet stops modeling cash impact correctly. Cap individual rows at 25 to keep the simulation tractable.
- Apply the regional fully-loaded multiplier. SF/NYC ≈ 1.42×, remote-US ≈ 1.38×, Berlin ≈ 1.32×, Warsaw ≈ 1.28×, Manila ≈ 1.20×. The multiplier captures employer payroll tax, benefits, equity amortization, and tooling.
- Layer in recruiter fees and ramp loss. Recruiter fees of 18–25% of base on agency hires; standard ramp curve of 60% / 40% / 25% / 15% / 8% productivity drag in months 1–6.
- Project month-by-month cash and MRR. The simulation runs MRR forward geometrically at
(1 + growth_rate)per month and adds AE quota contributions after their ramp. Net burn = burn − (MRR × gross margin). Runway is the linear-interpolated month at which cash crosses zero. - Score affordability per row. Any row whose presence pushes runway under your target by itself earns a Breaks Runway verdict; the rest land in Affordable or Tight.
The canonical SaaS team structure by stage
SaaS team structure follows a predictable shape as headcount scales. Early-stage startup teams over-index on engineering because product is the bottleneck; mid-stage plans rebalance toward go-to-market because revenue is the bottleneck; growth-stage plans add customer success and operations as scale becomes the bottleneck. The benchmark mixes below match the targets used by the Function Balance dimension inside this tool:
| Stage | Eng | Sales | Marketing | CS | Ops | Leadership |
|---|---|---|---|---|---|---|
| Seed (3–6 hires) | 55% | 15% | 10% | 10% | 5% | 5% |
| Series A (7–15) | 45% | 20% | 10% | 10% | 10% | 5% |
| Series B+ (16+) | 40% | 25% | 10% | 15% | 5% | 5% |
Use these as a startup team and startup staffing reference, not a rule. A product-led growth company with no outbound motion will run hotter on engineering and lighter on sales than the table suggests; a sales-led enterprise SaaS company at Series A will look closer to 35/30/10/15/5/5. The Function Balance dimension grades the gap between your plan's mix and the matching stage row, then surfaces the biggest deviation in the report card narrative.
How to make a startup org chart
Group every planned role by function — Engineering, Sales, Marketing, Customer Success, Operations, Leadership — then stack them vertically inside each column with the most-senior role at the top. That is the startup org chart pattern and it is what the SVG visualizer above produces directly from your hire rows. Each node is a planned role with its label, start month, and region; the node color matches its function (purple = engineering, green = sales, orange = marketing, cyan = customer success, violet = operations, gold = leadership).
At Seed there are usually two layers — founders + ICs. At Series A a managerial layer appears (Engineering Manager, Sales Manager, Head of Marketing). At Series B and later, a VP / C-suite layer is added on top. The visualizer infers the reporting line from each role title (IC → Manager → VP → C-suite), so the same component works as a startup org chart template across stages — no manual reporting-line wiring required.
The org chart is not just decorative. Showing the planned hires as a tree surfaces three problems a flat list hides: span-of-control gaps (8 ICs and zero managers will break by hire 12), missing functions (no head of marketing across 15 hires), and seniority inversions (a junior engineer scheduled before the engineering manager who would onboard them). Open the Exec Deck overlay with the [E] key to drop the chart straight into a board slide.
Fully-loaded cost: why the multiplier matters for hiring plans
Fully-loaded cost is base salary plus every dollar a company spends to keep one person employed: employer payroll tax, benefits, retirement match, equity amortization, recruiter fee, ramp loss, tools and software, office allocation, and training budget. Across SaaS hires the multiplier typically lands between 1.20× and 1.50× of base — meaning a $140K base engineer in SF actually costs $200K+ per year on the income statement.
The regional multipliers built into this calculator: SF and NYC at 1.42×, remote-US at 1.38×, Toronto and London at 1.30×, Berlin at 1.32×, Warsaw at 1.28×, Manila at 1.20×. Those numbers reflect a blended view — US regions carry higher employer payroll tax, European regions carry national-healthcare offset on benefits, and emerging-market regions carry lower equity expectations. The companion Fully-Loaded Employee Cost Calculator breaks out every burden line per role; this tool uses the multiplier shorthand so the headcount plan stays readable.
Two regional swaps consistently produce six-figure annual savings without losing output: SF engineering → Warsaw or Lisbon (≈ 0.55× of SF base × 0.90× multiplier ≈ 50% loaded cost), and US-based customer support → Manila (≈ 0.30× of US base, 1.20× multiplier ≈ 25% loaded cost). What-If > offshore-shift quantifies this for your specific plan.
The runway-cliff: spotting the hire that breaks the plan
The runway-cliff is the month at which projected cash crosses zero. It is the most-actionable single number in any hiring plan because it answers a binary question — do we make it to the next milestone? — without ambiguity. The chart above renders cash on hand month-by-month for 48 months; the red dashed vertical is the cliff. If it lands inside the plan window, the plan is unfundable as drawn.
The hire that breaks the plan is rarely the most expensive one. It is usually the one that lands in the wrong quarter. A $260K VP Engineering at month 10 in a $1.5M-cash plan tips runway from 14 months to 7 — Risky zone, board-uncomfortable. The same hire deferred to month 16, after a presumed bridge raise or revenue milestone, might fit comfortably. The Reverse Calculator (mode: latest-start-for-hire) binary-searches the latest start month that keeps your runway target intact.
The five zone labels — Comfortable (≥18 months), Healthy (12–17), Tight (9–11), Risky (6–8), Breaks (under 6) — match the conventional thresholds for board-acceptable runway after a plan. Comfortable and Healthy plans focus on growth; Tight plans defer one hire; Risky plans require a bridge or a structural cut; Breaks plans cannot ship.
What makes a hiring plan "affordable"?
Headcount affordability is not about whether the plan fits the cash balance. It is about whether the plan fits the cash balance after the runway target is honored. The verdict logic in this calculator: if the plan's runway-after lands at or above your target, every hire is Affordable. If it lands between 75% and 100% of target, hires are Tight. Below 75%, hires that individually push runway under target by themselves earn a Breaks Runway flag. That is how the engine answers how many employees can a startup afford in a single screen instead of three spreadsheet tabs.
Three factors most often cause a plan to fail this test even when total cash > total cost: front-loaded start months (every hire starts in the first 6 months), no offshore mix (every hire in SF or NYC at 1.42× multiplier), and zero quota-carrying hires before month 12 (burn grows; revenue does not). The 6-dimension report card surfaces each of these as a graded dimension — Sequencing Quality, Regional Diversification, Function Balance — so the diagnosis lands in one screen.
Headcount plan example: a Series-A 8-hire breakdown
A representative headcount plan example, available as the Series A preset above: $8M cash, $100K MRR, 8% monthly growth, 78% gross margin, 18-month runway target. Eight planned hires across the first nine months — one Staff Engineer (SF, M0), two Senior Engineers (remote-US, M1 and M3), two AEs (NYC, M2 and M4), one SDR (Austin, M5), one CS Manager (remote-US, M6), one Head of Marketing (remote-US, M8).
Loaded annual burn from the eight hires lands near $2.4M with a blended multiplier of about 1.40×. Adding $38K/mo of fixed opex and the existing MRR contribution, the plan keeps the runway after plan above 18 months — Comfortable zone. Sequencing Quality scores well because three quota-carrying roles (2 AEs + 1 SDR) start before the cost-only hires concentrate. Function Balance is B+ because engineering still runs slightly hot for Series A; deferring the second Senior Engineer by one quarter or swapping it for a regional shift to Warsaw improves the grade without reducing output.
That is the difference a series a hiring plan with cash discipline produces. The same eight hires shipped front-loaded in months 0–4 instead of staggered across nine months produces a Tight zone verdict and a B- composite grade — the cliff-ladder shape of the cash chart is visible at a glance, and Reverse Calculator (mode: latest-start-for-hire) returns a 4–6 month deferral as the cheapest fix.
Frequently Asked Questions
What is a startup hiring plan?
A startup hiring plan is a quarter-by-quarter list of the roles a founder intends to hire over the next 12–24 months, paired with the cash and revenue assumptions that determine which hires are affordable. A useful plan has six fields per row — role, region, base salary, start month, employment type (FTE or contractor), and recruiter fee — and a single output: how many months of runway remain after every hire is on the books. Without that runway link, a hiring plan is wishful thinking.
How do you build a headcount plan?
Start with three numbers: cash on hand, current MRR, and your runway target (12 months for early stage, 18 for Series A+). List the next 12 months of intended hires with role, region, and a realistic start month. Apply a regional fully-loaded multiplier — 1.42× for SF/NYC, 1.32× for Berlin, 1.28× for Warsaw, 1.20× for Manila — to get the true annual cost per hire, then layer in recruiter fees (typically 18–25% of base) and ramp-loss for the first three months. The plan is a headcount planning template only when every row produces a runway-impact number.
How many employees can a Seed-stage startup afford?
A standard $1.5M seed round with $20K MRR and 12% monthly growth supports about three hires inside the first six months — typically two mid-engineers and one head of growth — while keeping 12+ months of runway. The Seed-3-in-6mo preset in this calculator models that exact shape: total annual burn lands near $850K loaded, runway after the plan stays in the Healthy zone, and the plan grades B or higher on the report card. Bootstrapped solo founders on $200K cash usually pace one hire per quarter to keep runway above the cliff.
What's the canonical SaaS team structure by stage?
Industry SaaS team structure benchmarks land near these mixes: Seed (3–6 hires) ≈ 55% engineering, 15% sales, 10% marketing, 10% CS, 5% ops, 5% leadership. Series A (7–15 hires) shifts to 45/20/10/10/10/5. Series B+ (16+ hires) settles at 40/25/10/15/5/5 as go-to-market scales. The Function Balance dimension in this tool scores your plan against the matching stage mix and flags the biggest deviation in the report card narrative.
What is a startup org structure and how do you map it?
A startup org structure is the map of who reports to whom, grouped by function (Engineering, Sales, Marketing, CS, Operations, Leadership). At Seed it is usually two layers — founders + ICs. At Series A a managerial layer appears (Engineering Manager, Sales Manager, Head of Marketing). The org-chart visualizer in this tool renders your planned roles as a startup org structure template grouped by function, with reporting lines inferred from each role title (IC / Manager / VP / C-suite).
How do you make a startup org chart?
Group every planned role by its function — Engineering, Sales, Marketing, Customer Success, Operations, Leadership — then stack roles vertically inside each column with the most-senior at the top. The startup org chart visualizer here does exactly that: each planned hire becomes a node colored by function, labeled with role, start month, and region. It works as a startup org chart template that updates live as you reschedule hires or change the regional mix.
What ratio of engineers to AEs should a Series-A startup have?
A common engineer-to-AE ratio at Series A is between 1.5:1 and 3:1 — fewer engineers per AE if the product is product-led, more if engineering is the moat. Below 1:1 the GTM motion can outpace product development; above 4:1 the company is funding engineering output that sales cannot monetize. The Series A preset in this calculator ships eight hires at a 3:1 ratio (3 eng + 2 AEs + 1 SDR + 1 CSM + 1 marketing-lead), which scores B+ on Function Balance.
What's the difference between a hiring plan and a headcount plan?
A hiring plan is the list of intended hires (who, when, where). A headcount plan is the same list joined to cash and revenue, so each row produces a number — months of runway after this hire, dollars of fully-loaded burn, ARR contribution if quota-carrying. Headcount planning is the discipline; the hiring plan is the artifact. This calculator is built as a headcount plan: every row mutates the runway-cliff chart in real time so the plan stops being a wishlist and starts being a financial model.
How does this calculator handle ramp loss?
Ramp loss is the dollar value of the months a new hire is paid but not fully productive. The standard ramp curve here applies productivity drags of 60% / 40% / 25% / 15% / 8% / 0% across months one through six — meaning a $200K loaded engineer who is 40% productive in month two costs about $6.7K of extra burn that month over their steady-state output. AE-style quota-carrying roles use the same curve in reverse: an AE produces zero new MRR until ramp ends, then ramps up to their full $600K/yr quota equivalent.
How do you decide which planned hires to defer?
Look at the per-hire verdict column. Any hire flagged ❌ Breaks Runway should be deferred or removed first. Among the remaining, prefer to defer cost-only roles (engineering, ops) over revenue-generating ones (AE, SDR), since revenue hires shrink the gap between burn growth and MRR growth. The Reverse Calculator inside this tool answers the question quantitatively: given a runway target, what is the latest start month for hire #N that still keeps the plan affordable?