Email Sequence Plan — The 90-Second Pipeline™ Workshop

Campaign: Practice Builders Workshop — The 90-Second Pipeline™ Offer: $17 live build session, June 3, 2026 List: One universal segment — all warm contacts, excluding workshop buyers (see Platform Setup) Cadence: 5 emails over 12 days (May 22 – Jun 2) Pattern: Taki-style — each email uses a genuinely different format Modeled on: Taki Moore's Magnetic workshop sequence Platform: MailerLite — scheduled campaigns (not automation), exclude buyers

Taki Patterns Applied

Platform Setup (MailerLite)

These are scheduled campaigns, not automation steps. The workshop has a fixed date (June 3). Late opt-ins entering an automation would get stale urgency emails after the event. Schedule each email as a campaign on the specific send date.

One universal segment for all emails. Built in MailerLite Advanced filter — 5 OR blocks, each with the same 2 exclusions. Every campaign uses this segment.

Include (OR):

• Groups | Belongs to | Start | LTO-52 Claude Skills
• Groups | Belongs to | Complete | LTO-52 Claude Skills
• Groups | Belongs to | Start | Client Intelligence Brief
• Groups | Belongs to | Complete | Client Intelligence Brief
• Groups | Belongs to | Existing List — 52 Skills Campaign

Exclude (AND, repeated in each OR block):

• Groups | Does not belong to | Start | 90-Second-Pipeline-Workshop
• Groups | Does not belong to | Complete | 90-Second-Pipeline-Workshop

15 rows total. Exclusions must repeat inside every OR block — MailerLite evaluates each block independently. Segment screenshot saved in campaign folder (image.png).

Email 1 — Teaching Story

Send: Thursday May 22 Format: Teaching story — pattern recognition Sells: No. No link. No offer mention. Versions: One universal version (pipeline story works for both segments)

Subject line options:

1. "I looked at 8 names and spotted the pattern"
2. "the pipeline problem nobody talks about"
3. "one at a time is the problem"

Preview text: You're looking at names. The system looks at patterns.

Angle: Open with a real moment — Kathryn looking at a client's pipeline and realizing the problem isn't that they don't follow up, it's that they follow up one at a time. The system-level view reveals patterns invisible at the individual level. Name the pattern. End soft.

