Multi-location marketing on Service Autopilot: the operating model

The operating model that works for multi-location companies on Service Autopilot fits in one sentence: every location gets its own Google Business Profile, its own tracking numbers, and its own budget; the company keeps one shared playbook and one roll-up report. Local assets, central brain. Most multi-location marketing problems are one of those four pieces missing.

What breaks when you scale marketing past one location?

The short answer: attribution turns to mush. One phone number on the website means nobody knows which office the call belonged to. One Google Business Profile means location two is invisible on the map in its own city. One ad account with blended campaigns means the strong location subsidizes the weak one and both look average. And "how's marketing going?" gets answered by whichever location manager talks loudest, because there's no report that compares them honestly.

None of this shows up at one location, which is why growing companies get surprised by it. The fix isn't more spend: it's structure.

Should each location have its own GBP and tracking numbers?

Yes, without exception. One verified Google Business Profile per physical location (its own reviews, photos, and posts) because Google's local results are built around proximity to a real address, and a single HQ profile caps your map presence at one city. We've covered the mechanics in our GBP guide. Alongside it, every location gets its own tracking numbers: one for the website, one for GBP, one for print if you mail. That's the raw material for every honest report you'll ever run.

The same logic extends to Local Services Ads, each location runs its own service area and review base, and to landing pages: a real page per location with local proof, not a /locations dropdown.

How do budgets work per location?

Set each location's budget against its own stage, not a company-wide average. A defending, mature location might run 5–8% of its revenue in marketing; a launch-mode location several times that for its first seasons (illustrative: set the real number with the budget guide). Two rules keep it sane:

• Budgets are per-location commitments, not a pool. A pool always drains toward the location whose manager asks loudest.
• Pacing is tracked per location. Company-wide pacing can look perfect while one office is 40% overspent and another went dark in March. Budget pacing per location makes the drift visible in days, not at year-end.

What is a shared playbook, and what stays local?

The playbook is the part you build once and run everywhere: campaign structures, ad creative, offer calendars, review-request timing, quote follow-up sequences. The local layer is the data those plays run on: each location's client list, service area, completed visits, and reviews. When a visit closes in Springfield, the review request and the neighborhood campaign fire around that job with that location's number on them: same play, local fuel. This is the same franchise logic we laid out in the franchise marketing playbook, and it works identically for company-owned branches.

Decision	Per location	Shared / central
Google Business Profile	Yes: one per address	Never shared
Tracking numbers	Yes: per location, per channel	None
Ad campaigns & budgets	Yes: own geo, own budget	Shared account structure
Creative & offers	Local proof swapped in	Built centrally
Automations & sequences	Local data feeds them	One playbook
Reporting	One row per location	One roll-up view

What does roll-up reporting look like?

One screen, one row per location: spend, leads, cost per lead, booked revenue, budget pacing: all pulled from tracking numbers and synced CRM data, not from location managers' memories. Because the client data syncs from Service Autopilot with location attached, "booked revenue by location by source" stops being a quarterly archaeology project and becomes a dashboard. The roll-up earns its keep by answering two questions fast: which location needs help this week, and which location found a play worth copying. When one office's review velocity or lead cost breaks away from the pack, that's not noise: that's the next playbook page.

Does Service Autopilot need to be set up a certain way?

Less than you'd think. Some operators run one Service Autopilot org with locations separated by tags and service areas; others run an account per entity. Both work, because the marketing layer runs on a data sync: what matters is only that each client record can be attributed to a location. If your current setup can't answer "which location does this client belong to?", fix that before spending on anything else; it's the multi-location version of database cleanup.

Who shouldn't run this model?

Honestly: single-location companies, and second locations younger than about six months. If location two just opened, it doesn't need an operating model: it needs one GBP, one tracking number, launch-weighted spend, and your full attention. Bolt on the roll-up when there's something to roll up. And if your locations are really one service area with two shops ten miles apart, run it as one market; splitting assets that share a city creates the confusion this model exists to prevent. Franchisors have an extra layer of brand-control questions we cover separately on the franchise systems page.

Questions owners ask us

Should each location have its own Google Business Profile?

Yes: one verified profile per physical address, each with its own reviews and tracking number. It's the single highest-leverage move in multi-location local marketing.

One Service Autopilot account or one per location?

Either works. What matters is that a data sync can tell which client belongs to which location: that's what powers per-location audiences, suppression, and reporting.

How should budget split across locations?

By capacity and growth stage, not evenly: a launch location may run several times a mature location's percentage. Track pacing per location so drift shows up early.

Can LSAs run per location?

Yes: each location runs its own service area, reviews, and budget. Per-location GBPs make this cleaner since LSA verification hangs off the profile.

What should the roll-up show?

Spend, leads, cost per lead, booked revenue, and pacing: one row per location, from tracking data rather than self-reporting.

The takeaway: local assets, central brain. Give every location its own GBP, numbers, and budget; keep one playbook and one honest roll-up. Most multi-location marketing pain is one of those four pieces missing, not a spend problem.

Set it up this quarter

1. Verify a Google Business Profile for every physical location; separate the reviews and photos.
2. Issue per-location tracking numbers for website, GBP, and print.
3. Confirm every Service Autopilot client record attributes to a location: fix that first if not.
4. Set per-location budgets by stage, and turn on per-location pacing.
5. Build the one-page roll-up: spend, leads, CPL, booked revenue, pacing, one row per location.