Prompt · Product launch
Feature launch email for existing users
Get existing users to try the feature once.
- Email type
- Product launch
- Business
- SaaS
- Tone
- Professional
- Length
- 110-160 words
The product launch email prompt
Write a plain-text feature announcement from [PRODUCT] to existing users about [THE FEATURE]. Words only — no HTML, no layout notes. The single action this email drives: trying the feature once. Rules: - 110 to 160 words. - Open on [THE OLD PAIN], not on the feature. One or two sentences naming the workaround people have been living with. A reader who does not recognise the problem has no reason to read about the solution. - Then say what shipped, in one sentence, in the words a user would use. Not the internal name, not the version number. - Say exactly where to find it: [WHERE TO FIND IT]. A path, not a vague location. This is the line that decides whether anyone actually tries it. - One ask, written as an ordinary sentence with the link inside it. - Do not tease what is coming next. Do not thank anyone for their patience. Do not describe the engineering. - Never invent a number, statistic, time saving, adoption figure or customer count. Where a figure belongs and I have not supplied it, leave [XX]. - No exclamation marks. No emoji. Sentence case. Write a subject line under 45 characters describing what the user can now do, not what we built. Return subject, preheader, body, sign-off.
What to fill in first
[PRODUCT]- What you build, in the words a customer would use.
[THE FEATURE]- What shipped, named the way a user would describe it rather than the internal name.
[THE OLD PAIN]- What people did before. Name the workaround. This is what makes the feature legible.
[WHERE TO FIND IT]- The actual path. "Settings, then Imports" beats "in your dashboard".
[XX]- Leave as written. The placeholder for a figure you supply, never one the model supplies.
When to send it
On release day, once the feature is on for everyone receiving the email. A launch email that lands before the rollout finishes generates support tickets from the people most inclined to try things, which is exactly the wrong group to disappoint.
What to change first
[THE OLD PAIN]. Feature emails fail by describing the feature to people who never articulated the
problem it solves. Naming the workaround — the spreadsheet, the copy-paste, the thing everyone does
twice — is what makes the reader recognise themselves and read the next sentence.
What good output looks like
Subject: Bulk edit is finally here
Preheader: Settings, then Imports. It works on anything you can filter.
Changing a field across two hundred records has meant opening two hundred records. Most people gave up and did it in a spreadsheet, then re-imported, which broke the links.
You can now select a filtered set and edit any field across all of it at once.
It is under Settings, then Imports, on the same screen you already use for uploads.
Try it on something small first.
The prompt writes the words. Bring them here and the studio builds the campaign — branded, dark-mode safe, and ready to import.
Generate your ownIn the studio
A model writes copy. It does not write email.
Production HTML that survives Outlook, dark mode and a Gmail clip is a different job from writing the words. Describe the send once and export it to Mailchimp, Klaviyo, ActiveCampaign or MailerLite.