Intern
What you actually do
Day one: pick the one scoreboard. Write definitions in a paragraph each. Kill two vanity metrics. Do not build a Looker project. Do not add a second dashboard 'for leadership'.
Library / franchise systems / Reporting rollout
Franchise coaches inherit a brand. They also inherit whatever HQ forgot to systemize.
Read it once, then stop negotiating with it. Reporting rollout for coaching franchises is a wiring job: see it → spec it → install it → review it. Objects, then edges, then one test conversion. You do not need a new tool to start. You need the first writer to land on one contact this week.
Coaching franchises do not have a Reporting rollout problem because they lack Analytics. They have it because dashboards exist. Decisions still happen in Slack.
Wire these objects first: One weekly scoreboard, shared metric definitions, GHL + GA4 (or Klaviyo) sources, vanity demoted list, action log attached to numbers, owner of the Monday meeting.
Then these edges, in order: Definition sheet → each scoreboard number names its object (opportunity stage, GA4 event, Klaviyo metric) · Weekly scoreboard → three to seven numbers; vanity (opens, likes, 'reach') demoted · Number movement → one written action or 'hold'; Slack screenshots are not the action · Owner → named human runs the 15-minute review; tools do not 'own' it
Done looks like a test you can repeat: Hold a fake Monday. Read each scoreboard number and point at the object that produces it. If a number cannot be pointed at, it leaves the board. Write one action. Confirm last week's action is marked done or killed.
Start here: Write what is locked vs local. Pick one pilot location. Do not email a zip to everyone.
Coaching franchises already have Analytics. The leak is not a missing feature. Dashboards exist. Decisions still happen in Slack. Software did not cause it. A missing write-in did: the person exists in one tool and not in the pipeline.
Here is how you actually wire it. Name the objects: One weekly scoreboard, shared metric definitions, GHL + GA4 (or Klaviyo) sources, vanity demoted list, action log attached to numbers, owner of the Monday meeting. Then connect these edges, in order: Definition sheet → each scoreboard number names its object (opportunity stage, GA4 event, Klaviyo metric) · Weekly scoreboard → three to seven numbers; vanity (opens, likes, 'reach') demoted · Number movement → one written action or 'hold'; Slack screenshots are not the action · Owner → named human runs the 15-minute review; tools do not 'own' it. If you skip an edge, the next one is decoration. If you add a Analytics feature first, you usually skip an edge without noticing.
Prove it with a test, not a screenshot. Hold a fake Monday. Read each scoreboard number and point at the object that produces it. If a number cannot be pointed at, it leaves the board. Write one action. Confirm last week's action is marked done or killed. How you know it worked on the board: Owner is named (or it will not run). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Write what is locked vs local. Pick one pilot location. Do not email a zip to everyone. An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: pick the one scoreboard. Write definitions in a paragraph each. Kill two vanity metrics. Do not build a Looker project. Do not add a second dashboard 'for leadership'.
Operator
You already feel dashboards exist. decisions still happen in slack. Franchise coaches inherit a brand. They also inherit whatever HQ forgot to systemize. Protect one sequence for 90 days. The four moves are see it → spec it → install it → review it. The edges are Definition sheet → each scoreboard number names its object (opportunity stage, GA4 event, Klaviyo metric) then Weekly scoreboard → three to seven numbers; vanity (opens, likes, 'reach') demoted. Locations will edit sacred pipelines unless permissions and a change log exist.
CEO
This is a money leak, not a preference about tools. Blog posts go live. Until owner is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Definition sheet → each scoreboard number names its object (opportunity stage, GA4 event, Klaviyo metric).
Before
Tuesday. Someone among coaching franchises. Franchise coaches inherit a brand. They also inherit whatever HQ forgot to systemize. Analytics is open. A colleague asks where a person sits. The answer is a screenshot, a Slack thread, or “I think they’re interested.” The writer (form, calendar, shop, or phone) and the pipeline are two databases.
After
Same Tuesday, after write-in exists. Locations will edit sacred pipelines unless permissions and a change log exist. Definition sheet → each scoreboard number names its object (opportunity stage, GA4 event, Klaviyo metric) The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in coaching franchises already paid for Analytics. Franchise coaches inherit a brand. They also inherit whatever HQ forgot to systemize. They add a page, a form, a calendar. None of it writes into a spec. By Friday the calendar has ghosts and the pipeline still looks like the snapshot.
The fix is not a better template. Search is a monthly loop: connect GSC, GA4, and the live site; rank what to fix, publish, link, and measure; ship on a boring cadence; write five lines on what moved. Prove write-in: Hold a fake Monday. Read each scoreboard number and point at the object that produces it. If a number cannot be pointed at, it leaves the board. Write one action. Confirm last week's action is marked done or killed. This week is one move: Write what is locked vs local. Pick one pilot location. Do not email a zip to everyone. If that feels too small, that is the point. Operators fail by starting at move four.
The leak
Blog posts go live. Search Console is a tab nobody opens. GA4 is a dashboard hobby. Technical issues, near-page-one URLs, and new content all feel urgent, so nothing is sequenced. AI search is treated as a separate religion.
The system
Search is a monthly loop: connect GSC, GA4, and the live site; rank what to fix, publish, link, and measure; ship on a boring cadence; write five lines on what moved. Answer engines cite structured pages — which is the same work, not a new department.
Queries that map to revenue beat branded vanity. Pages stuck in positions 8–20 are often the fastest work. Isolated articles start from zero. Internal links, titles, and Q&A blocks are how expertise becomes findable. More posts without a map is how you stay invisible.
One weekly scoreboard. Definitions are shared.
Locations will edit sacred pipelines unless permissions and a change log exist.
Dashboards exist. Decisions still happen in Slack when definitions are not shared. Reporting rollout is one weekly scoreboard, a definition for each number, vanity demoted, and actions that attach. A number without an object — 'engagement', 'brand health' — cannot be wired. GHL stages, GA4 conversions, Klaviyo placed-order, GSC clicks on money pages: those are objects. If two tools disagree, the disagreement is a ticket, not an average.
Wire the meeting: 15 minutes, owner, three numbers first. Then one action. A dashboard with no action is theatre. Franchise and training teams fail by giving every location a custom dashboard, then HQ cannot roll up. Same definitions, location as a dimension. Vanity is demoted explicitly — list what you will not discuss. Otherwise it will return as a screenshot.
Two databases: GA4 'conversions' that are pageviews, and GHL 'leads' that are form starts. Reconcile on one event that means money or a meeting. The intern updates the scoreboard and the action log. They do not interpret. If the CEO wants a new number, it needs a definition and an object first. Until then it is a story.
One weekly scoreboard, shared metric definitions, GHL + GA4 (or Klaviyo) sources, vanity demoted list, action log attached to numbers, owner of the Monday meeting.
Definition sheet → each scoreboard number names its object (opportunity stage, GA4 event, Klaviyo metric)
Weekly scoreboard → three to seven numbers; vanity (opens, likes, 'reach') demoted
Number movement → one written action or 'hold'; Slack screenshots are not the action
Owner → named human runs the 15-minute review; tools do not 'own' it
Hold a fake Monday. Read each scoreboard number and point at the object that produces it. If a number cannot be pointed at, it leaves the board. Write one action. Confirm last week's action is marked done or killed.
Day one: pick the one scoreboard. Write definitions in a paragraph each. Kill two vanity metrics. Do not build a Looker project. Do not add a second dashboard 'for leadership'.
One weekly scoreboard
Definitions are shared
Vanity metrics are demoted
Actions attach to numbers
On one line, for coaching franchises: Dashboards exist. Decisions still happen in Slack. Add who gets hurt (calendar, cash, inbox, or reputation). If two people write different sentences, you do not agree yet — stop and agree.
Why: Teams skip this and jump into settings. Then every person is fixing a different problem with the same login.
Done when: One sentence. Shared. No adjectives required.
One weekly scoreboard, shared metric definitions, GHL + GA4 (or Klaviyo) sources, vanity demoted list, action log attached to numbers, owner of the Monday meeting.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
One weekly scoreboard Then wire: Definition sheet → each scoreboard number names its object (opportunity stage, GA4 event, Klaviyo metric)
Why: Coaching franchises cannot skip this edge. Dashboards exist. If it is not true, Analytics is already a second database.
Done when: Definition sheet → each scoreboard number names its object (opportunity stage, GA4 event, Klaviyo metric) is true on a test.
Definitions are shared Then wire: Weekly scoreboard → three to seven numbers; vanity (opens, likes, 'reach') demoted
Why: Coaching franchises skip this and the leak returns as a private language. Wire the meeting: 15 minutes, owner, three numbers first. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Weekly scoreboard → three to seven numbers; vanity (opens, likes, 'reach') demoted is true on a test.
Vanity metrics are demoted Then wire: Number movement → one written action or 'hold'; Slack screenshots are not the action
Why: Coaching franchises feel this as Dashboards exist. Decisions still happen in Slack. Two databases: GA4 'conversions' that are pageviews, and GHL 'leads' that are form starts.
Done when: Number movement → one written action or 'hold'; Slack screenshots are not the action is true on a test.
Hold a fake Monday. Read each scoreboard number and point at the object that produces it. If a number cannot be pointed at, it leaves the board. Write one action. Confirm last week's action is marked done or killed.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Owner (Or it will not run), then weekly number (Or reporting is theatre). Write one action or write “hold.” A dashboard with no action is theatre.
Why: What gets reviewed gets run. What only lives in a tool gets ignored the week someone is busy.
Done when: Three numbers. One owner. Fifteen minutes. Actions attach.
Write what is locked vs local. Pick one pilot location. Do not email a zip to everyone.
Why: Operators fail by starting at move four. Interns fail by making a 40-item checklist. CEOs fail by adding a second priority. One proven write-in beats an elegant plan.
Done when: The move is true, or you can name the blocker in one sentence.
One weekly scoreboard, shared metric definitions, GHL + GA4 (or Klaviyo) sources, vanity demoted list, action log attached to numbers, owner of the Monday meeting.
If objects aren't named, software invents a second database.
Franchise coaches inherit a brand. They also inherit whatever HQ forgot to systemize.
One weekly scoreboard Then wire: Definition sheet → each scoreboard number names its object (opportunity stage, GA4 event, Klaviyo metric)
Coaching franchises cannot skip this edge. Dashboards exist. If it is not true, Analytics is already a second database.
On Analytics, this means the data model matches how coaching franchises actually work — not the snapshot demo. Edge: Weekly scoreboard → three to seven numbers; vanity (opens, likes, 'reach') demoted
Definitions are shared Then wire: Weekly scoreboard → three to seven numbers; vanity (opens, likes, 'reach') demoted
Coaching franchises skip this and the leak returns as a private language. Wire the meeting: 15 minutes, owner, three numbers first. Spec tags, fields, and states have to be the same objects the next workflow will read.
Locations will edit sacred pipelines unless permissions and a change log exist.
Vanity metrics are demoted Then wire: Number movement → one written action or 'hold'; Slack screenshots are not the action
Coaching franchises feel this as Dashboards exist. Decisions still happen in Slack. Two databases: GA4 'conversions' that are pageviews, and GHL 'leads' that are form starts.
write what is locked vs local. Pick one pilot location. Do not email a zip to everyone.
Because the login already exists. Blog posts go live. Search Console is a tab nobody opens. A new feature on a missing spec is a second database. Finish this edge first: Definition sheet → each scoreboard number names its object (opportunity stage, GA4 event, Klaviyo metric).
Day one: pick the one scoreboard. Write definitions in a paragraph each. Kill two vanity metrics. Do not build a Looker project. Do not add a second dashboard 'for leadership'. Workflows on unnamed objects fire on folklore. Name contact (or profile), stage or state, and the writer (form, calendar, metric) before any on-switch.
A test conversion creates or updates one person, on the right stage or state, with the fields the next sequence will read. Hold a fake Monday. Read each scoreboard number and point at the object that produces it. If a number cannot be pointed at, it leaves the board. Write one action. Confirm last week's action is marked done or killed. If you merge after the test, identity is wrong — fix that, do not add a dedupe automation.
If it is only in someone's head, a new hire needs a story, reporting cannot be defended, and automations fire on folklore. Writing is how two people mean the same object on Monday.
Because setup was a project, not a review. Stop rule (Or you will scale the leak) is how you stop the leak returning dressed as a new feature. Queries that map to revenue beat branded vanity. Pages stuck in positions 8–20 are often the fastest work. Isolated articles start from zero. Internal links, titles, and Q&A blocks are how expertise becomes findable. More posts without a map is how you stay invisible.
More leads into a leak is a more expensive leak. Locations will edit sacred pipelines unless permissions and a change log exist. Watch owner before you buy traffic. If that number is folklore, acquisition is a vanity spend.
Then you only have time for the objects page and one test conversion. Write what is locked vs local. Pick one pilot location. Do not email a zip to everyone. That is the intern version of strategy. Protect it from a second priority for seven days.
Skip this
Leaving objects unnamed because Analytics is “set up”.
Do this
One weekly scoreboard, shared metric definitions, GHL + GA4 (or Klaviyo) sources, vanity demoted list, action log attached to numbers, owner of the Monday meeting.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Definition sheet → each scoreboard number names its object (opportunity stage, GA4 event, Klaviyo metric)
Skip this
Calling it done because a screenshot looks busy.
Do this
Hold a fake Monday. Read each scoreboard number and point at the object that produces it. If a number cannot be pointed at, it leaves the board. Write one action. Confirm last week's action is marked done or killed.
Skip this
Leaving “Review it” to chance.
Do this
Actions attach to numbers
The usual miss
Calling Analytics “set up” because someone logged in and imported a snapshot.
Do this instead
One weekly scoreboard Then prove write-in: Hold a fake Monday.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Definition sheet → each scoreboard number names its object (opportunity stage, GA4 event, Klaviyo metric) first. Automations on a missing writer invent a second database.
The usual miss
Adding a page, form, flow, or campaign every time last week hurt.
Do this instead
Name which edge is missing. Fix that edge. Hurt is usually a skipped write-in, not a missing asset.
The usual miss
Reporting that nobody will defend in a meeting — screenshots, vanity opens, 'interested' counts.
Do this instead
Owner: Named. Or it will not run. If you cannot say it out loud, it is not a scoreboard.
The usual miss
Hiring or retaining an agency to invent the spec while also running the calendar.
Do this instead
Hands on a known sequence are useful. Hands inside a missing spec pick the louder job (the calendar) and the leak stays.
Owner
Named
Or it will not run
Weekly number
Believed
Or reporting is theatre
Stop rule
Written
Or you will scale the leak
This week
write what is locked vs local. Pick one pilot location. Do not email a zip to everyone.
US operators · Monday reviews, US-friendly hours. The spine is the same — the clock is not.
One weekly scoreboard
Definitions are shared
Vanity metrics are demoted
Actions attach to numbers
Want the longer lesson, not the page for this niche? A CRM login is not a system ↗
Working notes
A 30-day loop for Search Console, content, and priorities — without another generic audit. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Coaching franchises do not have a Reporting rollout problem because they lack Analytics. They have it because dashboards exist. Decisions still happen in Slack. Wire these objects first: One weekly scoreboard, shared metric definitions, GHL + GA4 (or Klaviyo) sources, vanity demoted list, action log attached to numbers, owner of the Monday meeting. Then these edges, in order: Definition sheet → each scoreboard number names its object (opportunity stage, GA4 event, Klaviyo metric) · Weekly scoreboard → three to seven numbers; vanity (opens, likes, 'reach') demoted · Number movement → one written action or 'hold'; Slack screenshots are not the action · Owner → named human runs the 15-minute review; tools do not 'own' it Done looks like a test you can repeat: Hold a fake Monday. Read each scoreboard number and point at the object that produces it. If a number cannot be pointed at, it leaves the board. Write one action. Confirm last week's action is marked done or killed. Start here: Write what is locked vs local. Pick one pilot location. Do not email a zip to everyone.
Blog posts go live. Search Console is a tab nobody opens. GA4 is a dashboard hobby. Technical issues, near-page-one URLs, and new content all feel urgent, so nothing is sequenced. AI search is treated as a separate religion. Locations will edit sacred pipelines unless permissions and a change log exist.
Before: Tuesday. Someone among coaching franchises. Franchise coaches inherit a brand. They also inherit whatever HQ forgot to systemize. Analytics is open. A colleague asks where a person sits. The answer is a screenshot, a Slack thread, or “I think they’re interested.” The writer (form, calendar, shop, or phone) and the pipeline are two databases. After: Same Tuesday, after write-in exists. Locations will edit sacred pipelines unless permissions and a change log exist. Definition sheet → each scoreboard number names its object (opportunity stage, GA4 event, Klaviyo metric) The next move is written. That is the difference between a login and a system.
Leaving objects unnamed because Analytics is “set up”. Building a workflow or flow before a writer lands on one contact. Do the four moves instead: see it → spec it → install it → review it.
Owner: Named — Or it will not run. Then weekly number (Or reporting is theatre). If those are folklore, do not add another Analytics workflow.
write what is locked vs local. Pick one pilot location. Do not email a zip to everyone.
Because the login already exists. Blog posts go live. Search Console is a tab nobody opens. A new feature on a missing spec is a second database. Finish this edge first: Definition sheet → each scoreboard number names its object (opportunity stage, GA4 event, Klaviyo metric).
Day one: pick the one scoreboard. Write definitions in a paragraph each. Kill two vanity metrics. Do not build a Looker project. Do not add a second dashboard 'for leadership'. Workflows on unnamed objects fire on folklore. Name contact (or profile), stage or state, and the writer (form, calendar, metric) before any on-switch.
A test conversion creates or updates one person, on the right stage or state, with the fields the next sequence will read. Hold a fake Monday. Read each scoreboard number and point at the object that produces it. If a number cannot be pointed at, it leaves the board. Write one action. Confirm last week's action is marked done or killed. If you merge after the test, identity is wrong — fix that, do not add a dedupe automation.
If it is only in someone's head, a new hire needs a story, reporting cannot be defended, and automations fire on folklore. Writing is how two people mean the same object on Monday.
The CRM is open. The operating system is not.
Read ↗Stages are labels. Nobody knows what 'won' requires.
Read ↗Tags multiply. Insight does not.
Read ↗The quiz converts. The follow-up is a spreadsheet.
Read ↗Traffic hits a page. The journey after that is improvised.
Read ↗Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.