Claude Prompt Library

20 Claude Prompts for Emails People Actually Open

20 copy-paste prompts

XML-structured prompts built for how Claude writes email copy. Subject lines, welcome sequences, re-engagement campaigns, and A/B variants — all with Claude-native formatting.

Subject Lines & Preview Text

4 prompts

Subject Line Generator

1/20

<context> I'm an email marketer at [COMPANY NAME] in the [INDUSTRY] space. Our audience is [DESCRIBE TARGET AUDIENCE]. Our average open rate is [CURRENT OPEN RATE]. The email platform we use is [PLATFORM]. </context> <task> Generate 10 subject lines for a [CAMPAIGN TYPE — e.g. product launch, seasonal sale, webinar invite, content roundup] email. For each subject line provide: 1. The subject line (under 50 characters) 2. A matching preview text (under 90 characters) that extends the curiosity without repeating the subject 3. The psychological trigger it uses (curiosity, urgency, social proof, self-interest, fear of missing out) 4. A predicted open-rate impact vs. our baseline (higher/neutral/risky) </task> <constraints> - No ALL CAPS or excessive punctuation - No spam trigger words: "free," "act now," "limited time," "congratulations" - At least 3 subject lines should be under 35 characters (optimized for mobile) - Include at least one question-based subject line and one number-based subject line - Don't start more than 2 subject lines with the same word </constraints> <format> Return as a numbered list. Each entry: Subject Line | Preview Text | Trigger | Predicted Impact </format>

Generates 10 subject lines with matching preview text, psychological triggers, and predicted performance.

💡

Pro tip: Save your brand voice and past winning subject lines in a Claude Project — Claude will learn your style and generate lines that match your tone over time.

Preview Text Optimizer

2/20

<context> I have a batch of emails going out this week and need to optimize the preview text for each. Our audience is [DESCRIBE AUDIENCE]. Our brand tone is [DESCRIBE TONE]. </context> <task> For each subject line below, write 3 preview text options that: 1. Complement the subject line without repeating it 2. Create enough curiosity to earn the open 3. Work on mobile (under 90 characters, ideally under 60) Subject lines: 1. [SUBJECT LINE 1] 2. [SUBJECT LINE 2] 3. [SUBJECT LINE 3] </task> <constraints> - Preview text must make sense even when truncated at 40 characters - Never start preview text with "Hey" or "Hi [name]" — that wastes prime real estate - Each option should use a different technique: (a) tease the content, (b) add a benefit, (c) create urgency </constraints>

Creates three distinct preview text options per subject line, each using a different persuasion technique.

💡

Pro tip: Use Claude's artifacts feature to get each subject-line group as a separate output — makes it easy to share options with your team.

Re-Engagement Subject Lines

3/20

<context> We have a segment of [NUMBER] subscribers who haven't opened an email in [TIMEFRAME]. These subscribers originally signed up via [SIGNUP SOURCE]. Our product/service is [DESCRIBE OFFERING]. Previous re-engagement attempts used subject lines like: "[PASTE 2-3 PREVIOUS SUBJECT LINES]." </context> <task> Write a 3-email re-engagement sequence, providing for each email: 1. Subject line (under 45 characters) 2. Preview text 3. The emotional angle (nostalgia, curiosity, loss aversion, fresh start, humor) 4. Recommended send timing relative to the previous email The sequence should escalate: Email 1 = soft re-engagement, Email 2 = value-driven nudge, Email 3 = last-chance before removal. </task> <constraints> - Don't guilt-trip ("We miss you" is overused — avoid it) - Don't use subject lines similar to our previous failed attempts listed above - Email 3 must clearly communicate "we'll remove you" without sounding threatening </constraints>

Builds a 3-email re-engagement sequence with escalating urgency, designed to avoid the cliches that inactive subscribers ignore.

💡

Pro tip: Turn on extended thinking — Claude will reason through what makes inactive subscribers ignore emails before generating alternatives.

Personalized Subject Line Formulas

4/20

