Email Marketing System

Trout Psychology

← All resources  ·  Action Plan

Contents

HOW TO USE THIS DOCUMENT

0. WHAT'S IN HERE

1. VOICE GUIDE

2. PLATFORM RECOMMENDATION

The recommendation: Kit (formerly ConvertKit), with Zapier (or Make) as the booking bridge.

Runners-up, and when to pick them instead

On Squarespace Campaigns

3. SEGMENTATION PLAN

3.1 The principle

3.2 Tag taxonomy

3.3 The four segments that actually get used

4. AUTOMATION TRIGGER MAP

4.1 The map

4.2 Trigger table

4.3 The four global suppression rules

5. COORDINATION WITH THE REVIEW GENERATION SYSTEM

5.1 The division of labor

5.2 The post-trip calendar, merged

5.3 The three collision risks, and the fixes

5.4 The one thing this system does that the review system asked for

W1 — WELCOME + DELIVER THE THING

W2 — THE ONE BIG IDEA

W3 — PROOF BY DEMONSTRATION

W4 — THE QUESTIONS PEOPLE ARE TOO POLITE TO ASK

W5 — THE ACTUAL ASK

W5-A — for people who can get to the river

W5-B — for people who can't

P1 — WHAT YOU ACTUALLY BOOKED

P2 — WHAT TO BRING, WHAT TO SKIP

P3 — TOMORROW

PT1 — YOUR BLUEPRINT

PT2 — HAVE YOU DONE THE THING

PT3 — THE NEXT DOOR

V1 — SAY THE NUMBER OUT LOUD

V2 — THE HOUR-BY-HOUR

V3 — GO WATCH THE FREE STUFF

V4 — LAST ONE

R1 — THE RIVER DID A THING

R2 — WHAT'S CHANGED

R3 — SHOULD I STOP

O1 — NOBODY GETS BETTER IN JULY

O2 — WHERE DO YOU WANT TO BE STANDING IN MAY

O3 — THE FIRST BUGS

12.1 Cadence, and how it reconciles with the Content Calendar

12.2 The repeatable section structure

12.3 Which product goes in "What's open," by month

12.4 The social proof section — the honest version

12.5 Sample issue — December 2026

From the boat

One thing about trout 🧠

What the Yakima's doing 🏞️

Ten minutes 🎣

The other thing 💬

What's open ❄️

CONCEPT 1 — THE RIVER JOURNAL

Opt-in page copy

CONCEPT 2 — THE REFUSAL FLOWCHART (a Strategy Blueprint)

Opt-in page copy

CONCEPT 3 — THE CAST DIAGNOSTIC (quiz / assessment)

Opt-in page copy

13.4 Lead magnet build order

14.1 Homepage hero / above the fold

14.2 Journal / blog sidebar (and mobile: after paragraph 3)

14.3 Exit intent

14.4 Footer (sitewide)

14.5 Content upgrade (end of blog post)

14.6 Placement strategy summary

15.1 Welcome sequence

15.2 Pre-trip sequence

15.3 Post-trip sequence

15.4 Virtual lesson nurture

15.5 Re-engagement

15.6 Off-season / winter

15.7 Newsletter / broadcast

15.8 Angle patterns worth reusing

16.1 Authentication — do this before importing a single contact

16.2 The subdomain question

16.3 ⚠️ The cold-list problem — the biggest deliverability risk in this engagement

16.4 Ongoing hygiene

16.5 Content-level deliverability

17.1 The honesty caveat — read before using any number below

17.2 The metrics that actually matter for this business

17.3 Send timing

18.1 Build order

18.2 Open items for Kristen

APPENDIX — DOCUMENT CONTENTS


Prepared: August 27, 2026
Phase: 2 — Content
Owner: Kristen Bufe (writer, sender, accountable) · Nate Tamarack (voice variants, dry-fly content)
Send-from identity: kristen@troutpsychology.com — never noreply@
Primary goal it serves: Brand authority, plus the two revenue goals underneath it — fill guide trips, scale the $250/month virtual casting subscription.


HOW TO USE THIS DOCUMENT

Every email below is finished copy. Subject lines (two per email, for A/B), preview text, body, CTA button label, timing, and design notes. Copy them into the platform as-is.

Conventions:
- [BRACKETS] = merge field or something Kristen fills in per-send.
- [CONFIRM: …] = a fact this document does not have and must not guess. Do not send an email containing one of these until it's resolved.
- Italics inside a template = a note to Kristen, not text to send.
- Every email is one CTA and one link. If you're tempted to add a second link, make it a second email.

Three rules that govern everything here:

  1. This list is not a broadcast channel. It is the Method in serialized form. The blog makes the argument in public for Google. Email makes the same argument in private, in first person, to people who already raised their hand. If an email doesn't teach something, it doesn't go out.
  2. One specific real detail beats any amount of polish. "That seam below the logjam" outperforms three paragraphs of well-crafted copy. The 20 seconds it takes to type a real detail is the highest-ROI 20 seconds in this system — same finding as the review playbook, and it holds here.
  3. Never send an email that a person couldn't have written. No "we're excited to announce." No "Dear Valued Angler." If a sentence sounds like software, delete the sentence.

0. WHAT'S IN HERE

§ Section Contents
1 Voice guide How Kristen sounds in email, with do/don't examples
2 Platform recommendation The pick, the reasoning, the runners-up, the migration
3 Segmentation plan Tag taxonomy: product, skill, geography, lifecycle
4 Automation trigger map What fires when, and what suppresses what
5 Coordination with the Review Generation System The collision table. Read before launch.
6 Welcome sequence 5 emails
7 Pre-trip sequence 3 emails
8 Post-trip sequence 3 emails
9 Virtual lesson nurture 4 emails
10 Re-engagement sequence 3 emails
11 Off-season / winter sequence 3 emails
12 Monthly newsletter template + full sample issue
13 Lead magnet concepts 3, fully specified with opt-in page copy
14 Signup form copy & placement 5 placements
15 Subject line bank 62 lines, by sequence and angle
16 Deliverability & list hygiene Authentication, warm-up, sunset policy
17 KPI targets With an explicit honesty caveat
18 Build order & open items for Kristen

Total sequence emails written: 21, plus one complete sample newsletter.


1. VOICE GUIDE

Kristen's voice, as it exists in public: warm, funny, irreverent, science-nerdy, first person, allergic to self-importance. She has a B.S. in Behavior Analysis that she found "by chance at a college party." She has described herself as an Absolute Silly Goose. She has spent roughly a decade teaching students on the autism spectrum and twenty years teaching on water. Both of those things are true at once and the voice has to hold both.

The formula: say the smart thing, then undercut yourself before anyone else can.

Do Don't
"Trout are not smart. They are conditioned. This is genuinely good news for you." "Unlock the secrets of trout behavior!"
"I have a degree in behavior analysis, which I acquired mostly by accident." "As a credentialed behavior analyst with 20 years of experience…"
"Reply and tell me. I read all of these, which is either charming or a sign I need a hobby." "We'd love to hear from you!"
"That's the whole pitch. I'm going to go tie streamers now." "Don't miss out — book today!"
"If it wasn't right for you, I don't want your money." "Satisfaction guaranteed."
Naming the actual mechanism: task analysis, shaping, chaining, reinforcement Vague science-flavored words: proven, scientific, optimized

Structural habits that make it sound like her:
- Short paragraphs. Frequently one sentence. Read on a phone in a truck.
- Lead with the interesting thing, not the greeting.
- Em dashes and parentheticals — she thinks in asides.
- End on something concrete and slightly abrupt. "Go tie some streamers." "Bring the 6-weight."
- Sign off Kristen alone. No title block. The footer handles credentials.
- Nate's variants are goofier and more mayfly-obsessed. Where a Nate variant is given, use it for dry-fly-tagged subscribers.

Things to never do in this voice:
- Fake urgency. Real scarcity exists here (two instructors, 3:1 ratio, a finite number of good days in March). Use the real thing.
- Fake testimonials or paraphrased "what students say." The business has zero locatable reviews as of this writing. Every social-proof slot in this document is either (a) proof by demonstration or (b) a marked [CONFIRM] slot waiting for a real quote from the review system. Do not fill them with anything else.
- Fake prices. The only confirmed price in this engagement is $250/month for virtual casting lessons. Everything else is [CONFIRM].


2. PLATFORM RECOMMENDATION

The recommendation: Kit (formerly ConvertKit), with Zapier (or Make) as the booking bridge.

Why this, for this business specifically:

Requirement this system creates Why Kit handles it
Six sequences running concurrently, some overlapping on the same person Kit's model is sequences + tags + visual automations. A subscriber can sit in a nurture sequence and get pulled out by a tag the moment they book. That's the single most important mechanic in §4, and it's the thing Kit is actually built around.
Suppression logic so the post-trip sequence doesn't collide with the review ask Tag-based exclusions on every sequence and broadcast. Trivial in Kit; painful or impossible in a template-first tool.
Written by one person who is also rowing a boat 200 days a year Kit's editor is a plain text field. It looks like writing an email, because it is. That matters more than it sounds — a heavy drag-and-drop builder is how a two-person team quietly stops sending.
The voice is text-first, not design-first Kit's default templates are near-plain-text and deliver well. This brand's emails should look like they came from a person, not from a design system. That is an aesthetic and a deliverability advantage.
Segmentation across product / skill / geography (§3) Unlimited tags on the free and paid tiers; segments built from tag logic.
Growing a list from roughly nothing Kit's free tier covers a meaningful subscriber count before paid tiers start. [VERIFY current tier limits and pricing at signup — these change.]

What Kit does not do natively, and the fix:

Runners-up, and when to pick them instead

Platform Pick it if Real drawback here
MailerLite Budget is the binding constraint. Automations are genuinely good for the price and the editor is friendly. Automation branching is shallower. Suppression logic across six sequences gets fiddly.
Mailchimp Native Squarespace Commerce sync matters more than anything else — i.e. gift certificates and e-comm become a big revenue line. Customer Journeys do support date-based triggers. Heaviest interface of the three. Pricing scales on contacts including unsubscribed ones unless managed. Most likely of the three to be quietly abandoned by a two-person team in July.
Brevo Kristen wants email and SMS in one tool — relevant, because the review system's highest-converting mechanic is a 7:30 p.m. same-day text. US SMS requires A2P 10DLC registration, which is real paperwork for a two-person shop. Recommend starting with the manual scheduled-text method the review system already specifies, and revisiting Brevo only if trip volume passes ~15/month.

On Squarespace Campaigns

The Review Generation System (Launch Checklist, step 5) says to load the eight review templates into "Squarespace Campaigns / email tool." This document supersedes that instruction. Squarespace Campaigns can send a broadcast and it can do a basic automation, but it cannot run six overlapping tag-suppressed sequences, and it cannot do date-relative triggers off a trip date. Trying to run this system in it will fail in month two.

