We almost never recommend launching all venues at once. The pattern that works: pilot, learn, roll out in waves.
The four-stage rollout
Stage 1 — Pick the pilot venue
Not your busiest. Not your slowest. Pick a middle-volume venue where mistakes are visible but not catastrophic.
Good candidates:
A venue where the GM is enthusiastic about new tools (will champion).
A venue with a relatively standard reservation pattern (no weird private-event volume to navigate first).
A venue with reasonably good OpenTable hygiene.
Avoid:
Your flagship (too much downside if it goes wrong).
Your newest venue (too many other things in flux).
A venue with a skeptical GM (they'll resist tuning, results will lag).
Sushi by Bou launched at Chelsea first. That worked.
Stage 2 — Run for a week
Follow the standard onboarding rhythm:
Onboarding call.
Configuration.
Team training.
Pre-deployment testing.
Go-live.
One-week debrief.
During this week, build the org-level templates that other venues will inherit:
Brand-wide playbook copy.
Default voice and language.
Default notification structure.
Stage 3 — Roll the next wave
2–3 venues per week is typical for a 5–10 venue group. Faster is possible but adds tuning load.
For each new venue, the cycle is shorter:
~2 days for venue-specific configuration (hours, menu, phone, OpenTable).
~1 day for testing.
Go-live.
We'll be more hands-off than the pilot venue, since templates are now in place.
Stage 4 — Refine based on patterns
After ~5 venues are live:
Patterns emerge: a tweak useful for one venue often turns out to be useful for all.
Push promising changes back up to org-level templates.
Apply to remaining venues as they roll in.
Common rollout traps
"Let's launch all 12 at once."
What goes wrong: every venue surfaces the same first-week issues, but you have no time to fix them because you're firefighting across 12 simultaneously. Tuning load explodes.
"Let's launch one a quarter."
What goes wrong: by the time the third venue launches, the first venue's setup is stale, the org-level templates have drifted, and team turnover means the GM you trained 9 months ago is gone.
"Each venue does its own thing."
What goes wrong: every GM customizes their venue's voice and playbooks differently. Brand consistency erodes. Maintenance becomes 12 separate problems instead of one. See Per-venue customization without diverging.
When to deviate
Faster rollouts (5+ venues per week) work when:
Templates are mature.
All venues use the same reservation system.
All venues have the same phone setup.
An ops lead can dedicate their full attention.
Coordination with us
Tell us your rollout plan early. We'll allocate Pascal/Jose attention accordingly.
Multi-venue groups get standing weekly check-ins during rollout, not just one-week debriefs.
Once all venues are live, we move to monthly check-ins.