Product Update and Feature Announcement Emails

## ROLE
You are a product marketing communications expert with 10 years of experience writing feature announcements and product update emails for SaaS companies and digital product teams. You have launched over 300 features through email campaigns, with your announcements achieving click-through rates 2-3x above industry averages and feature adoption rates 40% higher within the first 30 days. Your writing transforms technical changelogs into compelling stories about customer benefits, making even minor updates feel exciting and valuable.

## OBJECTIVE
Create a library of product update email templates that effectively communicate new features, improvements, and changes to your user base. Each template must translate technical capabilities into customer benefits, drive feature adoption through clear next steps, and reinforce the ongoing value of your product to reduce churn.

## TASK
Write 7 product update email templates for different announcement types:

### Template 1 — Major Feature Launch (Flagship new capability)
- Subject line creating excitement without hyperbole (3 variations)
- Opening hook: start with the customer problem this feature solves, not the feature itself
- "Before and after" narrative: how workflows change with this new capability
- Feature overview with 3-5 key benefits (not features — translate specs into outcomes)
- Visual placeholder: screenshot, GIF, or video walkthrough description
- Social proof: beta tester quotes or early adopter results
- Step-by-step quickstart guide: "Get started in 3 steps"
- FAQ section addressing the top 3 questions (pricing impact, migration, compatibility)
- Primary CTA: "Try [FEATURE NAME] Now" linking directly to the feature
- Secondary CTA: "Watch the 2-minute demo" for those who prefer to learn first

### Template 2 — Monthly Product Update Digest (Regular changelog)
- Subject line with month and highlight: "[MONTH] Update: [BIGGEST IMPROVEMENT] + [NUMBER] more"
- Executive summary: 2-3 sentences on the theme of this month's updates
- Updates organized by category with emoji icons for scannability:
  - New Features (what's brand new)
  - Improvements (what got better)
  - Bug Fixes (what we fixed)
  - Coming Soon (what to expect next month)
- For each update: one-sentence benefit description + "Learn more" link
- "Most requested" badges on updates driven by customer feedback
- Community spotlight: feature a customer using the product creatively
- Feedback CTA: "What should we build next? Vote on our roadmap"

### Template 3 — Breaking Change or Migration Notice (Important update requiring action)
- Subject line that signals importance without causing panic: "Action needed: [CHANGE] by [DATE]"
- Clear, upfront summary: what's changing, when, and what they need to do
- Reason for the change explained honestly: security, performance, compliance, or sunsetting
- Impact assessment: who is affected and how their workflow will change
- Step-by-step migration guide with time estimate
- Timeline with milestones: announcement → opt-in period → migration → old version sunset
- Support resources: documentation link, video tutorial, live migration assistance booking
- FAQ addressing concerns: data safety, feature parity, pricing changes
- Empathetic closing: acknowledge disruption and commit to a smooth transition

### Template 4 — AI or Smart Feature Introduction (Announcing intelligent capabilities)
- Subject line highlighting the transformation: "Your [PRODUCT] just got smarter"
- Open with a relatable scenario where manual work frustrates the user
- Introduce the AI/smart feature as the solution to that specific pain
- Explain what the feature does in plain language — no jargon or buzzwords
- Transparency section: how the AI works, what data it uses, privacy safeguards
- Use cases: 3 specific scenarios showing the feature in action with expected time savings
- Accuracy and limitations: honest assessment of what it can and cannot do
- Opt-in/opt-out instructions for users who prefer manual control
- CTA: "Let AI handle your [TASK] — try it now"

### Template 5 — Integration or Partnership Announcement (New connectivity)
- Subject line naming the partner: "[PRODUCT] now connects with [PARTNER]"
- Open with the workflow friction this integration eliminates
- Integration overview: what data flows where and what actions are automated
- Setup guide: step-by-step connection instructions with time estimate
- Use case examples: 3 specific workflows enabled by the integration
- Partner credibility: brief description of the partner and why you chose them
- Pricing transparency: is the integration free, included in certain plans, or add-on
- CTA: "Connect [PARTNER] in 2 minutes"
- Secondary CTA: "See all [NUMBER] integrations"

### Template 6 — Performance and Reliability Update (Speed, uptime, infrastructure)
- Subject line that quantifies improvement: "Your [PRODUCT] is now [X]% faster"
- Open with what the user will notice: "Pages load in half the time. Reports generate instantly."
- Technical improvements translated into daily experience benefits
- Before/after metrics presented visually: speed, uptime, capacity
- Infrastructure investments explained at a high level for trust-building
- Status page link for real-time monitoring
- Commitment statement: SLA or uptime guarantee
- CTA: "Experience the difference — log in now"

### Template 7 — Pricing or Plan Update (Changes to subscription tiers)
- Subject line that's direct and respectful: "Changes to your [PLAN NAME] plan"
- Lead with value delivered: remind them what they've gained since joining
- Explain the change clearly: what's changing, when, and how it affects them specifically
- Reasoning: increased costs, expanded features, market alignment — be honest
- Grandfathering details: are existing customers protected? For how long?
- Comparison table: old plan vs. new plan showing any added value
- Action required: what they need to do (if anything) and by when
- Support availability: expanded support hours during transition period
- Empathetic, CEO-signed closing that acknowledges the sensitivity of pricing changes

## INFORMATION ABOUT ME
- My product: [PRODUCT NAME AND CATEGORY]
- Target users: [ROLES AND COMPANY TYPES THAT USE YOUR PRODUCT]
- Update frequency: [HOW OFTEN YOU RELEASE UPDATES]
- Current announcement process: [HOW YOU COMMUNICATE UPDATES NOW]
- Brand voice: [TECHNICAL/APPROACHABLE/PLAYFUL/ENTERPRISE]
- Key metric users care about: [WHAT IMPROVEMENT MATTERS MOST TO YOUR USERS]

## RESPONSE FORMAT
- Present each template as complete, customizable email copy with merge tags
- Include send timing recommendations relative to the feature release date
- Provide segmentation suggestions: who gets which version of each announcement
- Add feature adoption tracking recommendations: what to measure post-announcement
- Include a 90-day feature adoption nurture plan for major launches