Migration path, in order:
1. Create the Kit account. Authenticate the domain (§16) before importing anyone.
2. Import the existing list — carefully, and cold. See §16.3, this is a deliverability landmine. [CONFIRM: does an email list exist today, how large, and where does it live? Phase 1 lists this as an open item in both the Content Calendar (§8 item 5) and the Review System (Appendix B item 3).]
3. Rebuild the eight review templates from the Review Generation System as Kit sequences/broadcasts, wired to the tags in §3.
4. Keep Squarespace forms as the capture layer (they're already on the site) and pipe them to Kit. Or replace with embedded Kit forms — either works; the Squarespace-native form is less work and one fewer thing to break.
5. Leave Squarespace Campaigns off entirely once the migration is done. Two sending platforms on one domain is a deliverability problem, not a redundancy.


3. SEGMENTATION PLAN

3.1 The principle

This business has one product that requires you to be within driving distance of the Yakima, and one product that works from Auckland. Those two audiences want almost nothing in common. Geography is the primary split. Everything else is secondary.

Do not over-engineer this. Four tag families, applied consistently, will carry the whole system for two years.

3.2 Tag taxonomy

Prefix every tag with its family. It keeps the tag list navigable when it's 60 tags long.

A. Geography — geo: (the primary split; set once at opt-in, rarely changes)

Tag Definition What they can buy
geo:local Kittitas County, Yakima Valley, Ellensburg, Cle Elum, Roslyn, Suncadia Everything. Day trips are a same-day drive.
geo:regional Rest of Washington, Portland metro, Idaho panhandle, BC lower mainland — a drivable weekend Guided days, casting camp, schools, retreats
geo:destination Rest of US / international, willing to travel Retreats, 3-day immersives, multi-day private education. This is the TripAdvisor audience.
geo:remote Anywhere, not planning to travel here Virtual lessons only. This is the $250/mo audience.
geo:unknown Not yet determined Gets geography-neutral content until resolved

How to set it: one optional question on the opt-in form — "Where do you fish?" with a free-text field, plus a required question that actually does the work: "Are you closer to the Yakima River or to a computer?" with the answers "Yakima, realistically" / "Computer, realistically" / "I'd travel for the right week." That's a segmentation question written in Kristen's voice, which is the only kind she'll actually put on a form.

B. Product interest — want: (behavioral; set by clicks, page visits, and lead magnet choice; a person can carry several)

want:guided · want:streamers · want:dryfly · want:virtual · want:private-ed · want:retreat · want:casting-camp · want:streamer-stomp · want:gift · want:school

C. Skill level — skill: (self-declared at opt-in or via the Cast Diagnostic lead magnet, §13 Concept 3)

Tag Self-description Content posture
skill:never "I have never held a fly rod" Zero jargon. Permission-giving. Bringing-a-friend content.
skill:beginner "I've been out a few times, I'm mostly guessing" Mechanics + the reasoning underneath. Highest conversion to casting camp / schools.
skill:stuck "I've fished for years and I've plateaued" The highest-value virtual-lesson segment. They know enough to know what they can't fix.
skill:experienced "I'm decent, I want to get sharp" Technique depth. Streamer Stomp. Private education.

D. Lifecycle — life: (mutually exclusive; exactly one at a time; drives every suppression rule in §4)

life:subscriberlife:prospect (showed buying intent) → life:booked (has a future trip date) → life:client-active (trip happened, inside 30 days) → life:client (past client) → life:lapsed (no booking in 12+ months) → life:sunset (unengaged, see §16.4)

Plus two parallel states that aren't part of the ladder:
- life:subscription-active — currently paying the $250/mo. Suppress from all sales sequences.
- life:gift-purchaser — bought for someone else. Different psychology entirely; they may never fish.

E. Operational flags — flag:

flag:review-left · flag:review-asked · flag:sms-consent · flag:nate (dry-fly affinity, gets Nate's variants) · flag:kristen (streamer affinity) · flag:do-not-sell (asked for content only) · flag:complaint-resolved (had a bad day, was made good — handle by hand, never automate at)

3.3 The four segments that actually get used

Everything above collapses into four practical audiences. If Kristen only ever remembers four things, remember these:

  1. Local trip prospectsgeo:local OR geo:regional, life:prospect. Sell: guided days, casting camp, schools. Seasonal, booking-window-driven.
  2. Remote virtual studentsgeo:remote, any skill:. Sell: the $250/mo subscription. Geography-independent, year-round, the scalable product. This segment is why the list exists.
  3. Destination buyersgeo:destination. Sell: 3-day immersives, multi-day private education. Low volume, high value, long consideration window. These are the people who read every email.
  4. Past clientslife:client. Sell: the next rung (day trip → private ed → retreat), plus off-season virtual. Highest-converting audience in the business and currently the most neglected.

4. AUTOMATION TRIGGER MAP

4.1 The map

                         ┌──────────────────────────────┐
                         │  LEAD MAGNET OPT-IN          │
                         │  (River Journal / Flowchart  │
                         │   / Cast Diagnostic)         │
                         └──────────────┬───────────────┘
                                        │ tag: life:subscriber
                                        │ + geo: + skill: from form
                                        ▼
                         ╔══════════════════════════════╗
                         ║  WELCOME SEQUENCE (5)        ║
                         ║  Day 0, 2, 4, 7, 10          ║
                         ╚══════════════┬═══════════════╝
                                        │
                  ┌─────────────────────┼──────────────────────┐
                  │                     │                      │
        clicks virtual CTA      clicks trip CTA          no action
        or visits /learn/       or visits /trips/*       by Day 20
        virtual-casting                 │                      │
                  │                     │                      ▼
                  ▼                     ▼            ┌──────────────────┐
      ╔═══════════════════════╗  tag: want:guided    │ MONTHLY          │
      ║ VIRTUAL NURTURE (4)   ║  life:prospect       │ NEWSLETTER only  │
      ║ Day 1, 4, 8, 14       ║        │             │ (3 broadcasts/mo)│
      ╚═══════════┬═══════════╝        │             └────────┬─────────┘
                  │                    │                      │
        ┌─────────┴────────┐           │                      │
   subscribes          doesn't         │                      │
        │                  │           │                      │
        ▼                  ▼           │                      │
 life:subscription-   back to          │                      │
 active               newsletter       │                      │
 SUPPRESS ALL SALES        │           │                      │
        │                  └───────────┼──────────────────────┤
        │                              │                      │
        │              ┌───────────────▼──────────────────┐   │
        │              │  BOOKING CONFIRMED               │   │
        │              │  (zap: booking tool → Kit,       │   │
        │              │   writes trip_date field)        │   │
        │              │  tag: life:booked                │   │
        │              │  EXIT all nurture sequences      │   │
        │              └───────────────┬──────────────────┘   │
        │                              ▼                      │
        │              ╔══════════════════════════════════╗   │
        │              ║  PRE-TRIP SEQUENCE (3)           ║   │
        │              ║  P1: on booking (or T-14)        ║   │
        │              ║  P2: T-5 days                    ║   │
        │              ║  P3: T-1 day, evening            ║   │
        │              ╚═══════════════╤══════════════════╝   │
        │                              ▼                      │
        │                        ┌───────────┐                │
        │                        │ TRIP DAY  │                │
        │                        └─────┬─────┘                │
        │                              │                      │
        │       ╔══════════════════════▼═══════════════════╗  │
        │       ║  ⚠ REVIEW SYSTEM OWNS DAY 0 AND DAY 5   ║  │
        │       ║  D0 19:30 — verbal ask + SMS/E1          ║  │
        │       ║  D5 — E5 nudge (only if no review)       ║  │
        │       ║  Email system sends NOTHING on D0 or D5  ║  │
        │       ╚══════════════════════╤═══════════════════╝  │
        │                              ▼                      │
        │              ╔══════════════════════════════════╗   │
        │              ║  POST-TRIP SEQUENCE (3)          ║   │
        │              ║  PT1: Day 2, 8 a.m.              ║   │
        │              ║  PT2: Day 9                      ║   │
        │              ║  PT3: Day 21                     ║   │
        │              ╚═══════════════╤══════════════════╝   │
        │                              │ tag: life:client     │
        │                              ▼                      │
        │              ┌──────────────────────────────────┐   │
        └─────────────►│  NEWSLETTER + SEASONAL           │◄──┘
                       │  (all engaged subscribers)       │
                       └───────────────┬──────────────────┘
                                       │
                 ┌─────────────────────┴────────────────────┐
                 │                                          │
        Dec 1 – Feb 28                          no booking in 12 months
                 │                                          │
                 ▼                                          ▼
      ╔══════════════════════╗                ╔═══════════════════════╗
      ║ OFF-SEASON / WINTER  ║                ║ RE-ENGAGEMENT (3)     ║
      ║ (3) — Dec, Jan, Feb  ║                ║ Day 1, 6, 12          ║
      ╚══════════════════════╝                ╚═══════════┬═══════════╝
                                                          │
                                              ┌───────────┴──────────┐
                                         re-engages            silent
                                              │                     │
                                              ▼                     ▼
                                      life:prospect          life:sunset
                                                          (suppress 6 mo,
                                                           then remove)

4.2 Trigger table

# Sequence Trigger Timing Entry condition Exit / suppression
1 Welcome (5) Lead magnet opt-in, any form D0 immediate, D2, D4, D7, D10 New subscriber, any tag set Exits on life:booked. Never re-enters.
2 Virtual nurture (4) Visited /learn/virtual-casting-lessons 2+ times in 14 days, OR clicked a virtual CTA, OR started checkout and abandoned D1, D4, D8, D14 NOT life:subscription-active, NOT flag:do-not-sell Exits immediately on subscribe, on life:booked, or on flag:do-not-sell. Runs once per person per 12 months.
3 Pre-trip (3) life:booked + trip_date populated P1 on booking (or T-14 if booked >30 days out); P2 T-5; P3 T-1 evening Any booked product Exits on cancellation. If booked <7 days out, send P1 and P3 only — skip P2 and fold the gear list into P1.
4 Post-trip (3) trip_date reached + trip not cancelled D2 at 8 a.m., D9, D21 life:client-active Hard block: nothing sends on D0 or D5 — those belong to the review system. See §5.
5 Re-engagement (3) life:lapsed — no booking in 12+ months AND no email open in 90 days D1, D6, D12 Not currently life:booked Exits on any open+click. Runs once per 12 months, max. Must not run within 30 days of review template E6 — see §5.
6 Off-season / winter (3) Date-based: Dec 3, Jan 7, Feb 4 (adjust to actual Tuesdays/Wednesdays each year) Monthly, Dec–Feb All engaged subscribers Suppress life:booked for a trip inside the window. Suppress life:subscription-active from the virtual-lesson pitch in O1 — send them the alternate paragraph.
Monthly newsletter Manual broadcast, Wed after the month's first blog post 1st, 2nd, 3rd Wednesday All engaged Suppress anyone inside the pre-trip window (they're getting logistics; don't add noise)
Review asks (E1–E8) Owned by the Review Generation System See that document See §5

4.3 The four global suppression rules

These matter more than any individual email. Wire them before writing a single send.

  1. Nobody receives two automated emails on the same calendar day. If a sequence email and a broadcast collide, the sequence wins and the broadcast skips that person.
  2. life:booked suppresses all sales sequences. Someone who has already bought should never receive a "have you considered booking" email. This is the single most common automation failure and it makes a small business look like it isn't paying attention.
  3. life:subscription-active suppresses every virtual-lesson pitch, everywhere — sequences, newsletters, seasonal sends. They already pay $250 a month. Asking them to buy it is insulting.
  4. flag:complaint-resolved pauses all automation for 60 days. Someone whose day went badly and got made good is handled by Kristen personally or not at all. Do not let a drip campaign walk into that.

5. COORDINATION WITH THE REVIEW GENERATION SYSTEM

Read this section before launching anything. The Review Generation System (Phase 1 - Foundation/Review Generation System.md) already owns eight email templates, several of which sit in the same days as the sequences here. Two documents sending into the same inbox on the same afternoon is how a good system produces an unsubscribe.

5.1 The division of labor

Owner Owns Never does
Review Generation System The review ask. Day 0 evening (E1 / SMS), Day 5 nudge (E5), Day 60 subscription ask (E4), second-platform ask (E7), gift-purchaser ask (E8) Teach. Sell. Deliver assets.
Email Marketing System (this doc) Teaching, asset delivery, expectation-setting, and the next-product invitation Ask for a review. Ever. Not once, in any of the 21 emails here.

That separation is deliberate. The review playbook's whole thesis is that a steered ask with one specific question converts; a review ask buried inside a teaching email converts nobody and dilutes both jobs.

5.2 The post-trip calendar, merged

This is the actual sequence a client experiences. Build it exactly like this.

Day Time What sends Which document owns it Notes
D0 Last 30–45 min on the water Verbal review ask + waterproof QR card Review System §4 (V1) Not an email. Plants the steering question.
D0 7:30 p.m. SMS (or E1 email if no SMS consent) — the review ask Review System §5 E1 / §6 This email system sends nothing on D0.
D1 Nothing. Deliberate silence. Let the review ask sit alone.
D2 8:00 a.m. PT1 — the recap + takeaway asset This document §8 Contains no review ask. Contains one line acknowledging the ask already made, which defuses the "they keep asking" feeling.
D5 Morning E5 review nudgeonly if no review has appeared Review System §5 E5 Suppressed by flag:review-left. This email system sends nothing on D5.
D9 Morning PT2 — the practice assignment This document §8
D21 Morning PT3 — the next door This document §8
D30+ Client moves to life:client, newsletter cadence only
D45–60 E7 second-platform ask, only for flag:review-left + delighted Review System §5 E7

5.3 The three collision risks, and the fixes

Risk Fix
PT1 lands the morning after the review ask and reads as a second ask. PT1 opens by explicitly closing the review loop: "I asked you for the one favor last night. That's the only one. This email is me holding up my end." Then delivers the asset. This turns a collision into a credibility moment.
Re-engagement R1 and review template E6 are the same email to the same person. Both are "hey, it's been a while, thinking of you." E6 asks for a review; R1 asks for a booking. Sent within a week of each other, they expose the machinery. Sequencing rule: E6 runs first, once, as the review-system kickstart (Launch Checklist step 11). The re-engagement sequence in §10 does not run against anyone who received E6 until 60 days have passed. Tag flag:e6-sent with a date. After the first year they naturally separate — E6 is a one-time list-wide kickstart, R1 is an evergreen 12-month-lapse trigger.
The Day-60 virtual subscription review ask (E4) collides with the virtual nurture sequence. It can't — nurture only runs against non-subscribers, and E4 only runs against active subscribers. Rule 3 in §4.3 covers it. Verify the tag logic once at build time and then stop worrying about it.

5.4 The one thing this system does that the review system asked for

Review System, Appendix B, item 7:

Write the expectation-setting line from Worked Example 1 into the booking confirmation and the guide-trip page. Do this before the season, not after the first bad review.

That line is now Pre-trip Email 1 (§7). It is the most important email in this entire document. The review playbook identified expectation mismatch — "I booked a guide trip and got a class" — as the single most dangerous review type for this specific business, because it reframes the Method as an excuse for a bad day rather than the product itself.

You cannot fix that with a review response. You fix it fourteen days earlier, in writing, in a friendly voice, before anyone gets in a boat. That's what P1 is for.


6. WELCOME SEQUENCE (5 EMAILS)

Trigger: any lead magnet opt-in.
Cadence: Day 0 (immediate), Day 2, Day 4, Day 7, Day 10.
Job: introduce the Method and Kristen, and convert to a guide trip (geo:local / geo:regional / geo:destination) or the virtual subscription (geo:remote).
Design note for all five: plain text or near-plain-text. One image maximum, and only where specified. No header banner — a banner is the fastest way to make a personal email look like a newsletter. Kristen's actual photo in the footer, not a logo.


W1 — WELCOME + DELIVER THE THING

Send: immediately on opt-in
Goal: deliver the magnet, set expectations, be a person

Subject A: Your river journal, plus a warning about me
Subject B: Here's the thing you asked for. Also, hi.
Preview text: Fair warning: I'm going to explain a lot of behavioral science at you.

Hey [FIRST NAME] —

Here's [LEAD MAGNET NAME]. Download it, print it, spill coffee on it. That's what it's for.

[ Grab it here → ]

Quick introduction, because you're about to start hearing from me.

I'm Kristen. I've been fishing for twenty-five years and teaching on water for twenty. I also have a degree in behavior analysis, which I found by accident at a college party, which is either the best or the worst reason anyone has ever chosen a field of study.

Here's what that combination turned into: trout are organisms. They follow the same laws of learning as every other organism, including you. Which means the fish in front of you isn't outsmarting you. It's been conditioned by its environment, and conditioning is legible if you know how to read it.

That's the whole business. It's called the Trout Psychology Method and I'll be explaining it at you in installments.

What you're signed up for:
- A few emails over the next week and a half, one idea each
- After that, roughly three a month — a real river report, one piece of trout behavior, one drill
- No "we're excited to announce" emails. I'd rather not.

Hit reply and tell me the one thing about fishing that most annoys you right now. I read every one of these, which is either charming or a sign I need a hobby.

Kristen

P.S. — I describe myself as an Absolute Silly Goose with a behavior analysis degree. Both halves are load-bearing.

CTA button: Grab it here →
Link: direct download URL — not a landing page. They already opted in; make them click once.
Send time: immediate. Non-negotiable — this is the highest-open email she will ever send.
Design note: the P.S. is the voice test. [CONFIRM: Kristen is comfortable with "Absolute Silly Goose" in email as well as social.] If not, cut the P.S. entirely; don't replace it with something safer.


W2 — THE ONE BIG IDEA

Send: Day 2, 7:00 a.m. Pacific
Goal: teach one genuinely useful thing; establish that this list is worth opening

Subject A: Trout are not smart. This is good news.
Subject B: The fish isn't outsmarting you
Preview text: It's been trained. By the river. Which means you can read the training.

[FIRST NAME] —

The most common sentence I hear on the water is some version of "that fish is smarter than me."

It isn't. I promise. A trout has a brain roughly the size of a pea and it is not out there strategizing about you.

What it has done is learn. Every day of its life, that fish has been running a very simple experiment: some things it eats are food, some things it eats hurt, and some places it sits cost more energy than they return. The river has been reinforcing and punishing its behavior on a continuous schedule since the day it hatched.

That's not intelligence. That's conditioning. And conditioning has rules.

Here's a usable one, right now:

A fish holding in a spot is telling you the energy math worked out. Not "the fish likes it there." The fish is there because the calories coming past exceed the calories spent holding position. So when you look at a run, stop asking where would a fish want to be and start asking where does the math work — where's the seam that delivers food to a place that costs almost nothing to sit in?

That one reframe changes where people cast more than any fly change I've ever recommended.

The longer version of this argument — with the actual learning-theory underneath it — is on the site.

[ Read: why trout aren't smart → ]

Tomorrow's off. Thursday I'll show you what it looks like when I break a skill apart.

Kristen

CTA button: Read: why trout aren't smart →
Link: /journal/trout-are-not-smart-they-are-conditioned (Content Calendar post #17 — scheduled Feb 9, 2027. Until it exists, link to /method/think-like-a-trout instead. Do not launch this sequence before /method is live.)
Design note: the bolded "conditioning" line is the screenshot people send to friends. Keep it on its own line.


W3 — PROOF BY DEMONSTRATION

Send: Day 4, 7:00 a.m. Pacific
Goal: show what the teaching actually looks like — this is the social-proof slot, and there is currently no social proof, so we demonstrate instead of claim

⚠️ Honesty note, for whoever is building this: Trout Psychology has zero locatable reviews as of August 2026. The standard welcome-sequence email 3 is "customer story + testimonial quotes." We are not writing one. No invented students, no composite quotes, no "one of my students told me." Instead this email proves the claim by doing the thing on the page — which, for a teaching business, is stronger than a testimonial anyway. There is a marked slot at the bottom for one real quote the moment the review system produces one.

Subject A: I broke a double haul into four pieces. Here are all four.
Subject B: What a lesson actually looks like
Preview text: Most instruction says "do it like this." Here's the alternative.

[FIRST NAME] —

Most casting instruction is a demonstration followed by encouragement. Someone shows you the motion, you fail to reproduce the motion, they say "yep, just like that but smoother," and you both quietly agree to move on.

That's not teaching. That's modeling and hoping.

Here's what I do instead. It's called task analysis — you take a complex skill, break it into its actual component behaviors, teach each one to mastery in isolation, then chain them together. It's the same procedure I used for ten years teaching students on the autism spectrum, and it works on a double haul for exactly the same reason it works on anything else: skills aren't hard, they're just made of smaller skills nobody separated out for you.

A double haul, decomposed:

  1. The hand travels. Nothing else. Line hand moves down and back, rod hand does nothing. Twenty reps standing still, no rod.
  2. The hand returns. The recovery — line hand comes back up to the reel before the loop unrolls. This is the part everyone skips and it's why everyone's haul dies in week two.
  3. Timing to the rod stop. Now we add the rod. Haul on the stroke, not before it, not after it.
  4. Chain it, both directions. Back cast and forward cast, then together, then live line.

Nobody drills step 2 in isolation. Step 2 is where the double haul actually lives.

That's the whole Method, applied to one skill: find the components, reinforce the right rep, chain to mastery. We do it with casting. We also do it with reading water, with mending, and with the decision of what to tie on — because those are learned behaviors too, and they decompose the same way.

[ See how the Method works → ]

Go move your line hand twenty times. It takes ninety seconds and it will annoy you.

Kristen

CTA button: See how the Method works →
Link: /method
Design note: the numbered list should render as a list, not a paragraph. It's the proof.
Future addition — do not add until it exists: [CONFIRM: once the review system produces a review that describes decomposition — the "she broke my double-haul into four pieces" kind — paste one sentence of it here, attributed to a first name and last initial, with a link to the Google review. One quote. Not three.]


W4 — THE QUESTIONS PEOPLE ARE TOO POLITE TO ASK

Send: Day 7, 7:00 a.m. Pacific
Goal: clear the five real objections; the reply-CTA makes this the highest-response email in the sequence

Subject A: Five things people are too polite to ask me
Subject B: "Am I too bad at this to book?" and four other questions
Preview text: Including the one about whether you'll actually catch anything.

[FIRST NAME] —

Five questions I get asked sideways, answered directly.

"Am I too much of a beginner?"
No. Genuinely no, and I'd tell you if you were. Beginners are the easiest people I teach because there's nothing to un-learn. The hardest students are people who've been fishing badly for fifteen years with great confidence. If you have never held a fly rod, you are not a problem to be managed. You're the good version.

"Is this a guided trip or a lesson?"
It's a lesson. On a river. From a boat. I want to be extremely clear about this because it's the one thing that goes wrong when it goes wrong. Every trip we run is instructional. I will explain why the fish are where they are. I will hand you a whiteboard. If what you want is a quiet day where somebody rows you, hands you a rigged rod, and says "cast there," I will genuinely refer you to someone excellent — that's a real service and there are people around here who do it beautifully. It just isn't what we do.

"Will I catch fish?"
Some days yes, some days no, and any guide who promises otherwise is selling you something. What I can promise is that you'll understand why the day went the way it did, which is the part that transfers to every river you fish for the rest of your life. Fish counts don't transfer. Reasoning does.

"I don't live anywhere near Washington."
Then the river trips are off the table and the virtual program isn't. It's $250/month, it's video analysis of your actual cast, and it exists specifically because someone who will never once fish the Yakima should still be able to learn this properly. More on that in a few days.

"I'm a woman / I'm neurodivergent / I get anxious in outdoorsy environments and I have been made to feel stupid before."
I know. I've heard a lot of versions of this and every one of them made me angry on the person's behalf. Two instructors, three students maximum, custom curriculum, and a decade of my career spent teaching people whose brains don't do things the standard way. Nobody is going to sigh at you. If there is something I should know about how you learn, tell me before the trip and I will build the day around it — that's not an accommodation, that's just the job.

Something I didn't answer? Hit reply. It comes to me, not to a support queue. There isn't a support queue. There's two of us and a drift boat.

Kristen

CTA: reply-only. No button in this email. (That's deliberate — a reply is worth more than a click here, and a button competes with it.)
Design note: bold the questions, plain the answers. Scannable — most people will read two of the five and one of those two is the one they came for.
Note on the fourth answer: $250/month is the only confirmed price in this engagement. Do not add a guide trip price here without [CONFIRM: current guided day rate, half vs. full, and the shared "split with a stranger" rate].


W5 — THE ACTUAL ASK

Send: Day 10, 7:00 a.m. Pacific
Goal: convert. Fork by geography. No manufactured urgency — the real scarcity is enough.

Build note: this email has two versions. Send version A to geo:local / geo:regional / geo:destination. Send version B to geo:remote. If geo:unknown, send version A with the version-B paragraph appended.

W5-A — for people who can get to the river

Subject A: Okay. The actual pitch. It's short.
Subject B: There are about forty good days and then there aren't
Preview text: Two instructors, three students max. That's the whole constraint.

[FIRST NAME] —

Ten days of me explaining fish. Here's the part where I ask for something.

Come fish with us.

That's it. That's the pitch. But here's the honest version of why it's worth doing sooner rather than "sometime":

There are two of us. Three students per instructor, maximum — that's not a marketing number, it's the number above which I can't actually watch anybody's hands. Which means a season has a hard ceiling on it, and the good weeks book first. [SEASONAL LINE — e.g. "Right now we're in prime streamer season, which is the best six weeks of the year to learn to move a fish on purpose."]

What a day is: you, [me or Nate], a boat, a whiteboard, and a curriculum built for you specifically rather than pulled off a shelf. You go home with a written strategy blueprint — the reasoning, on paper, so it doesn't evaporate on the drive.

What it isn't: a quiet day of being rowed. See email four.

[ See what's open → ]

If you're not ready, that's completely fine — stay on the list, I'll keep explaining trout at you, and the door doesn't close.

Kristen

P.S. — If you want the day but not alone in a boat with a stranger who has opinions about mayflies, the shared "split with a stranger" option exists and is genuinely fun. [CONFIRM: shared trip rate and how to book it.]

CTA button: See what's open →
Link: /trips/yakima-river-guided-trips
Seasonal line: rewrite this quarterly. Sep–Nov = streamer season. Dec–Feb = "we're booking spring now and March goes first." Mar–May = "this is the booking window and it is genuinely competitive." Jun–Aug = retreats and dry fly.

W5-B — for people who can't

Subject A: You're not coming to Washington. Fine. Let's fix your cast anyway.
Subject B: The version of this that works from your backyard
Preview text: $250/month. Here's exactly what that buys, and who shouldn't buy it.

[FIRST NAME] —

You told me you're realistically closer to a computer than to the Yakima. Good — that's most people, and it's why the virtual program exists.

Here's what it is: you film your cast in your backyard. I watch it. Not "watch it" like a friend at the boat ramp — watch it frame by frame, find the one fault underneath the six symptoms, and build a drill sequence for your hands specifically. Then we get on a call and I make you do the drills while I watch. Then you film it again.

That's the loop. It's $250 a month and it runs month to month.

Here's who shouldn't buy it: somebody who wants a library of casting videos. There is excellent free casting content on the internet and I recommend some of it to my own students. If what you want is instruction in general, go watch it — seriously, it's good, and I'd rather you have that than resent me.

What you can't get from a library is someone watching your cast and telling you which of your six problems is actually one problem.

[ How the virtual program works → ]

Kristen

P.S. — Most people who join are not beginners. They're people who've fished for a decade, hit a ceiling, and can't see their own hands. If that's uncomfortably accurate, that's the tell.

CTA button: How the virtual program works →
Link: /learn/virtual-casting-lessons
Design note: the "here's who shouldn't buy it" paragraph is the highest-converting paragraph in this email. It is not a risk. Telling someone not to buy is the single most credible thing a two-person business can do, and it pre-empts the exact review the playbook flagged (Worked Example 2, the "$250 is outrageous, YouTube is free" review).
Sequence exit: on completion, subscriber moves to newsletter cadence. Tag want:virtual if they clicked; that click also triggers the Virtual Nurture sequence (§9) after a 3-day gap.


7. PRE-TRIP SEQUENCE (3 EMAILS)

Trigger: life:booked with trip_date populated.
Cadence: P1 on booking (or T-14 if booked more than 30 days out) · P2 at T-5 days · P3 at T-1, evening.
If booked inside 7 days: send P1 immediately and P3 the evening before. Skip P2 and fold the gear list into P1.
Job: logistics, yes — but the actual job is P1, which is the single most valuable email in this document.

Why this sequence exists. The Review Generation System identified expectation mismatch as the most dangerous review risk this business faces (§10.3, Worked Example 1): a client books a guide trip, receives an education, and reviews it as a bad guide trip. The playbook's own conclusion was that the fix is "one line in every booking confirmation," written before the season, not after the first bad review. This sequence is that line, expanded into an email that does the job properly — warmly, in Kristen's voice, fourteen days before anyone gets in a boat, with a reply mechanism that catches the mismatch while it's still fixable.


P1 — WHAT YOU ACTUALLY BOOKED

Send: immediately on booking confirmation, or T-14 if booked far out
Goal: set the expectation that this is a teaching trip. Give anyone who wanted something else a graceful, no-cost exit.

Subject A: Read this one. It's the only one that matters.
Subject B: Before your trip: what you actually booked
Preview text: One honest paragraph before we get to gear lists and meeting times.

[FIRST NAME] —

You're on the books for [DATE] with [KRISTEN / NATE]. I'm genuinely looking forward to it.

Before the logistics emails start, one honest paragraph. It's the most useful thing I'll send you.

We teach. Every trip is instructional. That's the whole business.

Which means the day looks like this: I'm going to explain why the fish are sitting where they're sitting. I'm going to break whatever you're struggling with into pieces and make you drill the pieces. There will be a whiteboard in the boat. There may be a flowchart. I have a degree in behavior analysis and I am going to use it on you, and also on the trout, and I will be enjoying myself enormously the entire time.

Most people book us specifically for that. Some people book a guide expecting a quiet day where somebody rows them, hands them a rigged rod, and points — and that is a completely legitimate thing to want. It just isn't what we do, and I'd rather you find that out today than at 8 a.m. on the river.

So: if what you wanted was a rowed day and not a class, reply to this email and say so. No awkwardness, no fee, no hard feelings — I will personally refer you to someone excellent around here who does exactly that, and I'll do it happily. [CONFIRM: cancellation/rescheduling terms Kristen wants stated here.]

Still in? Good. Then one more thing, and it's a favor to both of us:

Reply and tell me the one thing about your fishing that most frustrates you. Doesn't matter how small or how embarrassing. "My cast collapses in wind." "I can't tell where to start on a run I've never seen." "I lose every fish I hook." Whatever it is.

I build the day around the answer. That's what "custom curriculum" actually means — it means I read your email and then plan a day for you specifically instead of running the standard float. It takes you thirty seconds and it changes what the day is.

Kristen

Gear list and meeting details come a few days out. Don't buy anything yet.

CTA: reply-only. No button. The reply is the conversion here — it sets expectations, catches mismatches, and feeds the curriculum in one motion.
Send time: immediate on booking. Design note: no images, no header. This should look like an email from a person, because a designed template undercuts the honesty of the content.
Operational note — this matters: somebody has to read the replies and act on them. Put a recurring task in the calendar: the morning of a trip, re-read the client's P1 reply. An unread reply is worse than no question asked. [CONFIRM: Kristen or Nate owns reply triage.]
Also apply this line verbatim to: the booking confirmation page, the guide-trip service page, and the Picktime/booking-tool confirmation email. Review System Appendix B, item 7.


P2 — WHAT TO BRING, WHAT TO SKIP

Send: T-5 days, 7:00 a.m. Pacific
Goal: logistics, plus permission to own less stuff — which is a real barrier for beginners and a real differentiator against shops that want to sell them a rod

Subject A: What to bring, what to skip, what I'll have
Subject B: Your gear list (it's shorter than you think)
Preview text: Please do not buy a new rod this week. I'm begging you.

[FIRST NAME] — [DATE] is close. Here's the whole list.

I bring:
- [CONFIRM: full list of what's provided — rods, reels, lines, flies, leader/tippet, boat, safety gear, lunch?]
- The whiteboard. Obviously.

You bring:
- A fishing license. Washington State, freshwater, valid for the date. This is the one thing I cannot fix for you at the boat ramp. [CONFIRM: link to WDFW licensing, and whether a Discover Pass is needed at the launch.]
- Layers. More than you think. The canyon runs cold in the morning and hot by noon in nearly every season. Cotton is the enemy; if it gets wet it stays wet.
- Polarized sunglasses. Non-negotiable, and not for the fish — for your eyeballs. There are hooks moving at speed.
- A hat with a brim. Same reason.
- Sunscreen, water, and any snack you'd be sad without. [CONFIRM: is lunch provided?]
- Rain shell if there's a hint of weather.
- Waders? [CONFIRM: needed for this trip type or not — this varies by boat and season and I don't want to guess.]

Please do not bring:
- A brand new rod you bought this week. I mean this sincerely. Learning a new rod and learning a new skill simultaneously is two variables, and two variables is how people conclude they're bad at this. Bring the rod you have, even if it's ugly. If you don't have one, I've got you — [CONFIRM: loaner gear availability].

What the day looks like: [CONFIRM: typical start time, on-water hours, takeout time]. Bring a change of clothes for the drive home; you'll be glad.

[ Anything I missed? Just reply → ]

Kristen

P.S. — If you replied to my last email with the thing that frustrates you, I've already read it and I'm already thinking about it. If you didn't, there's still time.

CTA: reply-only, or a soft button to a /trips/what-to-expect page if one exists.
Design note: this is the one email in the whole system that can be a formatted list. It's a reference document; people screenshot it. Make it scannable.
Nate variant: "I bring the dry flies and approximately four hundred opinions about mayflies. You bring the license."


P3 — TOMORROW

Send: T-1 day, 6:00 p.m. Pacific
Goal: meeting logistics, calm nerves, prime the learning with one question

Subject A: Tomorrow. Here's the plan.
Subject B: [TIME] at [PLACE]. One thing before you sleep.
Preview text: Where to meet, what the water's doing, and one question to think about.

[FIRST NAME] —

Tomorrow. [TIME] at [MEETING PLACE]. [CONFIRM: exact meeting location, parking notes, and what to do if they're running late.]

Important: there's no cell service on most of the river. If something goes sideways tonight or in the morning, call or text 206-659-5501 before you leave pavement. Once we're on the water we're wonderfully unreachable.

What the river's doing: [FLOW / WEATHER / HATCH — one or two sentences, written the night before. e.g. "Flows came down to [X] cfs this week and the water's got some color, which is genuinely good news for what we're going to work on."]

What the day is: [CONFIRM: start time, on-water duration, takeout, when you'll be back at your car]. Bathroom situation: [CONFIRM]. Dress for the morning, not the afternoon.

One thing to think about tonight, and then stop thinking about it:

Nobody learns anything while they're worried about looking stupid. That's not a nice sentiment, it's the actual mechanism — anxiety is incompatible with acquisition, which is a thing I could bore you about for an hour and won't. You are going to make bad casts tomorrow. I have made approximately nine million bad casts. We're going to laugh about several of them, and the laughing isn't a break from the learning — it's how the learning happens. You learn best when you're laughing. I have receipts.

See you at [TIME]. Bring the layers.

Kristen

CTA: none. This is a logistics-and-reassurance email; a CTA would cheapen it.
Send time: 6:00 p.m. the evening before — late enough that they're home, early enough to fix a problem.
Design note: phone number in bold. It's the only thing in this email someone might need at 5:40 a.m.


8. POST-TRIP SEQUENCE (3 EMAILS)

Trigger: trip_date reached, trip not cancelled → life:client-active.
Cadence: Day 2 at 8:00 a.m. · Day 9 · Day 21.
Hard constraint: ⚠️ Nothing from this sequence sends on Day 0 or Day 5. Those days belong to the Review Generation System (E1 at 7:30 p.m. on trip day; E5 nudge on Day 5). See §5.2 for the merged calendar.
Job: reinforce the learning, deliver a takeaway asset, hand off cleanly to the review ask, open the next door.


PT1 — YOUR BLUEPRINT

Send: Day 2, 8:00 a.m. Pacific
Goal: deliver the takeaway asset and re-state the reasoning before it evaporates. Contains no review ask.

Subject A: Your blueprint, written down
Subject B: What we actually did on [DAY], and why
Preview text: The reasoning, on paper, so it doesn't evaporate on the drive home.

[FIRST NAME] —

I asked you for the one favor on [TRIP DAY] night. That's the only one I'm going to ask. This email is me holding up my end.

[ Your strategy blueprint → ]

That's the day, written down: what we worked on, why we worked on it, and what to do next. I'd rather you have the reasoning than the memory, because reasoning is what transfers to water I've never seen.

The short version, in case you don't open the PDF for a week:

1. The thing you came in with. You told me [THE FRUSTRATION FROM THEIR P1 REPLY]. That's what we built the day around.

2. What we found. [THE ACTUAL DIAGNOSIS — e.g. "It wasn't your stroke. It was that your line hand quit at the top and your loop had nothing left to unroll with."]

3. The one thing to drill. [THE SINGLE COMPONENT. One. Not three.] Ten minutes in the yard beats two hours on the river, and I will keep saying this until it's annoying.

4. The moment it clicked. [SPECIFIC MOMENT FROM THE DAY — "that fish out of the seam below the logjam, on a cast you would not have made at 8 a.m." Do not skip this. This line is the reason the email gets read twice.]

Mark the blueprint up. Tell me where I'm wrong. Genuinely — if you drill the thing and it doesn't work, that's information about my teaching, not about your hands.

Kristen

CTA button: Your strategy blueprint →
Link: the personalized blueprint PDF or shared doc.
⚠️ Build note — the honest version: a genuinely personalized blueprint per client is 15–20 minutes of work. That is the correct amount of work and it is also the thing most likely to quietly stop happening in July. [CONFIRM: does Kristen want to commit to a per-client blueprint, or ship a templated one-pager with three filled-in fields?] A three-field template sent every time beats a beautiful custom document sent 40% of the time. Decide this before launch, not in the middle of a season.
Suppression: does not send if the trip was flagged flag:complaint-resolved. Kristen handles those by hand.
On the opening line: it is doing real work. It closes the review loop explicitly so the client doesn't spend the next two weeks braced for another ask. It also converts a potential collision into evidence that these people follow through.


PT2 — HAVE YOU DONE THE THING

Send: Day 9, 7:00 a.m. Pacific
Goal: reinforcement. This is the email that determines whether the trip produced a skill or a memory.

Subject A: Have you done the thing?
Subject B: Ten minutes in the yard. That's the whole email.
Preview text: Nine days is exactly when a new skill quietly dies.

[FIRST NAME] —

Nine days out. This is the window where a new skill quietly dies, so: have you drilled [THE ONE THING] yet?

If yes — good. Do it again this week and then stop; you're done. Overpractice is how a fixed motion becomes a new bad habit.

If no, here's the actual research-shaped reason to care, and then I'll leave you alone.

A skill you practiced once in a boat is a skill your body has performed under supervision, with an instructor's voice attached to it. That's not learned yet — that's prompted. It becomes yours when you can produce it without me, and that transfer happens through short, frequent, low-stakes reps. Not long ones. Ten minutes, three times a week, beats a two-hour session every time, and it isn't close.

Ten minutes. In the yard. With a hunk of yarn instead of a fly so you don't put a hook in the dog.

[ONE-LINE DRILL REMINDER — e.g. "Line hand down, line hand BACK UP before the loop unrolls. Twenty reps. That's it."]

That's the email. Go outside.

Kristen

P.S. — If you drilled it and something feels wrong, film ten seconds on your phone and reply with it. I'll tell you what I see. No charge, no pitch — I'm just constitutionally incapable of not looking at a cast.

CTA: reply-with-video. No button.
Why the P.S. matters: it is the softest possible demo of the virtual program. Someone who films a cast, sends it, and gets a real diagnosis back has just experienced the $250/mo product for free, in miniature. That's the strongest possible setup for PT3 and for the virtual nurture sequence. It's also just a nice thing to do, which is why it works.


PT3 — THE NEXT DOOR

Send: Day 21, 7:00 a.m. Pacific
Goal: open the next product. Exactly one recommendation, chosen for them.

Subject A: What I'd have you do next
Subject B: Three weeks out. Here's the honest recommendation.
Preview text: One suggestion, picked for you, and then I'll go back to the newsletter.

[FIRST NAME] —

Three weeks since [DATE]. Here's the one thing I'd tell you to do next if you asked me at a bar, which is the only recommendation format I trust.

[Pick ONE branch. Delete the others. One recommendation converts; three is a menu and a menu converts nobody.]

→ IF THEY CAUGHT THE BUG AND WANT DEPTH (skill:beginner / skill:stuck, high engagement):
A day was a start. What you actually want is consecutive days. One day is a demo of the Method; three days is where the reasoning takes hold, because you get to be wrong on day one, fix it on day two, and prove it on day three. That's the private education program, and it's the one I'd pick for you.
[ Private education → ]/learn/private-education

→ IF THEY'RE geo:remote OR THE LIMITING FACTOR IS THEIR CAST:
The thing that's holding you back doesn't need a river. It needs somebody watching your hands every two weeks. That's the virtual program — $250/month, month to month, you film, I diagnose, we drill. Also: I already looked at your cast for free once. This is that, on purpose, repeatedly.
[ How the virtual program works → ]/learn/virtual-casting-lessons

→ IF THEY WERE want:streamers AND HAD FUN:
You should do a Streamer Stomp. It is exactly as unserious as it sounds and exactly as technical as you'd want. [CONFIRM: next Streamer Stomp dates and format.]
[ Streamer Stomp → ]/learn/streamer-stomp

→ IF THEY CAME WITH SOMEONE, OR TALKED ABOUT SOMEONE THE WHOLE DAY:
Bring the person you kept mentioning. Half the good days I run are somebody teaching their favorite person to do the thing they love, and watching that happen is the best part of my job. Gift certificates exist for exactly this. [CONFIRM: gift certificate denominations and link.]
[ Gift certificates → ]/gift-certificates

Whichever it is — no rush, no expiring offer, no countdown timer. I'll be here, and so will the river, and I'll keep sending you trout behavior in the meantime.

Kristen

CTA: one button, chosen by branch.
Automation note: branch selection is by tag, or manually by Kristen for low volume. Under ~15 trips a month, pick the branch by hand. It takes ten seconds, it's always right, and automated product recommendation at this volume is a solution to a problem this business does not have.
Sequence exit: subscriber moves to life:client, newsletter cadence resumes.


9. VIRTUAL LESSON NURTURE (4 EMAILS)

Trigger: visited /learn/virtual-casting-lessons twice in 14 days, OR clicked a virtual CTA, OR abandoned checkout. Not life:subscription-active.
Cadence: Day 1, Day 4, Day 8, Day 14.
Runs once per person per 12 months.
The objection this sequence exists to answer: "$250 a month is a lot of money to learn casting over video."

The strategic note that governs all four emails. That objection is correct on its face and cannot be argued away. $250/month is a lot of money, and there is free casting content on YouTube that is genuinely good. The Review Generation System already anticipated this exact review (§10.3, Worked Example 2 — "There are free YouTube channels that cover the same material. Feels like you're paying for the branding") and its response was the right one: do not defend the price. Redefine the product.

A tutorial library and a diagnostic relationship are two different goods that happen to both arrive through a screen. The entire sequence does one job: move the reader from comparing this to YouTube to comparing it to a coach. Against YouTube, $250 is absurd. Against a coach who watches your specific hands twice a month, it is unremarkable.

The mechanism that makes this credible is recommending the free thing out loud. A business that tells you not to buy is a business you believe when it tells you to.


V1 — SAY THE NUMBER OUT LOUD

Send: Day 1, 7:00 a.m. Pacific
Goal: name the objection before they can. Removes the salesman/prospect dynamic entirely.

Subject A: $250 a month is a lot of money
Subject B: You looked at the virtual program and left. Fair.
Preview text: Let's just talk about the number directly.

[FIRST NAME] —

You looked at the virtual casting program and didn't sign up. I'd like to guess why, and I'd like to be right.

It's $250 a month, and $250 a month is a lot of money to spend on casting over video.

That's the objection. It's a good one. Here's the only honest thing I can say about it.

If you're comparing this to fly casting videos, it's insane. There are hundreds of excellent free casting videos. Some of them are made by people I admire. If what you need is "show me what a double haul looks like," close this email and go watch one — genuinely, I'm not being passive-aggressive, that's the correct purchase and it costs nothing.

But that's not what most people who land on that page are trying to solve.

Most of them have watched the videos. Repeatedly. They know what the motion is supposed to look like. And their cast still falls apart at forty feet and they cannot tell you why, because you cannot see your own hands, and video of a good cast doesn't tell you what's wrong with yours.

That's the actual product. Not instruction. Diagnosis.

Somebody watching your cast — the real one, in your backyard, with your rod and your bad habits — and finding the one fault underneath the six symptoms. Then building a drill sequence for your hands specifically. Then watching again in two weeks to see if it took.

That's not a video library. That's a coach. And $250 a month for a coach who watches you twice a month is an entirely different arithmetic problem than $250 a month for videos.

[ What actually happens in a month → ]

Kristen

P.S. — I'm going to send you three more emails about this and then stop forever. The next one is just a plain description of what a month looks like, hour by hour, so you can do the math yourself.

CTA button: What actually happens in a month →
Link: /learn/virtual-casting-lessons
Design note: put the price in the subject line. Every instinct says don't. Do it anyway — the people who were never going to pay $250 self-select out on Day 1 instead of sitting in the sequence unengaged for two weeks, and the people who stay have already accepted the number, which changes the entire conversation.


V2 — THE HOUR-BY-HOUR

Send: Day 4, 7:00 a.m. Pacific
Goal: kill the vagueness. Vagueness is what makes a subscription feel expensive.

Subject A: What actually shows up, hour by hour
Subject B: A month of the virtual program, described boringly
Preview text: No metaphors. Just the actual sequence of events.

[FIRST NAME] —

No metaphors this time. Here is literally what happens.

Week 1 — you film. [CONFIRM: exact filming instructions — angles, duration, whether front-and-side is required.] Phone on a fence post, two angles, ninety seconds. It will feel stupid. Everyone says it feels stupid.

Week 1 — I watch it properly. Not "glance at it." Frame by frame, slowed down, repeatedly. What I'm doing is separating symptoms from cause. A tailing loop, a collapsed front cast, a rod that creeps, and a haul that dies are usually not four problems. They're one problem wearing four hats, and the whole skill is finding which hat.

Week 1 — you get the diagnosis in writing. One fault. Named plainly. Plus the drill sequence built for it: the component to isolate, the number of reps, and what "correct" feels like so you can tell without me.

Week 2 — we get on a call. [CONFIRM: session length and how they're scheduled.] You cast, I watch live, I correct in real time. This is the part that can't be replaced by anything asynchronous — I can see a fault forming and say something before you've drilled it in.

Weeks 3 and 4 — repeat. Film, diagnose, drill, call.

Then the useful part: at the end of month two, I put your week-1 video and your week-8 video side by side on the screen. Same rod. Same backyard. That's usually the session where people go quiet for a second.

The whole thing is month to month. Do one month. If it isn't worth it, cancel it. I'd genuinely rather you leave after thirty days than pay for six months of something you resent.

[ Start a month → ]

Kristen

P.S. — Most people who do this are not beginners. They're twelve-year anglers who've hit a ceiling and can't see their own hands. If that sentence made you wince, that's your answer.

CTA button: Start a month →
Link: /learn/virtual-casting-lessons
⚠️ [CONFIRM] block — do not send this email until all four are answered: filming instructions and required angles · call length · call cadence (weekly, biweekly?) · whether the side-by-side comparison at day 60 is a formal deliverable. This email's entire power is specificity, and a specific email with a wrong specific in it is worse than a vague one.


V3 — GO WATCH THE FREE STUFF

Send: Day 8, 7:00 a.m. Pacific
Goal: the credibility move. Recommend the competition honestly and let the distinction do the selling.

Subject A: Go watch the free videos first. Seriously.
Subject B: When YouTube is the better buy
Preview text: I'm about to talk you out of this, and then back into it.

[FIRST NAME] —

Third email. This one's mostly me arguing against myself.

Do not pay me $250 a month if any of these is true:

You've never held a fly rod. Start free. Watch videos, go to a shop's free casting clinic, get a rod in your hand, find out whether you even like this. Paying for diagnosis before you have anything to diagnose is backwards.

You want to learn a specific named technique. Reach mend, roll cast, water haul — that's a knowledge problem, not a diagnosis problem, and the internet has solved it. Go get it for free.

You won't practice. This is the real one. The program is diagnosis plus drills, and drills are a thing you do, in a yard, on days when you'd rather not. If ten minutes three times a week isn't happening, you'll pay me to tell you the same thing twice and both of us will be sad about it.

You're hoping it will feel good. It's mostly the opposite. Finding out that the thing you've done for a decade is the thing that's wrong is not a pleasant twenty minutes. It's a useful twenty minutes, which is different.

Pay me $250 a month if this is true instead:

You've fished for years. You've watched the videos — probably all of them. You know roughly what good looks like. And your cast still falls apart in wind, or at distance, or with anything heavy on the end of it, and you have genuinely no idea which of your six problems is the actual problem.

That is a diagnosis problem, and diagnosis is not a content format. It requires someone looking at you.

Nobody can be talked into or out of that. You either recognize yourself in that paragraph or you don't.

[ If you recognized yourself → ]

Kristen

CTA button: If you recognized yourself →
Link: /learn/virtual-casting-lessons
Design note: the two bolded headers — "Do not pay me" / "Pay me" — should be visually distinct blocks. This is the highest-conversion email in the sequence because it disqualifies. It also pre-empts the Ray T. review from the playbook by making the "YouTube is free" argument first, in Kristen's own voice, on her own terms.


V4 — LAST ONE

Send: Day 14, 7:00 a.m. Pacific
Goal: close, or exit gracefully. Real risk-reversal, no false urgency.

Subject A: Last one about this, then I go away
Subject B: One month. Cancel whenever. That's the whole risk.
Preview text: No deadline, no discount, no countdown. Just the last email.

[FIRST NAME] —

Last email about the virtual program. I said four and this is four.

There's no deadline and no discount. I'm not going to invent a countdown timer, because the honest situation is that the program will still be there in March and so will I.

So here's the actual decision, stripped down:

What you risk: one month. $250. Cancel any time, month to month, no contract.
What you're buying: [CONFIRM: number of video analyses and live sessions in a month] — someone watching your specific cast, finding the one fault under the six symptoms, and building drills for your hands.
What you'd find out: within thirty days, whether the thing that's been broken for years is fixable. That's the part people underestimate. Most of them have been quietly assuming it isn't.

It usually is. Not always — sometimes the answer is "your rod is wrong for what you're trying to do" and that's a one-time gear problem, not a $250-a-month one, and I'll tell you that on day four and refund you. But usually the answer is that one component broke early, everything downstream compensated for it, and nobody ever separated it out.

That's a solvable problem. It's just not a solvable-alone problem.

[ Do a month → ]

And if not — genuinely, no hard feelings. You'll stay on the regular list, I'll keep sending trout behavior, and this sequence will never run at you again. That's a promise I've automated, which is the most binding kind.

Kristen

P.S. — If the answer is "not now, but maybe this winter," that's the correct answer. December through February is when this program does its best work — you're not fishing anyway, and you show up in April having actually fixed something instead of hoping it fixed itself over the winter. Reply "winter" and I'll poke you in December. That's it, that's the whole system.

CTA button: Do a month →
Link: /learn/virtual-casting-lessons
Automation note: the P.S. reply-"winter" mechanism is worth building. Tag want:virtual-winter on that reply and pull them into the off-season sequence (§11) with a personalized O1. It converts a "no" into a scheduled "later," which is the most under-used move in small-business email.
Sequence exit: all four sent → return to newsletter cadence, flag:virtual-nurture-complete with a date so it can't re-run inside 12 months.


10. RE-ENGAGEMENT SEQUENCE (3 EMAILS)

Trigger: life:lapsed — no booking in 12+ months AND no email open in 90 days.
Cadence: Day 1, Day 6, Day 12.
Runs once per 12 months, maximum.
⚠️ Do not run against anyone who received review template E6 within the previous 60 days. See §5.3 — E6 and R1 are structurally the same email with different asks, and sending both exposes the machinery.
Hook: seasonal. Send these against the river doing something, not against a calendar quarter. The Yakima is the reason to write.


R1 — THE RIVER DID A THING

Send: Day 1, 7:00 a.m. Pacific
Goal: re-open the relationship with a real, specific, seasonal observation. Not "we miss you."

Subject A: The Yakima flipped and I thought of you
Subject B: Random question about a day [SEASON, YEAR]
Preview text: Not a sales email. Well — 20% a sales email. I'll be honest about which part.

[FIRST NAME] —

Weird email, and I'll tell you upfront which 20% of it is a sales email so you can skip that part if you want.

The 80%: [SEASONAL HOOK — one real, specific, current thing about the river. Written the week of the send, never recycled. Examples:
"The flip-flop happened three weeks ago — irrigation season ended, flows dropped off a cliff, and the river turned back into the thing it actually is. Every fish in it has relocated and most people fishing it this week haven't noticed."
"First Skwalas showed up on the [X] stretch on Tuesday. Big ugly stoneflies, and the fish lose their composure about them in a way that's genuinely funny to watch."
"It's 34 degrees, the water's gin clear, and there is nobody out there. Which is the point."]

I went back through old trip notes this week and found yours: [SPECIFIC DETAIL FROM THEIR TRIP].

Genuine question, and I actually want the answer: did it stick? Are you still reading water the way we worked on, or did it quietly fade back to casting at the pretty spot?

No judgment either way. Skills fade. That's not a character flaw, it's an extinction curve — behavior that stops getting reinforced stops occurring, and if you haven't been on good water in a year, nothing's been reinforcing it. That's the river's fault, not yours.

The 20%: [SEASON] is [OPEN / BOOKING NOW / the best six weeks of the year for X], and I'd like to get you back out.

[ See what's open → ]

And if it faded and you'd rather rebuild it from your backyard than book a day, reply "backyard" and I'll tell you what I'd have you do. No charge for the recommendation.

Kristen

CTA button: See what's open →
Link: /trips/yakima-river-guided-trips
Design note: the seasonal hook paragraph must be genuinely current. Rewrite it every time. A recycled river report is worse than no email — this audience will know.
Reply routing: "backyard" → tag want:virtual and reply personally. Do not auto-drop them into the virtual nurture sequence; they asked a person a question and should get a person.


R2 — WHAT'S CHANGED

Send: Day 6, 7:00 a.m. Pacific
Goal: give a reason to re-engage that isn't a purchase. Curated best-of, per the standard re-engagement structure.

Subject A: Three things worth your time, then I'll shut up
Subject B: What's changed since you were out here
Preview text: Including one thing I got wrong and have since fixed.

[FIRST NAME] —

No ask in this one. Three things from the last year, in case any of them are useful.

1. [BEST-PERFORMING METHOD POST]
[One sentence on what it argues.] [e.g. "The full write-up of why trout aren't smart — they're conditioned — and what that changes about where you cast."]
[ Read it → ]

2. [BEST-PERFORMING TECHNIQUE OR YAKIMA POST]
[One sentence.] [e.g. "A month-by-month guide to what the Yakima actually does, written from twenty years of it rather than from a hatch chart."]
[ Read it → ]

3. [THE THING THAT CHANGED IN THE BUSINESS]
[One sentence — a new program, Nate's dry-fly trips, the virtual program, the retreats.] [CONFIRM: what's genuinely new since this segment last engaged.]
[ Have a look → ]

And one thing I got wrong: [SOMETHING GENUINELY REVISED — a technique opinion Kristen has changed her mind about, a piece of advice she'd now give differently. This is optional but it is the single most re-engaging paragraph available to a teaching business. Do not fake it. If nothing's changed, cut the section.]

That's it. Nothing to buy today.

Kristen

CTA: three links is a deliberate exception to the one-link rule. This is a menu email by design — the click tells you what they still care about, and that click retags them. Whichever they click sets want:.
Design note: cards or bold headers with a one-line description. Scannable in eight seconds.


R3 — SHOULD I STOP

Send: Day 12, 7:00 a.m. Pacific
Goal: clean the list. A genuine, respectful, one-button exit — which is also, reliably, the highest-open email in any re-engagement sequence.

Subject A: Should I stop emailing you?
Subject B: One button. No hard feelings either way.
Preview text: Genuinely asking. Both answers are fine.

[FIRST NAME] —

Straight question: do you want to keep hearing from me?

You haven't opened anything in a while, which is completely reasonable — inboxes are a nightmare and I am one more thing in yours.

Here's the thing about a small list: I'd rather have four hundred people who actually want this than four thousand who don't. Emailing people who've stopped caring is bad for me (it wrecks deliverability, which means the people who do want it stop getting it) and it's mildly rude to you.

So, one button, either one:

[ Keep me on the list → ]

[ Take me off → ]

If you pick the second one, no hard feelings and no follow-up campaign designed to win you back. That's not a thing I'd do to a person.

If neither, I'll take the hint and quietly stop in a few weeks. You'll still be able to book a trip; you just won't hear from me until you do.

Kristen

P.S. — If the real answer is "I like the fishing stuff, I just don't want to be sold anything," there's a version of that. Reply "just the trout" and I'll take you off everything except the monthly. That's a real setting and I'll set it by hand.

CTA: two buttons. Keep me on the list → (tags life:subscriber, resets engagement, exits sequence) and Take me off → (unsubscribe link).
Reply routing: "just the trout" → tag flag:do-not-sell. Suppressed from every sales sequence forever; receives newsletter only. Honor this permanently. A list of people who trust you not to sell at them is worth more than the sales you'd have made.
No response to all three:life:sunset. Suppress for six months, then remove. See §16.4.


11. OFF-SEASON / WINTER SEQUENCE (3 EMAILS)

Window: December – February. Send dates: Dec 3 · Jan 7 · Feb 4 (adjust each year to land on a Wednesday, matching the Content Calendar's Wednesday email slot).
Audience: all engaged subscribers. Suppress life:booked for a trip inside the window. Suppress life:subscription-active from the O1 virtual pitch — send them the alternate paragraph.
Job: keep the list warm through the quiet months, sell virtual lessons, and take next-season deposits.

Why this window matters more than any other. The Content Calendar is explicit: "Winter (Dec–Feb) sends are the highest-converting of the year — that is the virtual-lessons window" (§6), and the Dec–Feb row of the seasonality table names virtual lessons, gift certificates, and next-season deposits as the products. This is the quarter where a geography-independent product meets a captive, bored, planning-minded audience. Three emails is the floor, not the ceiling — these run alongside the monthly newsletter, not instead of it.

Aligns with Content Calendar posts #10 (Winter on the Yakima), #11 (Fix Your Cast Indoors), #12 (The Gift That Isn't Gear), #13 (How We Break a Cast Into Pieces), #14 (Yakima River Season Guide), #15 (Reading Water From Your Couch), #18 (Skwala Season).


O1 — NOBODY GETS BETTER IN JULY

Send: Dec 3, 7:00 a.m. Pacific
Goal: reframe winter from dead season to the only season where improvement actually happens. Sell virtual lessons.

Subject A: Nobody gets better in July
Subject B: The river's cold. This is your window.
Preview text: The counterintuitive case for December being the most useful fishing month.

[FIRST NAME] —

Unpopular opinion, delivered in December when it's easiest to accept: almost nobody improves at fly fishing during fishing season.

Think about what June actually looks like. You get four days on the water in three months, the fish are eating, and every one of those days you do the thing you already know how to do, because you drove two hours and you'd like to catch something. Nobody drills a fault on a good day. Why would you? There are fish rising.

That's not practice. That's performance, and performance under reward conditions is where bad habits get most reinforced. The tailing loop that catches a fish anyway is a tailing loop that just got paid.

Improvement happens where the stakes are zero. Which is a yard, in a coat, in January, with a hunk of yarn on the end of your line and nothing whatsoever riding on the outcome.

Two things that are worth your winter:

1. Ten minutes, three times a week, in the yard. More useful than a guided day, and I say that as someone who sells guided days. Short and frequent beats long and rare — that's not motivational, it's just how motor learning works.

2. Somebody watching you do it. [Alternate paragraph for life:subscription-active: "You've already got this part handled — I'll see you at your session, bring the 6-weight."] The virtual program is $250 a month, month to month, and December through February is when it does its best work. You're not fishing anyway. You show up in April having actually fixed something, rather than hoping it fixed itself over the winter. It does not fix itself over the winter. I've checked, repeatedly, for twenty years.

[ Fix something before spring → ]

Kristen

P.S. — Also, gift certificates exist, and "a day of instruction" is a substantially better present than the sixth fly box a person did not need. [CONFIRM: gift certificate link and denominations.]

CTA button: Fix something before spring →
Link: /learn/virtual-casting-lessons
Design note: the P.S. is the gift-certificate mention. Keep it there rather than promoting it — a December email that leads with gift certificates is every other December email in the inbox. Lead with the idea; let the gift be the aside. The dedicated gift push is a separate broadcast on Dec 15, aligned to Content Calendar post #12.


O2 — WHERE DO YOU WANT TO BE STANDING IN MAY

Send: Jan 7, 7:00 a.m. Pacific
Goal: convert planning energy into a booked date. January is the planning window per the Content Calendar.

Subject A: Where do you want to be standing in May?
Subject B: Let's put a date on it before March disappears
Preview text: January is when this gets decided, whether you decide it or not.

[FIRST NAME] —

It's January, which means you are currently the most optimistic version of yourself you will be all year. Let's use that productively before February arrives and ruins it.

A question worth sitting with: where do you want to be standing in May?

Not "would I like to fish more." Everyone would like to fish more. Specifically: what water, what month, doing what, having fixed what?

Because here's the mechanical problem. There are two of us. Three students per instructor, maximum. That's not a scarcity tactic, it's the number above which I can't actually watch anybody's hands, and I'd rather run fewer days properly than more days badly. Which means a season has a hard ceiling, and the good weeks — [CONFIRM: which weeks genuinely book first] — go to whoever decided in January.

I put together the whole year on the Yakima, month by month, so you can pick a month for a reason instead of by accident: what's hatching, what the flows are doing, what the fish are actually up to, and what each month is good for learning, which is a different question than what it's good for catching.

[ The Yakima, month by month → ]

Then reply and tell me the month. I'll tell you honestly whether it's the right one for what you want to work on — including if the answer is "come in a different month," which it sometimes is.

Kristen

P.S. — [CONFIRM: does Kristen take deposits to hold a date, and is there a deposit amount / policy she wants stated?] If so, this is the email it goes in.

CTA button: The Yakima, month by month →
Link: /journal/yakima-river-season-guide (Content Calendar post #14 ⭐, publishes Jan 19 — send O2 after that post is live, or move O2 to Jan 21. A cornerstone post is a much better destination than a service page here.)
Design note: no image. The strength of this email is that it asks a question the reader answers in their own head before they finish reading it.


O3 — THE FIRST BUGS

Send: Feb 4, 7:00 a.m. Pacific
Goal: seasonal urgency that's genuinely real. Skwalas are coming; booking season is opening; last virtual push before spring.

Subject A: The Skwalas are coming and I'm getting weird about it
Subject B: First bugs of the year. Time to pick a day.
Preview text: Big ugly stoneflies, and the fish completely lose their composure.

[FIRST NAME] —

Every year around now I become insufferable about a bug, and I'd like to warn you that it's starting.

Skwalas. [CONFIRM: actual timing on the Yakima — this document should not guess at hatch dates, and Kristen's twenty years beat any public hatch chart.] Big, ugly, unglamorous stoneflies that show up while it's still genuinely cold, and the fish — who have spent three months eating nothing but tiny nymphs in slow water — completely lose their composure about them.

What makes it worth a day off work isn't the bug. It's what the bug does to the behavior. You get fish that have been conservative all winter making genuinely reckless decisions in shallow water, in February, in daylight. Every rule you learned about winter fish stops applying over about ten days. It's the clearest demonstration I know of the whole argument — that fish aren't following preferences, they're following an energy calculation, and when the calculation changes, everything about them changes with it.

It's also, for that reason, an excellent day to learn on. Obvious cause, obvious effect, fish willing to show you the answer.

Two things, and then I'll stop:

If you want a spring day — this is the window where the calendar fills. [CONFIRM: current booking status / which months are already tight.]
[ Pick a day → ]

If spring's not realistic this year — you've got about eight weeks before you'd want your cast working, which is exactly one round of the virtual program. Not a coincidence; that's why I'm mentioning it in February rather than April.

Kristen

P.S. — Nate would like it noted that he thinks I'm wrong about Skwalas and that the March Browns are the real event. He is incorrect, but he rows a nice boat, and if dry flies are your thing he's your guy.

CTA button: Pick a day →
Link: /trips/yakima-river-guided-trips
Design note: the Nate P.S. is doing three jobs — it introduces the second instructor, it segments (flag:nate if they reply about dry flies), and it makes a two-person business feel like a two-person business rather than a brand. Use variants of it regularly.
Sequence exit: subscribers return to normal newsletter cadence March 1. Anyone who clicked a booking CTA → life:prospect + want:guided.


12. MONTHLY NEWSLETTER TEMPLATE

12.1 Cadence, and how it reconciles with the Content Calendar

The Content Calendar's repurposing system (§6) specifies a Wednesday email send after each Tuesday blog post — three per month. This system keeps that cadence and gives the three sends different weights, so the list gets one substantial email a month rather than three medium ones:

Send When Format Length
The Monthly Wednesday after the month's first post Full newsletter, all seven sections. The month's first post is the featured piece. 500–700 words
Single-topic #1 Wednesday after the month's second post One idea, one link, Kristen's voice, no sections 150–250 words
Single-topic #2 Wednesday after the month's third post Same 150–250 words

Plus whatever sequence emails a given subscriber is in. Global suppression rule 1 (§4.3) prevents doubling up on a day.

Send time: Wednesday 7:00 a.m. Pacific. [CONFIRM against actual data after 90 days — see §17. This is a starting point, not a finding.] The reasoning for the starting point: this audience reads about fishing at the edges of the day, and a 7 a.m. Pacific send lands early-morning on the West Coast and mid-morning for the East Coast half of the virtual-lesson audience.

12.2 The repeatable section structure

Seven sections, same order every month. The consistency is the product — people learn where their favorite part is and skim to it, and a newsletter people know how to skim is a newsletter people keep.

# Section Standing name Words Sourced from Job
1 Personal note "From the boat" 60–90 Kristen's actual month Human. Sets the voice before anything else loads.
2 Featured content "One thing about trout" 150 🧠 Method pillar — the month's Method post The authority engine. Never skip.
3 River report "What the Yakima's doing" 100 🏞️ Yakima pillar + actual current conditions The reason locals open it. Must be genuinely current.
4 Drill "Ten minutes" 75 🎣 Technique pillar One drill, one component, doable this week. The most-forwarded section.
5 Human side "The other thing" 75 💬 Human pillar Differentiation and shareability.
6 Social proof "From a student" 50 The Review Generation System's output ⚠️ Leave this section out entirely until real reviews exist. Never fabricate. See §12.4.
7 What's open "What's open" 50 Seasonality table, Content Calendar §1 The only sales section. One product, chosen by month.
Footer Kristen's photo, address, one-click unsubscribe, preference link

The rule that keeps this sustainable: every section except 1, 3, and 7 is cut from a blog post that already exists. The newsletter is assembled, not written. That's the whole reason a two-person team can sustain it in July.

12.3 Which product goes in "What's open," by month

From the Content Calendar seasonality table (§1):

Months "What's open" promotes
Sep–Nov Streamer trips, Streamer Stomp, late-season guided days
Dec–Feb Virtual lessons, gift certificates (Dec), next-season deposits (Jan–Feb)
Mar–May Guided trips, casting camp, schools — this is booking season
Jun–Aug Group retreats, dry fly trips (Nate), schools

12.4 The social proof section — the honest version

Trout Psychology has zero locatable reviews as of August 2026. Section 6 therefore does not ship in the first issues. Do not write a placeholder testimonial, a composite, or a "here's what people tell me" paraphrase.

The section switches on when the Review Generation System produces real material — which, per its own Launch Checklist, should be roughly three weeks after the E6 kickstart send. Then:
- One quote. Real, attributed to first name + last initial, ideally linked to the live Google review.
- Prefer the pedagogy reviews over the fish-count reviews, always. A review that describes how a skill got decomposed is worth ten that say "great day, caught fish." That is the whole thesis of the review playbook and it applies identically here.
- Two sentences maximum. If it needs three, it's a blog post instead.

12.5 Sample issue — December 2026

Built from Content Calendar posts #10 (Winter on the Yakima), #11 (Fix Your Cast Indoors), #12 (The Gift That Isn't Gear). Section 6 omitted — see above.


Subject: December: the most useful month of the year, if you're weird about it
Preview text: Winter fish, an indoor drill, and why gear is a bad present.


From the boat

Hello from a house, which is where I am, which is upsetting.

The flip-flop finished up and the river's settled into its winter shape. I rowed [DAY] in 31 degrees with [CONFIRM: real detail], caught two fish, and lost feeling in my hands somewhere around noon. Worth it. Mostly worth it. Roughly 60% worth it.

Here's December.


One thing about trout 🧠

Winter fish aren't lazy. They're solving a harder math problem.

The standard winter advice is "fish slow, fish deep, they're sluggish." True as far as it goes, but it's a description, not a reason, and descriptions don't transfer to water you've never seen.

Here's the reason. A trout in 38-degree water has a metabolic budget roughly a fraction of its August budget. Every movement is a withdrawal against an account that isn't being replenished quickly. So the fish does what any organism under those conditions does: it relocates to wherever the ratio of calories-delivered to calories-spent is highest, and it stops taking any bet that doesn't clearly pay.

That's not sluggishness. That's the same energy calculation running all year, with the constants changed.

Which tells you exactly where to look — not "deep water," but slow water immediately adjacent to a food conveyor. The fish wants a couch next to a buffet. In August it'll walk across the room for a snack. In December it will not.

[ The full winter breakdown → ] (post #10)


What the Yakima's doing 🏞️

[CONFIRM — written the week of the send: flows, clarity, water temp, what's hatching if anything (midges, BWO on the grey days), which stretches are fishing and which are frozen mud. Access notes — what's plowed, what isn't. Never recycle this section. A stale river report is the fastest way to lose a local reader permanently.]


Ten minutes 🎣

This month: the pause.

Rod, no line, living room, ten minutes. Make your back cast stop — and then count one full second before you start forward. Out loud. You'll feel like an idiot. Do it anyway.

Nearly everyone's loop problem is a timing problem wearing a technique costume: the forward stroke starts before the line has straightened, so the rod loads against slack instead of against line. You cannot feel this happening. You can only feel the result, which is a cast that dies at forty feet.

Counting out loud works because it makes an invisible interval into an audible one. That's the whole trick. It's not sophisticated. It just works.

[ More indoor drills → ] (post #11)


The other thing 💬

Please do not buy the angler in your life more gear.

They have gear. They have a fly box they don't use and a net they complain about. What they don't have is somebody explaining why, which is the thing that actually makes fishing stop being frustrating.

I'm biased. I'm also right.

[ The gift that isn't gear → ] (post #12)


What's open ❄️

Virtual casting lessons — $250/month, month to month. Winter is when this program does its best work. You're not fishing anyway; you may as well arrive in April having fixed something.

Gift certificates — [CONFIRM: denominations and link]. Order by [CONFIRM: date] for delivery before the 25th.

[ Both, here → ]


Kristen
Trout Psychology · Cle Elum, WA · 206-659-5501

You're getting this because you asked for [LEAD MAGNET] or fished with us. [Change what you get] · [Unsubscribe]


Design notes for the template:
- Emoji section markers map to the Content Calendar's pillar icons — 🧠 🏞️ 🎣 💬. Same visual vocabulary across blog, email, and Instagram. This is cheap brand consistency and it costs nothing to maintain.
- Horizontal rules between sections. No colored boxes, no card layouts. Text with air around it.
- One image maximum, and only if it's a real photo from that month — a fish, a frozen guide, a whiteboard in a boat. A stock photo in this newsletter would be a betrayal of the whole voice.
- Footer must carry: Kristen's photo (not a logo), a physical mailing address [CONFIRM — CAN-SPAM requires one; the Phase 1 audit found no published street address. A PO box is acceptable and is the usual answer for a service-area business], one-click unsubscribe, and a preference-center link.


13. LEAD MAGNET CONCEPTS (3)

The selection principle: two of these are already committed. The Content Calendar (§8, item 3) names "two lead magnets to build before their post dates: the river journal template (before Nov 24) and the strategy blueprint flowchart (before Jun 15)." Those aren't inventions — they are streamside artifacts Kristen already uses. The Client Profile lists "portable streamside teaching materials: workbooks, whiteboards, flowcharts" and "river journaling to build observational skill" as core instructional mechanics of the Method.

That means Concepts 1 and 2 are not marketing assets dressed up as teaching tools. They are teaching tools that already exist in physical form, moved to PDF. That is the difference between a lead magnet somebody downloads and a lead magnet somebody uses, and it is the entire reason these will outperform a generic "10 Tips" PDF.

Concept 3 is the one built for the funnel rather than the river — and it earns its place by being the segmentation engine that makes §3 work.


CONCEPT 1 — THE RIVER JOURNAL

Title: The River Journal — A Twelve-Page Field System for Learning Water Instead of Just Fishing It
(Short form on the site and in subject lines: "The River Journal")

Format: 12-page PDF. Two versions in one download: a print version (5×8, designed to be printed double-sided, folded, and shoved in a wader pocket) and a fillable digital version for people who'd rather type. Deliberately not pretty — grid paper, wide margins, room to draw badly. A journal that looks too nice doesn't get written in.

Who it targets: skill:beginner through skill:experienced, any geography. Broadest appeal of the three, and the best top-of-funnel asset the business can own. Especially strong with skill:stuck — people who've fished for years and can feel they've plateaued but can't say why. A journal is how you find out why.

Why it's a genuine extension of the Method: river journaling is listed in the Client Profile as one of the Method's instructional mechanics. This is the take-home version of a thing Kristen already teaches on the water — and journaling is itself a behavior-analytic technique: self-monitoring. Recording your own behavior changes it, reliably, before any instruction is applied. That's a real finding and it's the honest sales pitch for the asset: this works even if you never buy anything from me.

Content outline:

  1. Page 1 — Why write anything down. The self-monitoring argument in 250 words. The observation that anglers remember fish and forget conditions, which is precisely backwards: the fish is the outcome, the conditions are the data.
  2. Page 2 — How to use this without it becoming homework. Four minutes at the takeout. Not an essay. The single most important page, because it's the one that prevents abandonment in week three.
  3. Pages 3–4 — The observation page (repeatable template). Date · water temp · flow · clarity · air temp · sky · wind · what was hatching · where fish were holding · where they weren't. Boxes, not prose.
  4. Page 5 — The sketch box. Draw the run. Mark where you fished it and where the fish actually were. Half a page of blank space with a prompt. This is the page that changes people — most anglers have never once drawn a piece of water, and drawing forces you to notice structure you'd otherwise walk past.
  5. Page 6 — The three questions. What did I predict? What happened? What was the difference? The entire scientific method, compressed onto one page, applied to a day of fishing.
  6. Page 7 — The refusal log. Every fish that looked and said no. What it looked at, and what you changed. Refusals are the highest-information event on the water and almost nobody records them.
  7. Page 8 — The one-thing-I'd-do-differently box. One line. Not five.
  8. Page 9 — Reading your own journal. How to review three months of entries and find the pattern — including the two patterns nearly everyone finds, which are (a) you fish the same water type over and over and (b) your best days share a variable you've never noticed.
  9. Page 10 — A worked example. One of Kristen's actual filled-in pages, handwriting and all. [CONFIRM: Kristen supplies a real page. This is non-negotiable — a blank template with no example is a template nobody uses, and a fabricated example would be dishonest and would also be obviously fake to anyone who fishes.]
  10. Pages 11–12 — Ten blank observation pages to print as many times as needed.

Ships: before Nov 24, 2026 — Content Calendar post #9 (River Journaling) is its launch vehicle, and /method/river-journaling must be live first.

Opt-in page copy

H1: Most anglers remember the fish and forget everything that mattered.

Subhead: A twelve-page field journal for learning water instead of just fishing it. Free, printable, and designed to be ruined by rain.

Body:

Here's a thing that happens to nearly everyone.

You have a genuinely great day. Everything works. You drive home turning it over in your head and you think: right, I've got it now.

Six weeks later you're standing in similar water on a similar day and you have absolutely no idea what you did. You remember the fish. You do not remember the flow, the temperature, the light, where they were holding, or the thing you changed that made it start working.

The fish was the outcome. Everything you forgot was the data.

I have a degree in behavior analysis and I'll tell you the least glamorous finding in the entire field: when people start recording their own behavior, their behavior changes — before anyone teaches them anything. It's called self-monitoring. It works on exercise, it works on spending, and it works alarmingly well on fly fishing, because the act of writing down "I fished the pretty water and ignored the seam" is very hard to keep doing without eventually fishing the seam.

This is the journal I use and the one I hand my students. Twelve pages. It takes four minutes at the takeout, not an hour at home. There's a page for sketching the run, a page for logging refusals — which is the most useful and most ignored data in fishing — and a page that asks you the only three questions that matter: what did I predict, what happened, and what was the difference?

There's also one of my own filled-in pages, handwriting and all, so you can see it doesn't need to be tidy. Mine isn't.

It's free. It works whether or not you ever fish with me. That's genuinely the point.

Form fields: First name · Email · "Are you closer to the Yakima River or to a computer?" (three options — sets geo:) · (optional) "Where do you fish?" free text
Button: Send me the journal →
Under button: You'll also get a few emails from me about how trout actually make decisions. Unsubscribe whenever; I won't take it personally.

Thank-you page:

It's on its way. Check your inbox in about a minute — it's from kristen@troutpsychology.com, and if it's not there, look in Promotions, because Google has opinions.

While you wait, one instruction: don't try to fill in every box on your first trip. Fill in three. Water temp, where the fish were, and one thing you'd do differently. That's it. Three fields for a month, and then add the rest.

The reason journals fail isn't laziness — it's that people start with a twelve-field template on day one, feel behind by day four, and quit by day nine. Start small enough that you can't fail. That's the whole technique, and it's the same one I use to teach a double haul.

— Kristen


CONCEPT 2 — THE REFUSAL FLOWCHART (a Strategy Blueprint)

Title: Why Did That Fish Say No? — A Decision Flowchart for Refusals
(Subtitle on the artifact: "A Trout Psychology Strategy Blueprint")

Format: A single-page decision flowchart, laid out for one sheet of paper, designed to be printed and laminated or screenshotted to a phone. Plus a 4-page companion explaining the reasoning behind each branch — because the whole pedagogy is that you learn the reasoning, not just the mechanics, and a flowchart with no reasoning behind it is a superstition with arrows.

Who it targets: skill:beginner through skill:experienced; strongest with skill:stuck, which is also the highest-value virtual-lesson segment. Any geography — refusals happen everywhere, which makes this the most portable proof of the Method's central claim that it transfers to any fishery.

Why it's a genuine extension of the Method: the Client Profile lists flowcharts among the portable streamside teaching materials Kristen already uses, and strategy blueprints"that let students problem-solve independently" — as a defining mechanic. This is a strategy blueprint. The Content Calendar has it committed as a build (§8 item 3), with post #29 (Strategy Blueprints ⭐, Jun 15) and post #33 (The Refusal, Jul 27) as its content homes, targeting keyword sub-cluster 3C. It is also the best possible demonstration of the Method's core argument: a refusal is a behavioral event with a cause, and causes can be worked through in order.

Content outline:

The flowchart — the decision tree:

  1. START: Did the fish move to the fly?
    - No → it never saw it, or it isn't there. → Presentation / position branch.
    - Yes → it saw it and declined. → Decision branch. (This distinction is the whole chart. Nearly everyone treats "no eat" as one event; it is two completely different events with almost no overlap in solution.)
  2. Position branch: Are you covering water fish are actually in? → Depth: is the fly in the feeding lane vertically? → Drift: is it moving at the speed of the water it's in? → Approach: did the fish know you were there before the fly did?
  3. Decision branch: How far did it move? (A long move means high interest and one wrong detail. A short lift means low interest and a bigger problem.) → At what point did it refuse? (At range = silhouette/size. At the last inch = drag, tippet, or a micro-drag you can't see.) → Did it refuse once or repeatedly? (Repeated refusals from the same fish are the single most information-rich event available to you, and most people leave and go find a different fish.)
  4. Terminal nodes — eight of them, each naming the actual fix in order of what to change first: drift before fly, position before pattern, size before color, tippet before either. The ordering is the value. Everyone's instinct under refusal is to change the fly. The fly is almost never first.
  5. The bottom bar: "Change one variable at a time. If you change three, you learn nothing — you just got lucky or didn't."

The companion pages: why each branch exists, what the behavior underneath it is, and the honest note that a percentage of refusals have no discoverable cause and the correct response to those is to move on without theorizing.

Ships: before Jun 15, 2027 per the Content Calendar. Recommend pulling this forward to spring 2027 — it's the strongest of the three for skill:stuck, which is the segment that buys the $250/mo product, and it should be live before the March–May booking peak.

Opt-in page copy

H1: A trout looked at your fly and said no. There is a reason, and it's usually not the fly.

Subhead: A one-page decision flowchart for working through a refusal in the correct order. Print it, laminate it, put it in the boat.

Body:

Watch what happens on the water when a good fish rises to a fly and doesn't eat it.

The angler changes the fly.

Almost every time. It's the most available lever and it feels like doing something. It's also, statistically, close to the last thing that should have changed.

Here's the thing that reframes it. A refusal isn't a rejection of your fly — it's a behavioral event with a cause, and there are only so many causes. A fish that moved three feet and turned away at the last inch is telling you something completely different from a fish that lifted an inch and settled back down. One of those is a fish that wanted it and found one detail wrong. The other is a fish that was never really convinced. Same non-eat. Opposite problems. Opposite fixes.

This is the flowchart I use, and the one I draw on a whiteboard in the boat when someone's third fish in a row has said no and they're getting quietly furious about it.

It starts with one question — did the fish move to it? — and branches from there through drift, depth, position, approach, size, and tippet, in the order you should actually check them. Eight endpoints. Each one names the specific fix.

There's a companion piece explaining why each branch is where it is, because a flowchart you follow without understanding is just a superstition with arrows, and I refuse to teach that.

One page. Free. Designed to get wet.

Form fields: First name · Email · "Are you closer to the Yakima River or to a computer?" (sets geo:) · "How long have you been fishing?" (four options — sets skill:)
Button: Send me the flowchart →
Under button: Also gets you a few emails about how trout make decisions. It's the most interesting thing I know and I'm normal about it.

Thank-you page:

On its way. From kristen@troutpsychology.com — check Promotions if it's hiding.

How to actually use it: print it, laminate it or slide it in a zip bag, and keep it in the boat. Not because you'll need to read it every time — because the first six times you do read it, you'll build the sequence into your head, and after that you'll run it automatically without the paper.

That's how it's supposed to work. The chart is scaffolding. The goal is that you throw it away.

— Kristen


CONCEPT 3 — THE CAST DIAGNOSTIC (quiz / assessment)

Title: The Cast Diagnostic — Eight Questions to Find the One Thing Actually Wrong With Your Cast

Format: Interactive 8-question self-assessment. Built in [CONFIRM: Typeform, Squarespace Forms, or Kit's native form — Typeform gives the best completion rate for a scored quiz; Squarespace is one fewer tool]. Returns one of four diagnostic profiles, delivered on-screen and again by email with a profile-specific drill.

Who it targets: skill:beginner and skill:stuck, all geographies. This one's job is different from the other two: it is the segmentation engine. It sets skill: and geo: accurately at opt-in, and it routes people to the right product without anyone having to guess. It is also the most direct on-ramp to the virtual program, because it produces the exact realization the program sells — there's one thing wrong and I can't see it.

Why it works for this brand specifically: the whole Method is decomposition — find the component, isolate it, drill it. A diagnostic quiz is that argument, performed. And it's honest about its own limits, which is what makes the paid product make sense: eight questions can narrow you to a category; only somebody watching your actual hands can find the specific fault. The quiz doesn't oversell. It creates an accurate appetite.

Content outline — the eight questions:

  1. When your cast falls apart, at roughly what distance? (under 30 ft / 30–45 / 45–60 / only when I try to go long)
  2. What does the failure look like? (pile of line / tailing loop and wind knots / line lands but the fly slaps / it just... stops)
  3. Wind: (fine / falls apart into a headwind / falls apart in any wind at all / I go home)
  4. Heavy flies or an indicator rig: (no change / everything gets worse / I dread it / I don't fish those)
  5. Have you ever seen video of your own cast? (never / once, briefly, and I disliked it / yes, regularly)
  6. How long have you been fishing, and how long have you been casting like this? (sets skill:)
  7. When you practice, what does that look like? (I don't / I practice on the water / 10 min in the yard sometimes / regularly and deliberately)
  8. Where do you fish, realistically? (sets geo:)

The four result profiles:

Profile Diagnosis Drill delivered Routed to
The Timing Problem You start forward before the line's straight. Everything downstream is a symptom. The one-second pause count Virtual lessons — timing is invisible without video
The Power Problem You apply force through the whole stroke instead of accelerating to a stop. Rod-tip-to-a-stop, no line Casting camp / schools if local; virtual if not
The Slack Problem Your line hand and rod hand are having different conversations. Hauls die, loops open. The isolated line-hand drill (from Welcome email 3) Virtual lessons
The It's-Not-Your-Cast Problem Your cast is fine. You're catching fewer fish for reasons that have nothing to do with casting — position, drift, or where you're choosing to fish. The refusal flowchart (Concept 2) Guided trip / private education

That fourth profile matters. A casting quiz that concludes "you need casting lessons" 100% of the time is a sales funnel wearing a lab coat. Telling a meaningful share of respondents your cast isn't the problem is what makes the other three results believable — and it routes them to the higher-value in-person products, which is better business anyway.

Ships: before Dec 1, 2026 — it should be live for the winter virtual-lessons push, which the Content Calendar identifies as the highest-converting email window of the year.

Opt-in page copy

H1: You have one casting problem, not six. Eight questions to find out which one.

Subhead: A free diagnostic. Takes two minutes. Ends with a drill built for whatever it finds.

Body:

A tailing loop, a cast that dies at forty feet, wind knots, a fly that slaps the water, and total collapse the moment you tie on a streamer.

That looks like five problems. It's almost always one problem wearing five hats.

This is the single most useful thing I know about teaching casting, and it comes straight out of behavior analysis: complex skills are made of components, and when a component breaks early in the chain, everything downstream compensates for it. The compensations are what you notice. The compensations are not the problem. And you will never fix a problem by drilling its symptoms — you'll just get very good at compensating.

So: eight questions. Not about technique — about failure patterns, which is the useful data. When does it break, what does the break look like, what makes it worse.

At the end you get one of four diagnoses and a drill built for it. Two minutes.

One honest caveat, because I'd rather say it upfront: eight questions can put you in the right category. They cannot find your specific fault — that genuinely requires someone watching your actual hands, which is a different thing that I also do. But the category is worth having. Most people have never even had that much, and they've been drilling symptoms for years.

Form fields: the eight questions, with email captured before the result is shown (standard practice, and defensible here because the result is genuinely substantial — but [CONFIRM: Kristen's preference. Showing the result first and gating the drill email is friendlier and more on-brand, at some cost to capture rate. Given that this brand's entire differentiator is not being pushy, the friendlier version may well outperform.])
Button: Show me the diagnosis →
Under button: Two minutes. Four possible answers. One of them is "your cast is fine, the problem is elsewhere," and about a quarter of people get it.

Thank-you / result page:

You're a [PROFILE NAME].

[PROFILE DESCRIPTION — 100 words, plain, no flattery. Name the mechanism.]

Your drill: [DRILL — one component, specific rep count, and what "correct" feels like so you can tell without me.]

Do it for two weeks. Ten minutes, three times a week — short and frequent genuinely beats long and rare, and it isn't close.

I've emailed you the drill plus the reasoning behind it, so you don't have to remember any of this.

Then the honest part: the diagnosis above is a category, not a diagnosis of you. If the drill fixes it, wonderful — that happens more than you'd think, and it cost you nothing. If it doesn't, that's real information too: it means the fault is one layer deeper than eight questions can reach, and finding it requires someone watching your hands.

That's [what the virtual program is / what a day on the water is for], and it'll be here when you want it.

— Kristen


13.4 Lead magnet build order

Priority Asset Ship by Gated on
1 The Cast Diagnostic Dec 1, 2026 Nothing. Fastest to build, feeds winter virtual push, sets skill: and geo: for the whole list. Build this first even though it's Concept 3.
2 The River Journal Nov 24, 2026 /method/river-journaling live · Kristen's real filled-in page
3 The Refusal Flowchart Spring 2027 (pulled forward from Jun 15) Design time for the chart · post #29 / #33 as content homes

Yes, priority 1 ships after priority 2's date. That's not an error — the journal has a hard date because a blog post launches it; the diagnostic has the higher strategic value and no dependencies, so it should be started first even though the journal lands first.


14. SIGNUP FORM COPY & PLACEMENT

Five placements. Each has a different job and therefore different copy. Do not run the same form copy in all five slots — a footer form and an exit-intent form are talking to people in completely different states of mind.

14.1 Homepage hero / above the fold

Trout are not smart. They're conditioned.
Which means their behavior is readable, and reading it is a teachable skill. Get the River Journal — the twelve-page field system I hand my students — plus a running argument about how trout actually make decisions.

[First name] [Email] [ Send me the journal → ]

Free. Printable. Designed to get wet.

Placement: below the primary hero CTA (which should always be "book a trip"), not above it. Email capture is the fallback for people not ready to book, not the primary conversion.

14.2 Journal / blog sidebar (and mobile: after paragraph 3)

The River Journal

Twelve pages. Four minutes at the takeout.

[Email] [ Send it → ]

Placement: sticky sidebar on desktop; inline after the third paragraph on mobile. [CONFIRM: Squarespace template supports a sticky sidebar — several don't.]

14.3 Exit intent

Before you go —

One question that'll change where you cast: where does the energy math work?

Not "where would a fish like to be." Where do the calories delivered exceed the calories spent holding position. That's the whole reframe, and there are eleven more where it came from.

[Email] [ Send me the trout stuff → ]

No pop-ups after this one. Promise.

Placement: desktop exit-intent only. Never on mobile — mobile exit-intent fires on scroll and is indistinguishable from a hostile ad. Cap at once per visitor per 30 days.
Voice note: the promise in the last line must be true. Configure the frequency cap before enabling.

Trout behavior, roughly monthly. No launches, no "we're excited to announce." Just what the river's doing and one thing worth practicing.

[Email] [ Sign up → ]

Placement: every page. This is a low-conversion, high-volume slot — the copy's whole job is to promise it won't be annoying.

14.5 Content upgrade (end of blog post)

Match the offer to the post's pillar. This converts several times better than a generic form because it's continuous with what they just read.

Post pillar Offer Copy
🧠 Method The River Journal "This whole argument is a lot easier to run on yourself if you're writing things down. Here's the journal I hand my students — twelve pages, free, includes one of my own filled-in pages."
🎣 Technique The Cast Diagnostic "Not sure whether this is your problem? Eight questions, two minutes, and one of the four possible answers is 'your cast is fine, it's something else.'"
🏞️ Yakima The River Journal "If you fish this river more than twice a year, start writing it down. You'll find your pattern inside a season. Here's the template."
💬 Human The River Journal "If any of that landed, the journal's the practical version of it. Free, and it works whether or not you ever fish with me."

14.6 Placement strategy summary

Placement Job Expected relative performance
Content upgrade (end of post) Highest-intent capture Best converting of the five. They just read 1,500 words.
Homepage hero Volume Moderate. Most homepage traffic is brand-search and already knows what it wants.
Blog sidebar Passive volume Low per-view, high total views
Exit intent Recovery Moderate, but only if capped and desktop-only
Footer Baseline Lowest, and worth having anyway — it costs nothing

Deliberately not stating conversion-rate benchmarks here. Published "average signup form conversion rates" vary by an order of magnitude depending on who measured them and how, and quoting one as a target for this site would be inventing a number. Measure these five against each other for 90 days and optimize against your own baseline. The relative ranking above is what to expect; the absolute numbers are Kristen's to discover.

A/B tests worth running, in order:
1. Lead magnet swap on the homepage hero — River Journal vs. Cast Diagnostic. (Probably the biggest single lever on the site.)
2. Two form fields vs. four. The geo: question is worth its friction; the "how long have you been fishing" question may not be. Test it.
3. Button copy: Send me the journal → vs. Send it →.


15. SUBJECT LINE BANK (62)

Organized by sequence, then by angle. Every line below is written in Kristen's voice and is usable as-is — these aren't templates with blanks to fill, they're finished lines, because a template in the wrong voice is worse than no template.

Four rules for anything added to this bank later:
1. Under 45 characters where possible. Mobile truncation is real and this list is read on phones.
2. No emoji in subject lines. They're in the newsletter section headers, which is enough. Emoji in the subject undercuts a science-forward brand.
3. Never manufacture urgency. Real scarcity exists — two instructors, 3:1 ratio, a finite March. Use the real thing or use none.
4. The best subject line is usually the strangest true sentence in the email. Look for it there before writing a new one.

15.1 Welcome sequence

Curiosity
1. Your river journal, plus a warning about me
2. Here's the thing you asked for. Also, hi.
3. Trout are not smart. This is good news.
4. The fish isn't outsmarting you
5. I broke a double haul into four pieces
6. The part of the haul nobody drills

Benefit
7. What a lesson actually looks like
8. One reframe that changes where you cast
9. Where does the energy math work?

Personal / conversational
10. Five things people are too polite to ask me
11. "Am I too bad at this to book?"
12. Okay. The actual pitch. It's short.

Real scarcity
13. There are about forty good days and then there aren't
14. Two instructors. Three students each. That's the ceiling.

Geography fork
15. You're not coming to Washington. Fine.
16. The version of this that works from your backyard

15.2 Pre-trip sequence

  1. Read this one. It's the only one that matters.
  2. Before your trip: what you actually booked
  3. We teach. That's the whole business.
  4. What to bring, what to skip, what I'll have
  5. Your gear list (it's shorter than you think)
  6. Please do not buy a new rod this week
  7. Tomorrow. Here's the plan.
  8. [TIME] at [PLACE]. One thing before you sleep.
  9. No cell service. Read this tonight.

15.3 Post-trip sequence

  1. Your blueprint, written down
  2. What we actually did on [DAY], and why
  3. Have you done the thing?
  4. Ten minutes in the yard. That's the whole email.
  5. Nine days is when a skill quietly dies
  6. What I'd have you do next
  7. Three weeks out. The honest recommendation.

15.4 Virtual lesson nurture

Objection-first
33. $250 a month is a lot of money
34. You looked at the virtual program and left. Fair.
35. Go watch the free videos first. Seriously.
36. When YouTube is the better buy

Specificity
37. What actually shows up, hour by hour
38. A month of the virtual program, described boringly
39. Six problems, one cause

Recognition
40. You can't see your own hands
41. Twelve years in and stuck. Sound familiar?
42. Week 1 you vs. week 8 you

Close
43. Last one about this, then I go away
44. One month. Cancel whenever. That's the risk.

15.5 Re-engagement

  1. The Yakima flipped and I thought of you
  2. Random question about a day two summers ago
  3. Did it stick? (⚠️ reserved for review template E6. Do not reuse in the re-engagement sequence — see §5.3)
  4. Three things worth your time, then I'll shut up
  5. What's changed since you were out here
  6. One thing I got wrong last year
  7. Should I stop emailing you?
  8. One button. No hard feelings either way.

15.6 Off-season / winter

  1. Nobody gets better in July
  2. The river's cold. This is your window.
  3. Where do you want to be standing in May?
  4. Let's put a date on it before March disappears
  5. The Skwalas are coming and I'm getting weird about it
  6. First bugs of the year. Time to pick a day.
  7. It fixed itself over the winter, said no one

15.7 Newsletter / broadcast

  1. December: the most useful month, if you're weird about it
  2. What the Yakima's doing, and one drill
  3. Winter fish aren't lazy. They're doing harder math.

15.8 Angle patterns worth reusing

When writing new lines, these five patterns carry this voice better than anything else:

Pattern Structure Example from above
Contradict the received wisdom "[Common belief] is wrong. [Better frame]." #3, #53, #62
Say the objection out loud State the reason they didn't buy, as the subject #33, #34
Recommend against yourself "Don't buy this / go do the free thing" #35, #36
The oddly specific number A count that implies the email is structured and finishable #5, #10, #48
The self-deprecating aside Undercut before anyone else can #1, #57

A/B testing discipline: run two per email for the first 30 sends of any sequence, then lock the winner. Test one variable at a time — subject or preview text, never both. With a small list, differences under a few percentage points are noise; wait for a real gap or wait for more sends.


16. DELIVERABILITY & LIST HYGIENE

None of the twenty-one emails above matter if they land in spam. This section is the least interesting part of the document and the one most likely to determine whether it works.

16.1 Authentication — do this before importing a single contact

Record What it does Notes for this domain
SPF Authorizes your sending platform to send as troutpsychology.com One SPF record only. If Google Workspace and Kit both send, they go in the same record — two SPF records is a hard fail.
DKIM Cryptographically signs each message Kit (or whichever platform) provides CNAMEs. Add them in Squarespace DNS or wherever the nameservers actually point. [CONFIRM: where DNS for troutpsychology.com is managed.]
DMARC Tells receivers what to do with mail that fails the above, and gives you reporting Start p=none with a reporting address for 30 days. Read the reports. Then move to p=quarantine. Do not start at p=reject — you will silently break something.

Required, not optional. Google and Yahoo's bulk-sender requirements (in force since February 2024) mandate SPF, DKIM and DMARC for anyone sending at volume to Gmail/Yahoo addresses, plus one-click list-unsubscribe headers and keeping spam complaints under 0.3%. Any modern platform handles the unsubscribe header automatically; the DNS records are on Kristen.

The streamsidecovenco.com note: Phase 1's addendum verified that domain 301-redirects cleanly. Do not send email from it. One sending domain, one brand, one reputation. If any legacy address still receives mail, forward it — don't send from it.

Sending identity: kristen@troutpsychology.com, display name "Kristen Bufe · Trout Psychology" — first name first. Never noreply@, never info@, never hello@. Matches the Review Generation System's global email rule, and it's also just true: a person is sending these.

16.2 The subdomain question

Standard advice is to send marketing mail from a subdomain (mail.troutpsychology.com) to isolate its reputation from transactional mail.

Recommendation here: don't, at least not yet. That advice exists for senders doing tens of thousands of messages a month, where a bad campaign can poison the domain that carries invoices. At this list size the tradeoff runs the other way — a fresh subdomain has no reputation at all and has to build one from zero, whereas troutpsychology.com has whatever history Kristen's regular correspondence has already earned. Revisit at 10,000+ subscribers.

16.3 ⚠️ The cold-list problem — the biggest deliverability risk in this engagement

The Review Generation System's Launch Checklist step 11 is to send template E6 to every past client on file, described as "the volume kickstart" that takes the review count from 0 to double digits.

As written, that is a mass send to a list that has never received an email from this domain, some of whose addresses may be years old. It is the single most reliable way to get a new sending domain flagged. Old addresses become spam traps. Recipients who don't remember opting in hit "report spam." One send above 0.3% complaints on a domain with no positive sending history can suppress deliverability for months — which would take out this entire system before it starts.

Do not skip the E6 send. Stage it.

Step Action Why
1. Verify first Run the entire imported list through a validation service before sending anything. Remove hard bounces, role addresses (info@, bookings@), and anything syntactically broken. [CONFIRM: list size determines cost; validation is inexpensive and non-negotiable here.] Removes spam traps and dead addresses before they touch your reputation
2. Segment by recency Three buckets: fished within 12 months · 12–36 months · older than 36 months Recency is the strongest predictor of both engagement and complaint risk
3. Warm up over three weeks Week 1: send to the most recent bucket only, in batches of ~50/day. Week 2: if bounces are under ~2% and complaints under 0.1%, add the middle bucket. Week 3: the oldest bucket, batched smallest. Gives mailbox providers a gradually rising volume curve with good engagement signals attached
4. Re-permission the oldest bucket For anyone 36+ months cold, send a single re-permission email — "We fished together in [YEAR]. I'm starting a proper email list. Want in?" — with an explicit opt-in button. Only people who click get added. Legally cleaner, dramatically safer, and it produces a list that actually opens things
5. Stop at the first bad signal If any batch bounces above ~5% or complains above 0.3%, stop and clean. Do not push through. One bad day is recoverable. Three is a reputation.

This changes the Review System's timeline. That document's Launch Checklist has E6 going out on Day 8. With staged warm-up it's Day 8 through roughly Day 29. Its estimate of "0 to roughly 8–15 reviews in the first three weeks" stretches to four or five weeks. That's the correct trade — the alternative risks the domain that every subsequent email in this system depends on.

16.4 Ongoing hygiene

Practice Cadence Rule
Bounce handling Automatic Hard bounces removed immediately. Soft bounces: remove after 3 consecutive.
Sunset policy Quarterly No opens in 180 days → run the re-engagement sequence (§10) → still nothing → life:sunset, suppressed. After 12 months total silence, delete. Paying a platform to not-reach people is the most common small-business email waste.
Complaint monitoring Weekly, 60 seconds Any send above 0.1% complaints gets reviewed. Above 0.3%, stop sending and diagnose.
Preference center Always available Three options: everything · just the monthly · nothing. The middle option converts would-be unsubscribes into retained readers and it's what flag:do-not-sell is built on.
Never buy or scrape a list Obviously. Also: don't add someone because they gave you a business card. That's not consent and it produces complaints.
Re-confirm nothing quietly Never move someone from "past client" to "subscriber" without telling them. §16.3 step 4 is how it's done properly.
Engagement segment Monthly Maintain a "most engaged" segment (opened 3 of last 10). Occasionally send to only them — it's the fastest way to repair a wobbling reputation.

16.5 Content-level deliverability


17. KPI TARGETS

17.1 The honesty caveat — read before using any number below

Trout Psychology has no email performance history. The Client Profile lists the email list itself as [CONFIRM], and the Content Calendar's measurement table (§7) shows email subscribers as [CONFIRM] at baseline.

Therefore: nothing in this section is Trout Psychology data, and none of it should be presented to anyone as a prediction of what this list will do. The ranges below are generic, publicly circulated industry reference ranges — they vary substantially between the sources that publish them, they're calculated differently by different platforms, and Apple Mail Privacy Protection has made open rates a materially inflated and unreliable metric since 2021.

Use them for one thing only: sanity-checking the first 90 days. After that, Kristen's own first-quarter numbers become the benchmark and everything here should be discarded.

Metric Generic reference range What to actually do
Open rate Roughly 20–40% is commonly cited across small-business/hobby lists, with wide variance Record your own week-1 number. Beat it next month. Ignore everything else. Treat opens as directional only — MPP inflates them.
Click-through rate Low single digits is typical; a well-targeted small list often runs higher This is the metric to actually manage. Clicks are real behavior. Opens are increasingly not.
Unsubscribe rate Under ~0.5% per send is generally considered healthy Spikes point at a specific email. Find it and fix it.
Spam complaints Must stay under 0.3% Not a benchmark — a hard requirement from Gmail/Yahoo. Non-negotiable.
List growth Content Calendar §7 targets +75 subscribers in Q1 rising to +800 by Q4. Those are this engagement's own targets. Use them.

17.2 The metrics that actually matter for this business

Open rates are vanity here. These five are the ones tied to revenue and to the stated authority goal:

Metric Why it's the right one Target
Replies per send This system is built on reply CTAs — P1's frustration question, W4's questions, PT2's cast video. A reply is worth ten clicks. It also feeds the custom curriculum, which is the product. Track it from send one. No external benchmark exists and none is needed — beat last month.
Virtual-lesson inquiries from email The scalable revenue product. Content Calendar §7 targets 10 blog-sourced virtual inquiries in Q2 (the winter window); email should meet or beat that, since it's the higher-intent channel. Match the blog's Q2 target
Trips booked with an email touch in the path Attribution is imperfect. Approximate it: ask "how'd you hear about us?" at booking and include an email option. Establish a baseline in Q1
P1 reply rate (pre-trip) The expectation-setting email. A high reply rate means it's being read — which is the whole point, since it's the defense against the review risk in §5.4. Target >30%. If it's under 15%, the subject line is wrong.
Post-trip → repeat booking within 12 months The single best measure of whether the teaching is landing. Also the cheapest revenue in the business. Establish a baseline, then move it

17.3 Send timing

Starting point: Wednesday, 7:00 a.m. Pacific for newsletters and broadcasts. Sequence emails at 7:00 a.m. Pacific, except P3 (6:00 p.m., evening before a trip) and PT1 (8:00 a.m., Day 2).

This is a hypothesis, not a finding. Reasoning: this audience reads about fishing at the edges of the day, 7 a.m. Pacific lands mid-morning for the East Coast half of the virtual audience, and Wednesday matches the Content Calendar's existing repurposing schedule.

Test it properly after 90 days, when there's enough volume: Wednesday 7 a.m. vs. Sunday 6 a.m. Pacific. Sunday morning is a genuinely plausible winner for a hobby audience — that's when people plan trips — but it is a guess until measured, and this document is not going to present a guess as a finding.


18. BUILD ORDER & OPEN ITEMS

18.1 Build order

Phase A — Infrastructure (weeks 1–2). Nothing sends until this is done.
1. Choose the platform (§2 recommends Kit). Create the account.
2. Authenticate the domain — SPF, DKIM, DMARC at p=none. Before any import. (§16.1)
3. Build the tag taxonomy from §3.2. All five families, named exactly.
4. Add the physical mailing address for the footer. [CONFIRM — CAN-SPAM requirement, and Phase 1 found no published address.]
5. Build the preference center with the three options from §16.4.

Phase B — Capture (weeks 2–4).
6. Build the Cast Diagnostic (§13 Concept 3). Fastest to ship, sets skill: and geo:, feeds the winter push.
7. Build the River Journal PDF. Requires Kristen's real filled-in page.
8. Install the five signup forms (§14).
9. Write and load the Welcome sequence (§6). Test it end-to-end on three real addresses, including one Gmail and one Outlook.

Phase C — The list (weeks 3–7). Runs in parallel; slowest step.
10. Validate the past-client list. (§16.3 step 1)
11. Staged warm-up import and the E6 review kickstart, over three weeks. (§16.3)

Phase D — Client sequences (weeks 5–8). Highest revenue impact.
12. Build the booking-tool → platform zap that writes trip_date. Clean up the Picktime page first.
13. Load the Pre-trip sequence (§7). P1 is the highest-priority single email in this document. Also paste its expectation-setting paragraph into the booking confirmation and the guide-trip page — Review System Appendix B item 7.
14. Load the Post-trip sequence (§8) with the Day 0 / Day 5 suppression rules wired. Verify against §5.2 before enabling.
15. Migrate the eight Review System templates in as sequences/broadcasts.

Phase E — Nurture and seasonal (weeks 8–12).
16. Load the Virtual nurture sequence (§9) — before December.
17. Load the Off-season sequence (§11) — before December 3.
18. Send the first monthly newsletter (§12).
19. Load the Re-engagement sequence (§10) — lowest urgency; nobody hits the 12-month trigger for a while.
20. Build the Refusal Flowchart (§13 Concept 2) for spring.

18.2 Open items for Kristen

Blocking — a sequence cannot send without these:

  1. [CONFIRM] Does an email list exist, how large, how old, and where? Gates all of Phase C. Also open in Content Calendar §8.5 and Review System Appendix B.3.
  2. [CONFIRM] Guided trip pricing — full day, half day, and the shared "split with a stranger" rate. Needed for W5-A and PT3. No price has been invented anywhere in this document; $250/mo is the only confirmed figure used.
  3. [CONFIRM] Physical mailing address for the footer. CAN-SPAM requires one. A PO box is fine.
  4. [CONFIRM] The virtual program's actual mechanics — filming instructions and required angles, call length, call cadence, number of analyses per month. V2 does not send until all four are answered. Its entire power is specificity.
  5. [CONFIRM] Which booking tool is real. Phase 1 found a live Picktime page advertising "Sample Service" and "Puget Sound School - Test Class" under the legacy name and an old Gmail address. That needs cleanup regardless, and the pre-trip/post-trip trigger depends on the answer.
  6. [CONFIRM] Gear list specifics — what's provided, whether waders are needed, whether lunch is included, loaner rod availability, license/pass requirements, meeting location, start and end times. All of P2 and P3.
  7. [CONFIRM] Gift certificate denominations and link. Referenced in O1, PT3, and the December newsletter.

Decisions:

  1. Blueprint: custom or templated? (PT1) A three-field template sent every time beats a beautiful custom document sent 40% of the time. Decide before launch.
  2. Who triages replies? P1, W4, and PT2 all use reply CTAs. An unanswered reply is worse than never having asked.
  3. Is "Absolute Silly Goose" in-bounds for email? (W1 P.S.) If not, cut it — don't soften it.
  4. Cast Diagnostic: gate the result behind email, or show it and gate the drill email? The friendlier version fits the brand and may well convert better. Kristen's call.
  5. Skwala timing and the seasonal lines throughout. Every seasonal reference in this document is placeholder text. Twenty years of firsthand knowledge beats every public hatch chart, and this is the same note the Content Calendar flagged as its highest-value review item.

Content Kristen must supply personally:

  1. One real filled-in journal page, handwriting and all, for the River Journal PDF. Cannot be faked and shouldn't be.
  2. A real "thing I got wrong" for R2 — a technique opinion she's genuinely revised. Optional, extremely powerful, must be true.
  3. Nate's voice variants. Several emails have Nate alternates marked. [CONFIRM: Nate's appetite for having a voice in email at all] — same question the Content Calendar raised about his byline.

Cross-document dependencies:

  1. The Review System's E6 timeline changes. §16.3 stages that send across three weeks rather than one day. Update the Review System Launch Checklist (step 11) to match, or the two documents will contradict each other.
  2. Do not launch the Welcome sequence before /method is live. W2 and W3 both point at it. Site Architecture Review §7 Phase 1 owns that page.
  3. O2 links to Content Calendar post #14 (Yakima River Season Guide, publishes Jan 19). Either send O2 after that date or point it at the service page instead.

APPENDIX — DOCUMENT CONTENTS

Item Count
Sequence emails, full copy 21
— Welcome 5 (W5 has two geographic variants)
— Pre-trip 3
— Post-trip 3
— Virtual lesson nurture 4
— Re-engagement 3
— Off-season / winter 3
Complete sample newsletter 1
Newsletter section template 7 sections
Lead magnet concepts, fully specified 3
Opt-in pages, full copy 3
Signup form variants 5
Subject lines 62
Tag families / segments 5 families, 4 working segments
Automation sequences mapped 6 + newsletter + review handoff

Prices used in this document: one — $250/month, the confirmed virtual casting lesson rate. Every other figure is [CONFIRM].
Testimonials used in this document: none. The business has no locatable reviews as of August 2026, and no quote, composite, or paraphrase has been invented to fill the gap. Every social-proof slot is either proof-by-demonstration or a marked placeholder awaiting real output from the Review Generation System.
Performance benchmarks presented as this client's data: none. See §17.1.

Go to
The Action PlanResource Library
On this page

HOW TO USE THIS DOCUMENT

0. WHAT'S IN HERE

1. VOICE GUIDE

2. PLATFORM RECOMMENDATION

The recommendation: Kit (formerly ConvertKit), with Zapier (or Make) as the booking bridge.

Runners-up, and when to pick them instead

On Squarespace Campaigns

3. SEGMENTATION PLAN

3.1 The principle

3.2 Tag taxonomy

3.3 The four segments that actually get used

4. AUTOMATION TRIGGER MAP

4.1 The map

4.2 Trigger table

4.3 The four global suppression rules

5. COORDINATION WITH THE REVIEW GENERATION SYSTEM

5.1 The division of labor

5.2 The post-trip calendar, merged

5.3 The three collision risks, and the fixes

5.4 The one thing this system does that the review system asked for

W1 — WELCOME + DELIVER THE THING

W2 — THE ONE BIG IDEA

W3 — PROOF BY DEMONSTRATION

W4 — THE QUESTIONS PEOPLE ARE TOO POLITE TO ASK

W5 — THE ACTUAL ASK

W5-A — for people who can get to the river

W5-B — for people who can't

P1 — WHAT YOU ACTUALLY BOOKED

P2 — WHAT TO BRING, WHAT TO SKIP

P3 — TOMORROW

PT1 — YOUR BLUEPRINT

PT2 — HAVE YOU DONE THE THING

PT3 — THE NEXT DOOR

V1 — SAY THE NUMBER OUT LOUD

V2 — THE HOUR-BY-HOUR

V3 — GO WATCH THE FREE STUFF

V4 — LAST ONE

R1 — THE RIVER DID A THING

R2 — WHAT'S CHANGED

R3 — SHOULD I STOP

O1 — NOBODY GETS BETTER IN JULY

O2 — WHERE DO YOU WANT TO BE STANDING IN MAY

O3 — THE FIRST BUGS

12.1 Cadence, and how it reconciles with the Content Calendar

12.2 The repeatable section structure

12.3 Which product goes in "What's open," by month

12.4 The social proof section — the honest version

12.5 Sample issue — December 2026

From the boat

One thing about trout 🧠

What the Yakima's doing 🏞️

Ten minutes 🎣

The other thing 💬

What's open ❄️

CONCEPT 1 — THE RIVER JOURNAL

Opt-in page copy

CONCEPT 2 — THE REFUSAL FLOWCHART (a Strategy Blueprint)

Opt-in page copy

CONCEPT 3 — THE CAST DIAGNOSTIC (quiz / assessment)

Opt-in page copy

13.4 Lead magnet build order

14.1 Homepage hero / above the fold

14.2 Journal / blog sidebar (and mobile: after paragraph 3)

14.3 Exit intent

14.4 Footer (sitewide)

14.5 Content upgrade (end of blog post)

14.6 Placement strategy summary

15.1 Welcome sequence

15.2 Pre-trip sequence

15.3 Post-trip sequence

15.4 Virtual lesson nurture

15.5 Re-engagement

15.6 Off-season / winter

15.7 Newsletter / broadcast

15.8 Angle patterns worth reusing

16.1 Authentication — do this before importing a single contact

16.2 The subdomain question

16.3 ⚠️ The cold-list problem — the biggest deliverability risk in this engagement

16.4 Ongoing hygiene

16.5 Content-level deliverability

17.1 The honesty caveat — read before using any number below

17.2 The metrics that actually matter for this business

17.3 Send timing

18.1 Build order

18.2 Open items for Kristen

APPENDIX — DOCUMENT CONTENTS