Marketing ops for RealGreen franchise networks: one playbook, fifty instances

One location on RealGreen is manageable. Fifty franchisees (each with their own instance, their own database, their own logins, and their own opinions about Facebook ads) is a different animal. Here's how the well-run networks turn that sprawl into one marketing operation without stripping franchisees of local ownership.

The multi-instance problem

Franchise networks on RealGreen usually grew one franchisee at a time, and the systems show it. Each location runs its own Service Assistant instance: separate database, separate credentials, separate configuration. Four problems follow:

• No roll-up. Corporate can't answer "how many active customers does the network have?" without emailing fifty owners for exports.
• The login shuffle. National support and sales staff bounce between instances all day. A customer calls the national line. Which instance are they even in?
• Attribution chaos. Source codes drift: one location's "GOOG" is another's "PPC" is a third's "Internet." Network-level marketing ROI becomes guesswork.
• Inconsistent local marketing. Location 12 runs a slick spring campaign; location 31 hasn't updated its Google Business Profile since it opened. Customers see one brand; the brand behaves like fifty companies.

The Chrome-extension pattern

The lowest-effort, highest-relief fix is at the browser level. A Chrome extension that knows every instance in the network can search for a customer across all of them at once and auto-log the user into the right instance: one search, one click, correct database. (This is a real thing our platform does. It started as an internal tool for exactly this pain and became one of the most-loved features among franchise support teams.)

The math is unglamorous but real: if national support handles 60 cross-location calls a day and the extension saves three minutes per call, that's ~3 staff-hours a day recovered: call it most of a headcount over a year. And it means corporate can finally spot-check any location's data without a credentials scavenger hunt.

The deeper fix runs alongside it: replicate each instance nightly into one warehouse (the same replication pattern that solves API limits for a single company solves reporting for a network), so roll-up numbers come from data, not from asking.

Centralized brand, local execution

The franchise marketing trap is treating this as either/or: corporate runs everything (locations feel like billboards) or locations run everything (the brand dissolves). The split that works:

• Corporate owns the assets: creative library, offer calendar, brand-consistent website with localized landing pages generated per market, and the automation playbooks (pre-pay, review requests, condition-code upsells) built once and switched on per location.
• Locations own the execution: their budget, their service area, their Google Business Profile, their local sponsorships, inside guardrails.
• Standardized source codes everywhere, so "what does a lead cost" means the same thing in every market.

We wrote a general version of this in the franchise marketing playbook; the RealGreen-specific advantage is that the automation layer plugs into data every location already generates.

Per-location pacing and roll-up reporting

Fifty locations spending $4,000 a month is a $2.4M annual media budget: run with the rigor of fifty separate hobby projects, at most networks. Two disciplines change that:

• Budget pacing per location: every location's Google, LSA, and Meta spend tracked against plan daily, with anomaly flags when a location's cost per lead doubles or its ads quietly stop. Even catching 5% waste across that budget is $120,000 a year.
• A corporate scorecard: cost per lead, close rate, review velocity, and booked revenue by location in one reporting view. Rankings do what memos can't: no franchisee wants to be 47th two quarters running.

Local presence at scale: pages and profiles

Two assets have to exist per location, and both are where network consistency usually dies:

• Local landing pages. Every location needs city-level pages for its actual service area: same brand system, local proof, local phone number. Built by hand across fifty markets this never finishes; generated from a template with per-market data (the bulk city-page approach in our website system), it's a project measured in weeks, not years.
• Google Business Profiles. Each location owns one, and each needs the weekly care described in our GBP playbook: photos, review responses, posts. Corporate's job is the system (photo pipelines, response templates, an audit dashboard) so that "location 31 hasn't posted since opening" shows up as a red cell on a report, not a surprise during a market visit.

Who pays for what

The money conversation goes smoother with a clean default: the brand fund covers shared infrastructure (platform, creative, playbooks, national reporting) because every location benefits identically. Franchisees fund their local media, with co-op matching (corporate matches a percentage of local spend) to nudge underinvesting markets. And data ownership is explicit both ways: locations see everything about their market; corporate sees the roll-up; nobody's data gets held hostage: the same no-hostage terms we apply to everything.

Rolling it out without a mutiny

Don't mandate fifty locations onto anything on day one. Pilot with 3–5 franchisees of different sizes, run a full season, and measure cost per lead, close rate, and review velocity against network baseline. Publish the numbers internally: franchisees trust other franchisees' results far more than corporate's slides, then roll out in waves. The pilot locations become your internal sales force.

One more rollout rule: keep the franchisee's first experience operational, not strategic. The cross-instance search and the location scorecard deliver value in week one without asking anyone to change how they market. Once owners are using the tools daily, turning on the automation playbook is an upgrade to something they already trust, not a corporate mandate landing on a busy spring.

The takeaway: the network's problem was never missing data: every instance is full of it. It's fragmentation. One search layer, one nightly warehouse, one playbook executed locally, and fifty instances start behaving like one company.

Start here

1. Standardize marketing source codes across every instance this quarter.
2. Stand up cross-instance customer search for national support staff.
3. Replicate all instances nightly into one reporting warehouse.
4. Pick 3–5 pilot locations for the automation playbook (pre-pay, reviews, upsells).
5. Publish a monthly location scorecard, and let the rankings do the talking.