← Vault Index
Source: frameworks/kit-email-sequence/00-email-sequence-start-here.md

Email Sequence Kit — Start Here

What This Kit Does

This kit produces email sequences for skill campaigns. Two operating modes: gift emails that deliver a free skill to the list, and offer sequences that sell a paid product using Taki Moore's format-variety mechanics. Both use one sentence per line, HTML reference docs, and real proof.

Email is the parallel delivery channel to LinkedIn DMs. DMs deliver to people who comment on the handraiser post. Email delivers to the existing subscriber list. Both point to the same delivery page.

What It Produces

#AssetFormatPurpose
1Sequence Plan.htmlMaster plan — all emails outlined with timing, formats, subject lines, CTAs, notes
2Individual Email Docs.html eachOne per email — copy ready to paste, subject line options, send notes

The sequence plan is built first. Individual emails are written one at a time as send dates approach.

Two Operating Modes

Gift Mode

A single email (or short 2-3 email sequence) that delivers a free skill to the subscriber list. Pure value. No selling. Series framing at the bottom is the only forward-looking element.

PropertyValue
Length1-3 emails
CTALink to delivery page
Sells?No. Pure value.
FormatTeaching story — real proof, one sentence per line
TimingAligned with LinkedIn handraiser post and DM sequence

Offer Mode

A multi-email sequence (typically 5-7 emails) that builds from teaching to offer to urgency. Each email uses a genuinely different format. Modeled on Taki Moore's Magnetic workshop sequence.

PropertyValue
Length5-7 emails over 10-14 days
CTAProgresses from soft (no link) → register link → urgency
Sells?Yes, starting Email 2. Email 1 teaches.
FormatsTeaching story → System reveal → FAQ → Value stack → Urgency
TimingTimed to lead up to the offer date

Email Format Types

Taki's core insight: not variations on the same email, but genuinely different reads.

FormatModeJobTaki Reference
Skill giftGiftDeliver a free skill — teaching story + link to delivery pageEmail 1 CIB golden example
Teaching storyOfferOpen with a real moment, teach through the story, end soft (no link)"I cheat at content"
System revealOfferShow the offer — outcomes, structure, format, price"Freestyle Rap for you"
FAQ / Q&AOfferHandle objections with bold questions and direct answers"Let me clear this up"
Value stackOfferList every component, make the math obvious"[12 hours] posting like it's cardio?"
Urgency / Last callOfferShort, direct, name the choice — status quo vs. alternative"typing quietly so i don't wake him"

Prerequisites

DependencyWhyBlocking?
Skill file (from Skill Build Kit)Gift emails reference the skill's real testing resultsYes for gift mode
Delivery page (from Skill Delivery Page Kit)Gift emails link to the delivery pageYes for gift mode
Real testing results / teaching storyEmail 1 always needs a real story with real numbersYes (both modes)
Offer details (price, dates, format)Offer mode emails need specific logisticsYes for offer mode
Registration link / sales pageEmails 2-5 in offer mode need a linkYes for offer mode

Sequence Architecture (Offer Mode)

Email 1: Teaching story (no link, no sell)
    ↓ 2 days
Email 2: System reveal (first link, outcomes + price)
    ↓ 2 days
Email 3: FAQ (objection handling + link)
    ↓ 3 days
Email 4: Value stack (full breakdown + math + link)
    ↓ 4 days
Email 5: Urgency (short, stakes-based + link)

Key principle: The hard sell comes late. Email 1 teaches. By Email 4 they've seen teaching, the offer, objection handling, and value stacking. Email 5 is just urgency.

Key Mechanics

One sentence per line. Every email. Reads like a conversation, not a newsletter. No walls of text. This is the Taki format.

Each email stands alone. Someone who only reads Email 4 should understand the offer and want to register. No "as I mentioned in my last email" references.

Teaching in every email. Even the urgency email names the pattern. The teaching IS the sell.

Subject lines are short and curiosity-driven. Under 50 characters. No "WORKSHOP STARTS SOON" energy. "I was sitting on $40K and didn't know it" not "Register for the Intensive."

Personal stories carry the teaching. Every teaching email opens with a specific moment. Drop into the story — not "I want to tell you about..."

Personality is the differentiator. Kathryn's voice: direct, pattern-revealing, calm authority. Not Taki's humor — Kathryn's quiet confidence.

Gift emails don't sell. No Intensive. No Practice Builders. No Advisory OS. Series framing at the bottom is the only forward-looking element.

File Inventory

FilePurposeWhen to Use
00-email-sequence-start-here.mdOrientation — modes, formats, architectureStart here every time
01-email-sequence-context.mdRequired inputs — concept brief templates (gift + offer)Before every build — complete inputs first
02-email-sequence-terminology.mdLocked vocabulary and email voice rulesReference when writing
03-email-sequence-golden-example.mdStructure analysis of both golden examplesStudy before building
04-email-sequence-quality.mdQC checklist — sequence plan, individual emails, voice, Taki patternsRun after every build
05-email-sequence-output-skill.mdProduction workflow — step by stepFollow for every build

Relationship to Other Kits

DM Sequence Kit (content/frameworks/kit-dm-sequence/): DMs deliver to LinkedIn commenters. Email delivers to the subscriber list. Same skill, same delivery page, different channel. Gift emails and DM 1 should be written close together for consistency.

Handraiser Post Kit (content/frameworks/kit-handraiser-post/): The post drives LinkedIn engagement. Email hits the existing list. Gift Email 1 can send on the same day as the LinkedIn post or within a day.

Skill Delivery Page Kit (content/frameworks/kit-skill-delivery-page/): Gift emails link to the delivery page. The page must be live before the email sends.

Skill Build Kit (content/frameworks/kit-skill-build/): Email 1 (gift or offer mode) uses testing results from the skill build. Real numbers, not generic.

business-aos (Connected Repo): Voice, audience, and copy QC patterns. Load business-aos/reference/core/voice.md before writing.

Golden Standard References

Two golden examples: