Intern
What you actually do
Logins, queue, one ship, five lines. You sequence. You do not screenshot.
Library / System / Analytics is a weekly operating habit, not a dashboard hobby
Intelligence as an operating layer is a loop: connect GSC, GA4, and the live site (and GHL when the question is pipeline), rank what to fix, publish, link, or measure, ship on a boring cadence, write five lines on what moved. The leak is every number feeling urgent — technical issues, near-page-one URLs, new content, AI search as a religion — so nothing is sequenced. This hub is the habit, not a Looker build.
Intelligence as an operating layer is a loop: connect GSC, GA4, and the live site (and GHL when the question is pipeline), rank what to fix, publish, link, or measure, ship on a boring cadence, write five lines on what moved. The leak is every number feeling urgent — technical issues, near-page-one URLs, new content, AI search as a religion — so nothing is sequenced. This hub is the habit, not a Looker build.
Queries that map to revenue beat branded vanity. Park ego terms. They can exist; they do not jump the queue.
Pages stuck in 8–20 are often the fastest work. New URLs are slower. The hobby is launching. The habit is lifting.
GA4 landings that bounce after ads are often a CRM problem (dead thank-you) dressed as a content problem. Check the handoff.
A dashboard with no action is theatre. Fifteen minutes, one decision, or write hold.
AI search does not need a new department. Structured pages, Q&A, and links are the same loop.
Intern
Logins, queue, one ship, five lines. You sequence. You do not screenshot.
Operator
Loop over tools. Revenue-proximate queue. Handoff vs content. Protect cadence from religion.
CEO
Intelligence is a habit that changes work. Until five lines and a queue exist, more data products are more hobby.
GSC, GA4, live URL, GHL Monday numbers (when relevant), ranked queue, five-line log, cadence, vanity-query parking lot.
GSC position/query → decision: fix title, link, or leave
GA4 landing + bounce after a campaign → CRM/handoff check as often as content check
GHL write-in/show rate → do not scale traffic if these are broken
Five-line log → next week’s one job
GSC, GA4, sitemap/live site. GHL scoreboard if you spend to forms. Access for the intern, not only an agency.
Why: Agency-only logins are how the habit never lands in the company.
Done when: Intern can open GSC and GA4 without asking Slack.
Mix: 8–20 URLs, broken handoffs, one technical if it blocks, one new gap. Not fifty. Rank by revenue proximity.
Why: An infinite backlog is how you hide from shipping.
Done when: Ten items, ordered. The rest is parking lot.
Weekly: complete item one or a defined slice. Do not start item four.
Why: Parallel 'urgency' is the original leak.
Done when: The log shows one completion.
What moved, what did not, what we will do, what we will not, what we need from the CEO (usually protection).
Why: Decks substitute for shipping. Five lines compound.
Done when: This week’s five lines exist in a dated note.
New 'AI SEO' tools and branded-vanity panics go to the parking lot unless they beat item one on revenue proximity.
Why: Interrupts are how the loop dies.
Done when: A parked request with a date. Item one still shipped.
Get logins. Pull 8–20 URLs and one campaign landing. Check if bounce is a dead thank-you. Write a queue of ten. Ship item one. Five lines. You are not building a Looker.
Another analytics SaaS, an AI SEO auditor, or more content volume until the weekly loop exists and traffic is not scaled onto a broken handoff. Tools on an unowned queue are hobbies.
GA4 pretty. GSC unopened. Agency PDF. Everything urgent. No five lines. Traffic onto dead thank-yous. That is a dashboard hobby.
Intern has access. Queue of ten. One ship per week. Five lines. Vanity parked. Handoff checked when landings bounce after ads.
Not to maintain a hobby dashboard. An intern plus a ranked queue is the layer. Analysts later if volume demands, still on the same loop.
A PDF is not a loop unless it changes next week’s work and you can run it if the agency pauses.
Then the first queue item may be 'make one conversion event true'. Mess is not a reason to skip the habit. It is the first job.
This week
This week: access, queue of ten, ship one, five lines, park one vanity interrupt. No new dashboard.
Until stages, fields, and write-in have owners, the sub-account is a filing cabinet.
Read ↗If every automation can fire, none of them is an operating system.
Read ↗If the thank-you does not change the contact, you paid for a brochure.
Read ↗Broadcasts feel like work. A spine with manners is the product.
Read ↗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.
Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.