100 Claude Prompts That Write Email Sequences

<context> Someone downloaded my [lead magnet] and joined my list. I want a nurture sequence that builds trust and moves them toward [offer]. </context> <inputs> - Lead magnet topic and audience: [fill] - The offer and its core benefit: [fill] - Main objection that stops people: [fill] </inputs> <task> Write a 6-email nurture sequence. For each email give: send day, goal, subject plus an A/B alternative, preview text, body, and one CTA. Arc the sequence from pure value to soft pitch to a clear offer. </task> <constraints> - First two emails deliver value with zero pitch - Dedicate one email entirely to the main objection - Keep each email under 180 words and conversational </constraints> <format> Markdown artifact: one section per email with a labeled header. </format>

<context> New subscribers for [audience] know little about [topic]. I want to educate them before any selling so they trust me as the guide. </context> <inputs> - Topic and the transformation it enables: [fill] - Three core concepts they must understand: [fill] - Common misconception they arrive with: [fill] </inputs> <task> Write a 5-email education series. Each email teaches one concept and builds on the last. For each give: send day, learning goal, subject plus A/B alternative, preview, teaching body, and one micro-CTA to reply or read more. </task> <constraints> - Open email 1 by naming and correcting the misconception - Use a concrete example or mini-story in every email - No product pitch anywhere; CTAs are engagement only </constraints> <format> Markdown artifact, one section per email, with a one-line "what they now understand" recap at the end of each. </format>

<context> My leads feel the pain of [problem] but have not yet defined it clearly or gone looking for solutions. They are problem-aware, not solution-aware. </context> <inputs> - The problem and how it shows up day to day: [fill] - The hidden cost of leaving it unsolved: [fill] - Audience and their role: [fill] </inputs> <task> Write a 5-email problem-aware nurture sequence that sharpens their understanding of the problem and its stakes, ending by naming the category of solution. For each email: send day, goal, subject plus A/B, preview, body, single CTA. </task> <constraints> - Do not mention my product until the final email, and only as a category - Quantify the cost of inaction in at least one email - Each email ends with a reflective question, not a hard ask </constraints> <format> Markdown artifact, one section per email. </format>

<context> My leads know solutions like mine exist and are comparing approaches for [goal]. They are solution-aware but not yet convinced mine is right. </context> <inputs> - My approach and what makes it different: [fill] - The alternatives they are weighing: [fill] - The decision criteria they care about most: [fill] </inputs> <task> Write a 5-email solution-aware nurture sequence that frames the decision criteria in my favor and builds confidence in my approach. For each email: send day, goal, subject plus A/B, preview, body, one CTA moving toward [offer]. </task> <constraints> - Reframe at least one buying criterion they may be underweighting - Acknowledge alternatives fairly rather than trashing them - Escalate CTA commitment across the sequence </constraints> <format> Markdown artifact, one section per email, plus a final note on the criterion each email reinforced. </format>

<context> I want to nurture leads using real customer results for [offer]. Stories convince better than claims for my [audience]. </context> <inputs> - Customer story, their starting pain, and the result: [fill] - The specific feature or step that drove the result: [fill] - The objection this story quietly answers: [fill] </inputs> <task> Write a 5-email case-study nurture sequence that unfolds one transformation across the arc: before state, turning point, the work, the result, and the reader's invitation. For each email: send day, goal, subject plus A/B, preview, body, one CTA. </task> <constraints> - Use concrete numbers and quotes where given, never invent metrics - Each email ends on a small cliffhanger pulling them to the next - Final email connects the story directly to the reader's situation </constraints> <format> Markdown artifact, one section per email, with a "story beat" label on each. </format>

<context> Interested leads are not converting on [offer] because of recurring objections. I want a sequence that resolves them one at a time. </context> <inputs> - The offer and price point: [fill] - Top four objections, most common first: [fill] - Proof or reframe available for each: [fill] </inputs> <task> Write a 5-email objection-handling sequence. Email 1 surfaces and validates the objections; emails 2 to 4 each dismantle one; email 5 removes the final friction and asks for the decision. For each: send day, goal, subject plus A/B, preview, body, one CTA. </task> <constraints> - Validate the objection before answering it in every email - Use a reframe, proof point, or guarantee, not just reassurance - Keep tone calm and confident, never defensive </constraints> <format> Markdown artifact, one section per email, each labeled with the objection it handles. </format>

<context> My [audience] does not yet see me as a credible authority on [topic]. I want a nurture series that builds trust before I ask for anything. </context> <inputs> - My relevant credentials, results, or unique perspective: [fill] - A contrarian or hard-won belief I hold about [topic]: [fill] - Audience and what they are skeptical of: [fill] </inputs> <task> Write a 6-email authority-building series that earns trust through demonstrated thinking, not bragging. For each email: send day, goal, subject plus A/B, preview, body, one light CTA to engage. </task> <constraints> - Show expertise through useful insight, never through self-praise - Anchor one email around the contrarian belief with evidence - CTAs stay low-commitment until the final email </constraints> <format> Markdown artifact, one section per email, plus a one-line "trust signal" each email plants. </format>

<context> People registered for my [webinar topic] webinar on [date]. I want to maximize show-up rate and prime them to act on the offer after. </context> <inputs> - Webinar topic, date, and time with timezone: [fill] - The transformation attendees will get from attending: [fill] - The offer revealed at the end: [fill] </inputs> <task> Write a 6-email registrant sequence spanning confirmation, two pre-webinar warm-ups, day-of reminder, replay, and a closing nudge. For each: send day or hour relative to the webinar, goal, subject plus A/B, preview, body, one CTA. </task> <constraints> - Pre-webinar emails build anticipation and reduce no-show, not pitch - Day-of reminder includes the join link placeholder and a reason to attend live - Post-webinar emails handle both attendees and no-shows </constraints> <format> Markdown artifact, one section per email, labeled with its timing relative to the webinar. </format>

<context> I have leads who joined for [lead magnet] months ago and went cold. I want to re-warm them before they fully disengage. </context> <inputs> - Why they originally signed up: [fill] - What has changed or improved since then: [fill] - The offer or next step I want to reintroduce: [fill] </inputs> <task> Write a 5-email re-warming sequence that reconnects, delivers fresh value, and gently reopens the relationship. For each: send day, goal, subject plus A/B, preview, body, one CTA. </task> <constraints> - Email 1 acknowledges the gap honestly without guilt-tripping - Lead with new value before any ask - Final email offers a clear path back or a graceful opt-down </constraints> <format> Markdown artifact, one section per email. </format>

<context> My list mixes distinct personas for [offer], and one-size nurture underperforms. I want parallel tracks tailored to each persona. </context> <inputs> - Persona A, their goal, and their objection: [fill] - Persona B, their goal, and their objection: [fill] - Shared offer and its core benefit: [fill] </inputs> <task> Write a 4-email nurture track for each of the two personas, eight emails total. Tailor pain, language, proof, and CTA to each persona while pointing both toward the same offer. For each email: send day, goal, subject plus A/B, preview, body, one CTA. </task> <constraints> - Mirror each persona's vocabulary and priorities, do not just swap names - Keep the two tracks structurally parallel for easy A/B comparison - Each track addresses that persona's specific objection </constraints> <format> Markdown artifact with two top-level sections, one per persona, each containing four email subsections. </format>