<context> I want to build a reusable subject line formula library for my team at [COMPANY]. We send [TYPES OF EMAILS]. Our subscribers expect a [DESCRIBE TONE] tone. Our ESP supports these personalization tokens: [LIST TOKENS — e.g. first_name, company_name, last_purchase_item]. </context> <task> Create 15 subject line formulas my team can reuse. For each formula: 1. The formula template with merge tag placeholders shown in {{double_braces}} 2. A concrete example filled in for our business 3. Best use case (which email type it works for) 4. One thing that would make it fail (the anti-pattern) </task> <constraints> - At least 5 formulas should use personalization tokens beyond just {{first_name}} - Organize into 3 groups: Curiosity-Driven, Benefit-Driven, Urgency-Driven - No formula should require data we don't have - Flag any formula that risks looking spammy if the personalization fails </constraints>

Builds a reusable subject line formula library your whole team can reference, with merge tags, examples, and failure modes.

💡

Pro tip: Save the output as project knowledge in Claude Projects — then whenever you ask Claude to write a subject line, it can pull from your own proven formulas.

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.

Start 14-Day Free Trial

Email Sequences

4 prompts

Welcome Sequence Architect

5/20

<context> I'm building a welcome email sequence for [COMPANY NAME]. We sell [PRODUCT/SERVICE]. New subscribers come from [SIGNUP SOURCE]. Our goal for the welcome sequence is [GOAL]. Our brand voice is [DESCRIBE VOICE]. </context> <task> Design a 5-email welcome sequence. For each email, provide: 1. Email number and send timing (e.g. "Email 2 — Day 2, 10am") 2. Subject line and preview text 3. Email purpose (one sentence) 4. Full body copy (150-250 words) 5. Primary CTA (button text + destination) 6. What to track (the metric that tells you this email is working) </task> <constraints> - Email 1 must deliver any promised lead magnet or confirm the signup within 30 seconds of the trigger - Don't ask for a sale in Emails 1-2 — build trust and deliver value first - Email 3 should include social proof - Each email must work as a standalone - Total sequence should span 7-10 days </constraints>

Designs a complete 5-email welcome sequence with body copy, CTAs, timing, and tracking metrics.

💡

Pro tip: Paste your existing welcome email as context and ask Claude to compare it against the generated sequence — it will identify specific gaps.

Abandoned Cart Recovery Sequence

6/20

<context> I run email marketing for [ECOMMERCE BRAND]. Our average cart value is [AMOUNT]. Our current cart abandonment rate is [RATE]. We sell [PRODUCT TYPE]. Our existing recovery email has a [CURRENT RECOVERY RATE] conversion rate. </context> <task> Build a 3-email abandoned cart sequence with two variants: - Variant A: For first-time visitors (no purchase history) - Variant B: For returning customers (1+ previous purchases) For each email in both variants, provide: 1. Send timing (hours after abandonment) 2. Subject line and preview text 3. Full email body copy (100-200 words) 4. Whether to show the cart items inline 5. Whether to include a discount and at what level 6. CTA button text </task> <constraints> - Never lead with a discount in Email 1 — try value and urgency first - Variant B should acknowledge the relationship - If offering a discount, only in Email 3 and frame it as exclusive - Don't use "You forgot something!" — it's overused and condescending </constraints>

Creates a full abandoned cart sequence with separate paths for new visitors and returning customers.

💡

Pro tip: Use extended thinking to have Claude reason through your specific product's purchase objections before writing the copy.

Product Launch Email Sequence

7/20

<context> We're launching [NEW PRODUCT/FEATURE] on [LAUNCH DATE]. Target audience: [DESCRIBE SEGMENT]. Price point: [PRICE]. The key differentiator is [DIFFERENTIATOR]. We have [LIST SIZE] subscribers with [OPEN RATE] open rates. </context> <task> Create a 4-email launch sequence: - Email 1: Teaser/anticipation builder (sent before launch) - Email 2: Launch day announcement - Email 3: Social proof and deeper dive (Day 2-3 after launch) - Email 4: Last chance / urgency closer (Day 5-7 after launch) For each email provide: 1. Subject line and preview text 2. Full email body (200-300 words) 3. Primary CTA 4. One visual/design suggestion 5. Segment exclusion rule (who should NOT get this email) </task> <constraints> - The teaser email must NOT reveal the full product — create genuine curiosity - Launch email should lead with the customer's problem, not features - Urgency closer must use real scarcity, not manufactured deadlines - No email should exceed 300 words </constraints>

Plans a 4-email product launch sequence from teaser to urgency closer, with copy, CTAs, and design direction.

💡

