Teams & appointments
How to Track Revenue Per Staff Member
By Bruno Melani, founder of Gaplessly · · 8 min read

The short answer
Revenue per staff member is what one stylist, therapist or server brings in from their own completed bookings, unlike revenue per employee, which splits total revenue across everyone on the payroll.
A single week tells you little on its own.
Read the 7-day, 30-day and 90-day numbers side by side to see whether a dip is a one-off or a pattern.
Revenue per employee vs revenue per staff member
The same name covers two different numbers. Finance and HR guides usually mean revenue per employee: total business revenue divided by everyone on the payroll, so reception, admin and kitchen staff count alongside the people who take bookings. That tells a company how efficiently it turns headcount into revenue overall. It says almost nothing about whether one stylist is pulling their weight.
Revenue per staff member, in the sense that matters for a service business, is narrower: the revenue from what each provider booked and completed over a period. A stylist's column adds up their own appointments, a colleague's adds up theirs, and reception's wages never enter either total. It is also the number a booking system's own reports track, because it comes straight from the bookings and needs no payroll export.
The revenue per staff member formula
With the two definitions separated, the formula is simple: add up the revenue from one staff member's own completed bookings over the period you are measuring. Most of the work is deciding what goes into that total and what stays out of it.
Take a three-stylist salon with $18,000 in total service revenue for the month. That averages $6,000 per stylist. But if one works part-time and books fewer clients, another does a heavier colour and treatment mix at a higher average ticket, and the third is new and still building a client base, the split might be $9,500, $6,200 and $2,300. The average hides what you need to know: which stylist is driving the number, and by how much.
The textbook revenue per employee formula divides total revenue by everyone on the payroll, including staff who never touch a booking. It roughly measures how the whole business turns headcount into revenue, which makes it the wrong number for deciding whether one provider needs a conversation, a schedule change or more training.
Why one week misleads, and what 30 and 90 days show
A single week of revenue per staff member moves for reasons that have nothing to do with performance. A sick day, a run of cancellations, a mid-week public holiday or an ordinary quiet week can make a provider's number look like a problem when it is not.
A 30-day view smooths most of that out. One bad week is averaged against three ordinary ones, so someone who is consistently under target starts to stand out from someone who had one off week. A 90-day view is long enough to catch a seasonal dip or a slow decline that a 30-day window would still read as normal variation.
Read the 7-day, 30-day and 90-day numbers for the same staff member side by side. A provider whose week is down but whose 30-day and 90-day trend is flat just had an off week. One whose numbers are down across all three has a pattern worth a conversation.
Read revenue next to service mix and peak hours
Revenue per staff member tells you how much each person brought in. What to do about a low number depends on why it is low, and two staff members can post the same low number for different reasons that need different fixes.
One reason is service mix. A stylist doing lots of quick, low-priced services will show lower revenue than a colleague doing fewer, longer, higher-priced appointments, even when both are fully booked. That calls for upselling or add-on training rather than a talk about effort.
The other is scheduling. A staff member consistently rostered outside the business's peak hours will show lower revenue because there are fewer walk-in and last-minute bookings to fill their calendar in those hours. That is a roster problem, and coaching will not fix it.
Put revenue per staff member next to the same period's breakdown by service and by peak hours to tell these two cases apart. Without it, choosing between a training conversation and a roster change is a guess, and a wrong guess leaves the real problem in place.
What to do once you have the number
Once service mix and peak hours have ruled out the wrong explanation, the number points to one of three next steps:
- For a service-mix gap, have a training and upselling conversation: an add-on that is being under-recommended, or a higher-value service worth coaching toward. Keep it as coaching rather than a warning.
- For a scheduling gap, change the roster: move a provider's hours to overlap more with the business's peak periods, or rotate who covers the quiet shifts.
- A sustained decline across all three windows, with service mix and peak hours ruled out, is the one case that warrants a direct performance conversation. Have it with three months of trend behind you, not one bad week.
For a small team this can be a five-minute look at the numbers each month, early enough to catch a small pattern before it becomes a bigger problem.
Revenue per staff member in salons, clinics and restaurants
The examples so far come from a salon, where it is a stylist's revenue against their own bookings. The same reading works in a clinic or a restaurant.
In a clinic it becomes revenue per practitioner: a physiotherapist's or chiropractor's completed appointments against their own booked hours. The same service-mix and peak-hours reading applies. A practitioner doing longer, higher-value consultations will look different from one doing a high volume of quick follow-ups, and neither is automatically the problem.
In a restaurant or venue, the unit is a server's or a shift's revenue across a service period rather than one provider's appointments. A Thursday dinner sitting and a quiet Tuesday lunch are not comparable in raw terms. Reading a shift's revenue against the same period's peak-hours data tells a quiet shift apart from one that underperformed even allowing for lower footfall.
In every case the report has the same shape: revenue over a chosen window, broken down by person and by when it happened. Only the unit changes, from stylist to practitioner to server.
When a spreadsheet is enough, and when to automate
A very small team does not need software for this. A solo operator has nobody to compare against, so there is nothing to track. A team of two or three can use a spreadsheet, tallying each person's takings from the booking calendar once a month, and that works for as long as the tally stays quick enough to get done every month.
The spreadsheet stops being enough when the tally starts taking real time, when the team is big enough that eyeballing the calendar no longer shows the pattern, or when comparing this month with three months ago means digging through old exports instead of looking at a chart.
At that point a report built into the booking system does the job: revenue over 7, 30 and 90-day windows, broken down by service, staff member and peak hours, with nothing to re-export and no monthly tally to keep up.