Intern
What you actually do
Run steps 01 and 02 this week. Do not add a feature. One page. Pipelines locked. Local hours or offer names allowed if you say so.
Library / Guides / A snapshot is not governance
HQ emails a snapshot. Locations install it. Then everyone edits the sacred pieces. Reporting becomes a negotiation. Governance is the product: what is locked, what is local, how updates ship, how you roll back. This is the lesson franchise operators skip because the demo looked finished.
Lock pipelines, tags, routing, and brand assets at HQ. Name local exceptions on purpose — a field, not a secret edit.
Lock pipelines, tags, routing, and brand assets at HQ. Name local exceptions on purpose — a field, not a secret edit.
Roll out through a real pilot, with training inside the work, not a Zoom after go-live.
Change log. Breaking vs safe updates. Notify locations. Rollback. If those four do not exist, you have a zip file with extra steps.
Intern
Run steps 01 and 02 this week. Do not add a feature. One page. Pipelines locked. Local hours or offer names allowed if you say so.
Operator
Protect the sequence. Roll out through a real pilot, with training inside the work, not a Zoom after go-live.
CEO
Do not fund more traffic or more seats until the scoreboard in this lesson is a number you will defend. Change log. Breaking vs safe updates. Notify locations. Rollback. If those four do not exist, you have a zip file with extra steps.
One page. Pipelines locked. Local hours or offer names allowed if you say so.
Why: Unnamed exceptions become drift.
Done when: A location can point at the page, not at a person.
Real work, not a sandbox nobody uses.
Why: A zip emailed to everyone is how you discover breakages in production.
Done when: The pilot can run a week without HQ Slack.
Sample pipeline, first ten leads, day-1 checklist.
Why: A Zoom after go-live is how new coaches inherit chaos and call it culture.
Done when: Day one is a checklist, not a personality.
Breaking vs safe. Notify. Rollback.
Why: Silent updates break locations and destroy trust in HQ.
Done when: A change log with dates.
Stages mean the same thing in every seat.
Why: Otherwise HQ dashboards are fiction.
Done when: You can compare locations without a translation meeting.
Ask: what can a location not edit? If the answer is 'they shouldn't', they already did.
They will. Then you cannot see stolen leads, you cannot train, and you cannot tell if the brand works. Custom is allowed — named, not accidental.
Locations drift. The brand pays for it.
Open the playbook ↗Working notes
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.
Email and WhatsApp stay open. A call is for installing the system.