Pro tip: Create a Claude Project for your launch and add your product brief and customer testimonials as project knowledge.

Post-Purchase Nurture Sequence

8/20

<context> I need a post-purchase email sequence for [COMPANY]. After buying [PRODUCT/SERVICE], customers typically [DESCRIBE USAGE PATTERN]. Our repeat purchase rate is [RATE] and average time to second purchase is [TIMEFRAME]. Our customer support sees the most tickets about [COMMON ISSUE]. We also sell [COMPLEMENTARY PRODUCTS]. </context> <task> Design a 5-email post-purchase sequence: 1. Order confirmation + what to expect next 2. Getting started / best practices (Day 2-3) 3. Check-in + handle the #1 support question proactively (Day 7) 4. Request a review or testimonial (Day 14) 5. Cross-sell recommendation (Day 21) For each email provide: - Subject line and preview text - Body copy (100-200 words) - CTA - Conditional logic: when should this email be suppressed </task> <constraints> - Email 1 must arrive within 5 minutes of purchase - Don't cross-sell before Email 5 - The review request should make it easy (direct link, no login required) - If the customer has opened a support ticket, pause the sequence - Tone should feel like a helpful person, not a marketing machine </constraints>

Builds a 5-email post-purchase flow from confirmation to cross-sell, with suppression logic and proactive support.

💡

Pro tip: Ask Claude to output each email as a separate artifact — you can edit and export them directly into your ESP.

Email Body Copy

4 prompts

Newsletter Content Writer

9/20

<context> I write a [FREQUENCY] newsletter called "[NEWSLETTER NAME]" for [AUDIENCE]. The newsletter covers [TOPICS]. Our tone is [DESCRIBE TONE]. Average read time: [X minutes]. We have [SUBSCRIBER COUNT] subscribers with a [OPEN RATE] open rate. </context> <task> Write the complete next edition of my newsletter on the topic: [THIS WEEK'S TOPIC OR THEME]. Include: 1. A subject line and preview text 2. A compelling opening hook (2-3 sentences) 3. The main body content in our usual format 4. 1 actionable takeaway the reader can implement today 5. A closing CTA that drives [DESIRED ACTION] </task> <constraints> - Total word count: [TARGET WORD COUNT] - Write in first person — this should sound like me - The opening must NOT start with "In today's newsletter" or "This week" - Include at least one specific data point, example, or anecdote - Break up text with subheadings every 150 words max </constraints>

Writes a complete newsletter edition in your voice and format, with a hook, body, takeaway, and CTA.

💡

Pro tip: Paste 2-3 of your previous newsletters into a Claude Project — Claude will match your writing voice much more accurately than any style description.

Promotional Email Copywriter

10/20

<context> I need to write a promotional email for [COMPANY]. We're promoting [OFFER]. The offer runs from [START DATE] to [END DATE]. Target segment: [DESCRIBE SEGMENT]. The landing page URL is [URL]. </context> <task> Write a complete promotional email with: 1. Subject line (under 45 characters) + preview text 2. Hero headline 3. Body copy following the PAS framework: Problem → Agitation → Solution 4. Offer details section (clear, scannable) 5. Primary CTA button text (under 5 words) 6. Objection handler (one line addressing the #1 reason people don't convert) 7. P.S. line with a secondary angle </task> <constraints> - Total email body under 200 words - The CTA should appear twice: once after the offer, once at the bottom - Don't bury the offer — clear within the first 3 lines - Use specific numbers over vague claims - The P.S. should feel like a personal aside </constraints>

Writes a complete promotional email using the PAS framework with scannable offer details and a dual-CTA structure.

💡

Pro tip: Ask Claude to generate 3 versions with different emotional angles — then A/B test the best two.

Storytelling Email

11/20

<context> I want to write a story-driven email for [COMPANY/BRAND]. Our product is [PRODUCT/SERVICE]. The audience is [DESCRIBE AUDIENCE]. The email's goal is [GOAL]. I want to tell a story about [STORY SEED]. </context> <task> Write a narrative email that: 1. Opens with a scene or moment (not a summary) 2. Builds tension or curiosity in the middle 3. Resolves with an insight that connects to our product/value 4. Closes with a CTA that feels like a natural next step Also provide subject line and preview text. </task> <constraints> - Use the "But and Therefore" story structure - The product mention should occupy no more than 20% of the email - Write at a 7th-grade reading level - The story must be about a PERSON, not an abstraction - Total length: 250-400 words - No bullet points — this is a narrative </constraints>

