30 Claude Prompts That Write Newsletters
Describe your audience and Claude returns a full issue: subject line, preview text, sections, and a clear CTA, ready to paste into your email tool or previewed as a self-contained HTML email. Prompts for welcome emails, weekly digests, product updates, promos, roundups, and re-engagement.
In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 15 prompts are free instantly โ no signup needed. Hand-curated and tested by the AI Academy team.
Welcome & Onboarding Emails
5 promptsFirst Welcome Email
1/30You are an email lifecycle strategist who writes warm, high-open welcome emails. <context> A new subscriber just joined my list. I need a complete first welcome email as a ready-to-send, self-contained deliverable: subject line, preview text, body sections, and one clear CTA. </context> <inputs> - Newsletter / brand name: [NAME] - What subscribers signed up for: [TOPIC OR OFFER] - Who they are: [AUDIENCE] - The one thing I want them to do next: [PRIMARY CTA] - Sender voice: [FRIENDLY, EXPERT, PLAYFUL] </inputs> <task> Write the full email: a subject line plus two alternates, preview text under 90 characters, a warm greeting that confirms what they signed up for, a short "here is what to expect and how often" block, a single clear CTA to the most valuable first action, and a human sign-off. Set clear expectations so the second email gets opened. </task> <constraints> - One CTA only; no competing links. - Real, specific copy in the stated voice; no "we are thrilled" filler. - Subject lines under 50 characters; skimmable short paragraphs. </constraints> <format> Return the complete email as a copy-paste block (Subject / Preview / Body / CTA), then a one-line note on how to adapt it for a double opt-in confirmation. </format>
Produces a complete first welcome email with subject, preview text, expectations, and one CTA, ready to use.
Pro tip: Tell Claude the single best free resource you have and make that the first-action CTA instead of a generic 'visit our site'.
5-Email Welcome Series Plan
2/30You are a lifecycle email architect who designs onboarding sequences that turn new subscribers into fans. <context> I want a full 5-email welcome series mapped out and drafted, delivered as a ready-to-use document I can load into my email tool. </context> <inputs> - Brand and product: [NAME PLUS WHAT IT IS] - Audience and their goal: [WHO PLUS WHAT THEY WANT] - The core transformation or value: [WHAT THEY GET FROM YOU] - Conversion goal by end of series: [TRIAL, PURCHASE, HABIT] - Send cadence: [E.G. DAYS 0, 2, 4, 7, 10] </inputs> <task> Deliver a series table (email number, send day, goal, subject line, one-line angle) followed by full drafts for all five emails, each with subject, preview text, body, and one CTA. Escalate from welcome and expectations to value, proof, soft pitch, and a clear ask, so each email builds on the last. </task> <constraints> - One CTA per email; distinct goal per email, no repetition. - Specific copy in a consistent voice; subject lines under 50 characters. </constraints> <format> Return the plan table first, then the five drafts as copy-paste blocks, then one line on which email to A/B test first. </format>
Generates a full 5-email welcome series (plan plus drafts) with escalating goals and CTAs, ready to load.
Pro tip: Give Claude your activation 'aha moment' so it front-loads the series toward that action instead of a slow drip.
SaaS Onboarding Welcome (HTML)
3/30You are a SaaS lifecycle marketer and email designer. <context> A user just created an account. I need a welcome email built as one self-contained, responsive HTML email I can preview instantly as an artifact and paste into my ESP. </context> <inputs> - Product name and what it does: [NAME PLUS ONE-LINER] - The activation action: [E.G. CONNECT A DATA SOURCE, INVITE A TEAMMATE] - Top three things they can do: [FEATURES] - Support or help link: [URL OR PLACEHOLDER] - Brand color: [HEX OR DESCRIPTION] </inputs> <task> Build the email: preheader text, a branded header, a personalized greeting, a single primary button to the activation action, a three-step "get set up in minutes" block, a short list of what they can explore next, and a footer with help link and unsubscribe. Write all copy toward getting them to the aha moment fast. </task> <constraints> - One self-contained HTML email using table-based layout and inline CSS for client compatibility. - One primary button (the activation action); other links are secondary text. - Real benefit copy; accessible alt text on any image placeholders. </constraints> <format> Return the full HTML email as an artifact, then explain the single activation metric this email is optimized for and what to test in the button. </format>
Builds a self-contained HTML onboarding welcome email focused on the activation action as a previewable artifact.
Pro tip: Name the exact activation action (connect X, invite Y) and Claude will point the one button straight at it instead of the dashboard.
Creator Newsletter Welcome
4/30You are a personality-driven newsletter writer who welcomes new readers in an authentic voice. <context> I run a personal or creator newsletter. I need a complete welcome email that sets the voice and hooks new readers, delivered ready to send. </context> <inputs> - Newsletter name and topic: [NAME PLUS WHAT IT COVERS] - Who I am and why I write it: [SHORT BIO PLUS MISSION] - What every issue delivers: [RECURRING VALUE] - Cadence: [WEEKLY, BIWEEKLY] - One best past piece to link: [TITLE PLUS URL] </inputs> <task> Write the full email: a subject line plus two alternates, preview text, a short personal intro that establishes voice and why they should trust me, a clear "here is what you will get and when" block, a link to my single best past issue as an instant-value hook, and a warm sign-off inviting a reply. Make it feel like a real human, not a brand. </task> <constraints> - Distinct, human voice; specific details over generic gratitude. - One primary link (the best past piece); reply-friendly close. - Subject lines under 50 characters. </constraints> <format> Return the complete email as a copy-paste block (Subject / Preview / Body), then one line on how to turn the best-piece link into a lasting 'start here' anchor. </format>
Produces a voice-driven creator newsletter welcome that hooks readers with a best-of link, ready to send.
Pro tip: Ask Claude to end with a specific one-question reply prompt; replies train inbox providers that your list is engaged.
Ecommerce Welcome + First-Order Offer
5/30You are a retention marketer for a direct-to-consumer brand. <context> A shopper just subscribed for a first-order discount. I need a welcome email that delivers the code and drives a first purchase, built as one self-contained, responsive HTML email I can preview as an artifact. </context> <inputs> - Brand and product category: [NAME PLUS WHAT YOU SELL] - The welcome offer: [E.G. 10% OFF FIRST ORDER, CODE HELLO10] - Bestsellers to feature: [2-4 PRODUCTS] - Brand vibe and color: [DESCRIBE PLUS HEX] - Offer expiry: [E.G. 7 DAYS] </inputs> <task> Build the email: preheader, branded header, a warm welcome that presents the discount code prominently, a shop-now button, a 2-to-4 product grid of bestsellers with names and one-line hooks, a short brand-story or values strip to build trust, an expiry-driven urgency line, and a footer with unsubscribe. Make the code and CTA impossible to miss. </task> <constraints> - One self-contained HTML email, table layout, inline CSS. - The discount code and primary shop button are the dominant elements. - Labeled color-block placeholders for product images with alt text; real copy, no filler. </constraints> <format> Return the full HTML email as an artifact, then explain how you handled code visibility and urgency and what to test for first-order conversion. </format>
Builds an HTML ecommerce welcome email that delivers a first-order code and features bestsellers as a previewable artifact.
Pro tip: Set a real expiry in the inputs; a countable deadline in the copy lifts first-order conversion more than a bigger discount.
XML tags are just the start. Learn the full Claude workflow.
A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.
Weekly Digest Issues
5 promptsBlog / Content Weekly Digest
6/30You are a content marketer who turns the week's posts into an inbox-worthy digest. <context> I publish content and want a weekly digest that recaps it and drives clicks, delivered as a complete, ready-to-send issue. </context> <inputs> - Newsletter name and audience: [NAME PLUS WHO] - This week's items: [3-6 TITLES WITH ONE-LINE SUMMARY AND URL] - The single most important item: [WHICH ONE] - Voice: [SMART, CASUAL, EXPERT] - Optional footer CTA: [E.G. FOLLOW, REPLY, SHARE] </inputs> <task> Write the full digest: a subject line plus two alternates that tease the strongest item, preview text, a one-paragraph intro that frames the week, a lead story block with a compelling 2-3 sentence pitch and a read-more link, then the remaining items as a scannable list each with a title, one-line hook, and link, and a short sign-off with the footer CTA. </task> <constraints> - Lead with the strongest item, not the newest; every link has a reason to click. - Skimmable formatting; specific hooks, no "check out our latest post". - Subject lines under 55 characters. </constraints> <format> Return the complete digest as a copy-paste block (Subject / Preview / Body), then one line on how to reorder items by expected click-through. </format>
Produces a complete weekly content digest with a lead story and scannable link list, ready to send.
Pro tip: Tell Claude which item you most want clicked; it will give that one the lead-story treatment and demote the rest to the list.
Industry News Roundup Digest
7/30You are a newsletter editor who curates industry news into a signal-rich weekly briefing. <context> I curate the week's most important industry news. I need a complete digest issue that adds a point of view, not just links, delivered ready to send. </context> <inputs> - Newsletter name and industry: [NAME PLUS FIELD] - This week's stories: [4-6 HEADLINES WITH SOURCE, LINK, AND WHY IT MATTERS] - Audience and what they care about: [READER PROFILE] - My editorial angle or lens: [E.G. WHAT IT MEANS FOR OPERATORS] - Cadence and tone: [WEEKLY, ANALYTICAL] </inputs> <task> Write the full issue: a subject line plus two alternates, preview text, a sharp one-paragraph "the big thing this week" intro, then each story as a block with a headline, a two-sentence summary, a bolded "why it matters" take in my editorial voice, and a source link. Close with a one-line forward-looking note. Make the analysis the product, not the links. </task> <constraints> - Every story includes an original 'why it matters' take, not a rehashed summary. - Neutral on facts, opinionated on implications; cite each source. - Subject lines under 55 characters; skimmable blocks. </constraints> <format> Return the complete issue as a copy-paste block (Subject / Preview / Body), then one line on how to keep the 'why it matters' voice consistent week to week. </format>
Generates a curated industry news digest where each story carries an original 'why it matters' take, ready to send.
Pro tip: Feed Claude raw headlines plus your one-line reactions; it will polish them into the 'why it matters' takes that make people forward the issue.
SaaS Product Weekly Digest (HTML)
8/30You are a product marketer who writes the weekly customer digest for a SaaS app. <context> I send active users a weekly digest of what shipped, tips, and usage nudges. I need it built as one self-contained, responsive HTML email I can preview as an artifact. </context> <inputs> - Product name: [NAME] - What shipped this week: [1-3 UPDATES] - One power-user tip: [TIP] - A relevant resource or blog post: [TITLE PLUS URL] - Primary CTA: [E.G. TRY THE NEW FEATURE] - Brand color: [HEX] </inputs> <task> Build the email: preheader, branded header, a short intro, a "new this week" section listing updates with a one-line benefit each and a primary button to try the top one, a "tip of the week" block, a linked resource card, and a footer with help and unsubscribe links. Keep it useful enough that users open it every week. </task> <constraints> - One self-contained HTML email, table layout, inline CSS, one primary button. - Benefit-led feature copy (what the user can now do), not release-note jargon. - Accessible alt text; scannable sections. </constraints> <format> Return the full HTML email as an artifact, then explain how you ordered the sections for retention and what to A/B test in the subject. </format>
Builds a self-contained HTML SaaS weekly digest with updates, a tip, and a resource as a previewable artifact.
Pro tip: Have Claude phrase each update as 'you can now...' so the digest reads as user value, not an internal changelog.
Community Weekly Digest
9/30You are a community manager who writes an engaging weekly recap for members. <context> I run a community and send a weekly digest of highlights, discussions, and events. I need a complete issue that pulls members back in, delivered ready to send. </context> <inputs> - Community name and platform: [NAME PLUS WHERE] - Top discussions or wins this week: [3-5 ITEMS WITH LINKS] - Member spotlight: [NAME PLUS WHAT THEY DID] - Upcoming events: [EVENT PLUS DATE PLUS LINK] - A prompt or question to spark replies: [OPTIONAL] </inputs> <task> Write the full digest: a warm subject line plus two alternates, preview text, a friendly intro, a "top conversations" block linking the best threads with a one-line hook each, a member-spotlight block that celebrates a specific person, an "upcoming" events block with dates and links, and a closing discussion prompt that invites a reply or a post. Make members feel seen and give clear reasons to come back. </task> <constraints> - Celebrate specific people and threads by name; warm, inclusive tone. - Each link has a reason to click; one clear engagement prompt at the end. - Subject lines under 55 characters. </constraints> <format> Return the complete digest as a copy-paste block (Subject / Preview / Body), then one line on how to rotate the member spotlight fairly each week. </format>
Produces a warm community weekly digest with top threads, a member spotlight, and events, ready to send.
Pro tip: Give Claude one real member win with a name; a specific spotlight drives more re-engagement than a generic 'great week everyone'.
Internal Team Weekly Update
10/30You are a chief of staff who writes crisp internal weekly updates that people actually read. <context> I send a weekly internal newsletter to keep the team aligned. I need a complete issue that reports progress and priorities without becoming a wall of text, delivered ready to send. </context> <inputs> - Team or company name: [NAME] - Wins this week: [2-5 WITH OWNER PLUS METRIC IF ANY] - Priorities for next week: [2-4 ITEMS] - One key metric and its trend: [METRIC PLUS UP OR DOWN] - Shout-outs or new hires: [OPTIONAL] - One decision or ask needing attention: [OPTIONAL] </inputs> <task> Write the full update: a clear subject line with the week, a one-line TL;DR, a "wins this week" bulleted section with owners, a "focus next week" section, a metric-of-the-week callout with the number and trend, a shout-outs block, and a clearly flagged "needs your input" item if provided. Keep it scannable in under two minutes. </task> <constraints> - Lead with a one-line TL;DR; bullets over paragraphs. - Attribute wins to owners; flag any action item explicitly. - Plain, direct tone; no corporate filler. </constraints> <format> Return the complete update as a copy-paste block (Subject / TL;DR / Body), then one line on how to template it so it takes five minutes to fill each week. </format>
Generates a scannable internal team weekly update with wins, priorities, and a metric callout, ready to send.
Pro tip: Ask Claude to keep the TL;DR to one sentence; a skimmable top line is what gets a busy team to read the rest.
Product Update & Announcement Emails
5 promptsNew Feature Announcement (HTML)
11/30You are a product marketer who announces new features in a way that drives adoption. <context> We just shipped a new feature. I need an announcement email built as one self-contained, responsive HTML email I can preview as an artifact and paste into my ESP. </context> <inputs> - Feature name and what it does: [NAME PLUS ONE-LINER] - The problem it solves: [PAIN POINT] - Who it is most useful for: [SEGMENT] - How to start using it: [ACTION OR URL] - Brand color: [HEX] </inputs> <task> Build the email: preheader, branded header, a hero that names the feature and the outcome it unlocks, a short "the problem" and "now you can" before-and-after block, a three-point benefit list, a single primary button to try it, an optional short GIF or screenshot placeholder with caption, and a footer with docs link and unsubscribe. Sell the outcome, not the mechanics. </task> <constraints> - One self-contained HTML email, table layout, inline CSS, one primary button. - Lead with the user outcome; no hype words like 'game-changing'. - Accessible alt text on placeholders; benefit-led copy. </constraints> <format> Return the full HTML email as an artifact, then explain the before-and-after framing you used and what to test in the subject line for open rate. </format>
Builds an HTML new-feature announcement email framed around the outcome it unlocks as a previewable artifact.
Pro tip: Give Claude the exact task the feature makes faster; a concrete before-and-after beats a feature-name headline every time.
Monthly Changelog Newsletter
12/30You are a product communications writer who packages a month of shipping into a digestible update. <context> I send a monthly product update summarizing everything we shipped. I need a complete issue that groups changes clearly and highlights the big ones, delivered ready to send. </context> <inputs> - Product name and month: [NAME PLUS MONTH] - Headline features this month: [1-3 MAJOR] - Improvements: [LIST] - Bug fixes worth mentioning: [LIST] - Primary CTA: [E.G. SEE WHAT IS NEW] </inputs> <task> Write the full issue: a subject line plus two alternates, preview text, a one-paragraph intro on the month's theme, a "headline features" section where each major item gets a benefit-led paragraph and a link, an "improvements" bulleted section, a short "fixed" bulleted section, and a closing CTA. Make big items feel big and keep the rest scannable. </task> <constraints> - Group into headline features, improvements, and fixes; benefit-led on the majors. - Scannable bullets for minor items; specific, no vague 'various improvements'. - Subject lines under 55 characters. </constraints> <format> Return the complete issue as a copy-paste block (Subject / Preview / Body), then one line on how to keep this repeatable as a monthly template. </format>
Produces a monthly changelog newsletter grouped into headline features, improvements, and fixes, ready to send.
Pro tip: Tell Claude your single biggest ship of the month; it will give it a full paragraph while collapsing the rest into tidy bullets.
Beta / Early Access Invite
13/30You are a growth-focused product marketer inviting select users into a beta. <context> We are opening early access to something new and want engaged users to opt in. I need a complete invite email that makes the beta feel exclusive and worth the effort, delivered ready to send. </context> <inputs> - What the beta is: [FEATURE OR PRODUCT] - Why it is exciting: [THE BIG BENEFIT] - Who I am inviting and why them: [SEGMENT PLUS REASON] - What I need from them: [FEEDBACK, USAGE, SPOTS LIMITED] - How to join: [LINK OR ACTION] </inputs> <task> Write the full email: a subject line plus two alternates that signal exclusivity, preview text, a personal opener explaining why they specifically are invited, a short "here is what you get early" block, a clear "what we ask in return" expectation (feedback, a few minutes), a scarcity note if spots are limited, and a single join button. Make it feel like a genuine insider invite. </task> <constraints> - One CTA (join the beta); honest about what is unfinished. - Exclusive but sincere tone; set clear expectations on effort. - Subject lines under 50 characters. </constraints> <format> Return the complete email as a copy-paste block (Subject / Preview / Body / CTA), then one line on how to segment who receives this for the best beta signal. </format>
Generates a beta or early-access invite that frames exclusivity and sets clear expectations, ready to send.
Pro tip: Have Claude name the specific behavior that earned the invite ('you use X the most'); personalized reasons lift beta opt-in sharply.
Major Version / Relaunch Announcement
14/30You are a launch communications lead announcing a major version or brand relaunch. <context> We are shipping a major version (a big redesign or platform leap). I need a complete announcement email that conveys the magnitude and reassures existing users, delivered ready to send. </context> <inputs> - What the big release is: [VERSION OR RELAUNCH NAME] - The three biggest changes: [LIST] - What existing users need to know: [MIGRATION, WHAT STAYS THE SAME] - The primary CTA: [EXPLORE, UPGRADE, LOG IN] - Voice: [CONFIDENT, WARM] </inputs> <task> Write the full email: a bold subject line plus two alternates, preview text, a hero declaring what just launched and why it matters, a "what is new" section covering the three biggest changes with a benefit each, a reassurance block for existing users (what stays, any action needed), a single primary CTA, and a warm close. Convey momentum while keeping loyal users calm. </task> <constraints> - Balance excitement with reassurance; be explicit about any required action. - One primary CTA; concrete benefits, no vague 'better than ever'. - Subject lines under 55 characters. </constraints> <format> Return the complete email as a copy-paste block (Subject / Preview / Body / CTA), then one line on how to handle users who preferred the old version. </format>
Produces a major version or relaunch announcement that conveys scale while reassuring existing users, ready to send.
Pro tip: Ask Claude to add an explicit 'nothing you rely on is going away' line; it prevents the churn spike a big redesign can trigger.
Deprecation / Breaking-Change Notice
15/30You are a product communications specialist who writes clear, calm notices about changes users must act on. <context> We are deprecating something or shipping a breaking change and must notify affected users. I need a complete notice email that is unambiguous about what changes, when, and what to do, delivered ready to send. </context> <inputs> - What is changing or being removed: [FEATURE, API, PLAN] - Effective date: [DATE] - Who is affected: [SEGMENT] - What users must do: [ACTION STEPS] - Where to get help or docs: [LINK] </inputs> <task> Write the full email: a plain, specific subject line naming the change and date, preview text, a clear one-sentence summary of what is changing and when, a "who this affects" line, a numbered "what you need to do" action list with the deadline, a short "why we are doing this" note, and a help link with a support CTA. Prioritize clarity and calm over marketing. </task> <constraints> - Lead with the change and the date; unambiguous action steps. - No spin or upbeat filler; empathetic but direct. - Include the deadline in both the subject and the body. </constraints> <format> Return the complete email as a copy-paste block (Subject / Preview / Body), then one line on how to schedule reminder sends before the deadline. </format>
Generates a clear deprecation or breaking-change notice with dated action steps and a help link, ready to send.
Pro tip: Make Claude put the exact deadline in the subject line; action-required emails get ignored when the date is buried in the body.
Promotional & Offer Emails
5 promptsFlash Sale Email (HTML)
16/30You are a direct-response ecommerce email writer who drives urgency without cheapening the brand. <context> We are running a short flash sale. I need an email built as one self-contained, responsive HTML email I can preview as an artifact and paste into my ESP. </context> <inputs> - Brand and what you sell: [NAME PLUS CATEGORY] - The offer: [E.G. 30% OFF SITEWIDE, CODE FLASH30] - Duration: [START AND END, E.G. 48 HOURS] - Products or categories to feature: [2-4] - Brand color: [HEX] </inputs> <task> Build the email: preheader that states the offer and deadline, a bold branded header, a hero announcing the sale with the discount and a countdown-style deadline line, a prominent shop-now button and the code, a 2-to-4 product grid with names and one-line hooks, an urgency reminder band, and a footer with unsubscribe. Make the offer and deadline unmissable. </task> <constraints> - One self-contained HTML email, table layout, inline CSS, one primary button. - Offer, code, and end time are the dominant elements; honest scarcity only. - Labeled color-block image placeholders with alt text; punchy copy, no hype. </constraints> <format> Return the full HTML email as an artifact, then explain the urgency devices you used and what to test in the subject for open rate. </format>
Builds an HTML flash-sale email with prominent offer, code, and deadline as a previewable artifact.
Pro tip: Put the real end time in the preheader and subject; a concrete deadline outperforms a bigger discount with no urgency.
Seasonal / Holiday Promo
17/30You are a seasonal campaign copywriter who ties offers to the moment without cliches. <context> I am running a seasonal or holiday promotion. I need a complete promo email that feels timely and drives sales, delivered ready to send. </context> <inputs> - Brand and offer: [NAME PLUS DEAL] - The occasion: [E.G. BLACK FRIDAY, SUMMER, NEW YEAR] - Who it is for: [AUDIENCE] - Featured products or gift ideas: [LIST] - Deadline: [DATE] - Voice: [FESTIVE, PREMIUM, PLAYFUL] </inputs> <task> Write the full email: a subject line plus two alternates that tie to the occasion, preview text, a seasonally framed hero with the offer, a short reason-to-buy-now tied to the moment, a featured products or gift-guide block with names and hooks, a deadline-driven urgency line, and a shop CTA. Make it feel of-the-moment without leaning on tired holiday cliches. </task> <constraints> - Tie the offer to the occasion authentically; avoid overused holiday phrasing. - One primary CTA; clear deadline; specific product hooks. - Subject lines under 55 characters. </constraints> <format> Return the complete email as a copy-paste block (Subject / Preview / Body / CTA), then one line on how to adapt it into a 3-email holiday sequence. </format>
Produces a timely seasonal or holiday promo email tied authentically to the occasion, ready to send.
Pro tip: Tell Claude the emotion of the season (cozy, celebratory, fresh-start) so the copy leans on feeling rather than clip-art cliches.
Loyalty Offer for Existing Customers
18/30You are a retention marketer who rewards existing customers to drive repeat purchases. <context> I want to reward current customers with an exclusive offer and make them feel valued. I need a complete email that reads as a thank-you, not a generic blast, delivered ready to send. </context> <inputs> - Brand and relationship: [NAME PLUS WHAT THEY BOUGHT BEFORE] - The exclusive offer: [E.G. VIP EARLY ACCESS, LOYALTY DISCOUNT, CODE] - Why they are getting it: [LOYALTY, ANNIVERSARY, MILESTONE] - What to feature: [PRODUCTS, NEW ARRIVALS, REPLENISHMENT] - Deadline: [DATE] </inputs> <task> Write the full email: a subject line plus two alternates that signal exclusivity, preview text, a warm thank-you opener that acknowledges the relationship, the exclusive offer presented as a reward, a featured products block relevant to a repeat buyer, an expiry note, and a shop CTA. Make loyalty feel recognized, not transactional. </task> <constraints> - Frame the offer as a reward for loyalty, not a public sale. - Reference their history where possible; one clear CTA and deadline. - Subject lines under 55 characters. </constraints> <format> Return the complete email as a copy-paste block (Subject / Preview / Body / CTA), then one line on how to segment this for highest-value customers. </format>
Generates a loyalty reward email that thanks existing customers and drives a repeat purchase, ready to send.
Pro tip: Ask Claude to reference what they bought before; a personalized 'because you loved X' reads far warmer than a blanket VIP code.
Bundle / Upsell Offer
19/30You are a monetization-focused copywriter who sells bundles by anchoring value. <context> I want to promote a bundle or upsell offer that raises average order value. I need a complete email that makes the bundle feel like an obvious deal, delivered ready to send. </context> <inputs> - Brand and the bundle: [NAME PLUS WHAT IS IN IT] - Individual value vs bundle price: [PRICES] - Who benefits most: [AUDIENCE] - The core outcome of the bundle: [WHAT THEY ACHIEVE TOGETHER] - Deadline or stock limit: [OPTIONAL] </inputs> <task> Write the full email: a subject line plus two alternates leading with the savings, preview text, a hero framing the bundle and the outcome it delivers, a clear value-anchor block showing individual prices crossed against the bundle price and the total saved, a "what is included" list with a one-line benefit each, a scarcity or deadline note if provided, and a get-the-bundle CTA. Make the math for buying obvious. </task> <constraints> - Show the value anchor (individual total vs bundle price) explicitly. - One primary CTA; benefit per item, not just names. - Subject lines under 55 characters. </constraints> <format> Return the complete email as a copy-paste block (Subject / Preview / Body / CTA), then one line on where to place the price anchor for maximum effect. </format>
Produces a bundle or upsell email that anchors value and makes the savings obvious, ready to send.
Pro tip: Give Claude the individual prices; a visible 'worth $X, yours for $Y' anchor sells bundles better than the discount percentage alone.
Webinar / Event Promo
20/30You are an event marketer who fills seats with a single well-structured email. <context> I am promoting a webinar or live event and need registrations. I need a complete promo email that sells the value of attending and drives signups, delivered ready to send. </context> <inputs> - Event name and format: [NAME PLUS WEBINAR OR LIVE] - Date, time, timezone: [WHEN] - The promise: [WHAT ATTENDEES WILL LEARN OR GET] - Speaker or host: [NAME PLUS CREDIBILITY] - Who should attend: [AUDIENCE] - Register link: [URL] </inputs> <task> Write the full email: a subject line plus two alternates leading with the benefit of attending, preview text, a hero with the event name, date, time, and a register CTA, a "what you will walk away with" three-point block, a short speaker credibility line, a "who this is for" note, an urgency line (limited seats or replay policy), and a final register CTA. Sell the outcome of showing up, not just the topic. </task> <constraints> - Date, time, and timezone unmissable; register CTA repeated top and bottom. - Lead with attendee outcomes, not the agenda; specific benefits. - Subject lines under 55 characters. </constraints> <format> Return the complete email as a copy-paste block (Subject / Preview / Body / CTA), then one line on how to turn this into a reminder email 24 hours before. </format>
Generates a webinar or event promo email that sells the value of attending and drives registrations, ready to send.
Pro tip: Have Claude phrase the three points as takeaways ('leave knowing how to...'); outcome bullets convert better than an agenda list.
Curated Roundup Issues
5 prompts"Links We Loved" Roundup
21/30You are a curation-savvy newsletter writer who turns a pile of links into a must-read roundup. <context> I curate the best links of the week for my readers. I need a complete roundup issue with a distinct voice around each pick, delivered ready to send. </context> <inputs> - Newsletter name and audience: [NAME PLUS WHO] - This week's links: [5-8 WITH TITLE, URL, AND WHY I PICKED IT] - My voice: [WITTY, EXPERT, CASUAL] - Optional theme tying them together: [OPTIONAL] </inputs> <task> Write the full roundup: a subject line plus two alternates, preview text, a short intro that sets the week's theme or mood, then each link as a compact block with a punchy title, a one-to-two sentence take in my voice on why it is worth their time, and the link. Vary the openers so it does not read like a template, and close with a light sign-off. </task> <constraints> - Each pick gets an original, specific reason to click, not a copied description. - Vary sentence openers; consistent voice throughout. - Subject lines under 55 characters. </constraints> <format> Return the complete roundup as a copy-paste block (Subject / Preview / Body), then one line on how to order picks by likely click-through. </format>
Produces a curated 'links we loved' roundup with an original take on each pick, ready to send.
Pro tip: Give Claude your raw one-line reactions to each link; it sharpens them into voice-y takes instead of bland summaries.
Tool / Product Roundup
22/30You are a product-savvy curator who reviews tools for a practical audience. <context> I curate useful tools for my readers. I need a complete roundup issue that helps them decide what to try, delivered ready to send. </context> <inputs> - Newsletter name and niche: [NAME PLUS FIELD] - Tools this issue: [4-6 WITH NAME, WHAT IT DOES, PRICE, AND LINK] - Audience and their goal: [WHO PLUS WHAT THEY NEED] - My honest take on each: [ONE LINE PER TOOL] </inputs> <task> Write the full roundup: a subject line plus two alternates, preview text, a short intro on the theme (e.g. tools for X), then each tool as a block with its name, a one-line "what it does", a "best for" line, price, my honest take (including any caveat), and a link. Close with a one-line "my pick this week". Be genuinely useful and a little opinionated. </task> <constraints> - Include a 'best for' and an honest take with caveats, not just praise. - Consistent block structure for scannability; name a single top pick. - Subject lines under 55 characters. </constraints> <format> Return the complete roundup as a copy-paste block (Subject / Preview / Body), then one line on how to disclose affiliate links if any are used. </format>
Generates a tool roundup issue with a 'best for', honest take, and top pick for each tool, ready to send.
Pro tip: Ask Claude to include one caveat per tool; honest downsides build the trust that makes readers act on your recommendations.
Best-of-the-Month Roundup
23/30You are an editor who compiles a monthly greatest-hits issue that re-surfaces top content. <context> At month end I send a best-of issue recapping the top pieces and moments. I need a complete issue that gives lapsed readers a reason to catch up, delivered ready to send. </context> <inputs> - Newsletter name and audience: [NAME PLUS WHO] - Top-performing pieces this month: [3-5 WITH TITLE, URL, AND WHY IT LANDED] - One overlooked gem worth resurfacing: [TITLE PLUS URL] - A stat or milestone from the month: [OPTIONAL] - Voice: [DESCRIBE] </inputs> <task> Write the full issue: a subject line plus two alternates framed as a monthly recap, preview text, a short intro noting the month's theme or a milestone, a ranked "most-read this month" list each with a title, one-line hook, and link, a "one you might have missed" spotlight for the overlooked gem, and a forward-looking closing line teasing next month. Make it a satisfying catch-up in two minutes. </task> <constraints> - Rank by performance; give the overlooked gem its own spotlight. - Each item has a fresh hook, not the original headline reused verbatim. - Subject lines under 55 characters. </constraints> <format> Return the complete issue as a copy-paste block (Subject / Preview / Body), then one line on how to reuse this as evergreen 'start here' content. </format>
Produces a best-of-the-month roundup that ranks top pieces and resurfaces an overlooked gem, ready to send.
Pro tip: Tell Claude which piece underperformed but deserved more; the 'one you missed' spotlight is what makes best-of issues feel curated.
Reading List / Resource Roundup
24/30You are a knowledge curator who assembles themed reading and resource lists. <context> I want to send a themed reading list or resource roundup on a single topic. I need a complete issue that positions me as a helpful guide, delivered ready to send. </context> <inputs> - Newsletter name and audience: [NAME PLUS WHO] - The theme: [TOPIC, E.G. LEARNING SQL, HIRING WELL] - Resources: [5-8 WITH TITLE, TYPE (ARTICLE, BOOK, VIDEO, TOOL), URL] - Skill level: [BEGINNER, INTERMEDIATE, ADVANCED] - Voice: [DESCRIBE] </inputs> <task> Write the full issue: a subject line plus two alternates naming the theme and payoff, preview text, a short intro on why this topic matters now, then the resources grouped or sequenced (e.g. start here, go deeper, tools) each with a title, type tag, a one-line reason it earns a spot, and a link, and a closing suggestion for how to actually use the list. Make it a genuine learning path, not a link dump. </task> <constraints> - Sequence or group resources into a real path (start here, go deeper). - One-line justification per resource; note the type of each. - Subject lines under 55 characters. </constraints> <format> Return the complete issue as a copy-paste block (Subject / Preview / Body), then one line on how to expand this into a multi-part series. </format>
Generates a themed reading-list roundup sequenced as a real learning path with justified picks, ready to send.
Pro tip: Ask Claude to order resources 'start here to advanced'; a sequenced path gets saved and reshared far more than a flat list.
Community Highlights Roundup
25/30You are a community editor who spotlights the best member content in a recurring roundup. <context> I want to showcase what members created, shared, or achieved this period. I need a complete highlights issue that celebrates members and drives engagement, delivered ready to send. </context> <inputs> - Community or brand name: [NAME] - Member highlights: [4-6 WITH MEMBER NAME, WHAT THEY DID, AND LINK] - A featured question or debate: [OPTIONAL] - A call to submit for next time: [WHAT YOU WANT] - Voice: [DESCRIBE] </inputs> <task> Write the full issue: a warm subject line plus two alternates, preview text, a short celebratory intro, a "member highlights" section where each entry names the member, describes what they did in one or two sentences, and links to it, an optional "question of the week" or debate block, and a clear closing call to submit work for the next roundup. Make members want to be featured next time. </task> <constraints> - Credit members by name; specific, generous descriptions. - One clear submit CTA at the end; warm, inclusive tone. - Subject lines under 55 characters. </constraints> <format> Return the complete issue as a copy-paste block (Subject / Preview / Body), then one line on how to source highlights each period without manual digging. </format>
Produces a community highlights roundup that credits members by name and invites next-round submissions, ready to send.
Pro tip: End with a specific submission prompt ('reply with what you shipped'); a clear ask turns a one-off roundup into a self-feeding series.
Most people use 10% of Claude. Tutorials unlock the rest.
AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.
Re-Engagement & Win-Back Emails
5 prompts"We Miss You" Win-Back
26/30You are a lifecycle marketer who writes win-back emails that feel personal, not desperate. <context> Some subscribers have gone quiet. I need a complete win-back email that reminds them why they joined and invites them back, delivered ready to send. </context> <inputs> - Brand or newsletter name: [NAME] - What they get from us: [CORE VALUE] - How long they have been inactive: [TIMEFRAME] - The best reason to come back now: [NEW THING, BEST CONTENT, OFFER] - Primary CTA: [READ, SHOP, LOG IN] </inputs> <task> Write the full email: a subject line plus two alternates that gently acknowledge the absence, preview text, a warm opener that reminds them of the value without guilt-tripping, a "here is what you have missed" highlight of the single best reason to return, a clear one-action CTA, and a low-pressure close. Keep it human and genuinely inviting. </task> <constraints> - No guilt or desperation; warm and confident tone. - One clear CTA; lead with the strongest reason to return. - Subject lines under 50 characters. </constraints> <format> Return the complete email as a copy-paste block (Subject / Preview / Body / CTA), then one line on how to trigger this by inactivity window. </format>
Produces a personal 'we miss you' win-back email that reminds subscribers of the value, ready to send.
Pro tip: Give Claude the single best thing they missed; one strong reason to return beats a laundry list of everything they skipped.
Re-Engagement With Incentive (HTML)
27/30You are a retention marketer running a re-engagement campaign with an incentive. <context> I want to win back inactive subscribers or lapsed customers with an offer. I need an email built as one self-contained, responsive HTML email I can preview as an artifact. </context> <inputs> - Brand and what you offer: [NAME PLUS CATEGORY] - The incentive: [E.G. 20% OFF, FREE MONTH, CODE COMEBACK] - Why they should return now: [WHAT IS NEW OR IMPROVED] - What to feature: [PRODUCTS, CONTENT, FEATURES] - Deadline: [DATE] - Brand color: [HEX] </inputs> <task> Build the email: preheader that hints at the offer, branded header, a warm "it has been a while" hero that presents the incentive as a welcome-back gift, a short "here is what is new since you left" block, a primary button to redeem, a featured items grid, a deadline-driven urgency line, and a footer with unsubscribe. Make returning feel rewarding and easy. </task> <constraints> - One self-contained HTML email, table layout, inline CSS, one primary button. - Frame the incentive as a welcome-back, not a fire sale; clear deadline. - Accessible alt text; specific copy, no guilt. </constraints> <format> Return the full HTML email as an artifact, then explain how you balanced incentive and 'what is new' and what to test in the subject. </format>
Builds an HTML re-engagement email pairing a welcome-back incentive with what's new as a previewable artifact.
Pro tip: Pair the offer with one concrete 'what changed since you left'; a reason plus an incentive wins back more than a discount alone.
Churned Customer Win-Back
28/30You are a retention specialist who wins back customers who cancelled or lapsed. <context> A customer cancelled or let their subscription lapse. I need a complete win-back email that addresses why they may have left and gives a compelling reason to return, delivered ready to send. </context> <inputs> - Product name: [NAME] - What they had before: [PLAN OR PRODUCT] - Common reasons people leave: [PRICE, MISSING FEATURE, TIME] - What has changed or improved since: [IMPROVEMENTS, NEW FEATURES] - The win-back offer: [E.G. DISCOUNTED RETURN, EXTENDED TRIAL] - Reactivate link: [URL] </inputs> <task> Write the full email: a subject line plus two alternates, preview text, an empathetic opener that acknowledges they left without pressure, a "here is what is better now" block that directly answers the likely reasons for churning, the win-back offer framed as a low-risk way to try again, a single reactivate CTA, and a genuine close. Sound like a company that listened, not one that is begging. </task> <constraints> - Address the likely churn reason directly; empathetic, not defensive. - One reactivate CTA; make returning low-risk. - Subject lines under 50 characters. </constraints> <format> Return the complete email as a copy-paste block (Subject / Preview / Body / CTA), then one line on how to personalize this by cancellation reason if you have it. </format>
Generates a churned-customer win-back email that addresses the likely reason for leaving and offers a low-risk return, ready to send.
Pro tip: Tell Claude the top cancellation reason; an email that names and resolves it converts far better than a generic 'come back' offer.
Sunset / Confirm-Opt-In Email
29/30You are a deliverability-minded email marketer running a list-cleaning sunset flow. <context> Before removing inactive subscribers, I want to send a final "are you still interested?" email to keep the engaged ones and clean the rest. I need a complete email that protects sender reputation, delivered ready to send. </context> <inputs> - Newsletter or brand name: [NAME] - What they get by staying: [CORE VALUE] - The action to stay subscribed: [CLICK TO CONFIRM OR UPDATE PREFERENCES] - What happens if they do nothing: [E.G. REMOVED IN 14 DAYS] - Optional preference options: [FREQUENCY OR TOPICS] </inputs> <task> Write the full email: a direct subject line plus two alternates that pose the stay-or-go question, preview text, a short honest opener explaining you noticed they have not engaged and want to respect their inbox, a clear single "yes, keep me subscribed" confirm CTA, an optional "or update how often you hear from us" link, and a plain statement that no action means removal by a date. Keep it respectful and reputation-protecting. </task> <constraints> - Honest and respectful; one primary confirm action. - State the consequence of inaction and the date clearly. - Subject lines under 50 characters. </constraints> <format> Return the complete email as a copy-paste block (Subject / Preview / Body / CTA), then one line on the ideal send count and spacing for a sunset flow. </format>
Produces a respectful sunset opt-in email that retains engaged subscribers and cleans the rest, ready to send.
Pro tip: Have Claude state the removal date plainly; the small consequence is exactly what nudges dormant-but-interested readers to click confirm.
Re-Onboarding After a Long Gap
30/30You are a lifecycle marketer who re-onboards users returning after a long absence. <context> A user is coming back after a long time away and the product has changed. I need a complete re-onboarding email that catches them up and points them to value fast, delivered ready to send. </context> <inputs> - Product name: [NAME] - How long they have been away: [TIMEFRAME] - The biggest changes since: [2-4 UPDATES] - The one action that recreates value fastest: [KEY ACTION] - Help or docs link: [URL] </inputs> <task> Write the full email: a warm subject line plus two alternates welcoming them back, preview text, a friendly "welcome back, here is what changed" opener, a short "what is new since you were last here" list with a benefit each, a single primary CTA to the fastest path back to value, a reassurance that their data or account is intact if relevant, and a help link. Make returning feel effortless, not like starting over. </task> <constraints> - Summarize changes as benefits; one primary CTA to fastest value. - Reassure about continuity (data, account) where relevant. - Subject lines under 50 characters. </constraints> <format> Return the complete email as a copy-paste block (Subject / Preview / Body / CTA), then one line on how to trigger this on a returning-user login. </format>
Generates a re-onboarding email that catches returning users up on changes and routes them to fast value, ready to send.
Pro tip: Point the single CTA at the fastest path back to value, not the homepage; returning users churn again when they have to re-figure everything out.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.