<context> Many of my [audience] are not ready to buy [offer] for months. I want a slow, value-heavy drip that keeps me top of mind without burning them out. </context> <inputs> - Topic area and the long-term goal it serves: [fill] - Three recurring content themes I can rotate: [fill] - The eventual offer and ideal trigger to revisit it: [fill] </inputs> <task> Write an 8-email long-term drip spaced over roughly two months. Rotate the three themes, keep value high, and seed the offer only twice and lightly. For each email: send day, goal, subject plus A/B, preview, body, one soft CTA. </task> <constraints> - At most two emails reference the offer, both as optional next steps - Vary format across emails: tip, story, question, resource, mini-guide - Every email stands alone and delivers value even if prior ones were missed </constraints> <format> Markdown artifact, one section per email, tagged with its rotating theme. </format>

<context> Leads signed up for a free [product or tool] but barely use it. I want a sequence that teaches them to get value so they convert to paid. </context> <inputs> - Product and its core paid benefit: [fill] - The three features that drive the aha moment: [fill] - The single action that predicts conversion: [fill] </inputs> <task> Write a 6-email product-education series that drives activation. Each email teaches one capability and prompts a specific in-product action. For each: send day, goal, subject plus A/B, preview, body, one action CTA. </task> <constraints> - Drive the conversion-predicting action by email 3 at the latest - Frame every feature around the outcome it unlocks, not the feature itself - Final two emails connect activated value to the paid upgrade </constraints> <format> Markdown artifact, one section per email, each naming the in-product action it asks for. </format>

<context> I want to nurture [audience] using a single narrative that carries my core message about [topic] across multiple emails. </context> <inputs> - The story premise and who it centers on: [fill] - The lesson or belief the story proves: [fill] - The offer the lesson naturally leads to: [fill] </inputs> <task> Write a 5-email story-based nurture sequence that tells one continuous story across the arc: setup, tension, choice, resolution, and lesson-to-offer. For each: send day, goal, subject plus A/B, preview, body, one CTA. </task> <constraints> - Each email picks up exactly where the last left off - The lesson surfaces through the story, never as a lecture - Only the final email connects the lesson to the offer </constraints> <format> Markdown artifact, one section per email, labeled with its narrative beat. </format>

<context> My leads are actively comparing [my category] options and weighing alternatives to [my offer]. I want a sequence that wins the comparison honestly. </context> <inputs> - My offer and its standout strengths: [fill] - The main alternatives and where each falls short: [fill] - The use case where I clearly win: [fill] </inputs> <task> Write a 5-email comparison nurture sequence that helps them choose well and shows where I fit best. For each: send day, goal, subject plus A/B, preview, body, one CTA toward [offer]. </task> <constraints> - Be fair to alternatives and credit their real strengths - Anchor the comparison on the use case where I win - Give an honest "not for you if" moment to build credibility </constraints> <format> Markdown artifact, one section per email, plus a final comparison-criteria recap. </format>

<context> I want to nurture [audience] purely with value for a stretch, building goodwill before any offer enters the picture for [topic]. </context> <inputs> - Audience and the outcomes they want: [fill] - Five genuinely useful insights or resources I can give: [fill] - The brand voice I want to reinforce: [fill] </inputs> <task> Write a 5-email value-first series with no pitch at all. Each email delivers one standalone useful insight and deepens the relationship. For each: send day, goal, subject plus A/B, preview, body, one engagement-only CTA. </task> <constraints> - No selling, no offer mention, not even a soft one - CTAs are reply, share, or implement only - Each email is immediately usable on its own </constraints> <format> Markdown artifact, one section per email, with a one-line takeaway the reader can act on. </format>

<context> A segment of leads opens my emails about [topic] but never clicks through to [offer or resource]. I want to convert that passive attention into action. </context> <inputs> - What I want them to click toward: [fill] - The likely friction stopping the click: [fill] - A stronger hook or incentive I can offer: [fill] </inputs> <task> Write a 4-email re-engagement sequence targeting openers who do not click. Each email tests a different angle to earn the click: curiosity, value, social proof, and direct ask. For each: send day, goal, subject plus A/B, preview, body, one CTA. </task> <constraints> - Make the click reason unmistakable and the CTA visually singular - Reduce the friction named in the inputs in at least two emails - Vary the hook angle in every email so something lands </constraints> <format> Markdown artifact, one section per email, labeled with the click angle it tests. </format>

<context> I want to nurture qualified leads for [product] toward booking a demo or call, without feeling pushy for my [audience]. </context> <inputs> - Product and the outcome a demo reveals: [fill] - What a great-fit lead looks like: [fill] - The hesitation that stops people from booking: [fill] </inputs> <task> Write a 5-email nurture-to-demo sequence that builds the case for a conversation and lowers the cost of saying yes. For each: send day, goal, subject plus A/B, preview, body, one CTA to book. </task> <constraints> - Frame the demo as value to them, not a sales meeting - Address the booking hesitation directly in one email - Each CTA links to the same booking action with rising urgency </constraints> <format> Markdown artifact, one section per email, plus a note on how each lowers booking friction. </format>

<context> I want to nurture [audience] by sharing my founder story so they connect with the mission behind [offer] and trust the brand. </context> <inputs> - The origin moment and the problem that sparked the company: [fill] - The struggle or failure that shaped the approach: [fill] - The mission and how the offer serves it: [fill] </inputs> <task> Write a 5-email founder-story sequence across the arc: the spark, the struggle, the turning point, the mission, and the invitation. For each: send day, goal, subject plus A/B, preview, body, one CTA. </task> <constraints> - Keep it vulnerable and specific, not a polished highlight reel - Tie each chapter back to a benefit for the reader - Only the final email invites them to the offer </constraints> <format> Markdown artifact, one section per email, labeled with its story chapter. </format>

<context> I want to nurture [audience] toward [offer] by escalating asks gradually, so each yes makes the next one easier. </context> <inputs> - The end offer and its price or commitment: [fill] - Smaller micro-yeses I can ask for along the way: [fill] - The value I deliver between each ask: [fill] </inputs> <task> Write a 6-email sequence built as a commitment ladder, escalating from tiny asks to the main offer. For each: send day, goal, the size of ask, subject plus A/B, preview, body, one CTA. </task> <constraints> - Each email asks for slightly more than the last, never a sudden jump - Deliver fresh value before every escalated ask - The biggest ask only appears in the final email </constraints> <format> Markdown artifact, one section per email, each tagged with its ask size on the ladder. </format>

<context> Leads engaged with my free ungated [content piece] on [topic] without opting in for a magnet. I want to nurture that interest into [offer]. </context> <inputs> - The content piece and the intent it signals: [fill] - The natural next step beyond that content: [fill] - The offer it ultimately leads to: [fill] </inputs> <task> Write a 5-email nurture sequence that picks up from the ungated content, deepens the topic, and bridges to the offer. For each: send day, goal, subject plus A/B, preview, body, one CTA. </task> <constraints> - Email 1 references the content they engaged with to establish continuity - Each email advances the topic rather than repeating the content - Bridge to the offer only after at least two value emails </constraints> <format> Markdown artifact, one section per email, with a note on how each builds on the original content. </format>

<context> We are launching [product] to our existing email list. This is the headline launch moment and I want a sequence that builds anticipation, reveals the product, and converts early buyers. </context> <inputs> - Product and what it replaces or improves: [fill] - Launch date and any launch-window offer: [fill] - Core transformation it delivers: [fill] - Proof we can show (results, beta users, testimonials): [list] </inputs> <task> Write a 5-email product launch sequence. For each email give send timing relative to launch day, the goal, subject plus an A/B alternative, preview text, full body, and one CTA. Move from teaser to reveal to benefit-deep-dive to social proof to launch-window close. </task> <constraints> - Only email 3 is allowed to go deep on features - Build genuine anticipation, do not hype empty promises - Every email has exactly one CTA </constraints> <format> Markdown artifact: one section per email, timing in the heading. </format>

