# Playbook: PLF Launch Sequence

**Deliverable type this produces:** `launch-sequence`
**Derives from:** Jeff Walker — Product Launch Formula, the open/close-cart methodology that launched an entire industry of internet product launches. Structured around prelaunch content (the "Problem/Transformation/Ownership" (PXO) sequence of value-first videos/content) building anticipation before the cart opens.
**Engine (the science):** Everett Rogers' Diffusion of Innovations (1962) plus Robert Cialdini's scarcity/urgency mechanics (*Influence*, 1984) — episodic launches manufacture a real deadline that concentrates decision-making, and pre-launch content builds the reciprocity/authority that makes the cart-open ask credible. BJ Fogg's Spark→Signal progression governs the arc: early emails raise motivation (Spark), the deadline-day emails are bare reminders once motivation is already high (Signal).

## When to use it

- Episodic, high-ticket launches with a real start/stop window — for 19Keys, a ZIION cohort or Passport drop with an actual enrollment window.
- The audience is Product-Aware or Most-Aware (Schwartz, §5.2) — they know roughly what this is and need proof + urgency, not education from zero.
- Best deployed to the whale/VIP wave first (Rogers' Innovators, ~top 1-4%) to harvest proof and testimonials that cascade into the majority-segment cart-open emails.

## When NOT to use it

- As an always-on, continuously-running motion — launch fatigue is real and explicitly named as a PLF failure mode (§4.10). If you're launching every month with no cooldown, the arc stops working and starts training the list to ignore your deadlines.
- When scarcity/urgency can't be made real — if the cart doesn't actually close, the bonus doesn't actually expire, or the price doesn't actually rise, do not use this playbook. Fake scarcity is explicitly named the #1 trust-destroyer at §8.2 #3.
- On an Unaware/Problem-Aware segment with no prior relationship — they need `soap-opera-sequence` first; jumping straight to a cart-open ask without narrative groundwork undersells the offer's actual value.

## The step-by-step build

1. **Confirm the deadline is real before writing a single email.** Name the exact enforcing mechanism: cart literally closes (platform-enforced), price literally rises, bonus literally expires. If none of these are true, stop — do not proceed with this playbook until one is.
2. **Write ≥2 prelaunch value emails** (Walker's PXO content, condensed to email form): each delivers real standalone value/proof related to the transformation the offer provides — not a sales pitch, a genuine "here's a piece of the puzzle" email. No CTA beyond consuming the content or a soft micro-commitment.
3. **Write the cart-open email.** This is the formal reveal: what it is, what it costs, what's included, and the one link to buy. Single CTA, single offer — the manual requires exactly one offer per sequence, no upsell/downsell muddying the arc.
4. **Write ≥1 proof/social-proof email mid-cart.** Real testimonials, results, or a live case study from the whale-wave early buyers (Rogers cascade mechanism) — this is what converts the majority segments who are watching to see if others commit first.
5. **Write ≥1 objection/FAQ email.** Address the top 3-5 real objections directly and honestly — price, time, "will this work for me." This is where high-ticket offers earn their conversion (Kennedy: money is in the follow-up, the 5th-12th touch).
6. **Write ≥2 deadline-day emails** with the exact same deadline stated identically across all of them — same date, same time, same timezone. A mismatch between deadline-day emails (e.g., "midnight tonight" in one, "end of day tomorrow" in another) is an explicit hard fail (§8.1).
7. **Tag every scarcity/urgency claim `[real]`** with the enforcing mechanism named inline (e.g., "`[real: cart closes via platform at 11:59pm PT, enrollment literally disabled`"). Untagged urgency claims are a hard fail.
8. **Write the post-close email.** Confirms the cart is closed, sets expectations for next contact, and (optionally) opens the next relationship beat (e.g., back to `daily-email` cadence). This email is required — a launch sequence that ends silently at the deadline is incomplete.
9. **Compliance tags on every email**, no exceptions for launch urgency.
10. **Route the wave order (§2.9, §5.1):** whale/VIP segment gets this sequence first; harvest their proof for step 4; cascade to warm segments days later with the same arc, updated proof.

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

| Stage | Email | Subject | Real urgency tag |
|---|---|---|---|
| Prelaunch 1 | "The readiness gap nobody talks about" | value/proof content | none needed |
| Prelaunch 2 | "What separates the 46 from the 4,591" | value/proof content | none needed |
| Cart-open | "Passport enrollment is open — here's everything" | offer reveal, single link | `[real: enrollment opens via platform at 9am PT]` |
| Mid-cart proof | "What happened when the first 12 joined" | testimonials from whale-wave buyers | none needed |
| Objection/FAQ | "The 4 questions everyone asks before joining" | objection handling | none needed |
| Deadline-day 1 | "Enrollment closes tonight at 11:59pm PT" | reminder | `[real: cart closes via platform, enrollment disabled at 11:59pm PT]` |
| Deadline-day 2 | "This closes in 3 hours" | final reminder, same deadline restated | `[real: cart closes via platform, enrollment disabled at 11:59pm PT]` |
| Post-close | "Doors are closed — here's what's next" | confirms close, sets next-contact expectation | n/a |

## How the verify gate applies

Per §8.1 `launch-sequence` rubric, checked for:
- **≥2 prelaunch value emails**, cart-open email, **≥1 proof/social-proof email**, **≥1 objection/FAQ email**, **≥2 deadline-day emails**, and a **post-close email** — missing any category is a hard fail.
- **Deadline stated identically across all deadline-day emails** — mismatched deadlines fail.
- **Every scarcity/urgency claim tagged `[real]` with the enforcing mechanism named** — untagged urgency fails outright (this is the launch-sequence's signature check, directly guarding against §8.2 #3, fake scarcity).
- Compliance tags on every email.
- **Single offer per sequence** — a launch sequence that quietly bundles a second offer or upsell fails.
- Reviewer note: cross-reference the wave order against §2.9/§5.1 — a launch fired identically to the whole list on day one without a whale-first cascade is not a mechanical linter fail but is a doctrine violation worth flagging.