Email 2 — "I didn't learn it from a course" · Saturday 2026-08-01

Channel: MailerLite broadcast · List: ~590; live segment is the 363 in "Complete | Client Intelligence Brief" Send: Saturday 2026-08-01 — the first Saturday of the Tuesday/Saturday rhythm Status: DRAFTED — awaiting Kathryn. Nothing scheduled, nothing sent. Written by: Sloane, directed by Piper, 2026-07-29

Subject lines

Same register as her 7/6 send (the hour you can't bill) — lowercase, plain.

1. i didn't learn it from a course ← recommended
2. two windows
3. the wall you keep hitting
4. how i actually learned it

Option 1 carries the angle in her own words and is the only one that earns the open on curiosity without manufacturing it. Lowercase i is consistent with the register; if it reads wrong to her, option 2 is the fallback.

Preheader:

1. The smallest version is smaller than you think. ← recommended
2. There was no course.

From / reply-to: Kathryn Brown | Creating Your Plan / kathryn@creatingyourplan.com.

Body

Hi {$name},

Toward the end of last year I wanted to get to Claude Code, and the way in was the terminal.

There was no course. I asked Claude to teach me as I went.

Two windows open at once — a Claude chat on one side, the terminal on the other.

I'd ask the chat what I was looking at, try it, get it wrong, and go back and ask why.

That went on for a while. Then it stopped being hard, and I was doing it on my own.

The thing I hear most when this comes up is some version of: I'd have to hire someone who actually knows this.

You don't.

The tool will work through it alongside you, if you let it — instead of handing it a job and walking away.

The only way past a wall you keep hitting is doing the thing in the smallest way you can, over and over, until it stops feeling like a threat.

And the smallest way is smaller than you think. One task you already do by hand. One conversation.

The goal this week is that it stops being unfamiliar.

If you're the one holding your business up and you've decided you're fine with that, you'll stay exactly where you are. That's a real choice, and plenty of people make it.

If it's stopped being tolerable, find the one move you can make and go make it.

What's the wall for you?

Hit reply — I read every one.

— Kathryn

Word count: 255 as counted by make-paste-ready.py (salutation and sign-off included).

Formatting

Built to the standard from Kathryn's Angle 8 edit (../social/STATUS.md): one sentence per line, blank line between thought-groups, no group longer than 2 lines. Two-sentence groups are used where the second completes the first ("There was no course. I asked Claude to teach me as I went.").

You don't. is isolated on purpose — it's the turn of the argument, and per the standard, solo lines carry the weight at the pivot.

Delivered as clean plain text for MailerLite.

How the sell is handled

This one carries the next step, and it's a reply — not a pitch.

The reasoning: this is the story slot, and the story's whole job is to take down the objection sitting between her buyers and using what they already bought. The earned close is her own — find the one move you can make and go make it — followed by the reply CTA she used verbatim on 7/6 (Hit reply — I read every one.). That closes the loop from Wednesday, which asked for nothing.

Kathryn's framing via Piper: the list's job is to nurture, add value, and sell — the sell being the next thing. Two sends into a rebuilt rhythm, the next thing is a conversation, and the replies tell her what her list is actually stuck on.

One gap, flagged rather than filled. If Kathryn wants a hard next step in the Saturday slot — an event, a product, a call — the paragraph beginning "And the smallest way is smaller than you think" is where it goes, because that is the moment the reader is looking for the smallest concrete thing to do. I did not write it. Naming a product, a price, or a link would mean asserting something live that I have not verified, and this list mostly already bought. Kathryn's call, and it needs a verified URL.

Source trace — every claim

Source: 7/24 Otter, "Client Communication Strategies" (ZVh0w2dlleoVegk9ZX4kUBGmATg). Full transcript read, not grepped.

Vertical stripped. Nothing tax-specific here to begin with — this is Kathryn's own story. Claude and Claude Code are named because they are the actual tools in the source and in her published copy; the terminal is named because it is the thing she learned. No software brand belonging to a reader's practice appears.

Claims cut for lack of a source

• How long it took her. The transcript gives no duration for the learning — only "the beginning of this year, maybe toward the end of last year" as a start point. The email says "that went on for a while" and stops there.
• What she built with it. Tempting and unsourced in this transcript. Cut.
• Any diagnosis of the reader's stalled state — "you've decided it's too technical," "you've been putting it off for months," an invented reader history. None of that is in the source. The only reader-state claim that survives is the one Kathryn actually reports hearing: I'd have to hire someone who knows this. (Same rejection that was applied to the Angle 6 Facebook post on 7/28 — a directed frame requiring a diagnosis the transcript doesn't carry.)
• That her list bought an AI-skills product. True per Piper's brief, but it is not in the transcript and the email does not need it. The copy never references a prior purchase.

QC run — in order

1. Recipient-first. The reader gets a route past the thing stopping them, and one question to answer. Passes.

2. Pride Gate. Her proof, not a client's — the strongest thing she can put in a story slot. Passes.

3. copy-qc.md.

• P1 twinning — one instance caught and removed. Her verbatim line is "I didn't learn it by going to a course. I learned it by asking Claude to help me" — a textbook mirror reversal (same verb, reversed positions), which copy-qc.md cuts on sight with no earned exception even when the writer said it. Rewritten to "There was no course. I asked Claude to teach me as I went." The mirror is gone; the fact is intact. The original phrasing survives only in the subject line, where it is a standalone fragment, not a sentence pair.
• Two more twinning attempts caught in drafting and cut: "You're not trying to be good at it this week — only to make it ordinary" and "Ordinary is the goal this week, not good." Both replaced by the plain statement.
• P1 question→silence→revelation — none.
• Correction-revelation family — one instance total ("The thing I hear most when this comes up is…"), inside the Pattern 7 exception: it is a belief she reports hearing from real clients on tape, not a strawman assigned to the reader. Frequency limit of one per piece respected, so no compound.
• P2 three-beat parallel — none. "ask, try, get it wrong, go back and ask why" is four clauses inside one sentence with varying length, not three parallel sentences.
• P2 quotable-line reach — none survived.
• P3 dramatic beat — exactly one (You don't.).
• P3 rhetorical hand-holding — none. No "here's the thing," no "sound familiar?"
• P3 identical openers — two consecutive "If you're / If it's" at the close, which is two, not three. Under the flag, and the parallel is doing real work: it's the fork Kathryn actually put to people.
• Narrative trackability — one character (Kathryn), one scene, then direct address. No pronoun ambiguity, no unannounced switch, no numbers.
• Read-aloud — passes.

4. linkedin-sentence-editor.md (sentence audit only; the zero-width-space delivery rule is for social schedulers and does not apply to MailerLite).

• R1 end strong — endings land on terminal, went, why, window, this, away, threat, think, hand, conversation, unfamiliar, are, it, make, you, one. Two land on pronouns ("this," "it") and both are deliberate: "someone who actually knows this" is the objection quoted as spoken, and "find the one move you can make and go make it" is her line.
• R3 economy / R8 adverbs — "actually" kept once, inside the quoted objection. "Exactly" kept once in "stay exactly where you are," which is her verbatim.
• R4 no repeats — every line advances.
• R5 vary word choice — "smallest" twice across 253 words, "wall" twice. Under the flag.
• R6 precision — light on purpose. This one works through directness.
• R7 two-comma — the longest sentence carries two.

Banned-list sweep: no coach language, no "walk through," no "honest/honestly," no "firm," no SaaS/builder jargon, no "silent/quiet," no hype, no hashtags. Contractions throughout. No figures, so nothing for the numerals rule to catch; "one move" / "one task" stay spelled, matching her email golden.

Full QC re-run, 2026-07-29

Re-run at Kathryn's instruction ("sloane - copy qc") even though this email was untouched today. The standard moved: the format standard was written this morning and two new gates were added after the Email 1 corrections. Two defects found, both pre-existing — missed by the original pass, not introduced.

Defect 1 — the source-trace quote gate (new today). The line Then it stopped being hard, and I didn't need the second window. asserts a specific mechanical outcome: that she dropped the chat window. The tape says only "And then I become very much more confident and competent to be able to do this on my own." The two-window setup is verbatim; which window she stopped needing is an inference. Tight inference, but the gate written today says a narrated outcome needs a quote, not a reading. Corrected to and I was doing it on my own — anchored to "do this on my own", same arc, nothing invented. Applying the new gate to this email is the whole reason for re-running it.

Defect 2 — R5 / R3, pre-existing. The only thing that gets you past a wall you keep hitting is doing the thing in the smallest way you can… carries "thing" twice in one sentence, and a third instance sits two lines above it (The thing I hear most…). Three across the piece, two of them audible together. Fixed to The only way past a wall you keep hitting is doing the thing in the smallest way you can… — which drops one, shortens the line, and lands closer to her verbatim ("the only way we get over this feeling…"). "Thing" now appears twice.

Everything else — checked, clean.

• P1 twinning: zero. The original mirror reversal in her verbatim (I didn't learn it by going to a course. I learned it by asking Claude) was already removed in the first pass; it survives only in the subject line, where it is a standalone fragment.
• Correction-revelation family: exactly one (The thing I hear most when this comes up is… → You don't.), inside the Pattern 7 exception — a belief she reports hearing on tape, not a strawman. Frequency limit is one. No compound.
• P2 three-beat: none. One task you already do by hand. One conversation. is two items, not three.
• P8 dramatic beats: one (You don't.), isolated on purpose at the pivot. One conversation. reads as the second half of a concrete pair rather than a second beat — the piece's only P3 exposure, and one P3 is under the action threshold.
• P11 identical openers: two consecutive The, and two consecutive If at the close. Both under the three-line flag, and the If / If fork is the choice Kathryn actually put to people.
• P3 borderline, kept: the smallest way is smaller than you think reuses one root. It is a comparative escalation rather than a positional reversal, it is the email's core mechanic, and it is her chosen preheader. Passes the would-she-say-it test.
• R7 two-comma: I'd ask the chat what I was looking at, try it, get it wrong, and go back and ask why. runs three commas — the once-per-piece long-rhythm exception, spent here deliberately.
• R1: three sentences end on pronouns (knows this, go make it, where you are). All three are quoted or verbatim, and knows this is a setup line feeding You don't., which Rule 1's anticipation exception covers.
• Cadence: 2–34 words per sentence. Jagged.
• Agreement test (new today): subject i didn't learn it from a course / preheader The smallest version is smaller than you think. The body's prescription is to start at the smallest version and repeat it. The preheader states the condition that method depends on — they agree, and the preheader carries information the subject does not. Passes.

Not a repurposed post

Written as an email. The 7/24 interview is the shared source with social; the copy is not shared. The "stay the bottleneck because it's tolerable" material overlaps with social Angle 1, but that post argues the bottleneck is a safety mechanism and stops there — it carries none of this story, and this email uses the tolerance fork only as its closing turn.