The next opening copies this one's defects.
Two to ten locations, run as one operation: one book, one guest record, one weekly number. The fee follows system stacks and sets of books.
The second location is where it shows.
One room forgives a lot. When the systems don't talk to each other, you are the thing that talks between them — and on a single site, that almost holds.
The second lease ends it. You can't be the integration layer in two buildings at once, and whatever lives in your head instead of in the operation gets cloned into the new room, workarounds included. The most expensive way to learn this is during opening week.
The cheapest time to rebuild how you run is before it's copied.
Two to ten locations, run as one thing.
Restaurants, bars, cafés, bakeries — whatever the rooms are, a group that runs as one operation has three things a collection of them doesn't:
One book, one order queue
Reservations and large parties handled one way, under one policy, so a guest booking either room is dealing with the same restaurant group — because they are.
One guest record
Your regular from the first room shouldn't be a stranger at the second. The history rides with the guest, in systems you control.
One weekly number
Sales, labor, payroll, and the software bill across every site, in one view that ties to the P&L, with a clear line on who can see or change what in each room — readable on a Sunday night without six logins and a spreadsheet ritual.
What has to be shared before the second location opens?
Before the second lease is signed, a restaurant group needs one reservation book and one order-queue policy that both rooms will follow, one guest record that travels between them, written permissions for who can see and change what in each room, and a software bill priced line by line so nothing gets cloned by accident. Before opening week, the weekly number, sales, labor, payroll and the software bill in one view, should already have been produced once from the first room. OpsRefresh rebuilds a group as one operation so the new room starts from a working system instead of a copy of the first room's workarounds.
One weekly number: what a group reconciles firstThe fee follows system stacks and sets of books.
The fee is set by how many separate system stacks and sets of books you run — not by how many doors you have. A second room on the same POS, reservation book, and P&L adds field time, not a second engagement.
That cuts both ways, and we mean it to. If you've already consolidated, the fee says so. If every location runs its own POS and closes its own books, the fee says that too — because walking three separate operations is three times the walking.
Finished means the group runs.
The engagement is finished when the business runs — not when a system goes live. For a group, “runs” means things you can check:
- The weekly number reads in one sitting, and you trust it enough to argue from it.
- A manager can run either room from the written record, without your phone number as the fallback.
- The next opening starts from the operation you actually want, instead of a faithful copy of this one's defects.
Before the next opening
If the second location is signed, open, or circling, the fit call is the half hour that sets the order of operations.