<context> We are running a limited-time promotion on [product] for [duration]. I want a sequence that drives urgency without feeling spammy to our list. </context> <inputs> - The offer and discount: [offer/discount] - Start and end dates: [fill] - Who the offer is best for: [audience] - The one objection that stops people buying: [fill] </inputs> <task> Write a 4-email limited-time promo sequence. For each email include send timing, goal, subject plus A/B alt, preview, body, and a single CTA. Open with the offer, then value-stack, then handle the key objection, then a deadline reminder. </task> <constraints> - State the exact end date and time in every email - Never repeat the same subject angle twice - Keep urgency honest, no fake scarcity </constraints> <format> Markdown artifact: one section per email with timing headings. </format>

<context> We are running a 48-hour flash sale on [product]. The window is short so every email has to earn the open and the click fast. </context> <inputs> - Flash sale offer and savings: [offer/discount] - Exact open and close times with timezone: [fill] - Hero product or bundle in the sale: [fill] </inputs> <task> Write a 3-email flash-sale sequence covering open, midpoint, and final-hours. For each email give precise send timing, goal, subject plus A/B alt, preview, short body, and one CTA. Tighten the language and shorten the body as the deadline approaches. </task> <constraints> - Email 3 must read as visibly more urgent and shorter than email 1 - Put a countdown reference in every email - No discount lasts beyond the stated close time </constraints> <format> Markdown artifact: one section per email, timing and countdown in heading. </format>

<context> People joined the waitlist for [product] before it goes on sale. I want to nurture them so they buy the moment the doors open. </context> <inputs> - What the product solves and for whom: [fill] - Expected launch date: [deadline] - Any waitlist-only perk: [fill or none] - Behind-the-scenes story or build details I can share: [fill] </inputs> <task> Write a 4-email pre-launch waitlist sequence. For each email include send timing before launch, goal, subject plus A/B alt, preview, body, and one CTA. Build belief and identity before any pitch, ending with a launch-day heads-up. </task> <constraints> - No buy link until the final email, earlier CTAs are soft engagement - Make subscribers feel like insiders - Reference the launch date in the last two emails </constraints> <format> Markdown artifact: one section per email with days-before-launch timing. </format>

<context> Shoppers add [product] to cart but do not check out. I want a recovery sequence that wins them back without leaning only on discounts. </context> <inputs> - Product and price point: [fill] - Common reasons people hesitate: [list] - Any incentive I can offer: [fill or none] </inputs> <task> Write a 4-email cart-abandonment sequence. For each email: send timing in hours or days after abandon, goal, subject plus A/B alt, preview, body, and one CTA. Escalate from reminder to objection-handling to a final time-bound nudge. </task> <constraints> - Do not lead with a discount in email 1 - Each email handles a different hesitation - Keep emails short and scannable </constraints> <format> Markdown artifact: one section per email with timing. </format>

<context> Users on a free trial of [product] are approaching the end of their trial. I want a sequence that converts them to paid before access expires. </context> <inputs> - Trial length and end behavior: [fill] - Paid plan and price: [offer/discount] - The aha moment users should have hit: [fill] - What they lose when the trial ends: [list] </inputs> <task> Write a 4-email trial-ending sequence. For each email give send timing relative to trial expiry, goal, subject plus A/B alt, preview, body, and one CTA to upgrade. Cover value-recap, loss-aversion, objection-handling, and a final expiry reminder. </task> <constraints> - Personalize around the value they already experienced in trial - Be specific about what access they lose and when - One upgrade CTA per email </constraints> <format> Markdown artifact: one section per email with days-to-expiry timing. </format>

<context> We are raising the price of [product] from [old price] to [new price] on [deadline]. I want to announce it in a way that drives a lock-in-now buying spike and keeps goodwill. </context> <inputs> - Old and new price: [fill] - Effective date: [deadline] - Why the price is going up (real reason): [fill] - Whether existing customers are grandfathered: [fill] </inputs> <task> Write a 3-email price-increase sequence. For each email give send timing before the change, goal, subject plus A/B alt, preview, body, and one CTA to buy or lock in the current price. Move from transparent announcement to value-justification to last-call. </task> <constraints> - Be honest and respectful about the reason for the increase - Make the lock-in-at-old-price action crystal clear - Reinforce the effective date in every email </constraints> <format> Markdown artifact: one section per email with timing headings. </format>

<context> We are running our biggest seasonal sale of the year for [product] over the Black Friday and Cyber Monday window. Inboxes are crowded so the sequence must cut through. </context> <inputs> - The seasonal offer and savings: [offer/discount] - Sale window dates: [fill] - What makes our deal different from competitors: [fill] - Best-selling or hero item in the sale: [fill] </inputs> <task> Write a 5-email Black Friday sequence covering early-access, BF day, weekend, Cyber Monday, and final-hours. For each email give send timing, goal, subject plus A/B alt, preview, body, and one CTA. Differentiate from the inbox flood and escalate urgency toward Cyber Monday close. </task> <constraints> - Every subject must stand out in a crowded seasonal inbox - Reuse no offer framing across the five emails - Final email is the hardest deadline push </constraints> <format> Markdown artifact: one section per email with date and timing heading. </format>

<context> Customers just bought [product] and I want to upsell them to [upgrade/higher tier] while satisfaction and momentum are high. </context> <inputs> - What they bought: [fill] - The upsell offer and price: [offer/discount] - Why the upgrade is the natural next step: [fill] - Time-sensitive incentive for upgrading now: [fill or none] </inputs> <task> Write a 3-email post-purchase upsell sequence. For each email give send timing after purchase, goal, subject plus A/B alt, preview, body, and one CTA to upgrade. Lead with delivering value on the original purchase before introducing the upsell. </task> <constraints> - Email 1 must reinforce their original buying decision, not pitch - Position the upsell as an extension of value, not a fresh sale - One upgrade CTA per email </constraints> <format> Markdown artifact: one section per email with timing headings. </format>

<context> Customers who bought [product] are a great fit for [complementary product]. I want a cross-sell sequence that connects the two naturally. </context> <inputs> - The product they own: [fill] - The complementary product and price: [offer/discount] - How the two work better together: [fill] - A use case that ties them: [fill] </inputs> <task> Write a 3-email cross-sell sequence. For each email give send timing, goal, subject plus A/B alt, preview, body, and one CTA. Frame the second product as completing the result they already started, using a concrete combined use case. </task> <constraints> - Anchor every email on the product they already own - Show the better-together outcome, not just a second pitch - One CTA per email </constraints> <format> Markdown artifact: one section per email with timing headings. </format>

<context> A prospect took a demo of [product] but has not bought yet. I want a follow-up sequence that moves them from interested to closed. </context> <inputs> - What we covered in the demo: [fill] - Their stated goal or pain: [fill] - The pricing or proposal on the table: [offer/discount] - Likely blockers (budget, timing, stakeholders): [list] </inputs> <task> Write a 4-email demo-to-close sequence. For each email give send timing after the demo, goal, subject plus A/B alt, preview, body, and one CTA. Recap their specific goal, address blockers one at a time, share relevant proof, and propose a clear next step. </task> <constraints> - Reference the actual demo conversation, not a generic follow-up - Tackle a different blocker per email - Each CTA proposes a concrete next action </constraints> <format> Markdown artifact: one section per email with timing headings. </format>