Structure (Taki's "I cheat at content" pattern):

• Drop into the moment. No preamble. "I was looking at a client's pipeline last week."
• Build through specifics — how many names, what she noticed looking at them all at once vs. one at a time
• Name the pattern: three people who all needed the same nudge, two who needed a direct ask, one who should have been let go months ago
• The shift: "You can't see that looking at one name at a time."
• Close soft: "More on this Monday." No link.

CTA: Soft. No link. "More on this Monday."

[PLACEHOLDER — REAL STORY NEEDED]: Kathryn needs a real pipeline moment — either from her own practice or from a client engagement (anonymized). The story needs: how many names, what she saw looking at the whole list, what pattern emerged that wasn't visible one name at a time. Cannot be fabricated.

Email 2 — System Reveal (Announcement)

Send: Monday May 26 Format: System reveal — outcomes, structure, format Sells: Yes. First link to sales page. Versions: One universal version (pipeline pain opener works for all segments)

Subject line options:

1. "what if your pipeline review took 90 seconds?"
2. "I'm building something live. Bring your data."

Preview text: 60-minute build session. Your pipeline. Your outreach. Your referral asks.

Angle: Reveal the workshop — what it is, what you'll build, what you leave with. This is the announcement. First link to the sales page.

Structure (Taki's "Freestyle Rap for you" pattern):

• Opens with pipeline pain → follow-up gap (concrete, specific — names the behavior)
• Pivot: 15 names deep, you're behind before you start
• System description: reads the whole list at once, 3 skills wired together
• What you'll build (5 bullets — pipeline review, priority, approach, outreach, referral asks)
• Framework context (WIN / DELIVER / GROW — one line)
• CTA: link to sales page

CTA: Sales page link. "Reserve your seat →"

NOTE: Drafted in workshop-nurture-email-draft.md. Merged from two versions to one universal version — Version B body works for all segments. Copy QC and sentence editor passed. Three-skill system language applied.

Email 3 — FAQ

Send: Wednesday May 28 Format: FAQ / Q&A — bold questions, direct answers Sells: Yes. Link to sales page. Versions: Universal (one version, both segments)

Subject line options:

1. "you probably have questions about June 3"
2. "do I need to know AI for this?"
3. "the two questions everyone asks"

Preview text: Quick answers. Then decide.

Angle: Handle the real objections. Bold questions, direct answers. Personality in the answers — not corporate FAQ energy. End with "still reading? You're probably coming."

Structure (Taki's "Let me clear this up" pattern):

• Open with one line: "A few questions keep coming up about June 3."
• 5-6 bold questions with direct answers:

1. "Do I need to know AI?" — No. You need Claude open and a list of names. We build together.
2. "What if I can't make it live?" — You get the recording. But Q&A is live-only and not recorded. The real value is building with your data in real time.
3. "Is this a webinar?" — No. You'll have Claude open. You'll paste your data. You'll build the system yourself with guidance.
4. "What do I need to prepare?" — 5-10 names from your pipeline. Name, how you know them, last contact, status. That's it.
5. "Will you pitch me something?" — I'll show you the full framework and mention the membership. No pressure. What you build is yours.
6. "Do I need a paid Claude account?" — Yes. The skills require uploads, which need a paid account.

• Close: "Still reading? You're probably coming."
• CTA: sales page link

CTA: Sales page link. Compact — after the closing line.

Email 4 — Value Stack

Send: Saturday May 31 Format: Value stack — every component listed Sells: Yes. Link to sales page. Versions: Universal (one version, both segments)

Subject line options:

1. "everything you get on June 3"
2. "here's what you're building Tuesday"
3. "60 minutes. your data. this is what you leave with."

Preview text: The full breakdown — build session, outreach, framework, recording.

Angle: List every component with a one-line description. Make it concrete — not "you'll learn" but "you'll build." The math isn't about comparing to the price (it's $17, the math is irrelevant). The math is about what the output is worth — a prioritized pipeline, personalized outreach, and referral asks for every name.

Structure (Taki's "posting like it's cardio" pattern):

• Open: "Here's exactly what happens on June 3."
• Component list (each with one-line description):
• 60-minute live build session — your pipeline, your data, your outreach
• The 90-Second Pipeline™ — three skills wired into one system, installed and working when you leave
• Personalized outreach for every contact — different strategy per person, ready to send
• Referral asks — identified and written for the right contacts
• WIN / DELIVER / GROW framework — the full map, nine systems, four levels each
• Q&A after the build — stay on for tactical questions (not recorded)
• Build session recording — reference if you can't make it live
• Bridge: "One follow-up to a stalled prospect. That's all this needs to pay off."
• CTA: sales page link

CTA: Sales page link. Direct.

Email 5 — Last Call

Send: Monday June 2 (day before) Format: Urgency — short, stakes-based Sells: Yes. Link to sales page. Versions: Universal (one version, both segments)

Subject line options:

1. "tomorrow at noon"
2. "last call — June 3"
3. "your pipeline list ready?"

Preview text: Build session is tomorrow. Bring your names.

Angle: Short. Name the choice: keep following up one at a time, or build the system tomorrow. No re-explaining the offer. No value stack repeat. Just the decision.

Structure (Taki's "typing quietly so I don't wake him" — short, creative):

• 4-6 sentences max
• Name the status quo (you'll keep following up when you remember to)
• Name the alternative (tomorrow we build the system that handles all of them at once)
• CTA: sales page link
• Close: "See you at noon."

CTA: Sales page link. "See you at noon." Close.

What's Still Needed

Sequence at a Glance

Buyer Sequence (Separate Automation — MailerLite)

Buyers are excluded from the nurture sequence above. They get their own cadence, triggered by joining group "Start | Workshop-90 Second Pipeline."

Trigger: Joins group "Start | Workshop-90 Second Pipeline" (ThriveCart webhook) Platform: MailerLite automation (not scheduled campaigns — buyers can purchase any time)

Pre-Workshop (Show-Up)

Pre-workshop emails are operational — no selling, no personality. Their only job is show-up rate with data ready.

Post-Workshop (Membership Bridge)

Post-workshop sequence maps to Deiss CVO — $17 workshop is the SLO, membership is the core offer. The bridge email is the critical conversion point.

Status: Not yet drafted. Pre-workshop reminders are simple (draft when sequence dates are locked). Post-workshop bridge needs membership offer details confirmed (Jules/Reid).

Non-Buyer Post-Sequence

Non-buyers who didn't purchase get nothing further about this workshop after the nurture sequence ends June 2.