Intern
What you actually do
If you are the run layer, demand the script. If there is none, that is the ticket — not your failure to 'figure out GHL'.
Library / Compare / Fractional vs in-house: who owns the 90, and what happens at day 91
In-house is right when the work is ongoing operations on a spec that already exists. Fractional is right when you need a 90-day install of a layer you will then run — or you cannot hire the seniority yet. The leak is hiring a junior to 'do GHL' with no map, or retaining a fractional forever so the company never grows a Monday owner. Choose by duration of the leak vs duration of the motion, and wire the handoff on day one.
In-house is right when the work is ongoing operations on a spec that already exists. Fractional is right when you need a 90-day install of a layer you will then run — or you cannot hire the seniority yet. The leak is hiring a junior to 'do GHL' with no map, or retaining a fractional forever so the company never grows a Monday owner. Choose by duration of the leak vs duration of the motion, and wire the handoff on day one.
Fractional is right for a missing layer, a political pause (someone has to say no to extra projects), and a dated exit. It is wrong as a permanent outsourced founder.
In-house is right for repeating Monday, campaign rails, list hygiene, location support. It is wrong as 'we hired, therefore we have a system' when the spec was never written.
Shared leak: nobody with pause power, numbers unowned, Notion as the brain, day 91 fog.
How to choose: is the next 90 install or run? Install: fractional or senior. Run: in-house on a script. If you need both, the fractional writes the script the hire runs — that is a plan, not two owners of the same leak.
Wiring implication: the Monday script and test bookings are the asset. Whoever leaves, those stay. Job descriptions mention the objects, not 'growth'.
Intern
If you are the run layer, demand the script. If there is none, that is the ticket — not your failure to 'figure out GHL'.
Operator
Match motion to install/run. Handoff is a document. One scoreboard owner after overlap.
CEO
Seats and retainers both fail without a 90 and a day 91. Name those. Until then, headcount is not a system.
Leak duration, seat vs 90, seniority, handoff, pause power, scoreboard owner after day 91, hiring plan.
Install layer (missing spec) → fractional or a senior hire with pause power; not a junior plus hope
Run layer (spec exists) → in-house intern/operator on the Monday script; fractional exits or shrinks
Day 91 owner named on day 1
Junior hire still gets a spec — they are not the author by default
Missing write-in/spec = install. Existing scoreboard = run.
Why: Misclassifying is how you hire a coordinator to do a principal’s job.
Done when: One word: install or run.
Person or role. If unknown, hiring is part of the 90, not a surprise.
Why: Unnamed day 91 is how fractional becomes accidental permanent.
Done when: A name or a hire date.
Three pauses visible. Junior in-house without pause cannot install.
Why: Seats without pause eat the 90.
Done when: CEO backs the pause list.
Intern-ready Monday and tests. This is the handoff object.
Why: Verbal culture is not a run layer.
Done when: A document the day-91 owner can execute.
If fractional: calendar the shrink. If hire: they inherit objects, not Slack history.
Why: Endless overlap is two owners, no owner.
Done when: A dated overlap with a single scoreboard owner.
Install, pause power, dated 90, missing seniority. Wiring: artifacts in the system, day-91 owner named, shrink calendar.
Run the script, locations, hygiene, rails that already exist. Wiring: job description = objects, intern tests, not 'own growth' with no map.
No pause, no Monday owner, brain in a person, day 91 unplanned. Hire vs fractional is a staffing tactic. The layer is the script.
Install vs run. Seniority matches install. Day 91 named on day 1. Script is the asset. Do not hire a junior to skip the spec, and do not retain a fractional to skip a Monday owner.
They can run tests and keep pauses if a senior names the leak. They should not be asked to invent the sale map against a founder’s hobby.
Then the founder is the 90, with the same objects: one leak, pauses, Monday. Not 'everyone does a bit'. Poverty is not a reason for zero pause.
Only if that someone has time and pause. A full-time busy person is not a counterpart. They are a second leak.
This week
This week: install vs run, day-91 name, pause list, Monday script started. No hire posting that says 'growth' without objects.
Both can be a filing cabinet. Neither is a system until write-in and stages are jobs.
Read ↗Pretty vs native does not matter if two links both take Discovery.
Read ↗DTC lifecycle and coaching spines are different jobs. Two senders is a tax.
Read ↗Rebuilding from memory every client is how you never productize. Blasting a zip is how you never train.
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.