A belief that circulates in leadership meetings: a company with higher revenue per employee is a better-run company. Journalists like it. Investors sometimes use it as a shortcut. It is also wrong often enough that you should treat it as a starting question, not a verdict.
The calculation, which is the easy part
Take a company with revenue of ₹2,400 crore, 6,000 employees and total people cost of ₹720 crore for the year.
Revenue per employee = ₹2,400 crore ÷ 6,000. Convert first: ₹2,400 crore is 24,000,000,000 rupees (2,400 × 1 crore, where one crore is 10 million), and dividing by 6,000 gives ₹40,00,000, or ₹40 lakh per employee.
People cost as a percentage of revenue = 720 ÷ 2,400 = 0.30, so 30%. Per employee, that is ₹12 lakh of cost against ₹40 lakh of revenue.
Two numbers, and each answers a different question. The first asks how much business the average head carries. The second asks how much of every rupee earned is spent on people. They can move in opposite directions, which is the first place the belief starts to crack.
Where “higher is better” breaks
Industry decides the baseline. A software product company, a cement plant, a retail chain and a BPO have completely different relationships between people and revenue. A trading business with thin staffing can show enormous revenue per head simply because it moves a lot of goods at low margin. Comparing it with a consultancy proves nothing. Compare within your sector, and ideally with firms of similar business model.
The ratio is silent on contractors. Suppose two firms each earn ₹1,000 crore. One employs 2,000 people directly. The other employs 800 and engages 1,500 contract workers through vendors. The second firm looks far more productive per employee. It has just moved the headcount off its payroll. If you use this ratio, count the people actually doing the work, or at least note how many are outside the count.
Revenue itself can be flattered. A price rise, a one-time contract, a pass-through of materials cost or an acquisition late in the year will lift revenue without anyone becoming more productive. And headcount is usually year-end or average? Use the same definition every time. A company that grew from 4,000 to 6,000 employees during the year and divides by the closing number understates the load each person carried.
Finally, high can mean thin. If revenue per employee climbs because the company froze hiring while workloads rose, the number looks good for a while and the attrition shows up a year later.
What the two ratios say together
Look at them as a pair across three years.
- Revenue per employee rising, people cost share flat: the company is growing output without paying proportionately more. Healthy if quality holds.
- Revenue per employee rising, people cost share rising: pay is growing even faster than productivity. Perhaps a talent shortage, perhaps a generous raise cycle, perhaps senior hires. Worth asking which.
- Revenue per employee falling, people cost share rising: capacity was added ahead of demand, or demand fell. A hiring plan problem, or a revenue problem presented as an HR one.
A fourth number helps: profit per employee. A company can raise revenue per head and still lose money on every extra rupee.
The HR-to-employee ratio, a close cousin
The same suspicion applies to another ratio: a company with 1,200 employees and 15 people in HR. That is 15 ÷ 1,200 = 0.0125, or 1.25 HR staff per 100 employees; put the other way, one HR person for every 80 employees. Is that reasonable? There is no universal answer. Published benchmarks differ by survey, industry and company size, and the figure moves with how much work is outsourced (payroll, recruitment, admin), how much is automated, and whether the organisation has factories with heavy compliance load or an office-based workforce. A 1:80 ratio could be lean in a services firm and stretched in a plant with unionised labour and dozens of contract vendors. Use it as a prompt to check workloads, not as a target.
How I would present it
Show a three-year trend, not a single year. Show it next to two or three named peers if public data exists. State what headcount definition you used. Mention contractors. And attach one sentence about what the movement means for decisions: hiring pace, pay review, automation spend.
Used this way the ratio earns its place on a dashboard. Used as a scoreboard, it rewards whoever has the best outsourcing agreement.
Figures and names in the examples are illustrative.
Leave a Reply