<context> I sent a proposal for [project/service] to a prospect and have not heard back. I want a follow-up sequence that revives the deal without sounding desperate. </context> <inputs> - What the proposal includes and the price: [offer/discount] - The outcome the client wants: [fill] - When I sent it and any stated decision date: [deadline] - Possible reasons for the silence: [list] </inputs> <task> Write a 4-email proposal follow-up sequence. For each email give send timing after sending the proposal, goal, subject plus A/B alt, preview, body, and one CTA. Progress from a helpful check-in to added value to a graceful final close-the-loop email. </task> <constraints> - Never sound needy or repeat 'just following up' - Add a new piece of value or reassurance in each email - The final email gives a clean yes-or-no path </constraints> <format> Markdown artifact: one section per email with timing headings. </format>

<context> A customer's subscription to [product] is up for renewal. I want a sequence that reminds them, reinforces the value they got, and secures the renewal. </context> <inputs> - Plan and renewal price: [offer/discount] - Renewal date: [deadline] - Value or results they got this cycle: [fill] - Any loyalty perk or renewal incentive: [fill or none] </inputs> <task> Write a 3-email subscription renewal sequence. For each email give send timing before the renewal date, goal, subject plus A/B alt, preview, body, and one CTA. Start with a value-recap, then highlight what is ahead, then a clear renewal reminder. </task> <constraints> - Quantify the value they received where possible - Make the renewal action and date unmistakable - One CTA per email </constraints> <format> Markdown artifact: one section per email with days-before-renewal timing. </format>

<context> Customers who used to buy or subscribe to [product] have gone quiet. I want a win-back sequence with an offer that pulls them back. </context> <inputs> - How long they have been inactive: [fill] - A comeback offer or incentive: [offer/discount] - What has improved or changed since they left: [fill] - The reason many of them likely lapsed: [fill] </inputs> <task> Write a 4-email win-back sequence. For each email give send timing, goal, subject plus A/B alt, preview, body, and one CTA. Move from a we-miss-you reconnect to what is new to the comeback offer to a final goodbye-or-stay email. </task> <constraints> - Acknowledge the gap without guilt-tripping - Hold the offer until email 3 - The final email respects their choice to leave </constraints> <format> Markdown artifact: one section per email with timing headings. </format>

<context> We are selling [product] as a bundle with stacked bonuses to raise perceived value and average order value. I want a sequence that makes the stack irresistible. </context> <inputs> - Core product and bundle price: [offer/discount] - The bonuses or items stacked in: [list] - Total value versus bundle price: [fill] - Who the bundle is perfect for: [audience] </inputs> <task> Write a 4-email bundle sequence. For each email give send timing, goal, subject plus A/B alt, preview, body, and one CTA. Introduce the bundle, then reveal the stacked bonuses one focus at a time, then drive the value-versus-price math, then close. </task> <constraints> - Spotlight a different bonus in the middle emails - Make the total-value math explicit and credible - One CTA per email </constraints> <format> Markdown artifact: one section per email with timing headings. </format>

<context> We are opening early-bird pricing on [product] before the full price kicks in. I want a sequence that rewards fast action and converts the eager segment first. </context> <inputs> - Early-bird price versus full price: [offer/discount] - When early-bird pricing ends: [deadline] - How many early-bird spots or units, if limited: [fill or unlimited] - The product outcome: [fill] </inputs> <task> Write a 3-email early-bird sequence. For each email give send timing before the early-bird deadline, goal, subject plus A/B alt, preview, body, and one CTA. Open the early-bird, reinforce the saving and reason to act now, then a deadline close. </task> <constraints> - Make the price gap between early-bird and full obvious - Tie urgency to a real deadline or spot count - One CTA per email </constraints> <format> Markdown artifact: one section per email with timing headings. </format>

<context> An offer on [product] is closing soon and I want a final-day urgency sequence sent to people who have not yet bought. </context> <inputs> - The offer that is ending: [offer/discount] - Exact close date and time with timezone: [deadline] - What they lose when it closes: [fill] - The single most compelling reason to act now: [fill] </inputs> <task> Write a 3-email last-chance sequence sent across the final day: morning, afternoon, and final hours. For each email give send timing, goal, subject plus A/B alt, preview, short body, and one CTA. Sharpen urgency and shorten the body with each send. </task> <constraints> - Reference the exact close time in every email - The final email is short, direct, and pure deadline - No urgency claim that is not literally true </constraints> <format> Markdown artifact: one section per email with timing headings. </format>

<context> We just shipped [new feature] and want to upsell existing customers on a higher plan or add-on that unlocks it. </context> <inputs> - The new feature and what it enables: [fill] - The plan or add-on that unlocks it and its price: [offer/discount] - The problem this feature solves for them: [fill] - Who benefits most from it: [audience] </inputs> <task> Write a 3-email new-feature upsell sequence. For each email give send timing, goal, subject plus A/B alt, preview, body, and one CTA. Announce the feature and the problem it solves, then show it in action, then make the upgrade-to-unlock case. </task> <constraints> - Lead with the problem solved, not the feature spec - Only the last two emails pitch the upgrade - One CTA per email </constraints> <format> Markdown artifact: one section per email with timing headings. </format>

<context> We have happy customers using [product] and want to turn them into referrers through a sequence that makes sharing easy and rewarding. </context> <inputs> - The referral reward for them and their friend: [offer/discount] - How the referral works in one step: [fill] - The result our happiest customers rave about: [fill] - Where they can share or refer: [fill] </inputs> <task> Write a 3-email referral-ask sequence. For each email give send timing, goal, subject plus A/B alt, preview, body, and one CTA. Lead with gratitude and their win, make the double-sided reward clear, then a friendly final nudge with a ready-to-share message. </task> <constraints> - Email 1 celebrates them before asking for anything - Make referring a one-click or one-step action - Provide a copy-and-paste share blurb in the sequence </constraints> <format> Markdown artifact: one section per email with timing headings. </format>

<context> I am the founder launching [product] and I want a personal, story-driven sequence written in my own voice, not a corporate campaign. </context> <inputs> - Why I built this product (origin story): [fill] - The launch offer and deadline: [offer/discount] - The transformation it creates for customers: [fill] - My personal stake or mission: [fill] </inputs> <task> Write a 4-email founder launch sequence in a first-person, personal tone. For each email give send timing, goal, subject plus A/B alt, preview, body, and one CTA. Tell the origin story, share the mission, show who it is for, then make a heartfelt launch ask. </task> <constraints> - Write as a person, not a brand, plain and warm - Story carries the first emails, the offer arrives later - Keep one clear CTA per email </constraints> <format> Markdown artifact: one section per email with timing headings. </format>

<context> Part of my list for [product/newsletter] has gone quiet (no opens in [period]). I want to win back the salvageable ones and let the rest go cleanly. </context> <inputs> - What I offer and the core value reminder: [fill] - How long they have been inactive: [fill] - Any incentive available: [fill or none] - Brand voice: [casual/warm/direct] </inputs> <task> Write a 4-email re-engagement sequence: a pattern-interrupt opener, a value reminder, an incentive or preference-update, and a final break-up email that triggers a clean unsubscribe if ignored. Per email: timing, goal, subject plus A/B alt, preview, body, single CTA. </task> <constraints> - The final email must make leaving easy and guilt-free - Vary the angle each email; do not repeat "we miss you" </constraints> <format> Markdown artifact: one section per email. </format>

