Verified against ChatGPT · 2026-08-13
Write a product launch email that leads with what's actually new, not generic launch-day hype
Drafts a launch announcement email built around the one specific thing that changed for the reader, avoiding stock launch-day phrasing that could describe almost any product release.
The prompt
Ready to copy — highlighted parts are example details you can swap.
You are writing the primary launch announcement email for something we're releasing today.
WHAT'S LAUNCHING
Real-time collaborative editing in the reporting tool — up to 5 people can edit the same report simultaneously, changes sync in under a second.
WHO THIS EMAIL GOES TO
Users on the Team plan who have created at least 3 reports in the last 60 days — the people who'd actually feel this pain.
THE SPECIFIC PROBLEM THIS SOLVES FOR THEM
Previously only one person could edit a report at a time, so teams were emailing screenshots back and forth to coordinate changes.
WHAT'S NOT INCLUDED (LIMITATIONS)
Doesn't support offline editing yet — all collaborators need an active connection.
Before writing the email, state in one sentence what a recipient in this segment could not do yesterday that they can do today because of this launch — if you can't state that concretely from the launch details given, ask me for the missing specific rather than writing a vaguer version of the email around the gap. Lead the email with that one sentence, or a sharper rewrite of it, rather than opening with "We're excited to announce" or any equivalent stock opener — the reader should understand what changed for them inside the first line, not after a paragraph of preamble. Mention the known limitations plainly, in one short line, rather than omitting them — a launch email that oversells by silence creates support tickets and trust erosion the moment someone hits the limitation themselves; frame the limitation factually, not apologetically. Write toward the recipient segment specifically named above, not a generic "valued customer" — if the segment has a distinguishing trait (existing users of a specific feature, people who previously asked for this exact thing, a specific plan tier), the email should read differently than it would to a segment without that trait.
WHAT NOT TO DO
Do not use superlatives ("game-changing," "revolutionary," "the future of X") anywhere in the copy. Do not include more than one call to action — a launch email exists to drive one action, typically try it or read more, not multiple competing links.
OUTPUT FORMAT
1. The one-sentence "what changed" statement, or the specific question needed if it can't be stated concretely.
2. Subject line.
3. Full email body.
4. The limitation line as it appears in the email, isolated for review.Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
GPT-5.1's default register for "write a launch email" pulls heavily from a training-data cluster of generic SaaS launch copy — "We're thrilled to announce," "game-changing," "the wait is over" — because that phrasing appears across thousands of real launch emails regardless of what actually launched, making it the model's path of least resistance unless explicitly blocked. Forcing the one-sentence "what changed yesterday versus today" statement as a mandatory first step, with permission to ask for a missing specific rather than writing around the gap, prevents the model from doing what it does by default when given thin launch details: smoothing an underspecified feature description into confident, generic excitement that describes the launch category rather than this specific launch. That one sentence, required to lead the email, structurally displaces the stock opener because there's no room left for both. Requiring the known limitation to appear plainly, not hedged or omitted, counters GPT-5.1's tendency toward maximally positive framing in promotional copy — left to its own judgment about tone, the model treats omitting a limitation as consistent with an upbeat launch voice, when in practice silently omitting it just moves the disappointment to the moment a customer discovers the gap themselves, at a worse time than in the announcement. Naming the recipient segment's distinguishing trait and requiring the copy to reflect it addresses the model's default fallback to "valued customer" framing whenever a segment is named generically — the specific trait (existing feature usage, prior request) is exactly the detail that makes a launch email read as relevant rather than mass-blasted, and GPT-5.1 will not surface that distinction on its own unless told the trait exists and must show up in the copy.
What you get back
What changed: "Teams on this plan can now edit the same report together in real time instead of emailing screenshots back and forth." Subject: "No more screenshot-emailing your report edits". Limitation line: "Heads up — this needs an active connection for now; offline editing isn't supported yet."
Verified against
ChatGPT GPT-5.1 · 2026-08-13
Changelog
- 2026-08-13 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
