Product update email template
Telling users what changed and why it matters to them.
A product update should describe changes as benefits to the reader, not as a changelog. Lead with the one change most people will notice, and put the rest in a short list. Version numbers belong at the bottom, if at all.
At a glance
| Use it when | Shipping changes users will notice |
|---|---|
| Length | 120 to 200 words |
| Tone | Plain, no hype |
| Ask for | Nothing, or a single link to the detail |
The template
Subject lines that work with it
- What's new in [product]
- [Product]: [the single biggest change]
- [Product] update - [month]
How to write this email well
- Lead with the change most people asked for. Burying it under smaller items reads as tone deaf.
- Write each item as what the reader can now do, not what you built.
- Say what you fixed as well as what you added. It builds more trust than the features.
Questions
How often should I send product updates?
When there is something worth a users attention. Monthly is a reasonable ceiling, and silence is better than filler.
Should I list every change?
No. Three to five that matter, with a link to the full notes for anyone who wants them.
Do version numbers belong in the subject line?
Rarely. Users recognise what changed, not which release it was.
More announcements templates
Announcements
Company news
A milestone, hire or change worth telling people about.
Announcements
Policy or terms change
Notifying people about changes they may not welcome.
Use this template in Gmail
Copy the HTML above and paste it into Mailplate, the free Gmail extension that inlines the CSS so the layout survives sending. Or edit the wording directly in the preview and insert it into your message.
See Mailplate