How do I compare revenue performance across locations fairly?
Normalize before you rank. Locations differ in market size, crew count, tenure, job mix and season, so raw revenue ranks markets rather than management. Compare revenue per technician-day, booking rate on bookable calls, and revenue per lead within the same job type. Those isolate what a location actually controls. Then study the spread rather than the average, because the spread is where transferable practices live.
Raw revenue ranks markets, not managers
The largest location usually posts the largest revenue. That tells you where you put the largest market, which you already knew. Ranking on it rewards inherited advantage and demoralizes the manager doing excellent work in a smaller territory.
Every useful cross-location metric is a ratio whose denominator is something the location did not choose.
Metrics that survive normalization
- Revenue per technician-day. The cleanest productivity measure. Controls for headcount, which is the biggest confound.
- Booking rate on bookable calls. Purely an execution metric once the denominator is defined consistently.
- Revenue per lead within job type. Removes the mix differences that come from different local demand.
- Close rate on presented estimates. Comparable across markets in a way that total sold revenue is not.
- Completion and cancellation rates. Operational hygiene, largely independent of market size.
The confounds that will still bite you
Tenure is the big one. A location opened eighteen months ago has no repeat customer base, no referral base and a crew still learning. Comparing it to a twenty-year location on any revenue-derived metric is meaningless. Group locations by maturity band before ranking, or plot performance against months open and look at the deviation from the curve.
Marketing exposure is the second. If one location receives a disproportionate share of paid demand, its revenue advantage is purchased rather than earned. Comparing marketing-attributed revenue separately from repeat and referral revenue separates the two.
Season is the third. Locations in different climates peak in different months, so a rolling twelve-month view is safer than any quarter-to-quarter comparison across regions.
Manage the spread, not the average
The average across locations is a number for the board deck. The spread is where the money is. When one location books at a materially higher rate on comparable calls, that is a documented, transferable practice sitting inside your own company, and finding it is worth more than any benchmark you could buy.
The practical requirement is that every location's data is defined identically, which in multi-location operators is usually the hard part rather than the analysis. Consolidating differing systems and definitions into one comparable model is standard integration work, and rolled-up briefs written per level, location and region are what makes it usable day to day. See intelligence briefs for how those rollups get structured.
Topics: multi-location · normalization · benchmarking · rollup · operations
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.