<context> Customers who cancelled [product] are still in my CRM. I want a winback sequence that re-earns them without sounding desperate. </context> <inputs> - Product and what is new since they left: [fill] - Why most people churned: [price/complexity/timing/competitor] - Reactivation offer: [fill or none] - Average time since cancellation: [fill] </inputs> <task> Write a 4-email winback sequence: acknowledge the gap, address the likely churn reason head-on, show what changed and proof, then make a low-risk return offer with a deadline. For each email give send day, goal, subject plus A/B alt, preview text, body, and one CTA. </task> <constraints> - Lead with empathy in email 1; never blame the customer - Only one offer, and only in the final email </constraints> <format> Markdown artifact, one section per email, with a one-line strategy note per email. </format>

<context> I run [brand] and a segment of customers has gone cold. I want a genuinely warm "we miss you" series that rebuilds the relationship before asking for anything. </context> <inputs> - Brand personality in three words: [fill] - What this audience originally loved: [fill] - A small gesture I can give (gift, credit, early access): [fill or none] - Last interaction type: [purchase/visit/open] </inputs> <task> Write a 3-email "we miss you" series that is relationship-first: email 1 is pure warmth and a single small gesture, email 2 reminds them what they are missing, email 3 invites them back with a soft prompt. For each: timing, goal, subject plus A/B alt, preview, body, one CTA. </task> <constraints> - Sound human, not corporate; short paragraphs - Do not stack offers or use urgency countdowns </constraints> <format> Markdown artifact: one section per email. </format>

<context> I am cleaning my list for [newsletter/product]. Before removing unengaged contacts, I want a respectful sunset sequence that gives them a real last chance to stay. </context> <inputs> - How long inactive before sunset: [fill] - What they will lose access to: [fill] - The one-click action to stay: [fill] - Removal date: [fill] </inputs> <task> Write a 3-email sunset sequence ending in removal: an honest heads-up, a single last-chance reminder, and a final "this is goodbye unless you click" email. Per email: send day relative to removal date, goal, subject plus A/B alt, preview, body, one CTA to stay. </task> <constraints> - Be transparent that no action means removal - The stay action must be one click; no logins or forms </constraints> <format> Markdown artifact, one section per email, plus a suggested countdown to the removal date. </format>

<context> People started a free trial of [product] but never activated (no key action taken). I want to reactivate them before the trial expires or shortly after. </context> <inputs> - The single activation action that predicts success: [fill] - Top friction that blocks first value: [fill] - Days left in trial or days since expiry: [fill] - A nudge I can offer (extension, onboarding call, template): [fill or none] </inputs> <task> Write a 4-email trial reactivation sequence: surface the one action that unlocks value, remove the top friction, show a quick win or template, then create gentle deadline urgency tied to the trial. Per email: timing, goal, subject plus A/B alt, preview, body, one CTA pointing to the activation action. </task> <constraints> - Every email drives toward the single activation action - Educate before pressuring; no hard sell until the last email </constraints> <format> Markdown artifact: one section per email. </format>

<context> Customers who bought [product] once have not purchased again in [period]. I want to bring lapsed buyers back for a repeat or replenishment order. </context> <inputs> - Typical repurchase cycle: [fill] - What they bought and natural next purchase: [fill] - Incentive for returning: [fill or none] - Any new products since their last order: [fill] </inputs> <task> Write a 4-email lapsed-buyer winback sequence: a timely replenishment reminder, a "here is what is new" nudge, social proof or a best-seller spotlight, then a time-boxed return offer. Per email: send day, goal, subject plus A/B alt, preview, body, one CTA to shop. </task> <constraints> - Tie the timing to their repurchase cycle, not a generic calendar - Reference their past category without sounding creepy about data </constraints> <format> Markdown artifact: one section per email, with a recommended send-day relative to last order. </format>

<context> A segment of [product] users has gone quiet. Instead of selling, I want to re-engage by asking what went wrong and what would bring them back. </context> <inputs> - Product and the moment people typically disengage: [fill] - Where the feedback link or reply goes: [fill] - Incentive for replying: [fill or none] - Tone: [humble/curious/direct] </inputs> <task> Write a 3-email feedback-ask sequence: a single low-effort question that re-opens dialogue, a follow-up that offers a couple of one-tap answer options, and a final "your reply shapes what we build" close. Per email: timing, goal, subject plus A/B alt, preview, body, one clear reply or click CTA. </task> <constraints> - Make replying effortless; one question, ideally a reply or single tap - Genuinely curious, not a survey disguised as care </constraints> <format> Markdown artifact: one section per email. </format>

<context> I want to win back inactive customers of [product] with a real offer, structured so the discount feels earned and time-bound rather than always-on. </context> <inputs> - The offer and its true value: [fill] - Expiry window: [fill] - What they get beyond the discount: [fill] - Segment being targeted: [lapsed buyers/churned/dormant] </inputs> <task> Write a 3-email offer-based winback sequence: a soft reintroduction that reminds them of value, the offer reveal with clear terms and deadline, and a final "last hours" reminder. Per email: send day, goal, subject plus A/B alt, preview, body, one CTA to redeem. </task> <constraints> - Do not lead with the discount in email 1; earn it first - State expiry clearly; the final email must reflect real scarcity </constraints> <format> Markdown artifact: one section per email, plus suggested offer-deadline timing. </format>

<context> My [newsletter/product] subscribers went cold. I want to re-engage purely with valuable content, rebuilding the open habit before any pitch. </context> <inputs> - My best-performing content themes: [fill] - A flagship resource or guide I can lead with: [fill] - What I ultimately want them to do later: [fill] - Cadence I can sustain: [fill] </inputs> <task> Write a 4-email content-led re-engagement series: each of the first three delivers a genuinely useful, standalone insight or resource, and the fourth gently bridges to the next step. Per email: timing, goal, subject plus A/B alt, preview, body skeleton with the content hook, one CTA. </task> <constraints> - First three emails ask for nothing but a click to read or use - Each subject must promise a specific, concrete payoff </constraints> <format> Markdown artifact: one section per email. </format>

<context> We shipped meaningful updates to [product] since these users went inactive. I want to re-engage them by showing that the thing they left has genuinely improved. </context> <inputs> - The biggest updates and the problems they solve: [fill] - The objection that likely drove them away: [fill] - A way to experience the update fast (demo, free use, template): [fill] - Segment: [dormant users/churned/lapsed] </inputs> <task> Write a 3-email product-update re-engagement series: lead with the single update that kills the old objection, follow with two-or-three supporting improvements and proof, then invite them to try the new experience. Per email: send day, goal, subject plus A/B alt, preview, body, one CTA. </task> <constraints> - Frame updates as "you asked, we fixed," not a changelog dump - Connect each update to a benefit, not a feature name </constraints> <format> Markdown artifact: one section per email. </format>

<context> I want to re-engage dormant subscribers of [newsletter/product] through a short survey, then convert respondents back into active, opted-in readers. </context> <inputs> - The 1 to 3 questions that matter most: [fill] - Where the survey lives: [fill] - Incentive for completing: [fill or none] - What I will change based on answers: [fill] </inputs> <task> Write a 3-email survey-to-resubscribe sequence: an invite framed around shaping what they receive, a reminder with the time estimate and incentive, and a post-survey "based on your answers, here is what changes" resubscribe confirmation email. Per email: timing, goal, subject plus A/B alt, preview, body, one CTA. </task> <constraints> - Promise and respect a short time commitment - The final email must close the loop and re-confirm their preferences </constraints> <format> Markdown artifact: one section per email. </format>

