Thoughts from the trench - by Prakash Muralidharan

July 30, 2007

Nederlands/Dutch Français/French ???????/Russian Deutsch/German Italiano/Italian Português/Portuguese Español/Spanish ????????/Greek 日本語/Japanese 한국어/Korean 中文(简体)/Chinese Simplified 中文(简体)/Chinese Traditional

Revenue per employee : A shortsighted productivity metric

Filed under: Software Services, Pricing, Strategy, Account Management — Prakash Muralidharan @ 1:59 pm

I came across this piece in the Times praising US tech companies. The article uses revenue per employee (RPE) as a yard stick and claims "US IT professionals more productive". Basically we have Wipro,Infosys,TCS etc on one side and IBM,Dell, HP etc on the other. The arguments are backed up by numbers but the logic is flawed. I find it hard to believe RPE can be linked to a professional's productivity. The revenue a services company makes is broadly (ignoring systemic factors like currency risk, credit risk etc) dependent on the following :
- Bill rate (significantly higher for 'Western' players)
- Utilization rate (More or less the same)
- Offshore onsite mix (Much better for Indian players).

The higher RPE that US companies make is largely on account of the following:
- Significantly higher bill rate
- Broader portfolio that includes software products and consulting which traditionally have a greater RPE than pure services
- Higher onsite/offshore ratios leading to a higher top line for the same number of FTE's billed.

None of these factors have anything to do with employee productivity. In fact for certain types of engagements staffing more productive employees could reduce RPE! A better caption for the article could have been "US companies turning people capital into cash more productively".


Linking and Sharing

If you found this page useful, consider linking to it.
Simply copy and paste the code below into your web site (Ctrl+C to copy)
It will look like this: Revenue per employee : A shortsighted productivity metric

del.icio.us:Revenue per employee : A shortsighted productivity metric   digg:Revenue per employee : A shortsighted productivity metric   fark:Revenue per employee : A shortsighted productivity metric
Trackback

Trackback URI for this entry:

http://www.prakashonsoftware.org/blog/index.php/2007/07/30/revenue-per-employee-a-shortsighted-productivity-metric/trackback/

4 Comments »

  1. While the metric may be flawed, it is undeniable that in USA, one can get more productive work done per employee -that is you can get more work done per employee, because of BIC processes and higher level of computing skills. Low cost outsourcing offsets the drop in productivity. Ask anyone who has spent an equal amount of working and managing people in both the countries - and you will know. Please note this is not a reflection of our innate skills and capabilities - we can do it - but are usually good at it, if we are in the valley. There is more poor to average talent here, than the exceptional. We are building armies of dotnet programmers, who know nothing about an alogorithm, and you want them to be more productive than USA? This is one reason why we have so few IP driven companies,and why there is an innate urge to copy rather than innovate.

    Comment by Sandip — August 6, 2007 @ 2:31 pm

  2. Thanks for your comments Sandip.

    Comment by Prakash — August 7, 2007 @ 8:08 am

  3. well put…couldn’t agree with you more.

    Comment by matthew — February 21, 2008 @ 9:01 pm

  4. Thanks Matthew for the comment.

    Comment by Prakash — February 22, 2008 @ 12:41 am

RSS feed for comments on this post. TrackBack URI

Leave a comment

Creative Commons LicenseDisclaimer : This blog site is published by and reflects the personal views of Prakash Muralidharan,in his individual capacity. It does not necessarily represent the views of any of his employers, past or present, and is not sponsored or endorsed by any of them. No representation is made about the accuracy of the information contained in this blog.