Revenue per Employee: Measuring Productivity from Quarterly Results

Every quarter, an IT company tells us two things it is quietly proud or nervous about: how much it billed and how many people it has on the rolls. Put those two side by side and you get revenue per employee, one of the simplest productivity checks you can run on a set of quarterly results. It takes a calculator and about thirty seconds. Reading it properly takes a little longer.

This guide walks through the formula, the traps in using quarterly numbers, and a worked example built from a real disclosure, Wipro’s datasheet for the quarter ended September 30, 2026. If you’re new to results season, our guide on how to analyse quarterly results of a company is a good place to start before this one.

What revenue per employee actually measures

The definition is plain. Investopedia describes it as a company’s total revenue divided by its current number of employees, a ratio that roughly measures how much money each employee generates for the firm. Note the word “roughly”. It’s a blunt tool. It doesn’t tell you whether those employees are profitable, only how much top line sits on each head.

The formula:

Revenue per employee = Revenue for the period ÷ Number of employees

A higher number generally points to a leaner, more productive organisation. A falling number can mean the company hired ahead of demand, lost pricing, or saw clients cut back while the bench stayed full. Which of those it is, the ratio alone won’t say. That’s where the rest of the results come in.

Some analysts swap revenue for net income and look at profit per employee instead. Same idea, one step further down the income statement. And sales per employee, which divides annual sales by total employees, is a close cousin.

Why it matters more in some sectors than others

For a people business, the workforce is the product. An IT services firm sells hours, projects and managed services delivered by engineers. A staffing company or a BPO is even more direct. In these businesses, revenue per employee is close to a direct read on how well the company is converting people into billing.

For a cement maker or a refiner, it’s far less useful. Revenue there depends on plant capacity, commodity prices and capital invested, and the headcount is a smaller part of the story.

That’s why the ratio only works when you compare like with like. Investopedia makes the point that labour needs vary across industries, so a company’s revenue per employee is most meaningful against its own history or against direct competitors. Labour-intensive industries such as agriculture and hospitality typically show lower ratios than businesses that need fewer people. Comparing an IT services firm with a private bank on this number tells you nothing.

Revenue per employee is a comparison tool, not a score. Against the company’s own past or its closest rival, it says a lot. Against anything else, it says very little.

The quarterly-results trap: periods and headcount

Here’s where most quick calculations go wrong. Quarterly results give you three months of revenue but a headcount figure taken on one day, usually the last day of the quarter. Two things follow.

First, don’t compare a quarterly figure with an annual one. If a company earns a certain amount in a quarter and you divide by headcount, you get quarterly revenue per employee. To compare it with an annual number from a peer’s annual report, either multiply the quarterly figure by four (a rough annualisation that assumes the quarter is typical) or sum the last four quarters of revenue. The trailing four-quarter sum is more honest when business is seasonal.

Second, closing headcount can distort the picture. If a company cut thousands of people in the last weeks of the quarter, closing headcount understates how many people actually did the work that produced the quarter’s revenue. The ratio then looks better than reality. The fix is to use average headcount, the opening count plus the closing count, divided by two.

Neither fix is perfect. But using the same method every time, for every company you compare, matters more than which method you pick.

A worked example: Wipro’s Q2 FY27 numbers

Let’s run the numbers on a real disclosure. Wipro’s Q2 FY27 datasheet gives IT Services revenue in US dollars and a closing employee count for each quarter. One caveat before we start: the revenue line is for the IT Services segment while the employee count is the company’s total headcount, so treat what follows as an approximate productivity read rather than a precise one.

From the datasheet:

Step 1: quarterly revenue per employee on closing headcount.

• Q2 FY27: $2,611.5 million ÷ 236,328 = about $11,050 per employee for the quarter.
• Q1 FY27: $2,614.5 million ÷ 243,044 = about $10,757.
• Q2 FY26: $2,604.3 million ÷ 235,492 = about $11,059.

On this measure, the ratio rose about 2.7% from Q1 to Q2 FY27, and is almost exactly where it was a year earlier.

Step 2: annualise. Multiply the Q2 FY27 figure by four and you get roughly $44,200 per employee a year. That’s the number you’d put next to a peer’s annual figure, with the usual caution that one quarter isn’t always representative.

Step 3: switch to average headcount. Headcount fell from 243,044 at the end of June to 236,328 at the end of September, a drop of 6,716 people, or about 2.8%. Average headcount for the quarter is (243,044 + 236,328) ÷ 2 = 239,686. Divide Q2 revenue by that and you get about $10,896 per employee, around $154 lower than the closing-headcount figure.