<context> Former customers of [product] left a while ago and have missed a lot. I want a "here is everything you missed" winback that makes returning feel exciting, not remedial. </context> <inputs> - The 3 to 5 biggest changes since they left: [fill] - The single most compelling new thing: [fill] - A reason to return now: [fill or none] - Time since they left: [fill] </inputs> <task> Write a 3-email whats-new winback sequence: a punchy "a lot has changed" teaser, a curated highlight reel of the best updates with proof, and a "come see for yourself" return invite. Per email: send day, goal, subject plus A/B alt, preview, body, one CTA. </task> <constraints> - Curate to the few changes that matter; do not list everything - Make missing out feel like fixable good news, not guilt </constraints> <format> Markdown artifact: one section per email. </format>

<context> I need to re-permission a segment of [list] that has not engaged in [period], to keep my list compliant and deliverable. I want them to actively confirm they still want my emails. </context> <inputs> - What they originally signed up for: [fill] - The value of staying subscribed: [fill] - Confirm action and where it leads: [fill] - Deadline before they are removed: [fill] </inputs> <task> Write a 3-email re-permission sequence: an honest "confirm you still want this" ask, a value reminder plus what they lose if they do not confirm, and a final deadline confirmation email. Per email: send day relative to deadline, goal, subject plus A/B alt, preview, body, one clear confirm CTA. </task> <constraints> - Confirmation must be explicit and one click - Be clear that no confirmation means removal; stay compliant in tone </constraints> <format> Markdown artifact: one section per email, plus suggested timing around the deadline. </format>

<context> Customers on [plan] have signaled intent to downgrade or have downgraded [product]. I want a saver sequence that keeps them on a value-appropriate plan instead of losing the relationship. </context> <inputs> - The plan they have and the one below: [fill] - The features they would lose by downgrading: [fill] - Why people usually downgrade: [price/underuse/missing feature] - An alternative to a full downgrade (annual, pause, right-size plan): [fill] </inputs> <task> Write a 3-email downgrade-saver sequence: acknowledge their usage honestly and present a right-sized option, show the specific value at risk on the lower plan, then offer a middle path (discount, annual, or pause) to keep more value. Per email: timing, goal, subject plus A/B alt, preview, body, one CTA. </task> <constraints> - Be honest if a lower plan genuinely fits; do not manipulate - Offer a real alternative, not just guilt about lost features </constraints> <format> Markdown artifact: one section per email. </format>

<context> A customer has started or completed cancellation of [product]. I want a cancellation-save sequence that gives a real reason to stay or a graceful path back. </context> <inputs> - Top cancellation reasons: [price/value/bugs/timing/competitor] - A save offer I can extend (discount, pause, plan change): [fill or none] - The one outcome they hired us for: [fill] - Whether cancellation is pending or final: [fill] </inputs> <task> Write a 3-email cancellation-save sequence: a calm "before you go" with one tailored save option, a reminder of the outcome they will lose and how to reach it, then a respectful "door stays open" close with an easy return path. Per email: timing, goal, subject plus A/B alt, preview, body, one CTA. </task> <constraints> - One save offer maximum; do not bombard with escalating discounts - Respect the decision; the final email must not guilt-trip </constraints> <format> Markdown artifact: one section per email, with a note on which reason each email best counters. </format>

<context> A customer requested and received a refund for [product]. I want to re-engage them later in a way that rebuilds trust rather than reopening a sore spot. </context> <inputs> - Likely refund reason: [fill] - What has improved or what else I offer: [fill] - A low-risk way back (free tier, trial, smaller product): [fill] - How long to wait before re-engaging: [fill] </inputs> <task> Write a 3-email post-refund re-engagement sequence: a no-pressure check-in that confirms the refund went smoothly and adds value, a later "things have changed / here is something useful" touch, then a soft low-risk invitation to try again. Per email: send day after refund, goal, subject plus A/B alt, preview, body, one CTA. </task> <constraints> - Never imply the refund was wrong or pressure an immediate re-buy - Lead with goodwill and usefulness before any invitation </constraints> <format> Markdown artifact: one section per email, with recommended wait time before the first send. </format>

<context> I want to reactivate dormant customers of [product] around [season/event], using the moment as a natural, non-pushy reason to reconnect. </context> <inputs> - The season or event and why it fits my product: [fill] - A seasonal hook, theme, or offer: [fill] - What dormant customers loved before: [fill] - Campaign window: [fill] </inputs> <task> Write a 4-email seasonal reactivation sequence: a timely seasonal hello tied to the moment, a themed value or roundup, a seasonal offer or reason to act now, and a "last call before the season ends" close. Per email: send day within the window, goal, subject plus A/B alt, preview, body, one CTA. </task> <constraints> - Tie every email to the season authentically; no forced theming - Build urgency from the event ending, not fake scarcity </constraints> <format> Markdown artifact: one section per email, mapped to the campaign window. </format>

<context> I want to re-engage former customers based on what they specifically bought before, so each message feels personally relevant to their history with [brand]. </context> <inputs> - The product or category segments I can target: [fill] - The natural next or complementary purchase per segment: [fill] - Proof or reviews tied to those items: [fill] - Incentive: [fill or none] </inputs> <task> Write a 3-email past-purchase winback sequence with personalization logic: email 1 references their prior purchase and a complementary next step, email 2 brings proof and a best-pairing, email 3 makes a relevant time-boxed offer. Per email: timing, goal, subject plus A/B alt, preview, body with dynamic-field placeholders, one CTA. </task> <constraints> - Use merge fields for product, category, and date rather than generic copy - Recommendations must logically follow the prior purchase </constraints> <format> Markdown artifact: one section per email, with the merge fields listed at the top. </format>

<context> Some of my highest-value customers of [product] have gone quiet or lapsed. They deserve a white-glove winback, not a mass-email discount. </context> <inputs> - What made them high-value (spend, tenure, advocacy): [fill] - A premium gesture I can extend (concierge, exclusive access, gift): [fill] - A named human who can sign or reach out: [fill] - Why they may have drifted: [fill] </inputs> <task> Write a 3-email VIP winback sequence with a personal, high-touch tone: a 1-to-1-feeling note from a named person, an exclusive gesture or access reserved for them, then a direct invitation to reconnect or talk. Per email: timing, goal, subject plus A/B alt, preview, body, one CTA (including a reply or call option). </task> <constraints> - Premium and personal; no generic discount language - Offer access or attention, not just money off </constraints> <format> Markdown artifact: one section per email. </format>

<context> For the truly unresponsive on my [list/product], I want a short, respectful break-up series that gives one final chance and then exits gracefully, protecting deliverability and goodwill. </context> <inputs> - How long unresponsive: [fill] - The one-click way to stay: [fill] - What I want them to feel even if they leave: [fill] - Brand voice: [warm/witty/plain] </inputs> <task> Write a 2-email respectful break-up series: email 1 is an honest "it might be goodbye" with a single easy stay action, email 2 is a graceful final farewell that leaves the door open and the door-handle visible. Per email: timing, goal, subject plus A/B alt, preview, body, one CTA. </task> <constraints> - No guilt, no manipulation; make leaving and staying both effortless - The farewell must be memorable enough that some choose to stay </constraints> <format> Markdown artifact: one section per email. </format>

