Product launch email prompt

When to use it

Use this prompt when drafting an announcement email for a new feature or standalone product. It helps email marketers produce focused, conversion-oriented copy without making unsubstantiated product claims or using generic launch clichés.

The prompt

## Role
Act as an email copywriter specializing in product marketing and lifecycle campaigns. Apply professional judgment while keeping your reasoning clear, practical, and accessible.

## Context
KiteMetrics is releasing Automated Churn Alerts, an add-on for B2B SaaS operations teams. It monitors account usage drops, flags renewal risks 60 days in advance, and pushes notifications directly to Slack or email. Pricing is $49 per month as an add-on to any existing KiteMetrics subscription, with a 30-day money-back guarantee. No public case studies or retention lift benchmarks exist yet.

## Objective
Write an announcement email to existing KiteMetrics account owners that explains the new add-on, frames the operational problem of late churn discovery, and drives activation of a 14-day free add-on trial.

## Audience
The primary readers are operations managers and customer success leads at growing software companies. Keep the copy focused on day-to-day workflow improvements rather than abstract executive metrics.

## Requirements
Provide 3 subject line options (under 50 characters each) with preview text; a concise body under 250 words; a bulleted breakdown of the 3 core capabilities; a single primary call to action; and a secondary link to the setup documentation. Include a post-draft claim audit listing any statement that requires verification by the product team.

## Constraints
Do not invent third-party integrations beyond Slack and email. Do not cite percentage reductions in churn, customer testimonials, or enterprise security tiers. Base all copy strictly on the provided feature set.

## Tone & style
Direct, functional, and respectful of the reader's time. Use short sentences, clear transitions, and conversational phrasing. Avoid hype words like "game-changer," "revolutionary," or "seamless."

## Output format
Deliver the subject lines and preview text first, followed by the complete email draft. Follow the email with a separate verification table comparing claims made against the provided context.

## What to avoid
Avoid vague buzzwords, artificial urgency, passive voice, and unearned statistical guarantees.

## Success criteria
An account owner immediately understands what the add-on monitors, how notifications are delivered, how much it costs after the trial, and where to click to enable it.

## Clarifying questions
If any critical parameters are missing, proceed using standard B2B SaaS onboarding assumptions, list them clearly, and state up to three specific questions for the user to confirm.

Why it works

• The scenario gives the model a clear product scope, specific integration limits, and confirmed pricing rather than open-ended parameters.
• The requirements restrict the email length and specify structural elements like character limits and secondary links.
• The constraints explicitly prohibit unsupported churn reduction claims, preventing misleading marketing copy.
• The success criteria give the reviewer a fast checklist to verify utility and accuracy before sending.

Make it yours

Build a tailored version with PromptDeck by replacing the fictional scenario with your own context, audience, and constraints. Keep the verification steps so the final result reflects what you actually know.