The Fleet

The short version

The first location works because you’re in it. The second one doesn’t: you can’t be in two places, so quality drifts. Add more, and each location becomes its own business with its own standards. Holding the standard across many locations isn’t about more oversight. Oversight doesn’t scale. It takes two things: the same system running in every location, and one view that shows you each location’s scores, so you only step in where it’s slipping. Set the standard once. Replicate it. Manage by exception.

Why this matters

The second location is where most good operators come unstuck.

The first one works. You’re there. You catch the problems, set the tone, fix the off day before the customer notices. The business runs on your presence, and it runs well, so you assume the next one will be the same.

It isn’t. You can’t be in two places at once. So the second location runs on someone else’s judgement, on a good day and a bad one, and you only find out how it went after the fact. Add a third and a fourth and the gap widens: each location drifts toward its own way of doing things, its own quality, its own standards. The brand on the sign is the same. What happens underneath is six different businesses.

I spent nine years running operations across more than seventy branch locations. You do not hold seventy branches together by visiting them. You hold them together with a system that runs the same whether you’re in the room or not, and a way to see, at a glance, which branch needs you this week.

That’s the whole problem of scale. Not doing the work in more places. Holding the standard in more places, without being in all of them.

What consistency at scale actually takes

Strip it back. There are only two ways to make many locations behave like one, and only one of them works.

The way that fails is more oversight: more visits, more checking, more of you. It feels responsible. It doesn’t scale, because it’s capped by your hours, and the day you’re stretched is the day standards slip everywhere at once. You become the constraint you read about in the SX Metrics guide, except now it’s the whole fleet waiting on you.

The way that works has two parts.

1. Governed replication. Take the operating system from the location that works, its Rules, Rails, Roles, and Reporting (see The Operating System), and replicate that, not just the storefront. Every location runs the same non-negotiables, the same boundaries, the same clear authority, the same reporting. You’re not copying a shop. You’re copying the system that makes the shop reliable. New locations inherit the standard instead of inventing their own.

2. One view, the cockpit. You can’t manage what you can’t see across locations, and you can’t compare what each one measures differently. So the cockpit starts with setup: every location measured the same way, from the same baseline. Then each reports the same six SX Metrics scores into one place: Plan, Engagement, Enquiry, Conversion, Retention, Operational Excellence, a row per location, red/amber/green. Now you don’t inspect everything; you scan for red, and a red in one place means the same as a red in another. That’s what the baseline buys you: one honest yardstick, so the board you read in two minutes is telling you the truth, not comparing apples to oranges.

Put together, these let you manage by exception: the system holds the standard, the cockpit shows you the one or two places it’s slipping, and your attention goes only where it’s needed. That’s how seventy branches stay consistent without seventy visits.

And you don’t roll it across the fleet in one move. You prove the standard on one location, practise it on a small pilot, then scale it. Test, pilot, scale, so by the time it’s everywhere, it’s already been proven and rehearsed, not gambled on at size. The reference location isn’t just where you copy from. It’s where you prove the system works before it costs you anything to be wrong.

How to build it: the steps

You don’t need fifty locations to start. Two is enough to feel the drift, and the build is the same. Each step leaves you with something concrete.

You now have a standard you can replicate, a board that shows you where it’s slipping, and a rule that keeps your attention where it counts. Two locations or fifty, that’s the machine.

What if…

Proof it works

This is the pillar I lived.

Across more than seventy branch locations for Amalgamated Pest Control, a national pest-control group, consistency never depended on me being there. It depended on the same system running everywhere and a way to see which branch needed attention. The numbers it produced: 122,000 tracked inbound calls, cost per call 52% below the industry benchmark, $1.9 million in acquisition-cost savings, and 3,000 to 5,000 unique inbound calls a year on repeat, with zero ad spend.

That isn’t seventy heroic branch managers. It’s one standard, held across every branch, not seventy people improvising, with attention going where it was actually needed. Legacy is designed. A fleet that holds its standard without you is something you build on purpose, not something that happens.

Your next move

If you’re past one location and can feel the standard slipping in the places you can’t be, the gap is in how you replicate and watch. Every location running its own way isn’t just margin slipping somewhere you can’t see: it’s less reliable data to decide on, so you end up guessing where you should be reading.

Start with the Constraint Audit: score one location, honestly. That’s the test: prove the standard on one before you pilot it across a few and scale it to the fleet. The standard you replicate is only as good as the one you start from. No obligation, no pitch, an honest baseline you can actually act on.

You can’t be everywhere. Build the thing that can.