Average Revenue per Employee - How to Calculate, Segment, and Benchmark

People analytics teams tend to shy away from calculating revenue per employee. It’s a very macro number. On its own, a single revenue per employee calculation tells you very little. Even large differences in revenue per employee do not necessarily mean anything or, at least, are not particularly “actionable” when immediately discovered. If I’m being honest, I feel like we people analytics folks have collectively decided we’re just a little too nuanced in our thinking to risk spending time on a data point that can be explained away almost as easily as we can calculate it.

But then again, it’s pretty easy to calculate. And, while it is a very macro number, you still ought to be attuned to how it’s changing. I check the weather, not the climate, before going out camping for the weekend, but that doesn’t mean it isn’t important to know if the climate is changing. 

So put aside your nuanced expertise with me and let’s do some basic calculations! 

How to calculate revenue per employee?

The most simplistic view of this metric is to use this formula:

The average revenue per employee = Revenue during period / Number of employees in that period

 Ok, so let’s say you get a number like $200,000. So what? It’s not necessarily good or bad. There are happy shareholders out there whose companies have a lower revenue per employee and unhappy shareholders whose revenue per employee is much higher. 

 So next you want to look at how that is trending over time, like so. 

Revenue Per Employee with Forecast and Hover Label(Source: One Model Storyboard Visualization for revenue per employee using test database)

 

Trending is probably the best way to look at this data. Ideally, the number trends up, right? But it might not always. Perhaps you are growing and investing heavily in building out teams that will deliver revenue in the future. Perhaps your employee mix is changing. You’re adding call center employees instead of research scientists. Perhaps perhaps perhaps. 

And so, even though we might be able to explain any changes away at this point, that’s exactly the value of making the simple calculation in the first place. The resulting thought process leads directly into asking really fantastic questions about your people strategy. Are we investing in people now for future revenue later? Are we running significantly leaner than we have in the past? Maybe too lean? 


Pulling this data together into a simple graph took me 5 minutes and 24 seconds.
Want a challenge? Play along and time your team while they answer question #1 on the People Analytics Challenge and let us know how long it took to create a similar trend view of this metric. #PeopleAnalyticsChallenge


Variations to Consider on Revenue per employee by industry

Thinking about direct vs indirect contributors

Ok, let’s get back to our thoughts about call center employees vs research scientists. Both are valuable but you would expect an organization with more of the latter to have a higher revenue per employee. So in your own analysis, you can do a couple of things next. 

  1. Segment by employee roles and do the same trend analysis. Again the face value number might be meaningless. “We make $10,000,000 per accountant.” The trend, however, IS interesting. “Say, we seem to need a lot more accountants per dollar of revenue than we used to. I wonder why that is?” 
  2. You could switch to a harder calculation like revenue per dollar of compensation. (check out Mike West. Estimating Human capital ROI. p.102 of People Analytics for Dummies.)

While you may not always be able to attribute revenue earned to specific departments, it will give you more insights if you monitor changes over time. If revenue per employee is dropping or increasing over time, it could indicate that adjustments need to be made on a departmental level.

Switching to net vs gross

If you do find some interesting insights as you trend out revenue per employee, you may want to check whether you are aligned with finance on the dollar amount that best aligns with the company's business strategy. If not, presenting this information to the C-level could be a mistake. You may find it relevant to look at net income or the amount left after all expenses. Here are the various levels of income to think about.

Gross Revenue

  • Sales discount = Net Revenue
  • Cost of goods = Gross Profit
  • Operating expenses = Operating Profit or EBIT
  •  Loan Interests = Profit before taxes (PBT)
  • Taxes = Net Income

If you’re losing money, Net Income could help you determine which areas of the business may be contributing to that more than others.

Again, these revenue per metrics are more of an early warning system than a root cause analysis. Use them as a scanner to home in on more specific analyses. Once you get going, you can start to cut the data in more ways to see what stands out. 

Grouping by Seasonality

Measuring this metric by quarter or by month may give you an idea of how the business cycle evolves. However, be sure to compare similar quarters YoY (year over year) or Months YoY to get a better idea of if things are improving or getting worse over time.

Considering the Role of Employee Turnover

These last few years have been tough. As HR leaders, we know that getting new employees can directly impact the productivity of the company. If you have had a lot of turnover, you may want to align dates to see how this has impacted your revenue per employee ratio. Rather than celebrating a spike in revenue per employee, you might raise the alarm that you are stretched much thinner than before.

Group by Tenure

If new employees cost more, then your most tenured employees must be worth the biggest bang for your buck, right? Breaking your data out by various cohorts will give you a better idea of how effectively you're building your talent.

Do you want to see how One Model builds the insights you need in under 6 minutes? Request a Demo Today.

 

How to find a Revenue per employee benchmark for your industry?

Another upshot of this relatively simplistic metric. You can often estimate it for publicly traded companies. 

The easiest way to do this is to choose at least 3 to 6 public companies in your space. Because they are publicly traded, finding that information on the investor relations section of their site is much easier than trying to collect that same intel on private companies. In most cases, you can find that information over time as well. Once you have that, finding the estimated number of employees can be found on many database websites, or even on Linkedin.

That said, revenue per employee by the industry for private companies can require a substantial amount of work. Look for investor information, and search for news articles on earnings. 

You Found Your Average Revenue per Employee and Benchmark
- Now what?

For starters, don’t panic (or celebrate). If you notice big differences between your organization and others. A competitor may use a much larger number of contingent workers who don’t appear in their employee counts. Or have a very different support model. Again this might feel like it devalues the comparison because so much just depends. That said, doing the calculation suddenly gets you thinking things like, “Hey has their people strategy changed significantly?” “Do they use more/less contingent staff?” These are great questions!

How Can You Change Average Revenue per Employee?

Now that you’re in a strategic mindset, start thinking about the levers you have at your disposal in order to adjust these numbers:

  1. Add Additional Hires focusing on their ability to contribute to your top and bottom lines. [Fun Game] Make a bet with yourself about how it will impact revenue per employee in the short and long term.
  2. See if your performance and engagement data trends align with the departmental trends you’re seeing. Are high-performing teams trending up in revenue per employee? If so, how might you quantify the value and find new ways to invest in these areas? 
  3. Create some buzz around the metric. Tell people that, of course you know it’s a macro data point, but get others thinking about how it’s changing. Take a break from fighting over how to measure promotion rates and enjoy the landscape view. 
  4. If paired with a high turnover rate, work to retain high-performing employees
  5. Look at tools that may increase the efficiency of your workforce
  6. Develop management to maximize performance in each of their departments.

Written By

As One Model’s Solution Architect, Phil gets paid to be excited about People Analytics. This is a pretty good deal for a naturally excitable person with 10 years of experience in HR and analytics - especially one who drinks more coffee than anyone on the team but David Wilson.

Ready to learn more?

Request a tailored demo to see how One Model could help you.