Rolling out new software across 3-15 existing shops is harder than starting from scratch. People resist. Existing workflows are sticky. This is a playbook for a multi-location rollout.
Phase 0 — Pre-decision (week -2 to -1)
Before the kickoff, the founder/HQ team needs alignment on:
- Standardization vs flexibility — will each location's catalog/pricing be identical, or do locations get autonomy within HQ-defined floors? Pick before rollout. Changing mid-rollout poisons morale.
- Champion per location — every shop needs ONE person on the ground who owns SalesThumb adoption. Identify them now. Pay them a $500-1,000 bonus tied to clean migration.
- Pilot shop selection — pick the shop with the best champion + most-motivated owner-operator. Not your biggest location, not your smallest. Pick the most coachable.
Phase 1 — Pilot rollout (weeks 1-2)
Migrate the pilot shop completely. The goal: prove every workflow works, every report looks right, every integration fires.
- Day 1 (Monday): Catalog setup at HQ level. Pilot shop's pricing, services, deposit policies, warranty tiers, photo templates all configured.
- Day 2 (Tuesday): Customer + vehicle import, plus cleanup and spot-checks.
- Day 3 (Wednesday): Payments + QuickBooks + calendar subscription feed wired; confirm messaging health on Messages → Deliverability.
- Day 4 (Thursday): Training session — 2 hours with the pilot team. Focus on quote → invoice → install → warranty.
- Day 5 (Friday): Run the day on SalesThumb. Old tool stays open as fallback.
- Days 8-12: Five business days where pilot runs everything on SalesThumb. Tune as needed.
By Friday of week 2, you should have:
- 50+ real quotes sent through SalesThumb
- 30+ jobs completed end-to-end
- Payments, QBO, calendar all syncing cleanly
- Customer SMS confirmations going out
- A full week of clean data showing up in the HQ cross-location dashboard
- Pilot champion comfortable enough to teach the next location
If any of those are broken, do NOT roll out to location 2. Fix first.
Phase 2 — Wave rollouts (weeks 3-6)
Roll out 1-2 locations per week. Each follows the same 5-day cadence as the pilot but accelerated because the catalog is already configured.
For each location:
- Day 1: HQ creates the location, applies catalog template. Champion confirms.
- Day 2: Customer + vehicle import.
- Day 3: Integrations — payments, QuickBooks, your own SMS carrier if you use one, and calendar feeds are all connected per location.
- Day 4: Training with the local team (1.5 hours, condensed from pilot's 2hr).
- Day 5: Go-live.
Order matters:
- Wave 2: your second-most-coachable shop. Builds momentum.
- Wave 3: a "neutral" shop — neither champion nor blocker.
- Wave 4-N: remaining shops in roughly any order. Save your most-resistant location for LAST so the wave of evidence is built.
DO NOT roll out the most-resistant location early. They'll find every bug, blame the software, and demoralize the wave.
Phase 3 — HQ dashboard adoption (weeks 4-8)
While locations are migrating, the HQ team starts using the cross-location dashboard:
- Daily: revenue per location, job count per location, close rate per location
- Weekly: cross-location KPI snapshot
- Monthly: royalty calculation, cross-location P&L, manager scorecards
The HQ team should be looking at the dashboard daily by week 6. If they're not, the rollout is incomplete.
Phase 4 — Steady state (weeks 9+)
What "done" looks like:
- 100% of bookings, quotes, invoices flow through SalesThumb
- All old tools are read-only (kept for historical reference) or archived
- All locations on the same catalog template with explicit per-location overrides documented
- HQ team has a weekly review meeting using SalesThumb's cross-location dashboards
- Royalty automation runs without intervention
Anti-patterns to avoid
- Big bang rollout — migrating all locations on the same week. It's risky: a problem at one location lands on every location at the same time.
- Skipping the pilot — "we'll figure it out as we go". You won't. Fix one location's workflow before scaling it.
- Training via Loom video only — works for some teams, but live training matters, especially for the first session.
- No champion per location — without local ownership, adoption tends to stall.
- Letting locations stay on old tools — even "just for the few customers who haven't transitioned". The old tool will outlive your patience and confuse everyone.
What HQ-tier features unlock
- Shared catalog with per-location overrides
- Centralized pricing floors
- Royalty + management fee automation
- Cross-location reporting
- Cross-location customer view (HQ → Customers lists every location's customers with their home shop; turn on Share customer database under HQ Settings → Data Sharing to let locations open each other's records — each location still keeps its own record)
- One login across locations (someone who belongs to several shops switches between them from the shop switcher)
- HQ-level marketing campaigns