We were growing. MRR was climbing month over month. The chart in our board deck looked like the kind of line founders dream about drawing on a whiteboard.
Then someone divided that number by the number of people on the team.
The result was not a crisis. It was worse — a slow leak disguised as momentum.
A rising top line is easy to celebrate. It signals demand. It justifies the next hire. It makes fundraising conversations shorter.
But MRR alone says nothing about whether the team underneath it is getting more efficient or less. You can double revenue and triple headcount in the same year and feel great about it — right up until the margin conversation.
We had been adding people roughly in step with new customers. Support hires to cover onboarding. Engineers for the next integration. A second designer because the first one was buried. Each hire made sense in isolation. None looked expensive. All of them, together, were eating the gains.
Revenue per headcount made the pattern visible in a single number.
No grand initiative. One month, during a planning session, we pulled up two numbers side by side: MRR and total team size (including contractors). We divided. Then we looked at the same ratio from six months earlier.
MRR was up forty-something percent. Revenue per headcount was flat.
Every dollar of new revenue had cost us roughly a dollar of new payroll. We were running faster on a treadmill.
We started tracking the ratio monthly. Not as a target with a hard floor — that leads to underinvestment. As a diagnostic. A lens that forced a question before every hiring decision: will this person move the ratio up over the next two quarters, or down?
Before, the hiring question was: "Do we need this role?" After, it became: "What happens to revenue per headcount if we fill this role — and what happens if we don't?"
Some roles clearly improved the ratio. A second account manager would let us close deals sitting in the pipeline. That hire pays for itself in weeks.
Other roles were important but ratio-neutral. A security-focused engineer doesn't directly generate revenue, but losing customer trust is an existential cost. We still made those hires — we just stopped pretending they were growth hires.
The roles we stopped filling were the ones that existed to patch process problems. Instead of hiring a second person to handle a manual workflow, we asked why the workflow was manual. In two cases, a few weeks of engineering time replaced a full-time role we had been about to post.
We didn't freeze hiring. We hired more deliberately. The difference matters.
Revenue per headcount also reshaped how we thought about features. We had a backlog full of requests from large prospects, existing customers, and internal conviction.
When we filtered the backlog through the ratio lens, a pattern emerged. The features that improved revenue per headcount were almost always the ones that reduced manual work for our team — not just for customers. Self-serve configuration. Better defaults that cut support questions. Clearer error messages that stopped tickets before they started.
The features that hurt the ratio were scope-heavy builds aimed at a narrow segment. They required ongoing maintenance, pulled engineers into specialized work, and served a handful of accounts.
We didn't abandon those narrow features forever. We deferred them until the ratio gave us room. That is a different decision than killing them, and it felt different to the team.
Optimizing for revenue per headcount has a failure mode: underinvestment. If you treat the ratio as a ceiling you can never push through, you will starve the company of the people it needs to reach the next stage.
We avoided this by treating the metric as a trailing indicator, not a leading target. We checked it monthly. We used it to prompt questions. We never set a rule like "no hire unless the ratio goes up." Some quarters, the ratio dipped because we made a bet. The point was that we knew it was a bet, not an accident.
You probably already track MRR. You probably track burn rate. Revenue per headcount sits between those two numbers and tells you something neither one does alone: whether your team is scaling with your revenue or against it.
It takes thirty seconds to calculate. It requires no new tooling. And once you see it, you can't unsee the hiring decisions, roadmap choices, and process gaps it exposes.
We didn't cut ambition. We cut fog. The company that came out of that month of measurement was leaner in the right places and more confident about where to invest — because we finally knew what growth was costing us per person, not just per month.
Be the first to comment.
0 comments
Loading comments...