Intern
What you actually do
Rail page and two-email test. Checklist before open. You reuse objects. You do not invent tags for the title.
Library / System / Campaigns sit on journeys. The week after is the business.
Workshops, webinars, and launches fail as heroics: a new stack every time, registration celebrated, attendance CSV next week, five offers after, alumni treated as webinar leads. The operating layer is a reusable rail — register, remind, attend, no-show, one offer, account vs participant, UTMs, suppressions — booked before go-live. This hub is that rail, so the next event is a date on a calendar, not a reinvention.
Workshops, webinars, and launches fail as heroics: a new stack every time, registration celebrated, attendance CSV next week, five offers after, alumni treated as webinar leads. The operating layer is a reusable rail — register, remind, attend, no-show, one offer, account vs participant, UTMs, suppressions — booked before go-live. This hub is that rail, so the next event is a date on a calendar, not a reinvention.
The room is not the business. The week after is. Same-day notes beat a Friday recap. The room is already in another meeting.
Reuse the objects. New speaker, same rail. If every event invents a new tag dialect, you do not have a campaign system. You have a scrapbook.
One offer. Five links is unsupervised. Scarcity must be operationally true or serious buyers feel it.
Alumni and past attendees are not a cold list. Launch that cannot coexist with evergreen will eventually have neither.
UTMs that die on the registration page make 'which campaign paid' a campfire story. The rail includes the query string.
Intern
Rail page and two-email test. Checklist before open. You reuse objects. You do not invent tags for the title.
Operator
Journeys under campaigns. Same-day. One offer. Account vs participant. Reuse. Recap in five lines.
CEO
The room is vanity if the week after is unowned. Rail reuse is the asset. Until it exists, every event is a custom tax.
Campaign id, registrant, attendee, no-show, replay, one offer, account vs participant, UTM, suppression vs evergreen, recap owner, reusable calendar.
Registration → GHL contact + campaign field same day
Reminders owned; attendance writes the same day; attendee ≠ no-show email
Same-day one offer; buyer packaged if B2B
Evergreen spines suppressed from launch pulses that would collide
States: registered, reminded, attended, no-show, replay, offered, booked/paid. Campaign id field. Do not add a sixth offer type this week.
Why: Unnamed objects are how each event becomes a new CRM.
Done when: A one-page rail. Next event uses it without new tags.
Zoom/webinar/GHL form → GHL. Attendance threshold. Same-day split workflows. No platform broadcasts as the process.
Why: Platform lists are second databases.
Done when: Two test emails: join vs skip, correct same-day mail.
Copy, offer, owner, suppressions, B2B buyer package. In the calendar as work, not 'when we have time'.
Why: Time after the event is when teams are tired. Unbooked work does not happen.
Done when: A dated checklist completed before registration opens.
Launch pulse excludes in-spine, just-purchased, just-attended where jobs collide. Evergreen stays on.
Why: Trample is how you train the list to ignore both machines.
Done when: Test segment excludes the collisions.
What registered, showed, booked/paid, what broke on write-in. Next date on the same rail. No heroics write-up as a substitute.
Why: Novels after the event are how you avoid fixing the rail.
Done when: Five lines in the campaign record. Next event date set.
Print the rail. Hook the next event’s registration to GHL. Build attendee vs no-show, not a third offer page. Confirm suppressions. You are not designing a new landing theme.
A bigger room, more speakers, or more ads to registration until the rail writes attendance and the week-after is booked. Larger rooms into CSV rituals are larger vanity.
New stack every workshop. Registration in Slack. Attendance next week. Five offers. Alumni in the cold blast. UTMs dead. That is heroics, not a campaign layer.
Next event uses the same objects. Same-day split works. One offer. Week-after booked before go-live. Five-line recap. Evergreen not trampled.
Different topic, same objects. A new funnel is allowed when the job changes (application vs webinar), not when the title changes.
You can ping. The number you manage is show and week-after conversion. Slack balloons are not a scoreboard.
Then GHL registration is still source of truth, or you accepted a CSV ritual. Write the exception. Do not pretend.
This week
This week: freeze the rail, write-in for the next event, same-day split, week-after booked, suppressions. No new offer type.
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
Webinar, workshop, and launch rails that survive the week after the event. 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.