Library / coaching franchises / Coaching franchises inherit a brand and whatever HQ forgot to lock

coaching franchisesHow to wire it

Coaching franchises inherit a brand and whatever HQ forgot to lockLocations will edit sacred pipelines unless permissions and a change log exist.

Coaching franchise HQ ships a snapshot. Locations invent stages named after personalities. Roll-up at QBR is a negotiation. This vertical wires locked discovery/enroll jobs, local offer names, a pilot location, and HQ speed-to-lead on shared definitions — not a zip emailed on Friday.

00

The short version

Intern through CEO

Coaching franchise HQ ships a snapshot. Locations invent stages named after personalities. Roll-up at QBR is a negotiation. This vertical wires locked discovery/enroll jobs, local offer names, a pilot location, and HQ speed-to-lead on shared definitions — not a zip emailed on Friday.

  1. 01

    The weekly HQ number is % of locations with write-in true on a test, plus blended show rate only after definitions match. A blended number on drifted stages is fiction.

  2. 02

    Coaches will create 'Mary’s pipeline'. That is a ticket, not creativity.

  3. 03

    Training is inside day-1: test form, test book, who owns replies. A Zoom after go-live is how WhatsApp wins.

  4. 04

    Stolen leads need timestamps, not culture talks.

  5. 05

    Two brands in one sub-account without a brand field will mix automations. Brand is first-class if you have it.

Who

Same system. Three jobs.

Read your row

Intern

What you actually do

Pilot and lock tests. You are governance, not a zip sender.

Operator

What you protect

Core locked. Pilot. Version. HQ numbers that mean one thing. Stolen leads visible.

CEO

What you refuse to fund

A franchise CRM is a product. Zip files do not roll up. Locked jobs and a signed pilot are the system.

Wire

How to connect it

Objects, then edges

HQ snapshot version, locked stages (inquiry, discovery booked/held, enrolled), local offer fields, location user roles, routing, stolen-lead visibility, HQ scoreboard, day-1 location checklist.

  1. 01

    Inquiry writes the same stages in every location; local cannot rename them

  2. 02

    Calendly/GHL calendar at location still writes HQ-defined jobs

  3. 03

    Snapshot apply → QA checklist; pilot before fleet

  4. 04

    HQ sees speed-to-lead and show rate with one definition

Steps

Do this in order

Why, then done when
  1. 01

    Lock coaching jobs

    Inquiry, booked, held, enrolled, lost. Print. Roles prevent rename.

    Why: Franchise reporting dies on nicknames.

    Done when: Location test user cannot rename Discovery booked.

  2. 02

    Name local exceptions

    Offer nickname, hours, GBP, users. Requests to change jobs go to HQ SLA.

    Why: Unnamed exceptions become sacred locally.

    Done when: Page exists.

  3. 03

    Pilot one franchisee

    Apply, QA, train, then two — not thirty.

    Why: Fleet blast is trust death.

    Done when: Signed checklist.

  4. 04

    HQ scoreboard

    Speed-to-lead, show rate, enroll. Same definitions.

    Why: Spreadsheet rituals at QBR mean the CRM failed.

    Done when: A weekly view that does not need translation.

  5. 05

    Change log

    Version, notify, breaking vs safe.

    Why: Surprise updates train shadow CRM.

    Done when: Last change has a row.

What an intern at HQ should wire first

Locked vs local page. Permissions test. Pilot checklist. Scoreboard definitions. You do not customize Site 12’s moods.

What the franchisor should refuse

Friday snapshot to all, more franchisees on GHL, or a custom pipeline for a loud owner. Growth on drift is QBR fiction.

The usual failure

Zip. Everyone admin. WhatsApp. HQ dashboard nobody believes. That is a brand with 40 CRMs.

The weekly number

Locations passing a write-in test, show rate on locked definitions, snapshot version adoption.

Why

Questions people actually ask

Pushback is normal

Each coach’s method is different.

Method can be local notes. Jobs cannot. Discovery held is held.

HQ doesn’t want to be the bottleneck.

SLA on requests. Not everyone-admin.

Can locations keep their own Calendly?

Yes if it writes locked stages. No if it is a second database.

This week

This week: lock jobs, local page, one pilot, permissions, definitions sheet. No fleet blast.

franchise systems

Other verticals in this lane

coaching franchises
dental groups and DSOs

Dental groups wire recare as a machine, not a card box at each front desk

New patient, recare, and unscheduled treatment are three journeys. One 'we miss you' is not a DSO.

Read ↗
home services franchises

Home services franchises wire speed-to-lead as the product HQ can actually lock

Call volume is national. Booking is local. Drift is how you pay for ads twice.

Read ↗
fitness franchises

Fitness franchises wire intro → member vs ghost, not a binder at the front desk

Day 7–21 after intro predicts member vs lapse. Club WhatsApp is not that clock.

Read ↗

All franchise systems · coaches training brands academies

Working notes

Multi-Coach CRM Map

What HQ should lock, what locations can change, and how rollout actually works. Request the file. It arrives by email — not a public dump, not a drip of slogans.

Request the notes ↗
Next

If the leak is expensive, talk.

Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.