# Playbook: Soap Opera Sequence

**Deliverable type this produces:** `welcome-sequence`
**Derives from:** André Chaperon — *Autoresponder Madness* (ARM, 2009+). Origin proof: ~$70K in a month off a list of ~1,000 (~$70/subscriber) via serialized storytelling. Layers in Jay Abraham's "Strategy of Preeminence" (be the reader's most trusted advisor).
**Correction on attribution:** Russell Brunson's 5-email "Soap Opera Sequence" in *DotCom Secrets* is a simplified, packaged derivative of Chaperon's original work. Chaperon is the source; Brunson is the popularizer. Credit accordingly — crediting Brunson with the invention is the exact tell of someone who read the summary, not the source.
**Engine (the science):** Bluma Zeigarnik (1927) — interrupted tasks are recalled ~2x better than completed ones. An open narrative loop occupies working memory until it's resolved; the reader opens tomorrow's email to relieve that tension.

## When to use it

- A brand-new subscriber has zero relationship with you yet (Schwartz: Unaware or Problem-Aware).
- You have a genuine founder/brand story with real stakes, turns, and a resolution that leads naturally into the offer.
- You're building the welcome-to-offer arc for a specific product (for 19Keys: ZIION Passport onboarding).

## When NOT to use it

- On an already-warm, product-aware segment (the whale/VIP tier) — they don't need five days of narrative before you make the ask; go straight to the launch arc (`plf-launch-sequence`) instead.
- When there is no real story — a manufactured, hollow narrative reads as manipulation and fails the "would you say this to someone's face" test (Bird). Don't invent stakes you don't have.
- On a reactivation/dead segment — a dead contact does not have the attention span for a 5-7 day arc; use `nine-word-reactivation` instead.
- When you cannot commit to closing every loop you open. An open loop with no payoff is worse than no loop at all (see verify gate below).

## The step-by-step build

1. **Map the story arc before writing a single subject line.** Identify: the inciting incident (why 19Keys/the founder started this), the struggle, the turning point, the proof, and the resolution that becomes the offer. This is a narrative outline, not an email outline.
2. **Decide the loop ledger.** For a 5-7 email sequence, plan which loop each email *opens* and which prior loop it *closes*. No email should open a loop with no planned payoff email downstream. Write this ledger out as a table before drafting copy — it is the artifact the verify gate checks.
3. **Draft email 1 — deliver the promised lead-magnet immediately.** Whatever the subscriber opted in for must arrive in email 1, not be dangled. Open the first story loop in the same email. Goal tag: `orient`.
4. **Draft emails 2-4 — story episodes.** Each: one open cognitive loop closed from the prior email, one new loop opened, one story beat, one soft pivot line connecting the story to the reader's situation. Goal tags: `story` (2-3), `proof` (4, bring in a real testimonial or result).
5. **No hard pitch before email 3.** Emails 1-2 build trust and open loops only — no CTA beyond "read tomorrow" / a soft, non-sales click.
6. **Exactly one hard-pitch email** in the sequence (typically the last or second-to-last). Goal tag: `pitch`. This is where all loops resolve into the offer reveal.
7. **Close every open loop by the final email.** Audit your ledger from step 2 — if any loop was opened and never paid off, add a closing beat before shipping.
8. **Attach compliance tags to every single email:** unsubscribe merge tag + CAN-SPAM postal-address merge tag. Non-negotiable, no exceptions for "just the welcome sequence."
9. **Set day offsets.** Typical Chaperon cadence is not strictly daily — allow 1-3 day gaps between episodes so the story breathes; document the offset for each email.
10. **Route by awareness (§5.2 of the manual).** If the subscriber segment is Product-Aware already, shorten to 5 emails and compress the pitch earlier; if Unaware, use the full 7 with more problem-agitation before the reveal.

## Worked mini-example (19Keys / ZIION Passport)

| # | Day | Subject (≤9 words) | Goal | Loop opened | Loop closed | CTA |
|---|-----|---------------------|------|-------------|--------------|-----|
| 1 | 0 | "The letter I almost didn't send" | orient | "Why I built this in secret" | — (delivers lead magnet) | Read tomorrow |
| 2 | 1 | "What the $611K taught me" | story | "The one buyer who changed everything" | Why-built-in-secret | Reply w/ your story |
| 3 | 2 | "The mistake that cost me the list" | story | "How I fixed the silence" | The-one-buyer loop | none (soft read-on) |
| 4 | 4 | "Proof it wasn't luck" | proof | "The number nobody believes" | How-I-fixed-it loop | Watch the proof clip |
| 5 | 6 | "Why I'm opening the door now" | pitch | — | The-number loop + all remaining | Claim your Passport (one link) |

Compliance tags present on all 5. Exactly one pitch email (#5). No loop left open at #5.

## How the verify gate applies

Per §8.1 `welcome-sequence` rubric, this playbook's output is checked for:
- **Count:** 5-7 emails — the worked example above is a valid 5.
- **Per-email fields:** day offset, subject ≤9 words, goal tag from `[orient|story|proof|soft-pitch|pitch]`, single CTA, open-loop annotation.
- **Sequence-level hard fails:** lead-magnet not delivered in email 1; any hard pitch before email 3; more than one hard-pitch email; any email missing unsubscribe/postal-address tags; any multi-CTA email; **any loop opened and never closed** — this is the Chaperon-specific failure mode (§8.2 #2: "cargo-cults Chaperon's SOS without understanding Zeigarnik").
- Before marking this deliverable done, re-read the loop ledger from step 2 against the shipped copy line by line — this is the single most common way this playbook fails review.