<context> People registered for my webinar [topic] on [date]. I want to maximize how many actually attend live. </context> <inputs> - Webinar topic, date, time, timezone: [fill] - The one big takeaway attendees get: [fill] - Typical registration-to-attendance show rate: [fill] - Host name and credibility hook: [fill] </inputs> <task> Write a reminder sequence from registration to live: confirmation, value-tease a few days out, day-before, one-hour-before, and we-are-live. Per email: timing, goal, subject plus A/B alt, preview text, body, single CTA (add to calendar / join link). </task> <constraints> - Each reminder must add a NEW reason to show up, never just repeat the time - Keep the two day-of emails under 80 words each - No spammy urgency words </constraints> <format> Markdown artifact: one section per email with timing as a header. </format>

<context> I run a recurring webinar and need a clean reminder drip that I can reuse for every session. </context> <inputs> - Webinar name and promise: [fill] - Send schedule I want covered (e.g. 1 week, 3 days, 1 day, 1 hour out): [fill] - Bonus or resource attendees receive for showing up: [fill] - Brand voice (formal / casual): [fill] </inputs> <task> Write a templated reminder sequence matching my send schedule. For each email give: timing offset, goal, subject plus A/B alt, preview text, body with a clear what-you-will-learn bullet block, and one CTA to confirm or join. </task> <constraints> - Make every email skimmable in under 20 seconds - Reference the show-up bonus in at least two emails - Use merge-field placeholders like [first_name] and [join_link] </constraints> <format> Markdown artifact, one labeled section per reminder. </format>

<context> Several people registered for my webinar [topic] but did not attend live. I want to re-engage them. </context> <inputs> - Webinar topic and the core lesson missed: [fill] - Replay link and how long it stays available: [fill] - Next-step offer or call to action: [fill] - Reason most no-shows gave (if known): [fill] </inputs> <task> Write a no-show follow-up sequence: same-day we-missed-you with replay, value-recap two days later, and a final last-chance replay email. Per email: timing, goal, subject plus A/B alt, preview, body, single CTA to watch the replay. </task> <constraints> - Lead with empathy, never guilt - Each email surfaces a different highlight from the session - Make the replay deadline concrete in the final email </constraints> <format> Markdown artifact with one section per email and timing headers. </format>

<context> People attended my webinar [topic] live. I want to keep momentum and move warm attendees to the next step. </context> <inputs> - Webinar topic and the transformation promised: [fill] - Resources to share (slides, replay, worksheet): [fill] - Next-step offer with price and deadline: [fill] - Key objection attendees raised: [fill] </inputs> <task> Write an attendee follow-up sequence: thank-you with resources, value-deepening lesson, objection-handler, and a deadline-driven offer email. Per email: timing, goal, subject plus A/B alt, preview, body, single CTA. </task> <constraints> - Acknowledge that they showed up and reward that engagement - Each email moves one notch closer to the offer - Address the named objection head-on in the third email </constraints> <format> Markdown artifact, one section per email with timing. </format>

<context> My event [event] just wrapped. Attendees are warm but not ready to buy. I want a slow-burn nurture. </context> <inputs> - Event name, theme, and audience: [fill] - Three pieces of value content I can share: [fill] - Long-term goal for this list (community, future event, eventual sale): [fill] - Cadence I prefer (weekly / biweekly): [fill] </inputs> <task> Write a multi-week post-event nurture sequence that builds trust without pitching hard. Per email: timing, goal, subject plus A/B alt, preview, body, single soft CTA (read, reply, or join). </task> <constraints> - No hard sell anywhere in the sequence - Each email gives standalone value before any ask - Invite replies to build two-way relationship </constraints> <format> Markdown artifact, one section per email with cadence noted. </format>

<context> I am promoting [event] on [date] and need an invite sequence that drives registrations. </context> <inputs> - Event name, format, date, location or platform: [fill] - The single biggest reason to attend: [fill] - Who the event is for and who it is NOT for: [fill] - Registration deadline or seat cap: [fill] </inputs> <task> Write an event-invitation sequence: announcement, agenda-and-speakers reveal, social-proof or FOMO email, and a closing deadline email. Per email: timing, goal, subject plus A/B alt, preview, body, single CTA to register. </task> <constraints> - The first email must qualify the right audience clearly - Build the value case before mentioning logistics - Use scarcity only if it is real (seat cap or deadline) </constraints> <format> Markdown artifact, one section per email with timing headers. </format>

<context> I met [contact] at [conference] and want to turn that hallway conversation into a real next step. </context> <inputs> - Conference name and what we discussed: [fill] - A specific detail from our chat to reference: [fill] - The next step I want (call, demo, intro): [fill] - My company and the value I can offer them: [fill] </inputs> <task> Write a post-conference follow-up sequence: warm same-week note, value-add follow-up with a relevant resource, and a gentle final nudge. Per email: timing, goal, subject plus A/B alt, preview, body, single CTA. </task> <constraints> - Reference the specific conversation detail so it never feels templated - Keep each email short and human, not corporate - The final email gracefully gives them an easy out </constraints> <format> Markdown artifact, one section per email with timing. </format>

<context> A prospect requested a demo of [product]. I want to confirm, reduce no-shows, and prime them to buy. </context> <inputs> - Product name and core value proposition: [fill] - Demo length, format, and who runs it: [fill] - One proof point or case study to share pre-demo: [fill] - The outcome the prospect is hoping to achieve: [fill] </inputs> <task> Write a demo confirmation and reminder sequence: instant confirmation with logistics, a day-before prime email with a proof point, and an hour-before nudge. Per email: timing, goal, subject plus A/B alt, preview, body, single CTA (confirm / join / reschedule). </task> <constraints> - The prime email should set an agenda so the demo feels worth their time - Make rescheduling frictionless, not a dead end - Keep the hour-before email under 60 words </constraints> <format> Markdown artifact, one section per email with timing headers. </format>

<context> I ran a hands-on workshop on [topic]. I want attendees to actually apply what they learned and stay engaged. </context> <inputs> - Workshop topic and the main skill taught: [fill] - Worksheets, templates, or recordings to share: [fill] - Common point where people get stuck after: [fill] - Optional next-step offer (coaching, course, community): [fill] </inputs> <task> Write a workshop follow-up sequence: thank-you with materials, an implementation prompt with the sticking-point fix, a quick-win check-in, and an optional next-step email. Per email: timing, goal, subject plus A/B alt, preview, body, single CTA. </task> <constraints> - Drive action, not just consumption - Address the known sticking point directly - Make the next-step email skippable for those still implementing </constraints> <format> Markdown artifact, one section per email with timing. </format>

<context> My webinar [topic] is now available on-demand. I want to drive replay views across my whole list. </context> <inputs> - Webinar topic and standout moment or stat: [fill] - Replay link and any expiry window: [fill] - Who on the list to target (registrants, no-shows, broader list): [fill] - The CTA after watching: [fill] </inputs> <task> Write a replay-promotion sequence: announcement with the standout moment, a curiosity-driven highlight email, and a closing expiry email. Per email: timing, goal, subject plus A/B alt, preview, body, single CTA to watch. </task> <constraints> - Each email teases a different moment from the replay - Use timestamps so people can jump to the good parts - Only use the expiry angle if the window is genuinely closing </constraints> <format> Markdown artifact, one section per email with timing headers. </format>

