The franchise marketing playbook for home service companies: consistency at HQ, hustle in the territory

Every franchise system in home service companies eventually hits the same wall: the brand that was supposed to be the product starts looking different in every market, nobody at HQ can say what the system spent last month, and your best operators are moonlighting as amateur media buyers. The fix isn't more brand-book enforcement emails. It's a cleaner split of who owns what.

The dividing line: build once vs. execute locally

The healthiest franchise marketing systems draw one line and defend it. Anything that defines the brand, or that benefits from being built once and reused fifty times, belongs to corporate. Anything that depends on being physically in the territory belongs to the franchisee.

Corporate should own

• Brand standards and creative templates: logos, colors, voice, ad creative, postcard designs. Built once, locked, localized by variable (city, phone, offer), not by redesign.
• Pricing architecture: how programs are packaged and quoted. Territories tune the numbers to their market; they don't invent new structures.
• Campaign and offer templates: the search campaigns, negative keyword lists, and seasonal offers that already work. Territory #51 should inherit ten years of learning on day one.
• The content engine: one editorial calendar, brand-consistent articles and pages published out to every location's site.
• The tech stack and the reporting standard: one platform, one definition of a lead, one dashboard everyone reads the same way.

Territories should own

• Their Google Business Profile presence: photos of real local jobs, posts, Q&A, and review replies that sound like a neighbor, not a brand.
• Review generation: reviews are earned on driveways. Corporate supplies the automation; the territory supplies the five-star work.
• Neighborhood presence: which streets get the postcard blitz, where the door-to-door reps knock, which HOAs get a proposal.
• Local relationships and sponsorships: the ball team, the home show booth, the chamber. HQ can't fake local.
• Their local budget: within system minimums, the franchisee decides how hard to push growth in their own market.

Notice what's not on the territory list: building websites, writing ads, choosing keywords, or picking software. When franchisees do those things, you don't get fifty experiments. You get fifty liabilities.

The brand-consistency traps

Two failure modes account for most of the brand erosion we see in outdoor-trades systems:

Fifty logo variants. It starts innocently: a franchisee's print shop "cleans up" the logo, another stretches it to fit a truck door, a third adds a drop shadow. Three years later, corporate runs a brand audit and finds the logo in five colorways and the tagline in three tenses. The cure isn't policing; it's supply. When corporate provides every asset a location could need (ready-made, localized, one click away), nobody opens Canva.

Rogue Facebook pages. A franchisee's spouse starts a page, posts for two months, and abandons it. Now there's an unclaimed, half-dead page outranking the real one, quoting 2019 prices. Multiply across a system and prospects can't tell which pages are real. Claim every page centrally, grant local posting rights, and retire the orphans, then make the official page useful enough that nobody needs a shadow one.

The tech-stack problem nobody sees until it hurts

Brand consistency is visible. Infrastructure inconsistency is worse, because you find it during a dispute or a resale:

• Tracking numbers. Every location needs its own tracking numbers, provisioned and owned by the system, not by whichever local agency set them up. When a franchisee's agency leaves and takes the number that's been on 40,000 postcards, that territory's call volume walks out with it. (The math on lost calls is ugly.)
• GBP ownership. The single most common mess we untangle: a location's Google Business Profile owned by an ex-employee's Gmail or a fired agency. Every profile should have the franchise entity as primary owner and corporate as a manager, full stop.
• LSA account structure. Local Services Ads run per location, with per-location verification (background checks, insurance, licenses where applicable). Systems that treat LSA as an afterthought discover the verification lead time only after the grand opening.
• The FSM layer. Many systems run a separate RealGreen or Service Autopilot instance per franchisee. That's fine operationally until marketing needs data from all of them. Solve for multi-instance access early; we wrote about the RealGreen version of this in One Playbook, Fifty Instances.

Roll-up reporting franchisees actually accept

Franchisees distrust reporting for one rational reason: it's usually used against them, assembled from numbers they can't verify. The reporting that gets accepted has three properties:

• Same numbers, both altitudes. The franchisee's dashboard and corporate's roll-up read from the same data. If corporate sees a cost per lead the franchisee can't reproduce, the meeting is over before it starts.
• Leads they can audit. Every lead ties to a recorded call, a form, or a quote, with the recording attached. When a location claims "the leads are junk," everyone can listen to the same ten calls and settle it in minutes.
• Pacing, not autopsies. Monthly retrospectives tell a franchisee what already went wrong. Daily budget pacing with anomaly flags tells them while it's fixable, which is the difference between reporting as surveillance and reporting as support.

Ad funds and co-op: the frameworks

Every system structures money differently, but most land on some blend of three layers. Treat these as common patterns, not prescriptions. Your FDD and your franchise attorney get the final word:

• A national/brand fund, commonly 1–2% of gross receipts, for system-level assets: the brand campaigns, the content engine, the website platform, the things that make sense to build once.
• A required local minimum, often in the 2–5% range, that each franchisee must spend in their own territory on approved programs. This is where LSA, local search, and neighborhood marketing live.
• Co-op matching: corporate matches some portion of local spend on strategic programs (a new-service launch, a market-share push) to steer behavior without mandates.

The framework matters less than the accounting: every dollar should be attributable to a location, a campaign, and a result. Ad funds lose franchisee trust the moment they feel like a black box. And per-location budget tracking is how you keep the box open.

Onboarding a new franchisee in 30 days

If corporate owns the playbook, launching a territory is configuration work. A realistic 30-day sequence: days 1–3, import their customer and job data from the FSM, provision tracking numbers, and start GBP and LSA verification (the longest lead times in the whole launch: never let them wait). Days 4–10, generate city landing pages for every town in the territory from the brand template, wire up forms and call tracking. Days 11–20, clone the templated search campaigns with local geography and budgets, connect review automation to their first completed jobs. Days 21–30, campaigns live, first neighborhood postcards out around the earliest jobs, and the location appears in corporate's roll-up dashboard like it's been there for years. (We go day-by-day, with budgets, in the 90-day launch plan.)

The takeaway: franchise marketing works when corporate owns everything that should be built once (brand, templates, stack, reporting standard) and territories own everything that requires being local. Draw the line, supply both sides generously, and the brand stays whole while fifty markets hustle.

The franchisor's checklist

1. Audit ownership today: every GBP, every tracking number, every Facebook page, owned by the system, not by vendors or ex-employees.
2. Centralize the assets locations keep recreating: templates, offers, campaigns, content.
3. Put every location on one reporting standard where franchisee and corporate see the same numbers.
4. Write the ad-fund rules so every dollar traces to a location and a result.
5. Turn your launch process into a checklist that runs in 30 days, starting with the Google verifications.