Revenue Per Employee: The Number That Tests Your Team Size

On every ecommerce stage there is someone quoting their revenue number. Almost nobody adds how many people it takes to produce it.

That gap is the difference between a company that carries itself and one that only looks big.

In my 12 years at PwC I saw hundreds of sets of accounts. One metric told me faster than any margin how a business was really doing: revenue divided by heads. It is simple, it cannot be talked up, and that is why nobody likes it.

Why revenue on its own is worthless

Ten million in revenue with eight people and ten million with sixty people are two completely different companies. One can sit out a weak season. The other has to lay people off in February.

Revenue tells you size. Revenue per head tells you something about structure. It answers the question that comes first in every crisis: how much output stands behind each salary?

The calculation is deliberately blunt. Annual revenue divided by all full-time equivalents. Founders count. Regular freelancers count pro rata. Anyone who leaves themselves out because they are the founder is cheating themselves out of the only interesting number.

I deliberately use revenue rather than contribution margin, even though margin would be cleaner in economic terms. The reason: everyone knows their revenue off the top of their head, and this number is meant to be used in daily work, not in a controlling meeting. If you start steering by it seriously, add contribution margin per head later.

Benchmarks you can work with

Up front: these numbers come from conversations with founders and from my consulting years. They are not a study. Take them as orders of magnitude, not as targets.

The most important note on this table: a high number is no achievement when it comes from outsourcing. If you buy fulfilment, support and bookkeeping externally, you have fewer heads and higher cost per order. The number goes up without anything getting more efficient.

So compare yourself with yourself over time, rather than with the founder on stage. The direction is what informs you. The absolute value tells you little.

How automation moves the number

At our own brands there are three labels and two people. nano, mate and MUSTAX are run by Damian and me. That works for reasons other than fast typing.

Across all processes we count 33 to 46 hours saved per week. That is a full position we never had to hire. We wrote up the concrete levers behind it in 3 brands with 2 people.

Two examples make the effect tangible. At mate, order processing took 4 hours a day. Today it takes 15 minutes. That is a whole position saved, not half of one. At MUSTAX, monthly reporting took 2 days. Today it takes 2 hours.

The interesting part is what happened afterwards. The freed-up time did not go into more processes of the same kind. It went into product development and marketing, so into revenue. Automation hits this metric twice over: the denominator stays small and the numerator grows.

That is exactly why I consider this number the hardest measure of impact for automation projects. Saved hours can be massaged. Revenue per head cannot.

A worked example you can check yourself

Take a brand with 1.2 million euros in annual revenue. Two founders, one part-time support person, one regular content freelancer working two days a week.

That is 2 plus 0.5 plus 0.4 full-time equivalents, 2.9 in total. Revenue per head comes to roughly 414,000 euros. For a D2C brand that is solid without being outstanding.

Now two ways out of that position.

The second path looks better. That does not automatically make it the right one. It assumes the requests are repeatable and the process is stable. Where both hold, it has worked for us. At nano and mate roughly 65 percent of support requests run automatically, and "where is my parcel" alone accounts for about 40 percent of all requests.

The point of the example is the calculation itself. It forces you to write down the expected revenue effect of a hire before you make it. In most companies that never happens.

The uncomfortable side of this metric

Now the counter-argument, and it matters to me.

Revenue per head is a metric. Make it your top goal and you will optimise it into the ground. Three ways that happens:

• Outsourcing instead of improving. Every external provider lowers the denominator. The number looks better. The margin does not.
• Cutting in the wrong place. An understaffed customer service lifts the number immediately and your return rate three months later.
• Losing knowledge. A team of two has zero redundancy. If one person is out, everything stops. We know that one very well ourselves.

And there are cases where a bigger team is simply right. I count four:

When you enter a new market. For that you need people with knowledge no system has. Language, law, contacts.

When your product needs advice. For complex or high-priced products, the person selling is the revenue.

When the process is still changing. Automation needs stability. Automate chaos and you get faster chaos. In that phase a person is more flexible than any system. When the effort does not pay off is covered in When automation makes no sense.

When you are the bottleneck yourself. Two people with a great metric and seventy-hour weeks are a burnout with a lead time.

I have lived through that. Before we automated, I was close to burning out at our brands. The metric looked fine back then. It did not see it.

How to use the number day to day

Three things, that is all it takes.

Calculate it once a quarter, no more often. Monthly values swing too much and tempt you into busywork.

Write down next to the number what happened. New person hired, fulfiller switched, support automated. Without context the curve is just noise.

Use it as a question rather than a target. Before any hire, ask: does our revenue per head rise or fall over the next twelve months because of this, and do we want that?

Sometimes the answer is: it falls, and it is still right. Then hire. But you decided it instead of letting it happen. If you want to check first whether an automation closes the same gap, Scaling without hiring helps.

A word on the alternative: not every gap has to be closed with a permanent hire or a system of your own. The third way is external implementation, and sometimes that is the cheapest. The trade-off is covered in Agency, freelancer or build it yourself.

Conclusion

Revenue tells you how big you are. Revenue per head tells you how stable you are.

The number is uncomfortable because it turns every hire into a conscious decision. That is precisely its value. It prevents the slow growth of a team that nobody decided on and that you can only undo painfully.

Work it out once for your last financial year. With yourself in the denominator. The number will either reassure you or show you where to look first.

If you want to know which processes would have the biggest effect on this number at your company: talk to us at Flowhouse. We will run the numbers with you, even if the answer turns out to be that you should hire someone.