<context> After [event], qualified leads need to move from marketing nurture into a sales conversation smoothly. </context> <inputs> - Event name and what qualified leads engaged with: [fill] - The sales rep or team taking over, with a human intro line: [fill] - The offer or solution being discussed: [fill] - Booking link for a sales call: [fill] </inputs> <task> Write an event-to-sales handoff sequence: a warm intro email handing the lead to a rep, a value-bridge email tying the event to their problem, and a low-pressure booking email. Per email: timing, goal, subject plus A/B alt, preview, body, single CTA to book. </task> <constraints> - The handoff must feel personal, signed by the actual rep - Bridge from event content to a real business outcome - Keep pressure low; this is a warm, not cold, lead </constraints> <format> Markdown artifact, one section per email with timing. </format>

<context> I am organizing [event] and want to recruit a great speaker or partner: [contact]. </context> <inputs> - Event name, audience size, and theme: [fill] - Why this specific person is a fit: [fill] - What is in it for them (exposure, audience, fee): [fill] - The ask and the deadline to confirm: [fill] </inputs> <task> Write a speaker/partner outreach sequence: a personalized initial invite, a value-and-logistics follow-up, and a polite final check-in. Per email: timing, goal, subject plus A/B alt, preview, body, single CTA to reply or book a call. </task> <constraints> - Lead with what is in it for them, not for me - Reference their specific work in the first email - The final email leaves the door open without nagging </constraints> <format> Markdown artifact, one section per email with timing headers. </format>

<context> A customer just bought [product]. I want to confirm the purchase, reduce buyer regret, and drive first use. </context> <inputs> - Product or service purchased: [fill] - The very first action they should take to get value: [fill] - Where to find support or onboarding help: [fill] - One quick win they can achieve in week one: [fill] </inputs> <task> Write a post-purchase thank-you and next-steps sequence: instant order confirmation and welcome, a get-started email with the first action, and a quick-win check-in. Per email: timing, goal, subject plus A/B alt, preview, body, single CTA. </task> <constraints> - Reinforce that they made a smart decision - Make the first action dead simple and unmissable - Point to support so nobody feels stranded </constraints> <format> Markdown artifact, one section per email with timing. </format>

<context> Customers have used [product] long enough to have an opinion. I want authentic reviews and testimonials. </context> <inputs> - Product and the typical result customers get: [fill] - Where I want the review posted (site, G2, Trustpilot): [fill] - Any incentive offered (or none): [fill] - A specific prompt question to spark a useful review: [fill] </inputs> <task> Write a review/testimonial request sequence: a warm ask referencing their result, a make-it-easy email with a prompt question and direct link, and a gentle final reminder. Per email: timing, goal, subject plus A/B alt, preview, body, single CTA to leave a review. </task> <constraints> - Lower friction at every step with a direct link - Use a prompt question so reviews are specific, not generic - Keep it gracious; never demand a five-star rating </constraints> <format> Markdown artifact, one section per email with timing headers. </format>

<context> I want to measure satisfaction with [product] via NPS and follow up intelligently based on the score. </context> <inputs> - Product and the audience being surveyed: [fill] - The single NPS question and scale: [fill] - What I will do with promoters vs detractors: [fill] - Booking or reply link for deeper feedback: [fill] </inputs> <task> Write an NPS feedback sequence: the initial one-click NPS ask, a promoter branch thanking and inviting a review or referral, and a detractor branch inviting a candid conversation. Per email: timing, goal, subject plus A/B alt, preview, body, single CTA. </task> <constraints> - The first email must be answerable in one click - Promoter and detractor branches must feel genuinely different - Detractor email opens a real dialogue, not a defensive reply </constraints> <format> Markdown artifact: initial email, then two clearly labeled branch sections. </format>

<context> New customers of [product] need to book an onboarding call so they actually get set up and succeed. </context> <inputs> - Product and what the onboarding call covers: [fill] - How long the call takes and who runs it: [fill] - The cost of NOT onboarding (slow start, churn risk): [fill] - Scheduling link: [fill] </inputs> <task> Write an onboarding-call scheduling sequence: an invite framing the call as a head start, a why-it-matters nudge, and a final easy-booking reminder. Per email: timing, goal, subject plus A/B alt, preview, body, single CTA to book. </task> <constraints> - Frame the call as a benefit, not an obligation - Make booking take one click - Give a self-serve option in the final email for those who skip the call </constraints> <format> Markdown artifact, one section per email with timing headers. </format>

<context> I collected booth leads at [trade show] and need to follow up fast before they go cold. </context> <inputs> - Trade show name and what we demoed at the booth: [fill] - The hook or giveaway that drew them in: [fill] - How to segment hot vs lukewarm leads: [fill] - Next step and booking link: [fill] </inputs> <task> Write a trade-show lead follow-up sequence: a fast next-day recap referencing the booth, a value-add email with relevant proof, and a soft booking nudge. Per email: timing, goal, subject plus A/B alt, preview, body, single CTA. </task> <constraints> - Send the first email within 24 hours and say so - Jog their memory with a booth-specific detail - Keep it consultative; trade-show leads are early-stage </constraints> <format> Markdown artifact, one section per email with timing. </format>

<context> I appeared as a guest on the [podcast] podcast. I want to nurture the host relationship and the new audience. </context> <inputs> - Podcast name, host, and episode topic: [fill] - A standout moment or quote from the episode: [fill] - What I want next (cross-promo, referral, repeat appearance): [fill] - A lead magnet for listeners who found me there: [fill] </inputs> <task> Write a podcast-guest follow-up sequence: a gracious thank-you to the host, a promotion-and-tag email coordinating the launch push, and a listener-welcome email for new subscribers. Per email: timing, goal, subject plus A/B alt, preview, body, single CTA. </task> <constraints> - The host emails build a real two-way relationship - The listener email delivers value before any ask - Make cross-promotion easy with ready-to-use copy </constraints> <format> Markdown artifact, one section per email with timing headers. </format>

<context> I hosted a community event [event] (meetup, AMA, or local gathering) and want to deepen belonging afterward. </context> <inputs> - Event name, vibe, and who attended: [fill] - A shared moment or highlight to reference: [fill] - Where the community lives between events (Slack, Discord, forum): [fill] - The next gathering or way to stay involved: [fill] </inputs> <task> Write a community-event follow-up sequence: a warm recap celebrating attendees, a keep-the-conversation-going email pointing to the community space, and a save-the-date for what is next. Per email: timing, goal, subject plus A/B alt, preview, body, single CTA. </task> <constraints> - Lead with belonging and connection, not promotion - Make joining the ongoing community feel effortless - Reference the shared highlight to rekindle the feeling </constraints> <format> Markdown artifact, one section per email with timing. </format>

<context> My webinar [topic] pitched [offer]. Now I need a focused sequence to close sales before the deadline. </context> <inputs> - Webinar topic and the offer with price: [fill] - The deadline and any bonus that expires with it: [fill] - Top two objections that stall buyers: [fill] - Proof (testimonial, result, guarantee) to deploy: [fill] </inputs> <task> Write a post-webinar offer sequence: an offer recap with the bonus, an objection-and-proof email, a fence-sitter FAQ email, and a final deadline cart-close. Per email: timing, goal, subject plus A/B alt, preview, body, single CTA to buy. </task> <constraints> - Each email handles a different objection or angle - Use the guarantee to remove risk before the deadline - The final email is short, urgent, and honest about the close </constraints> <format> Markdown artifact, one section per email with timing headers. </format>