How do I compare revenue across locations fairly?
Normalize for the three things that differ most: capacity, market size and job mix. Raw revenue ranks locations by how big they are. Revenue per technician day, revenue per lead and booking rate rank them by how well they operate. Then compare each location against its own history, because a mature market and a branch opened two years ago are not the same business.
Rank on rates, not totals
A location with twice the technicians and twice the market will produce more revenue while operating worse. Ranking on totals rewards inherited advantage and tells a manager nothing they can act on.
The rates worth ranking are revenue per technician day, booking rate on bookable opportunities, close rate by opportunity, and average ticket within job type. Every one of them is something a location's leadership actually influences.
The three normalizations that matter
- Capacity. Divide by technician days available. Without this, hiring and turnover dominate every comparison.
- Demand. Divide by qualified opportunities, not by population or by spend. Market size differences otherwise swamp everything.
- Mix. Compare within job type, or reweight to a common company mix. Locations differ in trade mix and in the age of the housing stock they serve, which drives repair versus replacement demand more than management ever will.
The like-for-like problem nobody solves cleanly
Even fully normalized, locations are not interchangeable. Labor markets, permitting, drive times, competitor density and local pricing all vary. A cross-location ranking is therefore a prompt for a question, never a conclusion.
The comparison that survives scrutiny is each location against its own trailing history, with the cross-location ranking used to identify where to look. That framing also tends to keep the conversation productive, since managers stop defending their market and start explaining their trend.
A useful habit is to require the top and bottom ranked locations to be explained before the ranking is circulated. If nobody can articulate why the gap exists, the ranking is measuring the denominator rather than the operation.
Roll up without flattening
Ownership needs a consolidated view. Location managers need their own numbers with their own denominators. Marketing needs source-level detail that crosses locations. These are different reports built from the same records, and generating them separately by hand is where most multi-location reporting quietly dies.
Building them from one integrated data layer is the practical answer, with each level receiving the version written for its decisions. That is the design behind intelligence briefs written per organizational level and the multi-location dashboards described in revenue intelligence. The integration work underneath is the same regardless of which field service or CRM platform each location runs, which is why it belongs in an integration layer rather than in any one tool.
Topics: multi-location · benchmarking · normalization · operations · reporting
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.