Email Sequence Kit — QC Checklist

Run this checklist after building. Section A applies to sequence plans. Section B applies to individual emails. Section C applies to both.

A. Sequence Plan

A1. Document Structure

• [ ] Metadata header present: campaign, list size, cadence, pattern, model reference
• [ ] Taki Patterns table mapping all 7 patterns to this sequence
• [ ] Gold bar separator after metadata
• [ ] Container width: 860px (wider than individual emails)
• [ ] CSS matches golden example (Inter, Cormorant Garamond, gold accents)

A2. Email Cards

• [ ] One .email-card per email in the sequence
• [ ] Each card has: email number, send date, format type (gold uppercase), subject line options, angle, structure instructions, CTA line
• [ ] Email format types are genuinely different — no two emails use the same format
• [ ] Each card references a specific Taki email pattern (not just "Taki style")
• [ ] Subject line options: 3 per email, all under 50 characters
• [ ] CTA progression visible across cards (soft → link → urgency)

A3. Placeholder Handling

• [ ] Any email needing real proof has a .placeholder block (dark background, gold label)
• [ ] Placeholder clearly states what Kathryn needs to do or provide
• [ ] Placeholders are marked as blockers, not suggestions

A4. Summary Sections

• [ ] "What's Still Needed" section listing all blockers
• [ ] "Sequence at a Glance" table: Email #, Date, Format, Sells?
• [ ] Post-sequence follow-up noted (but explicitly marked as separate)

A5. Sequence Design

• [ ] Email 1 does NOT sell — teaching story only, no link, no offer mention
• [ ] Hard sell progression: no link → first link → objection handling → value math → urgency
• [ ] Each email stands alone — no "as I mentioned last time" references
• [ ] Timing is realistic for the list size and audience (professional services owners)
• [ ] Total sequence length: 10-14 days for offer mode

B. Individual Email

B1. Document Structure

• [ ] Metadata header present: send date, list, format, CTA, sells (yes/no)
• [ ] Subject line options in .subject-options block (3 options)
• [ ] Email copy in .email-body card (white background, 1px border, 40px padding)
• [ ] Notes section with mechanics explained
• [ ] "What Happens Next" section (what follows this email)
• [ ] Container width: 680px
• [ ] CSS matches golden example

B2. Email Copy — Structure

• [ ] One sentence per line — no multi-sentence paragraphs
• [ ] Opens by dropping into the story or the content — no preamble ("I'm excited to...")
• [ ] Each paragraph is one

  tag with one sentence

• [ ] Link uses .link class (gold, weight 500, underlined) — not raw URL
• [ ] Sign-off: "Kathryn" — not "Best," "Warm regards," etc.

B3. Email Copy — Gift Mode

• [ ] Teaching story uses real proof — no fabricated numbers
• [ ] Numbers are specific (not "a bunch of items")
• [ ] Story builds through specifics — each sentence adds a new layer
• [ ] "It was right" / payoff moment present — earned by specifics before it
• [ ] Authority comes from action ("I build these every week") not credentials
• [ ] Gift stated simply: skill name + "I'm giving it away" — no conditions
• [ ] Delivery page link included (one link, not buried)
• [ ] Series framing: one paragraph at the bottom, light, forward-looking
• [ ] No selling — no Intensive, no Practice Builders, no Advisory OS services

B4. Email Copy — Offer Mode (Per Format)

Teaching story (Email 1):

• [ ] Real story with real moment — drops into it, doesn't announce it
• [ ] Pattern named at the end — the insight the story reveals
• [ ] Ends soft — "More on this Thursday." No link.
• [ ] No offer mention at all

System reveal (Email 2):

• [ ] Opens with outcomes, not with what the product is
• [ ] Lists sessions/components with specific outcomes per item
• [ ] Names the format clearly ("Build-along. Everyone builds on their own data.")
• [ ] Price, dates, time commitment stated plainly
• [ ] One clear register link

FAQ (Email 3):

• [ ] Bold questions, regular answers
• [ ] 6-8 questions minimum
• [ ] At least one answer with personality/humor
• [ ] Handles the top 2 objections for this audience
• [ ] Ends with a "still reading? You're probably coming" close
• [ ] Register link

Value stack (Email 4):

• [ ] Every component listed with one-line description
• [ ] The math moment — comparison that makes value obvious
• [ ] Not "worth $X" — just show what's included for the price
• [ ] Register link, urgency if appropriate

Urgency (Email 5):

• [ ] Short — 100-200 words
• [ ] Does NOT repeat value stack or re-explain the offer
• [ ] Names the choice: status quo vs. the alternative
• [ ] Replay/flexibility mention for schedule concerns
• [ ] Price + register link + short close ("See you [day].")

B5. Notes Section

• [ ] Each note has a bold label + explanation
• [ ] Notes explain WHY the email is structured this way (not just what)
• [ ] Real proof sourced (story attribution, numbers verified)
• [ ] Link destination stated explicitly

C. Both Formats

C1. Subject Lines & Preview Text

• [ ] All subject lines under 50 characters
• [ ] Curiosity-driven or story hooks — no announcement energy
• [ ] Lowercase energy — no ALL CAPS, no exclamation marks
• [ ] No emoji in subject lines
• [ ] 3 distinct options per email (different angles, not variations)
• [ ] Preview text / preheader present for every email — subject + preview text are a pair, no exceptions

C2. Voice

• [ ] One sentence per line throughout — no multi-sentence paragraphs
• [ ] Uses locked terms: skill, run, install, practice, practice owner, deploy
• [ ] No forbidden constructions (check 02-email-sequence-terminology.md)
• [ ] No hype: game-changer, revolutionary, powerful, transform, amazing
• [ ] No "I'm so excited" / "Don't miss out" / "Click here" energy
• [ ] Personality present — sounds like Kathryn, not a marketing template
• [ ] Read-aloud test: every line sounds like a person talking, not a newsletter

C3. Taki Patterns Applied

• [ ] Format variety: no two emails use the same format
• [ ] Teaching in every email — even urgency names a pattern
• [ ] Personal stories carry the teaching (where applicable)
• [ ] Hard sell comes late — Email 1 never sells
• [ ] Each email stands alone — readable without context from other emails

C4. Cross-Asset Consistency

• [ ] Skill name matches other campaign assets (DM sequence, handraiser post, delivery page)
• [ ] Delivery page URL matches DM sequence and delivery page
• [ ] Every mention of the lead magnet by name links back to its delivery page — don't assume the reader can find the original email
• [ ] Series position matches other assets
• [ ] Teaching story numbers are consistent across email, post, and DMs
• [ ] Trigger word (if mentioned) matches handraiser post