"Headcount is growing faster than revenue"
Lemur Media · author: Dominik Dębski · updated 28.10.2026
Headcount outpaces revenue when each department hires based on its current workload and the company does not plan the number of positions from goals and productivity. The solution is a headcount plan linked to the revenue model, productivity metrics for each function and automation of work that today scales with the number of people.
What are the symptoms?
- Revenue per employee has been falling for several quarters.
- Every department reports a shortage of people, while long-established teams are not becoming more efficient.
- Personnel costs are growing faster than gross margin and push back the point of profitability.
- The number of coordination and support roles is growing relative to revenue-generating roles.
What are the causes?
- 01Hiring based on workloadRequests for new positions stem from a sense of overload, without analysis of the process or alternatives.
- 02No headcount modelThe headcount budget is not derived from the revenue model and functional productivity metrics.
- 03Processes scaled with peopleRepetitive work in customer service, finance and operations grows linearly with the number of clients.
| Headcount | Typical picture |
|---|---|
| 50–249 employees | After a funding round, the company hires ahead of planned growth, which arrives later than expected. |
| 250–999 employees | Support functions grow faster than sales and product, and overheads weigh on the EBITDA margin. |
What questions should the board ask?
- How has revenue per employee changed over the last eight quarters?
- Which functions increased headcount without improving their productivity?
- Which repetitive tasks can be automated before another position is created?
Which metrics should you check?
- Revenue per employee (full-time equivalent), quarter on quarter
- Personnel costs as a share of revenue and of gross margin
- Ratio of people in support functions to people in sales and product
Which mistakes should you avoid?
- A hiring freeze across all departments without analysing which functions generate revenue.
- Job cuts without changing the processes that forced the hiring in the first place.
How does the solution work?
Methods: Unit economics + AI Use Case Portfolio. The Lemur Compass sets the sequence of actions based on the company's growth phase, scale, business model and profitability.
- 01Productivity analysisProductivity metrics and their change over time are calculated for each function.
- 02Headcount modelThe headcount plan is derived from the revenue model and target productivity metrics.
- 03Hiring gateEvery request for a new position requires a process analysis and an assessment of alternatives, including automation.
- 04Automation of repetitive workThe most labour-intensive support processes get an automation plan, including the use of AI.
Where should you start?
Analysis of productivity and the headcount plan (2–3 weeks).