Crafts a narrative email that hooks with a story and naturally connects to your product without feeling salesy.

💡

Pro tip: Use extended thinking and ask Claude to develop 3 story angles first, then pick the best one to write.

Social Proof Email

12/20

<context> I need a social-proof-driven email for [COMPANY]. We have the following proof assets: - Customer testimonials: [PASTE 2-3 TESTIMONIALS or describe them] - Key metrics: [e.g. "10,000+ customers," "4.8/5 rating"] - Case study data: [e.g. "Customer X increased revenue by 35% in 60 days"] Our goal is to [GOAL]. </context> <task> Write a social proof email that: 1. Opens with a relatable pain point 2. Introduces proof from someone like them 3. Presents the transformation with specific numbers 4. Stacks 2-3 additional proof points for reinforcement 5. Closes with a CTA that leverages "join the crowd" psychology Provide subject line and preview text. </task> <constraints> - The lead testimonial must match the target segment - Numbers must be presented in context - Don't just list testimonials — weave them into a narrative - The CTA should name-check the social proof - Under 250 words </constraints>

Writes a proof-stacking email that weaves testimonials, metrics, and case studies into a persuasive narrative.

💡

Pro tip: Store your best testimonials in a Claude Project — then any email prompt you run will automatically pull in relevant social proof.

These prompts give you the what. Tutorials give you the why.

Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.

Try AI Academy Free

Segmentation & Personalization

4 prompts

Segment-Specific Email Variants

13/20

<context> I have a core email written for [CAMPAIGN PURPOSE]. I need to create variants for different audience segments: 1. [SEGMENT 1 — e.g. Enterprise, 1000+ employees] 2. [SEGMENT 2 — e.g. SMB owners, 10-50 employees] 3. [SEGMENT 3 — e.g. Solopreneurs] 4. [SEGMENT 4 — e.g. Technical users / developers] Our product: [PRODUCT/SERVICE]. The core message: [ONE-SENTENCE CORE MESSAGE]. </context> <task> Create 4 tailored variants — one per segment. For each variant, adjust: 1. Subject line (speak to their specific pain) 2. Opening line (reference their world) 3. Value proposition framing (same product, different benefit emphasis) 4. Social proof (choose proof that matches their context) 5. CTA text and urgency framing Also create a comparison table showing what changed and why. </task> <constraints> - The core message must stay the same — only the framing changes - Each variant should feel like it was written from scratch, not find-and-replaced - Enterprise variant should mention ROI and stakeholder alignment - Solopreneur variant should emphasize speed and simplicity </constraints> Here's the core email: [PASTE YOUR BASE EMAIL]

Transforms one email into 4 segment-specific variants with tailored subject lines, framing, proof, and CTAs.

💡

Pro tip: Ask Claude to output the comparison table as one artifact and each variant separately — makes team review and ESP upload faster.

Behavioral Trigger Email Writer

14/20

