Intern
What you actually do
Day one: one theme sentence. Out-of-scope list. Kill criteria. Do not start three workstreams. An intern can run the weekly log. A CEO protects the theme.
Library / DTC brands / 90-day growth sprint
Event supply is seasonal and repeatable. Campaigns should not invent it every year.
Read it once, then stop negotiating with it. 90-day growth sprint for event supply brands is a wiring job: theme → cadence → kill → review. 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.
Event supply brands do not have a 90-day growth sprint problem because they lack Growth systems. They have it because roadmaps are annual. Execution is weekly panic.
Wire these objects first: One theme, weekly ship cadence, kill criteria, review that changes next month, owner, artifact in GHL or the tracker of record.
Then these edges, in order: Theme → all live campaigns/workflows must map to it or wait · Weekly ship → logged on the record; Slack is not the archive · Kill criteria → a metric and a date; dead work is marked killed, not 'paused forever' · Month review → next 30 days change; roadmap is not annual wallpaper
Done looks like a test you can repeat: Write this week's ship and the kill number. On a test project, mark something killed with a reason. If nothing can be killed, you do not have a sprint — you have a backlog. Confirm next month's list changed after a review.
Start here: Post-purchase asks when the next event is. A reminder before that window. Flows stay on in peak.
Event supply brands already have Growth systems. The leak is not a missing feature. Roadmaps are annual. Execution is weekly panic. 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 theme, weekly ship cadence, kill criteria, review that changes next month, owner, artifact in GHL or the tracker of record. Then connect these edges, in order: Theme → all live campaigns/workflows must map to it or wait · Weekly ship → logged on the record; Slack is not the archive · Kill criteria → a metric and a date; dead work is marked killed, not 'paused forever' · Month review → next 30 days change; roadmap is not annual wallpaper. If you skip an edge, the next one is decoration. If you add a Growth systems feature first, you usually skip an edge without noticing.
Prove it with a test, not a screenshot. Write this week's ship and the kill number. On a test project, mark something killed with a reason. If nothing can be killed, you do not have a sprint — you have a backlog. Confirm next month's list changed after a review. How you know it worked on the board: Themes is 1 (not a portfolio of panic). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Post-purchase asks when the next event is. A reminder before that window. Flows stay on in peak. An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: one theme sentence. Out-of-scope list. Kill criteria. Do not start three workstreams. An intern can run the weekly log. A CEO protects the theme.
Operator
You already feel roadmaps are annual. execution is weekly panic. Event supply is seasonal and repeatable. Campaigns should not invent it every year. Protect one sequence for 90 days. The four moves are theme → cadence → kill → review. The edges are Theme → all live campaigns/workflows must map to it or wait then Weekly ship → logged on the record; Slack is not the archive. The next event date is the second order. If you only captured the SKU, you rented a customer.
CEO
This is a money leak, not a preference about tools. Roadmaps are annual. Until themes is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Theme → all live campaigns/workflows must map to it or wait.
Before
Tuesday. Someone among event supply brands. Event supply is seasonal and repeatable. Campaigns should not invent it every year. Growth systems 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. The next event date is the second order. If you only captured the SKU, you rented a customer. Theme → all live campaigns/workflows must map to it or wait The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in event supply brands already paid for Growth systems. Event supply is seasonal and repeatable. Campaigns should not invent it every year. 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. One theme for 90 days. Prove write-in: Write this week's ship and the kill number. On a test project, mark something killed with a reason. If nothing can be killed, you do not have a sprint — you have a backlog. Confirm next month's list changed after a review. This week is one move: Post-purchase asks when the next event is. A reminder before that window. Flows stay on in peak. If that feels too small, that is the point. Operators fail by starting at move four.
The leak
Roadmaps are annual. Execution is weekly panic. If nothing can be paused, there is no strategy.
The system
One theme for 90 days. Weekly shipping cadence. Kill criteria for bad work. A review that changes next month.
Choose the leak. Instrument it. Pause three things. Ship weekly. Review monthly and be willing to kill a workstream that is not moving the number. That is a sprint. A roadmap PDF is a wish.
Vanity KPIs (followers, sends, 'awareness') do not get a seat unless they map to the leak. Otherwise the sprint becomes a content calendar with extra meetings.
The next event date is the second order. If you only captured the SKU, you rented a customer.
Annual roadmaps do not execute. Weekly panic does. A 90-day sprint is one theme, a ship cadence, and kill criteria. The objects are the theme (constraint), the weekly artifact (what shipped), and the number you will defend. Wire tools to that, not the other way around. If GHL, Klaviyo, and ads each have their own 'priorities', you have three sprints and no company sprint.
Kill criteria make the system honest. If a page, a flow, or a campaign cannot name the number that would stop it, it will live forever as zombie work. The review changes next month — otherwise you are journaling. Write ships and kills on a record a stranger can read. Handoff inside 90 days should not require the founder's memory.
Two databases: the board in a meeting deck and the actual calendars of the team. Pick one place the sprint lives. The intern updates the weekly log. They do not add a new OKR framework. If a second theme appears in week three, the first theme was never a constraint. Stop the second. That is the wire.
One theme, weekly ship cadence, kill criteria, review that changes next month, owner, artifact in GHL or the tracker of record.
Theme → all live campaigns/workflows must map to it or wait
Weekly ship → logged on the record; Slack is not the archive
Kill criteria → a metric and a date; dead work is marked killed, not 'paused forever'
Month review → next 30 days change; roadmap is not annual wallpaper
Write this week's ship and the kill number. On a test project, mark something killed with a reason. If nothing can be killed, you do not have a sprint — you have a backlog. Confirm next month's list changed after a review.
Day one: one theme sentence. Out-of-scope list. Kill criteria. Do not start three workstreams. An intern can run the weekly log. A CEO protects the theme.
One sentence. 90 days.
Something live every week.
Criteria written on day one.
Monthly: keep, kill, change. Next month is different if the number did not move.
On one line, for event supply brands: Roadmaps are annual. Execution is weekly panic. 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 theme, weekly ship cadence, kill criteria, review that changes next month, owner, artifact in GHL or the tracker of record.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
One sentence. 90 days. Then wire: Theme → all live campaigns/workflows must map to it or wait
Why: Event supply brands cannot skip this edge. Annual roadmaps do not execute. If it is not true, Growth systems is already a second database.
Done when: Theme → all live campaigns/workflows must map to it or wait is true on a test.
Something live every week. Then wire: Weekly ship → logged on the record; Slack is not the archive
Why: Event supply brands skip this and the leak returns as a private language. Kill criteria make the system honest. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Weekly ship → logged on the record; Slack is not the archive is true on a test.
Criteria written on day one. Then wire: Kill criteria → a metric and a date; dead work is marked killed, not 'paused forever'
Why: Event supply brands feel this as Roadmaps are annual. Execution is weekly panic. Two databases: the board in a meeting deck and the actual calendars of the team.
Done when: Kill criteria → a metric and a date; dead work is marked killed, not 'paused forever' is true on a test.
Write this week's ship and the kill number. On a test project, mark something killed with a reason. If nothing can be killed, you do not have a sprint — you have a backlog. Confirm next month's list changed after a review.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Themes (Not a portfolio of panic), then ship (Live, not a deck). 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.
Post-purchase asks when the next event is. A reminder before that window. Flows stay on in peak.
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 theme, weekly ship cadence, kill criteria, review that changes next month, owner, artifact in GHL or the tracker of record.
If objects aren't named, software invents a second database.
Event supply is seasonal and repeatable. Campaigns should not invent it every year.
One sentence. 90 days. Then wire: Theme → all live campaigns/workflows must map to it or wait
Event supply brands cannot skip this edge. Annual roadmaps do not execute. If it is not true, Growth systems is already a second database.
On Growth systems, this means the data model matches how event supply brands actually work — not the snapshot demo. Edge: Weekly ship → logged on the record; Slack is not the archive
Something live every week. Then wire: Weekly ship → logged on the record; Slack is not the archive
Event supply brands skip this and the leak returns as a private language. Kill criteria make the system honest. Spec tags, fields, and states have to be the same objects the next workflow will read.
The next event date is the second order. If you only captured the SKU, you rented a customer.
Criteria written on day one. Then wire: Kill criteria → a metric and a date; dead work is marked killed, not 'paused forever'
Event supply brands feel this as Roadmaps are annual. Execution is weekly panic. Two databases: the board in a meeting deck and the actual calendars of the team.
post-purchase asks when the next event is. A reminder before that window. Flows stay on in peak.
Because the login already exists. Roadmaps are annual. Execution is weekly panic. A new feature on a missing spec is a second database. Finish this edge first: Theme → all live campaigns/workflows must map to it or wait.
Day one: one theme sentence. Out-of-scope list. Kill criteria. Do not start three workstreams. An intern can run the weekly log. A CEO protects the theme. 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. Write this week's ship and the kill number. On a test project, mark something killed with a reason. If nothing can be killed, you do not have a sprint — you have a backlog. Confirm next month's list changed after a review. 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. Kill list (The pause is the strategy) is how you stop the leak returning dressed as a new feature. Pick the leak that costs the most. Instrument it if you do not trust the numbers. Pause three projects that do not serve it. Done means a system that runs without you in the room — not a longer Notion.
More leads into a leak is a more expensive leak. The next event date is the second order. If you only captured the SKU, you rented a customer. Watch themes 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. Post-purchase asks when the next event is. A reminder before that window. Flows stay on in peak. That is the intern version of strategy. Protect it from a second priority for seven days.
Skip this
Leaving objects unnamed because Growth systems is “set up”.
Do this
One theme, weekly ship cadence, kill criteria, review that changes next month, owner, artifact in GHL or the tracker of record.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Theme → all live campaigns/workflows must map to it or wait
Skip this
Calling it done because a screenshot looks busy.
Do this
Write this week's ship and the kill number. On a test project, mark something killed with a reason. If nothing can be killed, you do not have a sprint — you have a backlog. Confirm next month's list changed after a review.
Skip this
Leaving “Review” to chance.
Do this
Monthly: keep, kill, change. Next month is different if the number did not move.
The usual miss
Calling Growth systems “set up” because someone logged in and imported a snapshot.
Do this instead
One sentence. 90 days. Then prove write-in: Write this week's ship and the kill number.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Theme → all live campaigns/workflows must map to it or wait 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
Themes: 1. Not a portfolio of panic. 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.
Themes
1
Not a portfolio of panic
Ship
Weekly
Live, not a deck
Kill list
In writing
The pause is the strategy
This week
post-purchase asks when the next event is. A reminder before that window. Flows stay on in peak.
US operators · Monday reviews, US-friendly hours. The spine is the same — the clock is not.
One theme for 90 days
Weekly shipping cadence
Kill criteria for bad work
A review that changes next month
Want the longer lesson, not the page for this niche? Ninety days, one leak ↗
Working notes
Pick the one sequence that deserves the next 90 days. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Event supply brands do not have a 90-day growth sprint problem because they lack Growth systems. They have it because roadmaps are annual. Execution is weekly panic. Wire these objects first: One theme, weekly ship cadence, kill criteria, review that changes next month, owner, artifact in GHL or the tracker of record. Then these edges, in order: Theme → all live campaigns/workflows must map to it or wait · Weekly ship → logged on the record; Slack is not the archive · Kill criteria → a metric and a date; dead work is marked killed, not 'paused forever' · Month review → next 30 days change; roadmap is not annual wallpaper Done looks like a test you can repeat: Write this week's ship and the kill number. On a test project, mark something killed with a reason. If nothing can be killed, you do not have a sprint — you have a backlog. Confirm next month's list changed after a review. Start here: Post-purchase asks when the next event is. A reminder before that window. Flows stay on in peak.
Roadmaps are annual. Execution is weekly panic. If nothing can be paused, there is no strategy. The next event date is the second order. If you only captured the SKU, you rented a customer.
Before: Tuesday. Someone among event supply brands. Event supply is seasonal and repeatable. Campaigns should not invent it every year. Growth systems 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. The next event date is the second order. If you only captured the SKU, you rented a customer. Theme → all live campaigns/workflows must map to it or wait The next move is written. That is the difference between a login and a system.
Leaving objects unnamed because Growth systems is “set up”. Building a workflow or flow before a writer lands on one contact. Do the four moves instead: theme → cadence → kill → review.
Themes: 1 — Not a portfolio of panic. Then ship (Live, not a deck). If those are folklore, do not add another Growth systems workflow.
post-purchase asks when the next event is. A reminder before that window. Flows stay on in peak.
Because the login already exists. Roadmaps are annual. Execution is weekly panic. A new feature on a missing spec is a second database. Finish this edge first: Theme → all live campaigns/workflows must map to it or wait.
Day one: one theme sentence. Out-of-scope list. Kill criteria. Do not start three workstreams. An intern can run the weekly log. A CEO protects the theme. 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. Write this week's ship and the kill number. On a test project, mark something killed with a reason. If nothing can be killed, you do not have a sprint — you have a backlog. Confirm next month's list changed after a review. 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.
GSC and GA4 sit in silos. Nobody sequences the work.
Read ↗You have access. You do not have a Monday ritual.
Read ↗You write better emails into a worse inbox.
Read ↗Campaigns do the work flows should do.
Read ↗Lapsed buyers get a coupon and a shrug.
Read ↗Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.