There are "averages" for these types of numbers. I'm sure that Bruce will know right where to point you, but your question begs more questions:
Are you planning on paying developers as a function of what the company brings in? Would that be partial reliance on performance, or full reliance? (i.e., no revenue = no salary) The way you asked it makes me wonder.
Certainly sales people have a direct hand in bringing in revenue and (depending on your preferences) should be paid a commission. But developers... starts looking like equity, since they (ostensibly) don't have a direct hand in it. There are other metrics you could apply, if you're trying to figure out performance compensation.
There is a range of revenue per employee that might look like $100K to $200K. Less, in the beginning, and (perhaps) more, later on... depending on the value your Â?application industryÂ? places on your solution, what level of competition there is, etc. Grossing more than $1 million an employee is possible. So... there is a fairly large range!
For salespeople, the range may be $500K to $2 million or more. Again, it depends on the ASP of your product, etc.
The Â?profit versus investmentÂ? question is a function of what you want to do, how big you are now, etc. That isÂ? if you have a high-growth company and $1 spent in development, marketing or sales brings in $40 to $100, then IÂ?d stay that course! If every dollar you spend brings in $1.02, then a money-market fund might be better. All depends on your goals (assuming you are the CEO and making all the (final) business decisions).
One way to look at it isÂ? if there are any public companies in your Â?space,Â? then you can get their revenue #s and employee count. Then itÂ?s just simple math.
Perhaps Bruce can put up a(n anonymous) survey? The questions: WhatÂ?s your gross revenue, net profit, # of employees, # of sales people, # of developers, and commission rates that you pay. (I guess an Â?industry that you serveÂ? might be valuable, too.)
Just some thoughts to get the discussion going.
Categories: Strategy and Leadership
Are there ratios or metrics for industry averages for the revenue an developer or sales person should bring in for each dollar they are paid? Also at what point do you need to show a profit verse plowing every dollar you earn back into growing the company?
Here is a good place to start.
http://www.softwaremag.com/L.cfm?Doc=2005-09/2005-09software-500
You will be able to see corporate revenues and employees and go from there. Typically, you are doing well if you are above $200K per employee. Elite companies such as Microsoft are closer to $500K. You can also see margins of companies.
Revenue per salesperson and developer is highly relative, such that averages don't mean much if anything IMO. At Oracle for example, AEs carry $2M+ quotas, should that be comparable to a company that sells software at $10K a pop? No, so avoid apples and oranges comparisions. Look at competitors selling similar products in a similar sales process, and you can get a better idea how you are doing.
Check out the SoftareCEO site, Bruce here has been doing an ongoing survey to capture some of these metrics amongst site members, fill out the questionnaire and you can then see how you compare.
http://www.softwareceo.com/surveys.php
As for plowing back, MarKPaul is right on the money. Highly succesful salesforce.com was losing money up until not that long ago in order to "build" their business. I'm sure they could have pulled back to show a tidy profit much earlier, but that is a judgement call by management based on many, many factors.
---
Robert Dubicki
I'm sure that Bruce will know right where to point youHe will indeed! :) Since you're a full site member, he'll point you to the SoftwareCEO M&A/IPO Tracking Excel spreadsheet in our members-only download section. If you're fairly good with Excel, you can manipulate the spreadsheet to show numbers only for private companies, and so forth.
I hope that Bruce won't think I'm giving away too much of a free sample to say that for acquired companies that we tracked in 2003, the first quartile $/employee was $122K and the third quartile was $203K.
(There's LOTS of other good stuff in the full spreadsheet.)
If you are cost managing before your IPO, then you certainly are not creating wealth.
Your retained earnings need to be able to justify a stock split for your stock option holders. One company I worked at set a $10/share target price and split the shares accordingly.
You don't need to show a profit until after your IPO. And, then, only if you have set some dividend expectation for your stockholders. This is a relatively new issue with the revised tax code and the stock option accounting rules changes.
If your sales reps aren't generating enough sales and you have to worry about ratios, get new sales reps, new offers, or a new product. Do something other than focus on ratios.
What are you selling?
David Locke
Gee Dave, not EVERY software company is headed for an IPO. (It just seems that way.) I personally don't think it's ever too early to start looking at metrics. What do others think?
Of course you have to look at metrics!! You need yardsticks in football and business ...
---
Robert Dubicki
Ok, so I'm sitting here watching my dashboard, instead of selling or raising capital. I could while away the days staring at this thing. I could write a weekly report on it. Email to wife: nominal operations this week. Fix the Hamberger Helper.
If you are pulling up already, you won't need an indicator to tell you to do it.
Ok, so you are not going to IPO and you are not paying with stock options, when do you need profit? What events in a software company's life require profitability? Or, what events in the owners lives would require profitability? Will a bank loan you money, as a software company, even if you can show years of solid profitability?
I suppose you show profitabity as required by the IRS, something like once every five years.
David Locke
I agree that you have to measure. But, if you benchmark, you are letting someone else run your business. Are you running an average business? Are you running the same kind of business that built the benchmark? I hope not.
David Locke
But, if you benchmark, you are letting someone else run your business. Are you running an average business? Are you running the same kind of business that built the benchmark?
Benchmarks are derived from a statistical aggregate of many, not one business based on standardized conventions. How you fare statistically when it comes to measures such as revenue per employee, margins, costs, etc... are very important to running a businss. I can't see running a business otherwise. Dave, what you are suggesting is absolutely silly. Do you have an axe to grind with bean-counters? Did you not like being graded when in school and put on a bell-curve? Did you not like your last 360* performance review? I don't get it. Much of everything in business is about keeping score - like it or not - because money is involved.
---
Robert Dubicki
I had conducted some research examining the revenue per employee ratio to see what relationship, if any, there was between this number and profitability. Was $200,000 revenue per employee number a good bench-mark demarcating if your company has a higher ratio than it is more likely to be profitable and if it is lower than it is more likely to unprofitable. I was testing the notion that the higher the revenue per employee the more likely the company was going to be profitable. It turns out neither are valid assumptions. What seemed to be a more valid assumption is that if your revenue per employee ratio was on an upward trend, year-after-year, than you were more likely to be a profitable company.
Even so, I do think that the $200,000 revenue per employee ratio is a good benchmark to shot for.
I also strongly believe both in metrics judging how different parts of a company are performing and benchmarks, which let me know how I compare to the industry and competitors. I am interested in these numbers because they provide data from which to derive insights--that is, in the right hands, they provide insights--into how I can improve both my revenue growth and my margin.
I also believe that it is a turning point in the life of a software company when when they move from an intutive based management style to a more objective based management style. Certainly, as a start-up, you need to be very loose in trying to understand your marketplace and how your product fits in. This is usually an iterative trial-and-error process. But when you want to scale, then you need to have metrics that allow you to learn how to develop predictable and repeatable processes like in lead generation and sales.
I also agree that judging when a company should turn profitable is a strategic decision for which there is not particular formula.
Brian
Brian Turchin CEO/Founder Cape Horn Strategies, Inc. Helping CEOs Increase The Value Of Their Businesses [url]www.capehornstrategies.com[/url]
The problems with software businesses seem fairly typical. I hear from the posts on this forum that we are a low margin business. Since when? Probably since we started benchmarking.
Benchmarking is a best practice. Best practices are norms. Norms are commoditization, which is to be avoided. You need to do better than best practices.
If you only intend to be average, then outsource it and forget it, and I do mean forgetting it, otherwise, you've missed the point of outsourcing, which is to never think about it again, never manage it, judge the contract performance, but no, never manage the internal process, its a black box, so treat it that way. The benefit is in thinking about other things closer to your offer.
But, you can be a commoditized business if you like. Most vendors are, so I suppose that commoditization is unavoidable.
David Locke
Obviously, a lot also depends on what your company does and where it is located. If you are in Silicon Valley, and your employee mix consists primarily of high-end Java programmers, field consultants, and high-end sales reps on expense accounts, then you'll probably need $200K per employee just to break even. OTOH, if you are located in the mid-West and have a mix of admins, phone reps, and Crystal Reports programmers (please! no offense anyone) then you may need only $100K per employee to make a profit.
A lot depends on how highly leveraged you are. If your "company" consists solely of you working out of your house on an already paid-for PC, then you may be pretty happy at $80K per "employee." If you have a slick office, glossy magazine advertising, travel, entertainment, and lots of leased equipment, then you will need additional "per employee" revenue to cover that overhead that actually has little to do with headcount per se.
And of course, I haven't even touched on the fact that we are talking about US, Canadian, and European companies here. The numbers are obviously very different for India, Russia, and China.
Speaking of which, for a US etc. company, exactly what is the headcount? If you count a bunch of Indian developers in your headcount, then your revenue per employee could be correspondingly lower while still maintaining profitability. If you don't count them, then your revenue per employee will have to be much higher because they are now non-headcount overhead that must be covered out of other "per employee" revenue.
Bottom line: revenue per employee is a useful metric but there's no magic revenue per employee number. More is better.
Although it is certainly important to have sufficient revenue per employee (as an overall baselined
Now... cost per employee - that is a different matter.
Mark
Mark, I meant profitability at a given $/employee would be dependent on location. You can probably be profitable in India at $50K/employee (I'm not an expert) but not in Silicon Valley.
For that matter, shouldn't the $/employee target be dependent on geography? (You're the expert, not me.) If I am running a company in the Valley, I might well target $200K or $250K for obvious reasons. But if I were running an Indian outsourcing company, wouldn't I price myself out of this market -- where price is much of the competitive advantage -- if I billed my programmers at $100/hour ($200K/year)?
Charles,
Right you are. This might clear things up (or make this more contentious):
[1] Gross revenue (per employee): Should depend on the value your solution offers customers. Higher value = higher revenue.
[2] Costs (per employee): YesÂ? you want them as low as possible. Geography would make a difference.
[3] Profitability (per employee): Would be 1 minus 2, above (I know you know thisÂ? IÂ?m just trying to be ultra clear with what I was driving at):
What I was/am driving at: I would want to maximize our productsÂ? value (therefore, read Â?PriceÂ?) to customers, to maximize revenue. I would NOT want to lower my price, just to match industry Â?normsÂ? with another company in my geographic (or any other) region).
So, yesÂ? profitability (per employee) is a function of geography. Revenue per employee should not be.
So, it depends.
Mark
RSS