That gap is the point. Revenue was flat quarter on quarter, slipping 0.1% in reported terms and flat in constant currency, according to the datasheet. Almost all of the improvement in the closing-headcount ratio came from fewer people, not more billing. The average-headcount version shows a smaller gain, which is the fairer read of the quarter.

When revenue is flat and the ratio jumps, look at the denominator first. A shrinking headcount can flatter productivity without a single extra rupee of billing.

What to read alongside it

Revenue per employee rarely means much in isolation. In an IT company’s datasheet, three other numbers help explain why it moved.

Utilisation. This shows how much of the workforce is actually billed. Wipro’s net utilisation excluding trainees was 83.4% in Q2 FY27, against 83.6% in Q1 and 86.4% a year earlier. So the year-on-year flatness in revenue per employee came even as a smaller share of people were billable. Fewer idle people would push the ratio up; more idle people drag it down.

Attrition. Investopedia notes that turnover affects the ratio, since hiring and training replacements makes a company less productive for a while and adds costs. Wipro’s voluntary trailing-twelve-month attrition in IT Services (excluding BPS) was 13.8% in Q2 FY27, against 13.9% the quarter before. Our piece on attrition rate in IT results covers how to read that number.

Delivery mix. Where the work is done also shapes the ratio, because onsite and offshore work are rarely priced the same. Wipro reported 62.2% of services revenue from offshore in Q2 FY27, against 62.4% in Q1. When that mix moves sharply, read the ratio over several quarters before deciding productivity itself has changed.

And then there’s cost. Revenue per employee says nothing about what each employee costs. Pair it with the wage bill, which we covered in our guide to employee cost in quarterly results. If revenue per employee is flat and cost per employee is rising, margins are under pressure, whatever the headline ratio looks like.

A hypothetical comparison of two firms

Real numbers are useful, but a made-up case shows the comparison logic more cleanly. Take two IT services companies, Company A and Company B. These figures are purely hypothetical.

• Company A: quarterly revenue of $500 million, opening headcount 50,000, closing headcount 50,000.
• Company B: quarterly revenue of $520 million, opening headcount 56,000, closing headcount 52,000.

On closing headcount, Company A earns $10,000 per employee for the quarter ($500 million ÷ 50,000) and Company B earns $10,000 too ($520 million ÷ 52,000). A tie.

On average headcount, the story changes. Company A’s average is still 50,000, so it stays at $10,000. Company B’s average is 54,000, so it earns about $9,630 per employee ($520 million ÷ 54,000). Company B looked just as productive only because it cut 4,000 people during the quarter.

Now ask the follow-up questions. Did Company B cut because demand fell, or because it’s restructuring a low-margin account? Did its utilisation rise? What does its next-quarter revenue guidance say? The ratio started the conversation. The rest of the results finish it.

Common mistakes to avoid

• Mixing currencies. Wipro’s datasheet, for instance, gives IT Services revenue in dollars and its cost breakup in rupees. Pick one currency and stick with it, or rupee movements will look like productivity changes.
• Mixing segment and total numbers. As in the Wipro example, segment revenue and company-wide headcount don’t match perfectly. Say so when you compare, and compare the same pairing across companies.
• Comparing across industries. A software products company and a services company run very different models. Keep comparisons within one business type.
• Ignoring acquisitions. Buying a company adds revenue and people in one go, and the acquired firm’s ratio can be very different. Check the results commentary for any deal that closed in the quarter.
• Reading one quarter as a trend. Look at four to eight quarters before deciding productivity is genuinely improving or slipping.

A quick checklist for results day

1. Note revenue for the quarter and the opening and closing headcount.
2. Work out revenue per employee on both closing and average headcount.
3. Compare with the same quarter last year and the previous quarter.
4. Check whether the move came from revenue or from headcount.
5. Read utilisation, attrition and offshore mix to explain the change.
6. Put cost per employee next to it before drawing any conclusion about margins.

Revenue per employee is one of those numbers that looks too simple to matter. Used carefully, with the right headcount and the right comparison, it tells us quite a lot about whether a people business is getting more out of its people or just fewer of them on the rolls.

Disclaimer: This article is for educational purposes only and is not investment advice. The Wipro figures are taken from the company’s Q2 FY27 datasheet; the per-employee ratios are our own calculations. Company A and Company B and all their figures are hypothetical and used only to explain the arithmetic. Investments in the securities market are subject to market risks. Consult a SEBI-registered investment adviser before making investment decisions.