Claude Prompts for Product Managers: Write Feature Announcement Emails

You are an expert SaaS product marketing email specialist with 11 years of experience writing feature announcement emails that convert passive users into active adopters of new functionality. Help me generate personalized email templates so I can reduce time writing emails and increase the percentage of existing customers who try and retain new product features within 30 days of launch. My situation: - Product and feature being announced: [e.g., "a project management SaaS — announcing a new AI-powered task prioritization feature that automatically reorders a user's task list based on deadline proximity and dependency chains"] - Target user segment for this announcement: [e.g., "power users — customers who log in at least 4 times per week and have more than 50 active tasks — approximately 8,200 contacts out of a 42,000-contact customer base"] - Feature adoption goal and timeline: [e.g., "30% of power users activate the feature within 14 days of the announcement email — activation is defined as enabling the feature and allowing it to reorder their task list at least once"] - Current product email performance: [e.g., "previous feature announcement emails average 38% open rate and 11% click-to-activation rate — the product team wants to improve click-to-activation to 18% for this launch"] - Key objection or adoption barrier: [e.g., "power users have a high-effort investment in their current manual task ordering system — the primary adoption barrier is fear that the AI will disrupt a workflow they have spent time building"] - Email platform: [e.g., "Intercom — can personalize with first name, company name, current task count, and last login date"] - Brand voice and constraints: [e.g., "direct, confident, and product-focused — no hype language, no vague AI claims, no phrases like 'game-changing' or 'revolutionary'"] Deliver: 1. A two-email announcement sequence — email 1 sent on launch day and email 2 sent on day 7 for non-activators — with email 1 focused on the problem the feature solves for high-task-volume users and email 2 focused on a specific use case walkthrough for users who opened but did not activate 2. Three subject line variants for each email — one direct-benefit, one curiosity-gap, and one social proof framing — with a recommendation on which to use as the default for a power user segment and the rationale 3. A personalization strategy using Intercom data fields — how to use the contact's current task count to make the feature benefit feel personally relevant, with two example personalized sentences for users with 50-100 tasks versus users with 100+ tasks 4. An objection handling insert — a two-sentence block that can be inserted into the email body to directly address the fear of AI disrupting a manual workflow, written in plain product language without making promises the feature cannot keep 5. An in-email activation CTA framework — three CTA variants tested across different email positions (above the fold, mid-body, and end of email) with a recommendation on the single best placement for a feature that requires a multi-step in-app activation 6. A non-opener reactivation strategy — a push notification or in-app message brief for users who did not open either email in the sequence, covering the message format, the timing relative to the email sequence, and the single CTA that bridges from passive notification to active feature trial 7. A 30-day adoption tracking report template — a weekly snapshot the product manager sends to the team covering activation rate, retention rate at day 7 and day 14, and the top three support queries generated by the feature, identifying whether the adoption barrier is awareness, intent, or friction in the activation flow **Write every email as if the reader is a power user who has been burned before by a software update that changed a workflow they relied on — acknowledge the risk of change directly, demonstrate the feature's value with a concrete example drawn from the product's own use case, and make the CTA feel like a controlled experiment rather than a permanent commitment.**