A two-site operator in Melbourne said the second room would take the pressure off.
Site one still needed him Friday. Site two needed him Saturday. He became the relief chef in both.
Multi-site is a multiplier. Whatever is undocumented in site one gets copied, then blamed on the new team.
If you are searching when to open a second restaurant, use a test, not a mood board.
The four-week test
- Site one hits food cost and labour targets for four consecutive weeks without the owner on the tools.
- Recipes, opens, closes and pars are written, trained and used.
- Each site will have a named person who owns the number, not only the vibe.
- You can compare the two rooms on the same weekly metrics. If site A is 31% food and site B is 38% and nobody can say why, you are not ready.
If the first site "goes well" because you are inside it, the second lease is a bigger job, not a business.
What groups bleed on
Incomparable data. Hero managers. WhatsApp as the chain of command. A chef whose name is the concept.
FAQ
Is a second site a good way to keep a head chef?
Only if the first site already runs without them on every service. Otherwise you cloned the key-person risk.
Do I need multi-site software first?
You need comparable weeks first. Software on a lie is a prettier lie.
What does Hospo22 do with groups?
Same audit logic, then SOPs and roster that travel. Advisory if you want someone on the weekly number.
Bring four weeks from site one, not the lookbook for site two. Book.
---
