AI-Powered Product Launch & Feature Announcement Email Intelligence Engine prompt
You are a senior product marketing copywriter who has launched 50+ SaaS products and features.
by AICMO·Apache-2.0 license·GitHub ↗
Use now
Inside this prompt
prompt text · the author's own wordsYou are a senior product marketing copywriter who has launched 50+ SaaS products and features. Write a complete email announcement sequence… LAUNCH CONTEXT: - Product/Feature name: [Name of what you're launching] - What it does: [One sentence — the job it does for users] - Who benefits most: [Primary user persona — e.g., "Revenue Operations managers at B2B SaaS companies"] - The core problem it solves: [Pain state before this existed] - The measurable outcome: [What users can now achieve — e.g., "reduce reporting time by 4 hours/week"] - Availability: [GA / Beta / Early Access / Paid add-on / Included in all plans] - Key proof point: [1 stat, customer quote, or benchmark — e.g., "Beta users saved 3.2 hours per week on average"] Write a 3-email launch sequence for these two segments: SEGMENT A — EXISTING ACTIVE CUSTOMERS (already using the product) Email 1 — Launch Day Announcement - Subject line (+ 2 A/B variants)
Word-for-word excerpt, not a result. Read the full prompt ↓
| 1 | You are a senior product marketing copywriter who has launched 50+ SaaS products and features. Write a complete email announcement sequence for my product launch. |
| 2 | |
| 3 | LAUNCH CONTEXT: |
| 4 | - Product/Feature name: [Name of what you're launching] |
| 5 | - What it does: [One sentence — the job it does for users] |
| 6 | - Who benefits most: [Primary user persona — e.g., "Revenue Operations managers at B2B SaaS companies"] |
| 7 | - The core problem it solves: [Pain state before this existed] |
| 8 | - The measurable outcome: [What users can now achieve — e.g., "reduce reporting time by 4 hours/week"] |
| 9 | - Availability: [GA / Beta / Early Access / Paid add-on / Included in all plans] |
| 10 | - Key proof point: [1 stat, customer quote, or benchmark — e.g., "Beta users saved 3.2 hours per week on average"] |
| 11 | |
| 12 | Write a 3-email launch sequence for these two segments: |
| 13 | |
| 14 | SEGMENT A — EXISTING ACTIVE CUSTOMERS (already using the product) |
| 15 | Email 1 — Launch Day Announcement |
| 16 | - Subject line (+ 2 A/B variants) |
| 17 | - Preview text (under 90 characters) |
| 18 | - Full email body (250–350 words): Lead with the outcome, not the feature. Use Before/After/Bridge structure. One primary CTA. |
| 19 | - CTA: [Action that gets them to the feature — e.g., "Try it now", "See it in action", "Upgrade to unlock"] |
| 20 | |
| 21 | Email 2 — Follow-Up: Value Deepening (send Day 3 to non-openers and non-clickers) |
| 22 | - Different angle: lead with a specific use case or customer story |
| 23 | - Show the workflow, not just the feature |
| 24 | - Secondary CTA option if primary CTA wasn't taken |
| 25 | |
| 26 | Email 3 — Final Push (send Day 7 to non-converters) |
| 27 | - Urgency or social proof angle: "Here's what early adopters are saying" |
| 28 | - Remove friction: anticipate the #1 objection |
| 29 | - Soft deadline if applicable (beta seats, early pricing) |
| 30 | |
| 31 | SEGMENT B — PROSPECTS / FREE TIER USERS (haven't purchased yet) |
| 32 | Email 1 — Launch as conversion hook |
| 33 | - Lead with aspiration: "This is what [Persona] can now do with [Product]" |
| 34 | - Feature as proof of product trajectory and investment |
| 35 | - CTA leads to trial activation or demo booking, not just feature page |
| 36 | |
| 37 | For each email provide: |
| 38 | - Subject line with emotional or curiosity hook |
| 39 | - Preview text optimized for mobile |
| 40 | - Opening line that passes the "delete test" (would a busy VP read past line 1?) |
| 41 | - Full body copy with proper paragraph breaks |
| 42 | - PS line (drives 10–30% of clicks) |
| 43 | - Suppression logic: who should NOT receive each email |
Discussion
Alternatives
/bragTurn the current project website into a short, polished, shareable launch video using Hyperframes. Use when someone says "/brag", "let's brag about this", "make a launch video", "turn this into a video", or wants to share what they built. Reads the project code directly — no live URL or screenshots needed./brag-slimTurn a project directory or a website URL into a short, shareable launch video with music, motion, and share copy. One file, no bundled assets — built entirely by the model with the tools already on the machine. Use when someone says "/brag-slim", "let's /brag about this", "brag about <url>", "make a launch video", or wants to show off what they built. If the /brag skill is also installed, let /brag handle those phrases; it hands off here on Opus 5.5.Business motion filmPlan, build and quality-check a premium short commercial for a real business (roofing, property, ecommerce, B2B software) using AI-generated footage, code-built motion (HTML/GSAP), selective Three.js and an independent-critic "Gauntlet" loop. Use when asked to make a launch-style / SaaS-style video, business ad, explainer, sample reel or pitch video, or to review and improve one. Encodes motion principles distilled from 28 professional launch films, a quality bar, audio rules and a business-offer playbook.AI Product Launch PlaybookLaunch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.
Browse more free AI prompts or everything in Product.