Copyable template
Subject: New in [Product Name]: [Concrete capability in 4 to 7 words] Hi [First Name], You can now [core action the feature enables] directly inside [Product Name]. Why we built this: Until today, [describe the clunky workaround users had to do]. Several of you wrote in asking for a faster way to handle [specific workflow], so we built [Feature Name] to cut that step out. How to try it in under [time estimate]: 1. Open [exact page or tab inside the app]. 2. Click [button or toggle label] and choose [key option]. 3. [Immediate visible result the user sees]. A quick note on availability: [Feature Name] is included on [plan names] starting today. [Optional short note on limits, docs link, or beta status]. Try it now: [Direct deep link into the app or short changelog post] Hit reply if anything feels rough or if you run into an edge case. I read every reply. [Your Name] Founder, [Product Name]
When to use this template
Send a standalone feature email only when a release meaningfully changes a user's weekly workflow, removes a common blocker, or answers a top customer request. Minor bug fixes and UI polish belong in your changelog rather than everyone's inbox.
Ship the feature to production at least a few hours before sending the email, verify the onboarding path on a fresh account, and link straight to the exact settings screen or documentation page where users can turn it on.
How to fill each placeholder
- [Concrete capability in 4 to 7 words]: Lead the subject line with what the user can do now, such as 'Retry failed webhooks automatically', rather than 'Exciting Q4 product update'.
- [describe the clunky workaround]: Mirror the exact friction users complained about in support tickets so they immediately recognize the problem as theirs.
- [exact page or tab inside the app]: Give the literal navigation path so readers do not land on your dashboard wondering where the new button lives.
- [plan names]: State clearly whether the feature is free for all accounts or restricted to a higher tier so nobody clicks through only to hit an unexpected paywall.
- [Direct deep link]: Link directly to the screen or a 45-second GIF walkthrough rather than your marketing homepage.
Filled example (made-up product)
Example using a made-up scheduled webhook runner called CrateCron: Subject: New in CrateCron: Automatic retries with exponential backoff Hi Sam, You can now turn on automatic retries for any failing webhook job directly inside CrateCron. Why we built this: Until today, a brief timeout on your receiving server meant a missed run until you spotted the alert and clicked replay by hand. Plenty of you asked for hands-free recovery during deploy windows, so we shipped configurable retry rules. How to try it in under two minutes: 1. Open any job in your CrateCron dashboard and click the Delivery tab. 2. Toggle Automatic Retries on and pick your max attempts (up to 5) plus backoff spacing. 3. Save the job, and any non-2xx response will retry automatically and log every attempt in the run timeline. A quick note on availability: Automatic retries are live today on all Starter and Pro workspaces at no extra cost. Full retry headers and timeout details are in the docs: https://cratecron.example/docs/retries. Try it now: https://app.cratecron.example/jobs Hit reply if anything feels rough or if you run into an edge case. I read every reply. Devon Founder, CrateCron
Mistakes to avoid
- Celebrating your engineering effort ('we spent three months refactoring our queue') instead of explaining what the user gets.
- Sending an email with five unrelated features crammed together so the reader skips all five links.
- Forgetting to clarify plan eligibility, which frustrates free-tier users who click excitedly and hit a locked toggle.
- Mailing inactive signups who never finished setup without trimming your segment to people who care about the workflow.
Related tools and guides
Free tool
Value Proposition & Hero Tagline GeneratorCraft punchy hero headlines, Steve Blank positioning formulas, and tight 60-character directory taglines.Free tool
Launch Day ChecklistEverything to check before, during and after launch day, saved in your browser.Founder guide
How to Write a Changelog People Actually Read (2026)Why a public changelog is worth the effort, what goes in it, how to write entries for users, version numbers, where to publish it and how to turn it into posts.Founder guide
What to Do After Launch Day: The Two Weeks That Decide Whether It WorkedLaunch day gets the attention, but the next fourteen days decide whether a launch turns into users. A day-by-day plan for solo founders.More templates
Pritam Ghosh runs Hauntboard and maintains these templates.
Published · Updated
Ready to put your launch in front of real visitors?
A person reviews every launch on Hauntboard, and every view and visit it sends your site is published on your launch page. Free to submit.