Revenue per Employee: Sizing Your Ops Headcount

Take trailing twelve-month revenue divided by full-time equivalent headcount, counting contractors and fractional staff as a fraction of a full role based on hours committed, not as zero. Companies that exclude contractors from the denominator to make the ratio look better are lying to themselves about their actual cost structure, and the ratio stops meaning anything the moment the calculation changes between reviews.

Track it quarterly on a trailing basis rather than a single month, since a single month is too noisy, especially for a business with any seasonality, to draw a real conclusion from.

Calculate the ratio the same way every time:

1. Use trailing twelve-month revenue as the numerator, not a single month or a forecast.
2. Divide by full-time equivalent headcount, counting contractors and fractional staff as a fraction of a full role based on committed hours.
3. Record the result each quarter on a trailing basis, not from a single noisy month.
4. Compare it with your own trend over four to six quarters rather than an outside number.

The ratio is far more useful compared against your own history than against a generic industry figure, since business model, margin structure, and stage all shift what a reasonable number looks like more than industry label does. A software company and a services firm with the same revenue can have wildly different reasonable ratios, and neither is wrong.

Watch the direction of your own trend over four to six quarters. A ratio that's falling quarter over quarter while headcount grows faster than revenue is worth investigating, even if the absolute number still looks fine compared with anyone else's.

A falling ratio doesn't automatically mean you're overstaffed. It could mean you're investing ahead of revenue on purpose, building out a function before it's needed, which is a legitimate strategic choice as long as it's a deliberate choice and not a drift nobody noticed. The ratio is a prompt to ask why, not an automatic verdict.

What it should trigger is a specific conversation: which function grew headcount, was that growth tied to a documented plan, and is the expected revenue from that investment still reasonably on track. If nobody in the room can answer those three questions clearly, the drift probably wasn't intentional in the first place.

For example, suppose revenue per employee dips for two quarters after you hired a customer support team ahead of a planned product launch. The three questions apply directly: support headcount grew, the hiring was tied to a written launch plan, and the launch is still on schedule. In that case the ratio is doing its job by flagging an intentional investment, and the right response is to keep watching, not to freeze hiring. If the hires had no plan behind them, the same dip would point to drift. Write down the answer each quarter so the reasoning is on record.

The cost side of this ratio is often underestimated because operations and general management pay spans an unusually wide range. National wage data for this occupation runs from roughly $50,090 at the low end past $253,390 at the high end, a spread wide enough that two companies with the same headcount count can carry very different actual costs depending on seniority mix¹. Before treating headcount count alone as your efficiency signal, check whether the mix of seniority behind that count has shifted too.

The failure mode to watch for is freezing hiring in a function purely to protect the ratio, even when the function is genuinely understaffed relative to the work it's carrying. A tool like Toggl showing sustained overtime hours in a team is a better signal that headcount is actually too low than the ratio alone, and Rippling's headcount and org data makes it easier to see whether growth is concentrated in one function or spread evenly, which changes what the right response is.

If the ratio is being cited in a board meeting more often than it's being investigated internally, that's usually a sign it has become a talking point instead of a working management tool, and it's worth pulling it back into an actual operating conversation.