My SaaS company has 50 employees and $5M ARR. Are we overstaffed?

Diagnostics · Answered by Golden Section from more than 400 B2B software companies observed

The Golden Section answer

Probably, unless you can name what explains the gap. Fifty people on $5M ARR is $100,000 per employee, below the private SaaS median for companies at $1M to $3M ARR and well below the $152,000 to $177,000 median in the $5M to $10M band. Two things legitimately explain a gap like that: a meaningful services or implementation line that ARR does not count, and a deliberate investment the board approved with a dated return. If neither applies, the extra headcount is probably sitting in seats nobody owns or in a sales team ahead of its efficiency. Do not cut on the ratio alone. Draw the accountability chart, compute revenue per employee by department, and rebuild the budget from initiatives before deciding who stays.

The decision rule

A company well below the median revenue per employee for its size is overstaffed until it can show otherwise, with services revenue, an approved investment plan, or a burn multiple under control. Fix it through the accountability chart and the budget, one seat at a time, rather than a percentage cut.

Usually ready when

  • Every seat on the accountability chart has one name and a few outcomes
  • Revenue per employee is computed on both ARR and total annual revenue

Probably too early when

  • Cuts are being sized to a benchmark before anyone knows which seats produce what

The numbers

MetricValueWhat it meansSource
ARR per employee at 50 people and $5M ARR$100,000$5M divided by 50 FTEsthe same ratio applies at 100 people and $10M ARRIllustrativeArithmetic on the question
ARR per employee, $5M to $10M ARR$152,295 equity-backed; $177,240 bootstrappedmedian ARR per FTE2026 survey of more than 1,000 private SaaS companies; $1M to $3M median is $109,644External benchmarkSaaS Capital, 2026 Revenue Per Employee Benchmarks for Private SaaS Companies
Burn multipleunder 1x efficientnet burn divided by net new ARR, same periodGolden Section benchmark for B2B SaaSGolden Section, publishedThe Balanced Path
Burn multiple bands1x to 1.5x deserves a look; above 1.5x structuralnet burn divided by net new ARR, same perioda top-level view; the question underneath is sales efficiencyGolden Section operating viewGolden Section operating view
Company priorities completedtarget 80%share of quarterly priorities finished on timetwo quarters below 80% points to a capacity conversation, not a speech about accountabilityGolden Section playbookExecution Operating System

Why

Overstaffing rarely comes from one bad decision. It accumulates. Each department asks for help, each request sounds reasonable, and nobody sums the requests against the revenue they are supposed to produce. The result is a company where more people are doing less, because work routes around gaps in ownership and every issue becomes a negotiation about whose problem it is. That is why the fix starts with the accountability chart, not the headcount report.

The ratio matters because payroll is most of the cost base. At $100,000 per employee, fully loaded payroll can approach total revenue, which makes a burn multiple under 1x, the level we call efficient, hard to reach; every quarter above 1.5x consumes runway and dilutes the founder. But cutting to a benchmark is the wrong move too. It removes the seats easiest to cut rather than the ones producing least, and strong people read cuts without a structure as a leader who does not know what is wrong. Rebuild the budget from initiatives, find the seats with no initiative behind them, and decide from there.

Illustrative scenario

A company with 50 people and $5M ARR also bills $1.5M a year in implementation services, so total annual revenue per employee is $130,000. Mapping the accountability chart shows 14 people in services, which the services margin supports, and 17 in sales and marketing against a sales efficiency ratio of 1.6. The leadership team pauses sales hiring, consolidates two overlapping marketing roles, and moves one account executive into a customer success seat that had no owner. Headcount falls to 46 through attrition and two role eliminations, and the burn multiple improves over the next three quarters. All figures are illustrative.

By stage

$10M ARR

100 employees at $10M ARR is the same $100,000 per employee, and the same answer applies. The gap to the median is larger in absolute terms, roughly 35 to 45 people at the benchmark, so the review should be done department by department.

When this does not hold

A company that has just raised to fund a specific product or market expansion, with a board-approved plan and dated milestones, can run well below the median for a planned period. A heavy services mix changes the right comparison to total annual revenue per employee.

What to do on Monday

  1. Freeze open requisitions until the accountability chart is drawn
  2. Compute revenue per employee on ARR and on total annual revenue for each department
  3. Measure your burn multiple for the last four quarters
  4. List every seat without a strategic initiative or a single owner
  5. Rebuild next year's budget from initiatives and compare the headcount it implies

Mistakes founders make here

From the Golden Section mistakes list, each paired with the play that prevents it.

Mistake 145: Hiring isn’t enterprise value creating

The headcount was added on the assumption that more people would create more value, which is the assumption to test.

Mistake 114: Accepting the phrase “we’re too thinly staffed”

Every team will say it is too thinly staffed, including in an overstaffed company, so the complaint cannot decide the review.

Mistake 108: Fuzzy organizational chart

Overlapping responsibilities are where overstaffing hides, because two people in a seat means nobody owns it.

Mistake 147: Avoiding tough but proactive decision making

Delaying the decision keeps burning cash on seats you already suspect are not producing.

Plays we would run

In the order we would run them. Each is on its own page, most with a free Excel template.

Execution Operating System

Draws the accountability chart with one name per seat, which exposes duplicated and unowned roles.

Budget Creation

Rebuilds headcount from initiatives with an owner and a defended line for every department.

Dev Org Chart

Checks whether engineering roles map to a clear structure or have grown without one.

Sales Metrics by FTE/Role/Team

Shows whether each sales seat is producing against its metrics before you add or keep capacity.

Hiring A Players (Topgrading)

Ensures the seats you keep or refill are held by people scored against evidence.

Executive plays The executive plays hold the operating system, budget and hiring discipline that decide team size.

Questions this page answers

How do I know if my SaaS company is overstaffed?

Three signals together. Revenue per employee well below the median for your ARR band, a burn multiple above 1.5x without a funded plan to change it, and seats on the accountability chart that have no owner or no initiative. Any one alone can have an explanation; all three rarely do.

My SaaS company has 100 employees and $10M ARR. Are we overstaffed?

Likely, for the same reason: $100,000 of ARR per employee sits well below the $152,000 to $177,000 median for the $5M to $10M band. Check services revenue first, then work through the accountability chart and budget department by department.

Should I do a layoff?

Only after the chart and the budget tell you which seats are not producing, and only once. Repeated small cuts cost more trust than one clear decision. Often attrition, a hiring freeze and a few role eliminations close most of the gap.

Funding the next stage

Raising to carry excess headcount funds the problem, and we pass on burn profiles with no plan to change them. Once the team matches the plan, equity can fund a real structural change, and we would rather see the fix first.

Growth equity →

Reviewed by Dougal Cameron, CEO & Co-Founder on 2026-09-23. Golden Section observations are labeled separately from external benchmarks and illustrative arithmetic.