Install the operating system

BeginnerDuration ~10 min read + 30 min setupTools Notion (coverage tracker), Claude Code (daily prep), The direction memo (Library)

The big idea: you don’t decide what to do each day — the routine decides, so every one of your limited hours goes to executing, never to figuring out what to execute.

The analogy

A pilot with ten thousand hours still walks the same pre-flight checklist before every single flight. Not because she’s forgotten how to fly. Because the checklist means the flight never depends on her memory, her mood, or whether she slept well. Fuel, flaps, instruments — checked in the same order, every time. By the time she’s in the seat, everything is staged, and all of her attention is free for the one thing only a pilot can do: fly the plane.

Amateurs wake up and decide what today looks like. Professionals let the routine decide, and spend their judgment where judgment actually matters.

The last quarter, WPH flew without a checklist. Busy weeks, real work, and the important actions kept getting lost in the cockpit. This lesson installs the checklist. It comes before any theory for the same reason flight school starts with the walk-around: it prevents the most common crash, which here is drift — a week that felt full and moved zero accounts.

How it works

Start with the shape of a day. You get an hour, maybe two. The rule that makes that enough: you never open your window to prepare, only to execute. Claude’s job, before your window ever opens, is to have the day staged like a cockpit — the signal digest read for you, the post drafted, the interview prep done, the follow-up queue loaded, the account context in front of you. Your job inside the window is only the moves that must be human: posting under your name, conversations, asks, rooms, calls. If you ever catch yourself researching, formatting, or “getting organized” inside your window, the checklist failed. We fix the prep, not your discipline.

The week has a shape too. Each weekday has one named job — an ask day, a post day, a build block — so you never stand at the start of a morning wondering what kind of day it is. The calendar already decided. The full day-by-day cadence lives in the details below and in the direction memo; you don’t need to memorize it, you need to trust it. Julian handles video edits and cleanup. He doesn’t touch outreach.

Then Friday counts. Every account on the board sits at exactly one stage: unaware, aware, met, consumed research, multi-threaded, diagnostic, won. The Friday review is fifteen minutes and asks one question: which accounts moved right this week, and because of what? That board is your 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. This is also where signals come in. A signal is a reason to reach out that came from them — a new digital-head hire, a model launch, a site relaunch. Signal-timed touches land as relevance, not interruption.

Two more parts of the checklist, briefly. First, the playbook: every play you run gets captured in one living document as a procedure — what triggered it, who ran it, what was said, what happened. That document is quietly the second product of the next two months, because it’s the thing that makes the first sales hire possible. Nobody can inherit an undocumented founder motion; they can inherit procedures with conversion data. Lesson 3.7 turns that document into the hire itself.

Second, the honesty rule, and this one is load-bearing. Stages are earned, not aspirational. “Met” means met. “Consumed research” means they asked for it or engaged with it, not that you sent it. The old reporting system died partly because metrics drifted into counting output. Coverage counts their behavior, and their behavior can’t be inflated by working harder on the wrong thing.

The pattern

Claude preps, Richard executes, Friday counts. Prep always happens before the window opens. The window is execution only — human-only moves. Friday’s review counts what moved on the scoreboard and writes the play down. Lose any of the three and the week drifts.

The receipts (evidence, if you want it)

• Why this comes first: the audit found founder-gated actions stalling for ten straight weeks while the system built infrastructure around them (INTERNAL — the honest audit, Sections 3–4). The cadence exists to make those actions few, small, and pre-staged.
• Why coverage, not responses: with ~95% of buyers out-of-market at any time (Ehrenberg-Bass / LinkedIn B2B Institute — INDEPENDENT), weekly reply counts measure noise; per-account stage movement measures the thing that predicts the win. Full trail: the tiny-TAM evidence.
• Why the honesty rule: the previous reporting system drifted into counting output (posts shipped, tasks done) and stopped predicting anything (INTERNAL — status archive).
• The full cadence table and the first ten working days: the direction memo.

Your one move

Stand up the coverage tracker in Notion. Every account name you currently have, each assigned an honest stage. Most will land at unaware or aware — good, that’s the true baseline, and a flattering baseline would poison every Friday review after it. Thirty minutes. Done means: the tracker exists and no stage is generous.

The needle: the Friday review really asks one question: did this week cause a conversation, or move an account closer to one? A full week that can’t answer that is the old pattern back again.

Want to go further? (This is the Level 0 capstone)

Run the checklist in full, once, this week:

1. Create playbook.md v0 with the procedure template — trigger → owner → script → result → conversion — and one entry: this week.
2. Run one full cadence week, with Claude preparing each day’s brief the session before. 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 contacts, plus 15 minutes of comments on Tier 1 people. Thursday: benchmark work block, or dinner prep in event weeks. Friday: one named referral ask, then the review.
3. 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. Who does what in the daily loop?

   Julian runs outreach while Richard makes contentRichard does research and drafting; Claude handles the human conversationsClaude preps everything before Richard's window opens — digests, drafts, prep docs, follow-up queues — and Richard spends his hour or two only on human-only movesThe whole thing is automated end to end

2. Every play you run gets written into the playbook doc as it happens. Why bother?

   Claude needs written instructions to run the playsIt makes the weekly reports longerA documented playbook with conversion data is what makes the first sales hire possible — you can't hand someone an undocumented founder motionCompliance

3. A whole week goes by with zero replies from any account. Failed week?

   Yes — no responses means no progressYes, unless a deal closedNot necessarily — if accounts moved right on the scoreboard (met, read the research, know two of you), coverage grew, and coverage is what predicts the winDepends on how many posts went out

4. You emailed the benchmark report to an account yesterday. Can you move them to "consumed research"?

   No — stages track their behavior, not yours. They move when they request it or engage with it, not when you hit sendYes — sending it countsOnly if they don't bounce itYes, as long as the email was personalized

Check answers

You can move on when… the tracker is live, every account has a stage, and you’d be comfortable showing the stages to the account themselves — that’s the honesty test.

Mark this lesson complete

Go deeper

• The pipeline rulebook — the strict stage definitions and movement rules the Friday review runs on.

• The signal — the full 80/20 reasoning behind the whole cadence.

• the direction memo — 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.