# Playbook: Dinner Party Onboarding

**Deliverable type this produces:** `welcome-sequence` (post-purchase / onboarding variant)
**Derives from:** Val Geisler — SaaS lifecycle-email specialist who popularized the "host a dinner party, not a sales pitch" metaphor for onboarding sequences (customer.io / Fix My Churn consulting work). Distinct from Chaperon: Geisler's frame is explicitly for people who have *already bought or signed up* — the goal is successful first use and retention, not persuasion toward a sale.
**Engine (the science):** Cialdini's Commitment & Consistency plus Unity (*Pre-Suasion*, 2016) — a well-hosted onboarding builds a ladder of small, genuine wins (micro-commitments) and shared identity ("you're one of us now") rather than pitching. BJ Fogg's B=MAP also governs each individual send: right after signup/purchase, motivation is high but ability may be low (new user, unfamiliar product) — the prompt type should be a **Facilitator**, reducing friction, not a Spark trying to raise desire that's already there.

## When to use it

- Immediately after a purchase or signup — the relationship is the goal, not the immediate sale (there is often no next sale to make yet). For 19Keys: post-Passport-purchase onboarding.
- When the new customer needs to reach a genuine "first win" with the product/community before any upsell conversation is credible.
- Any moment governed by Layer 2's "post-purchase" lifecycle stage in the manual: relationship, no pitch.

## When NOT to use it

- Pre-purchase, prospect-facing sequences — that's `soap-opera-sequence` (selling inside a story toward a first offer) or `plf-launch-sequence` (selling toward a live cart). Using the dinner-party frame pre-sale under-monetizes a warm, ready buyer.
- On a segment with a live deadline or cart-open event — the dinner-party pace (unhurried, relational) is wrong when Fogg's Signal prompt (a bare deadline reminder) is what's actually needed.
- If the "host" voice can't commit to zero hard pitch in the sequence — if you're going to pitch anyway, use a different playbook; grafting a pitch onto a dinner-party frame breaks the promise the metaphor makes to the reader.

## The step-by-step build

Geisler's four-beat structure, one beat per email or email cluster:

1. **Greet.** Email 1, sent immediately (same day) after purchase/signup. Confirm what just happened, thank them by name for the specific action, set expectations for what's coming next (how many emails, how often, what they're for). No pitch, no product tour yet — this is the doorway greeting, not the house tour.
2. **Orient.** Email 2. Give the new customer their bearings: where is this thing they now belong to, what does the space look like, who else is here (social proof of a tribe, not testimonials-as-sales-proof). Deliver the single most important first step (Fogg Facilitator: reduce friction to that one action — log in, claim the readiness quiz, set up the profile).
3. **Serve.** Email 3-4. Deliver real value unprompted — a resource, a shortcut, an answer to the #1 question new customers ask, a personal welcome from the founder. This is the "here's your appetizer, no check yet" beat. Each is a genuine micro-commitment opportunity (Cialdini): a small voluntary action (reply, complete a step, join a channel) that escalates consistency toward deeper engagement.
4. **Deepen.** Email 5 (final of the arc). Invite the identity move — "you're one of us now" (Cialdini's Unity). This is where community, tribe, or next-level access gets introduced *as belonging*, not as an upsell pitch. If there is a natural next paid step, it can be *mentioned* here as an open door, but the arc itself does not hard-pitch.
5. **Attach compliance tags to every email** — even post-purchase relationship email is still a commercial email under CAN-SPAM.
6. **Keep every email single-CTA** (Fogg) — one next action, matched to where ability is lowest (early emails: reduce friction; later emails: invite the identity step).
7. **Watch for the tell Geisler warns against explicitly:** onboarding sequences that quietly become disguised upsell sequences. Audit each draft — if any email's real job is "get them to buy again," it does not belong in this arc.

## Worked mini-example (19Keys / post-Passport-purchase)

| Beat | Day | Subject | Content | CTA |
|---|---|---|---|---|
| Greet | 0 | "You're in — here's what happens next" | Confirm purchase, thank by name, set 5-email expectation | none / read next |
| Orient | 1 | "Where to go first inside the Passport" | Tour the readiness ladder, name the community | Complete your readiness quiz (one link) |
| Serve | 3 | "The one resource every new member asks for" | Deliver a genuine shortcut/resource unprompted | Reply with your goal |
| Serve | 5 | "A personal note from 19Keys" | Founder voice, real welcome, no ask | none |
| Deepen | 8 | "You're one of us now" | Identity/tribe framing; open door to next level, not a hard pitch | Join the members channel (one link) |

## How the verify gate applies

This deliverable is checked against the `welcome-sequence` rubric (§8.1) with the onboarding-specific reading:
- Day offsets, subject ≤9 words, goal tag, single CTA, and open-loop annotation still apply per email (a dinner-party sequence can still open/close small loops — e.g., "tomorrow I'll show you the shortcut," — but loops here are lighter-weight than a full Chaperon arc).
- **No hard-pitch email required or expected** — unlike `soap-opera-sequence`, this playbook is checked for the *absence* of a hard-pitch email, not the presence of exactly one. A reviewer finding a disguised upsell inside a "Serve" or "Deepen" email should fail the deliverable even if the linter's mechanical checks pass, per §8.2's spirit (a master's artifact is honest about its own intent).
- Compliance tags (unsubscribe + postal address) present on all.
- Cross-check against §8.2 #4 (multi-CTA) and #9 (corporate-blast tone / "Dear Valued Subscriber" — the Bird face-test) — a dinner-party email that reads like an automated onboarding drip rather than a hosted welcome fails the tone check even if the mechanics pass.