<context> I'm setting up behavioral trigger emails for [COMPANY/PRODUCT]. Our key user actions are: - [TRIGGER 1 — e.g. signed up but didn't complete onboarding] - [TRIGGER 2 — e.g. viewed pricing page 3+ times] - [TRIGGER 3 — e.g. used feature X for the first time] - [TRIGGER 4 — e.g. hasn't logged in for 14 days] - [TRIGGER 5 — e.g. reached a usage milestone] Our automation tool is [PLATFORM]. </context> <task> For each behavioral trigger, write: 1. The trigger condition (exact logic) 2. Send delay (how long after the trigger) 3. Subject line and preview text 4. Email body copy (100-150 words) 5. CTA that matches the user's current intent 6. Suppression rules (when NOT to send) </task> <constraints> - Each email must reference the specific action - Milestone emails should celebrate, not sell - Pricing-page emails must address objections - Inactivity emails should offer value, not guilt - No email should fire if another triggered email was sent within 48 hours </constraints>

Designs 5 behavioral trigger emails with automation logic, send timing, copy, and suppression rules.

💡

Pro tip: Use a Claude Project to store your product's feature list and user journey — trigger emails need deep product context to feel personal.

Win-Back Campaign for Churned Users

15/20

<context> We need to win back customers who cancelled [PRODUCT/SERVICE] in the last [TIMEFRAME]. Their most common cancellation reasons: 1. [REASON 1] 2. [REASON 2] 3. [REASON 3] Since they left, we've [LIST IMPROVEMENTS]. </context> <task> Create a 3-email win-back campaign: - Email 1: Address the #1 churn reason with proof that it's been fixed - Email 2: Address reasons #2 and #3 with a "here's what's new" angle - Email 3: Final offer with a specific incentive to return For each email provide: 1. Subject line + preview text 2. Body copy (150-200 words) 3. The specific churn objection it addresses 4. CTA 5. Win-back offer if applicable </task> <constraints> - Never pretend the churn didn't happen — acknowledge it - Don't be needy — be confident about improvements - Email 1 should not include any discount - The win-back offer in Email 3 should have a real expiration - If they churned due to price, offer a reduced tier, not a temporary discount </constraints>

Builds a 3-email win-back campaign that addresses real churn reasons with product improvements and strategic offers.

💡

Pro tip: Turn on extended thinking — Claude will map each churn reason to the right messaging strategy before writing.

Lifecycle Email Mapping

16/20

<context> I need to map out the full email lifecycle for [COMPANY/PRODUCT]. Our customer journey stages: 1. Awareness: [HOW THEY FIND US] 2. Consideration: [WHAT THEY EVALUATE] 3. Purchase: [HOW THEY BUY] 4. Onboarding: [FIRST 30 DAYS] 5. Retention: [ONGOING USAGE] 6. Expansion: [UPSELL OPPORTUNITIES] 7. Advocacy: [REFERRALS AND REVIEWS] We currently cover stages: [LIST WHICH]. We're missing: [LIST GAPS]. </context> <task> Create a complete lifecycle email map. For each stage: 1. Number of emails needed 2. Trigger or timing for each email 3. Purpose (one sentence) 4. Subject line 5. Priority level (build first / nice-to-have / advanced) 6. Key metric to track Then create an implementation roadmap prioritized by revenue impact. </task> <constraints> - Total lifecycle should not exceed 25 emails - Don't recommend emails for stages we've already covered well - Prioritize revenue-generating emails over nice-to-haves - Each email must have a single, clear purpose - The roadmap must be actionable for a team of [TEAM SIZE] </constraints> <format> Return as a table grouped by stage, followed by a prioritized implementation roadmap. </format>

Maps your entire customer lifecycle into a prioritized email plan with triggers, purposes, and an implementation roadmap.

💡

Pro tip: Save this lifecycle map as project knowledge — then every future email prompt will understand where it fits in the bigger picture.

Analytics & Optimization

4 prompts

Email Performance Diagnosis

17/20

<context> I need help diagnosing why our email performance is declining: Campaign: [CAMPAIGN NAME] - Open rate: [RATE] (was [PREVIOUS RATE]) - Click rate: [RATE] (was [PREVIOUS RATE]) - Unsubscribe rate: [RATE] (was [PREVIOUS RATE]) - List size: [SIZE] (was [PREVIOUS SIZE]) - Send frequency: [FREQUENCY] - ESP: [PLATFORM] Recent changes: [LIST ANY CHANGES] </context> <task> Analyze these metrics and provide: 1. Primary diagnosis: What's most likely causing the decline 2. Supporting evidence: Which metric combinations point to this diagnosis 3. Three hypotheses ranked by likelihood 4. A 2-week fix plan with testable actions 5. Metrics I should start tracking that I'm probably not </task> <constraints> - Diagnose based on the specific numbers, not generic advice - If open rates dropped but click rates held, that's different than both dropping — be precise - The fix plan must be testable within 2 weeks - Account for external factors (Gmail changes, iOS privacy, seasonal patterns) </constraints>

Diagnoses declining email performance with specific root causes, ranked hypotheses, and a 2-week action plan.

💡

Pro tip: Paste your last 10 subject lines and their open rates — Claude will spot patterns in what works and what doesn't.

A/B Test Plan Generator

18/20

<context> I want to run A/B tests on our email program to improve [PRIMARY METRIC]. Our current baseline is [VALUE]. We send [VOLUME] emails per [PERIOD] to [LIST SIZE] subscribers. Our ESP supports [LIST TEST CAPABILITIES]. We've previously tested: [LIST PAST TESTS]. </context> <task> Create a 4-week A/B testing roadmap. For each week: 1. What to test (the specific variable) 2. Hypothesis (why you think this will win) 3. Control vs. variant description 4. Sample size needed for 95% confidence 5. How long to run before calling a winner 6. How the result feeds into the next test </task> <constraints> - Only test one variable at a time - Don't recommend testing something I've already tested - Week 1 should test the highest-impact, easiest variable - Include minimum sample size calculations - Each test should build on the previous week's findings </constraints> <format> Weekly calendar with each test specified, plus a summary table. </format>

Creates a 4-week A/B testing roadmap with hypotheses, sample sizes, and sequential learning.

💡

Pro tip: After running each test, paste results back into the same Claude Project — Claude will adjust the remaining plan based on actual data.

List Cleaning Strategy

19/20

<context> Our email list health needs attention: - Total list size: [SIZE] - Estimated inactive (no open in 90+ days): [NUMBER] - Bounce rate: [RATE] - Spam complaint rate: [RATE] - ESP: [PLATFORM] - Double opt-in: [YES/NO] - Last list clean: [DATE OR "NEVER"] </context> <task> Create a list cleaning and deliverability plan: 1. Immediate actions (this week) to stop active damage 2. A 30-day re-engagement → sunset flow with exact criteria 3. Ongoing hygiene rules to prevent future decay 4. Technical checklist: SPF, DKIM, DMARC setup 5. Metrics dashboard: what to monitor weekly and action thresholds </task> <constraints> - Don't just say "delete inactive" — provide a re-engagement attempt first - The sunset flow must have clear exit criteria - Technical recommendations should be specific to [ESP] - Include the math: projected impact on open rate and deliverability - Frame list reduction in terms of revenue impact, not vanity metrics </constraints>

Builds a complete list hygiene plan with re-engagement flows, sunset policies, and technical checks.

💡

Pro tip: Provide your current revenue-per-email and Claude will calculate the dollar impact of cleaning your list.

Competitor Email Teardown

20/20

<context> I want to analyze competitors' email strategies. I've subscribed to: 1. [COMPETITOR 1] — [positioning] 2. [COMPETITOR 2] — [positioning] 3. [COMPETITOR 3] — [positioning] Our company positions as [OUR POSITIONING]. Our email weakness is [WHAT WE WANT TO IMPROVE]. </context> <task> I'm pasting competitor emails below. For each email, analyze: 1. Subject line effectiveness (score 1-10) 2. Opening hook technique 3. Copy structure (AIDA, PAS, storytelling, etc.) 4. CTA strategy (placement, text, urgency) 5. What they do better than us 6. What we could steal and adapt Synthesis: - Top 3 tactics we should adopt - 1 thing no competitor is doing that we could own - A specific email we should write this week (full draft) </task> <constraints> - Be honest about what's good — don't criticize just because they're competitors - "Steal and adapt" means adapt to our voice - Score subject lines based on our audience - Focus analysis on our stated weakness </constraints> Competitor emails: [PASTE COMPETITOR EMAILS HERE]

Tears down competitor emails with scoring, structural analysis, and tactics you should adopt.

💡

Pro tip: Paste full HTML or plain text — Claude can analyze design structure, CTA placement, and copy patterns all at once.

Frequently Asked Questions

Claude was trained to recognize XML tags as structural boundaries. When you separate your background info from your instructions and rules, Claude produces more focused output. For email marketing, this means Claude won't confuse your brand context with the copy it writes, and it will respect word count limits and formatting rules more consistently.
Yes. Describe your tone in the <context> tag, or better yet, save 3-5 examples of your best emails as project knowledge in a Claude Project. Claude learns your patterns, sentence length, vocabulary, and humor style from examples far better than from descriptions.
Claude Sonnet is the best choice for most email work — it balances speed and quality. Use Claude Opus for high-stakes emails like product launches, investor updates, or win-back campaigns where nuance matters. Claude Haiku works well for bulk tasks like generating subject line variations.
Ask Claude to generate multiple variants in one prompt by specifying different emotional angles or frameworks. For example: "Write version A using a curiosity hook and version B using a pain-point hook." Then test these in your ESP and feed winning variants back into your Claude Project.

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.

14-day free trial. Cancel anytime.