Install the operating system

BeginnerDuration ~30 min read + 60 min setupTools Notion (coverage tracker), Claude Code (daily prep), DIRECTION.md

Why this lesson

The audit’s core finding was that founder-gated actions stall and systems route around them. The antidote is installed before the theory, at recipe depth — the same way a color course front-loads a color-managed project setup because it prevents the most common failure. Here, the most common failure is drift: busy weeks that move zero accounts. This lesson makes drift structurally difficult.

The explainer

The shape of a day. You have 60–120 minutes. The rule that makes that enough: you never open the window to prepare — only to execute. Claude’s job, before your window opens, is to have the day’s brief ready: the signal digest, the drafted post, the interview prep doc, the follow-up queue, the account context. Your job is only the actions that must be human: posting under your name, conversations, asks, rooms, calls. If you ever find yourself researching, formatting, or “getting organized” inside your window, the system has failed and we fix the prep, not your discipline.

The shape of a week. Monday: read the signal digest, pick 3 accounts for personal touches. Tuesday: one interview ask or one recorded interview. Wednesday: one LinkedIn post aimed at the named 250–400, plus 15 minutes of comments on Tier 1 contacts. Thursday: benchmark work block (or dinner prep in event weeks). Friday: one named referral ask, then the 15-minute pipeline review — any account turning toward WPH gets the diagnostic offer, and the week’s plays get logged. Julian handles video edits and cleanup tasks; he does not touch outreach.

The scoreboard. Each of the 80 accounts sits at exactly one stage: unaware → aware → met → consumed research → multi-threaded → diagnostic → won. The weekly review asks one question: which accounts moved right, and because of what? This is the coverage scoreboard, and it replaces every response-rate instinct you have. A week with zero replies but three accounts moved right is a good week. A signal — a new digital-head hire, a model launch, a site relaunch, an executive job change — is the trigger for a personal touch, because signal-timed touches land as relevance, not interruption.

The playbook. Every play you run gets captured in one living document as a procedure: trigger → owner → script/template → what happened → conversion. This is not admin overhead; it is the second product of the next two months. You told us why hiring is currently impossible: there’s no proven, structured acquisition model to hand anyone. The playbook is that model, accumulating one tested play at a time. When a salesperson eventually joins, they inherit procedures with conversion data, not vibes. Lesson 3.7 turns this document into the hire itself.

The honesty rule. The scoreboard only works if stages are earned, not aspirational. “Met” means met. “Consumed research” means they requested or engaged with it, not that it was sent. The previous system’s reporting died partly because metrics drifted into counting output. Coverage counts their behavior, which cannot be inflated by working harder on the wrong thing.

Do it

This is the Level 0 capstone — the cadence runs once, end to end, this week:

1. Stand up the coverage tracker (Notion): all account names you currently have, each assigned an honest stage. Most will be unaware or aware. That’s the true baseline.
2. Create playbook.md v0 with the procedure template (trigger → owner → script → result → conversion) and one entry: this week.
3. Run one full week of the cadence with Claude preparing each day’s brief the session before.
4. Friday: hold the 15-minute review. Log which accounts moved, update the tracker, write the playbook entry.

Terms introduced

Terms introduced in this lesson

• Coverage scoreboard
• Signal
• Playbook

Each term links to the glossary, where it is defined by the way you just used it.

Check

Check yourself

1. What is the division of labor in the daily loop?

   Richard does research and drafting; Claude does the human conversationsJulian runs outreach while Richard creates contentClaude prepares everything (digests, drafts, prep docs, follow-up queues) before Richard's window opens; Richard spends 60–120 min on human-only actionsEverything is automated end to end

2. Why does every play get written into the playbook doc as it runs?

   Because Claude requires written instructionsTo make weekly reports longerFor compliance reasonsBecause a documented, conversion-tracked playbook is what makes the first sales hire possible — undocumented founder motion cannot be handed to anyone

3. A week passes with zero replies from any account. Under the coverage scoreboard, was it a failed week?

   Not necessarily: if accounts moved right (met, consumed research, multi-threaded), coverage grew, which is the metric that predicts the winYes, unless a deal closedIt depends on how many posts were publishedYes — no responses means no progress

Check answers

You can move on when… the weekly cadence has run once end to end: tracker live with honest stages, playbook v0 with one real entry, and a Friday review held.

Mark this lesson complete

Go deeper

• DIRECTION.md — the full cadence table and the first ten working days.
• Next up: 1.1 · How enterprise buyers buy — the buying reality everything above is built on.