Revenue Per Employee: SGD 200K Is Good, SGD 80K Is a Warning — Where Do You Stand?
- Revenue Per Employee — The Core Formula and Benchmarks
- RPE as a Diagnostic Tool — Not Just a Number
- Tracking RPE Trends — Monthly, Not Annual
- AskBiz Revenue Per Employee Tracking
- Converting Part-Time and Seasonal Staff to FTE Correctly
- Worked Example: Fixing the Jurong Outlet
- Common Mistakes When Acting on RPE
Retail chain: SGD 2.4M revenue, 18 employees = SGD 133K revenue per employee. Industry benchmark: SGD 180K. Gap: SGD 47K × 18 employees = SGD 846K revenue gap OR you have 4-5 excess employees (4 × SGD 133K = SGD 532K → reduce headcount to 14 and hit benchmark). Restaurant: SGD 1.2M, 15 employees = SGD 80K/employee = at lower end. Peak performers (Michelin-starred or high-volume fast casual): SGD 150K+. Gap to close: SGD 70K/employee × 15 = SGD 1.05M revenue to find without adding staff.
- Revenue Per Employee — The Core Formula and Benchmarks
- RPE as a Diagnostic Tool — Not Just a Number
- Tracking RPE Trends — Monthly, Not Annual
- AskBiz Revenue Per Employee Tracking
- Converting Part-Time and Seasonal Staff to FTE Correctly
Revenue Per Employee — The Core Formula and Benchmarks#
RPE = Annual Revenue ÷ Total FTE (full-time equivalent) headcount. Part-timers: convert to FTE (2 half-time = 1 FTE). Benchmarks by sector: retail SGD 150K-250K (simple product, self-service); restaurant/F&B SGD 80K-150K (labour-intensive); manufacturing SGD 200K-400K (capital-intensive); professional services SGD 200K-500K (billable hours). Technology/SaaS SGD 500K-2M+ (low marginal cost). Below the lower benchmark: staffing inefficiency OR revenue underperformance.
RPE as a Diagnostic Tool — Not Just a Number#
Low RPE has two causes: too many staff (overstaffed for current revenue) or too little revenue (understaffed stores, each employee productive but business underdeveloped). Diagnosis: check utilisation. If staff are idle 30%+ of time: overstaffed. If staff are at capacity, customers waiting: underdeveloped revenue (more customers available, not enough to serve them). Fix differs: overstaffed → reduce headcount. Underdeveloped → marketing and capacity expansion.
Tracking RPE Trends — Monthly, Not Annual#
Annual RPE misses seasonal variation and early warning signs. Monthly RPE: if February (slow month) RPE drops to SGD 90K annualised and you don't adjust staffing → you're carrying excess cost. Peak months RPE should be 30-50% higher than off-peak. If December RPE is SGD 200K and January is SGD 90K but headcount is same: January is inefficient. Consider: seasonal staffing (part-time for peak), shift scheduling optimisation, cross-training for multi-role efficiency.
AskBiz Revenue Per Employee Tracking#
Pulls revenue from sales system, headcount from payroll. Calculates monthly RPE with trend. "This month: revenue SGD 185K, 14 FTE = SGD 158K annualised RPE. Benchmark: SGD 180K. Gap: SGD 22K. Trend: RPE improving (was SGD 130K 6 months ago — revenue grew, headcount stable). Forecast: at current trajectory, hit benchmark SGD 180K in 3 months. By outlet: Orchard outlet SGD 220K RPE (above benchmark), Jurong outlet SGD 95K RPE (below — investigate: lower traffic or overstaffed?). Recommendation: review Jurong scheduling — 3 staff on off-peak Tuesday afternoon."
Converting Part-Time and Seasonal Staff to FTE Correctly#
RPE is only comparable across periods and outlets if your FTE calculation is consistent. The standard conversion: FTE = total hours worked in a period ÷ standard full-time hours for that period (typically 40 hours/week or the local statutory full-time definition). Two employees each working 20 hours/week count as 1.0 FTE, not 2 headcount. A common error is comparing RPE calculated on headcount at one outlet against RPE calculated on FTE at another — an outlet with many part-timers will show artificially low RPE on a headcount basis even if it's actually efficient on an FTE basis. Standardise the FTE formula across every location before comparing, and recalculate FTE monthly since part-time hours often fluctuate with scheduling.
Worked Example: Fixing the Jurong Outlet#
Following on from the AskBiz alert above, the Jurong outlet's SGD 95K RPE against a SGD 180K benchmark triggered a scheduling review. The investigation found average footfall data showed Tuesday 2-5pm traffic at roughly 30% of Saturday peak levels, yet the outlet scheduled the same 3-staff coverage across both. Cutting Tuesday afternoon to 1.5 FTE (one full-time plus a part-timer) freed 1.5 FTE of labour cost — reallocated to Saturday coverage where the outlet had been understaffed and losing sales to queue abandonment. Over the following quarter, Jurong's RPE rose from SGD 95K to SGD 142K: partly from the labour cost reduction (lower FTE denominator) and partly from the Saturday revenue capture (higher numerator) — a combined effect that a scheduling change alone wouldn't have delivered without both sides of the RPE formula improving together.
Common Mistakes When Acting on RPE#
The first mistake is comparing RPE across fundamentally different business models without adjusting the benchmark — a full-service restaurant will always show lower RPE than a quick-service outlet of similar revenue, because service model, not staffing competence, drives the difference. The second mistake is cutting headcount reactively the moment RPE dips below benchmark, without first checking whether the cause is a temporary revenue dip (seasonal, one-off event) rather than genuine overstaffing — cutting staff during a temporary lull can leave you unable to serve the rebound. The third mistake is optimising RPE in isolation from customer experience metrics; an outlet can hit an excellent RPE number by understaffing to the point that service quality and repeat visits suffer, which shows up as a delayed revenue decline a few months later. AskBiz cross-references RPE trends against customer wait-time and satisfaction signals where available, so a scheduling cut doesn't inadvertently trade short-term efficiency for longer-term revenue loss.
People also ask
Should I use revenue or profit per employee?
Both. Revenue per employee is the standard benchmark (comparable across companies). Profit per employee (or gross profit per employee) is more meaningful internally — shows how much value each employee generates after COGS. A retailer with 40% gross margin: target gross profit per employee of SGD 60K-100K (40% of SGD 150K-250K RPE). If gross profit per employee is below SGD 60K: staffing cost likely exceeds value generated.
What if my RPE is well above benchmark — am I understaffed?
Possibly — but high RPE can also mean high productivity (good training, efficient systems) or a lean business model. Check: are customers getting good service? Are staff burning out (high turnover)? If service quality is strong and turnover normal, high RPE is a strength, not a problem. Only add headcount if revenue growth is constrained by capacity.
Our team combines expertise in data analytics, SME strategy, and AI tools to produce practical guides that help founders and operators make better business decisions.
Track Revenue Per Employee Monthly (Benchmark Your Team Productivity)
AskBiz combines revenue and payroll data to calculate RPE by outlet and business unit. Flags below-benchmark locations. Try free.
Connects to Shopify, Xero, Amazon, QuickBooks, Stripe & more in minutes