Intern
What you actually do
Pauses and artifacts. Leak sentence alignment. You protect the 90 from extra projects.
Library / System / Ninety days, one leak, weekly ship — not a slide deck with a retainer
Fractional ownership as an operating layer is a sequenced 90 days: one leak (demand, conversion, show-up, delivery, or retention), instrumented if the numbers are untrusted, three projects paused, weekly ship, a scoreboard a human believes, kill criteria, and handoff notes if the operator is not staying forever. The leak is everyone busy, annual roadmap, weekly panic, decks instead of install. This hub is how to run that layer — whether Damir is in the seat or you are installing the habit without a vendor.
Fractional ownership as an operating layer is a sequenced 90 days: one leak (demand, conversion, show-up, delivery, or retention), instrumented if the numbers are untrusted, three projects paused, weekly ship, a scoreboard a human believes, kill criteria, and handoff notes if the operator is not staying forever. The leak is everyone busy, annual roadmap, weekly panic, decks instead of install. This hub is how to run that layer — whether Damir is in the seat or you are installing the habit without a vendor.
Pick the leak that costs the most. Not the most interesting. Not the founder’s hobby. Money, calendar, inbox, or reputation — name the hurt.
If the number is a vibe, do not add traffic, pages, or campaigns. Week one is write-in, event truth, or show rate. Tactics on a vibe scale the leak.
Pause three projects. If you cannot pause, you did not pick. You collected.
Done means a system that runs without the fractional in the room — spec, tests, Monday number — not a longer Notion.
Kill criteria: if X is not true by week 6, we stop this leak and say so. Endless retainers without kill are agencies with better vocabulary.
Intern
Pauses and artifacts. Leak sentence alignment. You protect the 90 from extra projects.
Operator
One leak. Instrument if needed. Ship in the system. Kill and handoff. Refuse second seats on the same 90.
CEO
Ninety days of sequenced ownership is the product. Slides are not. Until pause and kill exist, you are buying anxiety with a calendar.
Chosen leak, baseline number, paused-project list, weekly ship, scoreboard, kill criteria, handoff note, 90-day calendar, owner (fractional or internal).
Pick one leak → all other 'urgent' work parks or dies
Baseline → if untrusted, week 1 is instrument, not tactics
Weekly ship → visible in the system (write-in, flow, rail), not a slide
Day 90 → kill, continue, or handoff; no endless 'phase 2' fog
Hurt + who + the number if known. Two people write it. If they differ, stop and agree.
Why: Teams skip this and jump into settings. Then every person fixes a different problem.
Done when: One shared sentence. No adjectives required.
If you will not defend the number, week 1 is measurement. Do not start a funnel.
Why: Tactics on folklore are how 90 days disappear.
Done when: A number you will say in a meeting, or a dated plan to get it this week.
Write them down. Tell the people. Park vanity content, extra pages, extra tools.
Why: Unpaused work will eat the week.
Done when: Three named pauses. Visible to the CEO.
Each week: something true in GHL/Klaviyo/search loop. Screenshot or test. Slide optional, never the deliverable.
Why: Decks substitute for install.
Done when: Twelve weeks would have twelve artifacts in the system, not twelve PDFs.
Spec pages, test scripts, Monday script, who owns after. Kill criteria dated. Day 90 decision booked on day 1.
Why: Without handoff, you rented a brain. Without kill, you rented hope.
Done when: A stranger can run Monday. Day 90 is on the calendar.
Collect the two sentences of the leak. If they differ, escalate. List work that would violate the pause. Book the Monday slot. You are the keeper of pauses and artifacts, not a second strategist.
A second workstream, a new tool, or an annual roadmap workshop until the 90 has a leak, a baseline, three pauses, and a day-90 date. More work on an unpaused org is anxiety.
Retainer. Busy Slack. Slides. No pause. Numbers untrusted. Day 90 arrives with a longer Notion and the same leak. That is a vendor, not ownership.
One sentence. Defended number or week-1 instrument. Three pauses held. Weekly system artifacts. Day 90 booked. Handoff a stranger could run.
Then you have two owners and two 90s. One seat cannot. 'We’re big' is how both leaks get half-installed.
Then pick write-in or event truth. Everything is a missing spec. The first leak is the model.
Project plans hide pause and kill. This layer makes pause and kill first-class. That is the difference from a deck.
This week
This week: one sentence, baseline or instrument, three pauses, Monday booked, day 90 on the calendar. No second leak.
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
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.
Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.