Copyable template
Subject: We rebuilt [Product Name] (what changed since you tried it) Hi [First Name or "there"], You signed up for [Product Name] back when [context, e.g., we first launched v1]. If you tried it once and bounced, I do not blame you. The honest truth from user feedback was that [biggest weakness of the old version]. Over the past [timeframe], I rebuilt that part from scratch. Here is what is actually different in [Product Name] [Version/Update Name]: - Before: [old limitation 1]. Now: [concrete improvement 1]. - Before: [old limitation 2]. Now: [concrete improvement 2]. - Before: [old limitation 3]. Now: [concrete improvement 3]. [Optional account note: "Your old account still works with the same email, and I reset everyone's trial for 14 days so you can test the new build freely."] Take a quick look at the updated version here: [Relaunch URL or short changelog link] If you switched to another tool and no longer need [Product Name], no hard feelings at all. You can unsubscribe below in one click. If you do give it another spin, reply and tell me what still feels rough. Best, [Your Name] [Product Name]
When to use this template
Send a relaunch announcement email when you have shipped a substantive v2, fixed the main reason early users churned, or pivoted the workflow enough that dormant signups would have a genuinely different experience today. Do not call a minor color refresh or two small bug fixes a relaunch, because returning users will feel misled if the core friction is still there.
Segment your audience before sending: past churned users and dormant free signups need this candid 'what changed' message, whereas active paying customers should receive a feature announcement email that respects what they already use every day.
How to fill each placeholder
- Subject line: Signal clearly that something concrete changed since they last logged in. Avoid dramatic subject lines like 'We are back!' that give no reason to open.
- [biggest weakness of the old version]: Own the main complaint plainly in one sentence. Admitting that setup took too long or exports broke on large files builds far more credibility than pretending v1 was flawless.
- Before / Now bullets: Pair each improvement directly against a pain the reader likely experienced. This format lets skimmers judge in five seconds whether their blocker is gone.
- [Optional account note]: Remove re-entry friction. Tell people whether their old login still works and offer a fresh trial window if their previous trial expired months ago.
- Closing opt-out line: Give readers explicit permission to ignore or unsubscribe if they moved on. Low-pressure honesty keeps spam complaints low on older email lists.
Filled example (made-up product)
Example using a made-up static-site form backend called FormDock: Subject: We rebuilt FormDock (what changed since you tried it) Hi Sam, You signed up for FormDock back when we launched our first beta last spring. If you tried it once and bounced, I do not blame you. The honest truth from user feedback was that spam filtering barely worked out of the box and webhook retries silently failed when a destination timed out. Over the past 3 months, I rebuilt the ingestion pipeline from scratch. Here is what is actually different in FormDock v2: - Before: Basic honeypot fields that still let bot submissions into your inbox. Now: Built-in spam scoring with one-click Cloudflare Turnstile support and a quarantine tab. - Before: Webhooks fired once and disappeared on errors. Now: Automatic exponential retries for 24 hours plus a full payload log you can replay in one click. - Before: Exporting leads meant copying JSON blobs. Now: Scheduled CSV exports and direct Notion or Google Sheets sync. Your old account still works with the same email, and I reset every inactive workspace back to a fresh 14-day Pro trial so you can test v2 freely. Take a quick look at the updated version here: https://formdock.example/v2 If you switched to another form handler and no longer need FormDock, no hard feelings at all. You can unsubscribe below in one click. If you do give it another spin, reply and tell me what still feels rough. Best, Nadia FormDock
Mistakes to avoid
- Emailing an old cold list without cleaning bounced addresses first. High bounces hurt deliverability across transactional emails too.
- Pretending v1 had no flaws. People who churned remember why they left, and owning those gaps shows you listened.
- Forcing returning users to pay immediately after an expired trial. Reset trials for inactive accounts before sending.
- Listing twenty internal refactors instead of the three user-visible changes that fix real blockers.
Related tools and guides
Free tool
Startup Launch Readiness & Roast ScoreA candid 15-point diagnostic evaluating landing page clarity, pricing, proof, and launch readiness with an actionable letter grade.Free tool
Launch Day ChecklistEverything to check before, during and after launch day, saved in your browser.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.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.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.