launch-email-sequence
Skill1 starsChanged 4 months agoMITView on GitHub
Builds the open-cart email launch for a paid course - a 2-3 week pre-launch runway that seeds the problem, a day-by-day cart-open sequence of 6-8 emails over 5-7 days, honest deadline mechanics for the last-48-hours surge, and clicker/non-opener segmentation. Use when a creator says "write my launch emails", "plan my open cart sequence", "how many emails should I send during launch", or "how do I close the cart without fake scarcity". Do NOT use for always-on welcome or nurture automations - use email-drip-builder instead - or for the regular newsletter between launches - use email-newsletter-pro instead.
In this repository8 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 60
Every email: one idea, one call to action, the same URL.
- Distinctive: line 68
Never fabricate scarcity - no fake countdown resets, no "3 spots left" on a digital product with infinite spots.
- Distinctive: line 90
Do not skip the runway and open the cart cold.
- Distinctive: line 91
Do not go quiet in the final 48 hours to avoid "annoying people." That is where 40-50 percent of revenue lives.
- Distinctive: line 92
Do not fake scarcity or reset deadlines.
- Distinctive: line 93
Do not put three ideas and three links in one email.
- Distinctive: line 94
Do not keep emailing buyers the launch sequence.
- Distinctive: line 95
Do not let email copy drift from the sales page - quote the promise, the $1,688-for-$297 stack, and the guarantee identically.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Launch Email Sequence
An open-cart launch lives or dies on two things most creators get backward: the selling happens mostly before the cart opens, and 40 to 50 percent of sales land in the last 48 hours no matter how good the early emails are. Creators who skip the runway launch to a cold list, and creators who go quiet near the deadline - afraid of "too many emails" - leave half the revenue unsent. This skill builds both halves: the 2-3 week runway that seeds the problem, and the day-by-day cart sequence that serves the deadline instead of faking one.
This skill runs after course-outline-architect (the transformation statement is the campaign's spine) and in lockstep with course-sales-page - every email quotes that page's promise, value stack, and guarantee word-for-word, because a mismatch between email and page is where trust dies at the moment of purchase.
Worked example throughout: Dana, 8,000-subscriber list, launching "Notion OS for Consultants" at $297.
Operating procedure
Step 1: Collect the inputs
- List size, recent open and click rates. Label estimates as estimates.
- The transformation statement and module milestones from course-outline-architect.
- The sales page URL, value stack, and guarantee wording from course-sales-page.
- Cart window (default 6 days) and the real reason the deadline exists (Step 5 requires one).
- Proof assets: results, screenshots, early-student wins.
Set expectations with the math: a well-run launch to a warm list converts 1 to 2 percent of the list. Dana at 8,000 subscribers plans on roughly 120 sales at $297 - about $35,600 - and treats anything from 80 to 160 as normal variance, not success or failure.
Step 2: Build the pre-launch runway (2-3 weeks, no selling)
Three weekly value emails (or two weeks if the list is very warm) that make the problem vivid and the mechanism credible before anything is for sale. Each teaches something genuinely useful and seeds one launch theme:
- Runway 1 - name the problem. Dana: "The 5-hour tax: where a consultant's week actually goes." Teaches a time audit; seeds the before state.
- Runway 2 - shift the belief. "Why another productivity app won't fix it (and what will)." Teaches that tools without a system fail; seeds the mechanism.
- Runway 3 - show the after + open loop. "Inside the system that onboards a client in under a day." A real walkthrough; ends with "next week I'm opening something for you."
Replies to runway emails are the objection mine for the cart emails and for course-sales-page's FAQ. Read every one.
Step 3: Write the cart-open sequence - 6-8 emails over 5-7 days
Dana runs 7 emails over a 6-day window (Tuesday open, Sunday midnight close). The day-by-day spine, with Dana's subject lines:
Day 1 OPEN "Doors open: Notion OS for Consultants"
The full offer: transformation, stack ($1,688 value, $297),
30-day action-based guarantee, deadline stated plainly.
Day 2 PROOF "How Priya cut client onboarding from 3 days to 4 hours"
One story told end to end: before, the system, the numbers after.
Day 3 OBJECTIONS "But I'm not a Notion person"
Dismantle the top two objections (skill, time). Cite the 5-12
minute lessons and the 20-minute module-1 quick win.
Day 4 FAQ "Your questions about Notion OS, answered"
Real questions from runway replies, answered honestly -
including who should NOT buy.
Day 5 VALUE/BONUS "The 12 templates alone are worth the price"
Spotlight one stack element deeply. Deadline reminder.
Day 6am CLOSE 1 "Closes tonight: last call for Notion OS"
Recap offer + guarantee. Why the deadline is real.
Day 6pm CLOSE 2 "3 hours left (then the bonuses go away)"
Short, plain, one link. Sent 3-4 hours before close.Every email: one idea, one call to action, the same URL. Stack and guarantee wording identical to course-sales-page.
Step 4: Serve the last 48 hours honestly
Expect 40 to 50 percent of sales in the final 48 hours - for Dana, roughly 50-60 of her ~120 sales on days 5 and 6. This is deadline behavior, not failure of the early emails, so plan for it instead of panicking into hype:
- Schedule 3 of the 7 emails inside the final 48 hours. Silence here is the single most expensive mistake in launching.
- The deadline must be mechanically real: the price rises, the bonuses expire, or the cart actually closes. Dana's: the automations mini-course and the templates' rebrand license leave the offer at close, and the cart closes until the next cohort.
- Never fabricate scarcity - no fake countdown resets, no "3 spots left" on a digital product with infinite spots. One discovered lie forfeits the list's trust for every future launch.
- Close-day emails are short and calm. Urgency comes from the clock, not from exclamation marks.
Step 5: Segment - clickers vs non-openers
From day 3 onward, split:
- Clicked but didn't buy (hottest segment): they get the objection, FAQ, and both close emails; on close day, optionally a personal-toned "anything holding you back? reply and ask me" email.
- Opened, never clicked: standard sequence continues.
- Didn't open the last 3 emails: resend day 1 and day 6 with new subject lines only ("Doors open" becomes "This is what I've been building for you"). Do not resend to people who opened - that trains ignoring.
- Purchased: remove from the launch flow immediately and hand to community-engagement-playbook's onboarding ritual. Nothing burns goodwill like selling someone what they bought yesterday.
Step 6: Close out and hand off
Within 48 hours of close: record sales by day (verify the last-48-hours share), revenue, unsubscribes (under 1 percent of list across a launch is healthy; over 2 percent means the runway was too thin for the volume), and the top three objections that survived. Buyers flow to community-engagement-playbook. If the next launch should be webinar-driven, take the numbers to webinar-funnel-builder; to convert this campaign into an always-on funnel, email-drip-builder.
Deliverable
The full campaign calendar: 2-3 runway emails and 6-8 cart emails, each with subject line, one-sentence job, send day and time, the segmentation rules from day 3 onward, the stated real deadline mechanic, and the close-out metric sheet - with offer wording matched to course-sales-page.
Do NOT
- Do not skip the runway and open the cart cold. The runway is where the sale actually happens; the cart emails just collect it.
- Do not go quiet in the final 48 hours to avoid "annoying people." That is where 40-50 percent of revenue lives; the unsubscribes are people who were never buying.
- Do not fake scarcity or reset deadlines. One honest deadline outsells a decade of countdown timers that lie.
- Do not put three ideas and three links in one email. One idea, one CTA, every time.
- Do not keep emailing buyers the launch sequence. Purchase removes them instantly.
- Do not let email copy drift from the sales page - quote the promise, the $1,688-for-$297 stack, and the guarantee identically.
Quality bar
- Runway of 2-3 genuinely useful emails precedes the cart; each seeds one launch theme.
- 6-8 cart emails over 5-7 days, covering open, proof, objections, FAQ, and a two-email close, with 3 emails inside the final 48 hours.
- The deadline names its real mechanism; no manufactured scarcity anywhere.
- Segmentation rules written down: clickers, non-openers (subject-line-only resends), and buyer removal.
- Projected sales stated up front from the 1-2 percent benchmark, so the result is judged against a number set before launch.
Escalation and routing
Evergreen or trigger-based automation: email-drip-builder. The between-launches newsletter that keeps the list warm for the next runway: email-newsletter-pro. A live-webinar pitch layer on top of this sequence: webinar-funnel-builder. Email marketing is regulated (CAN-SPAM, GDPR and kin) - keep working unsubscribe links and honest subject lines; if list practices are in doubt, get compliance advice. This is not legal advice.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

