Templates
Email templates for SaaS
12 blueprints for the mail a software product actually sends. Each one is a rendered example, a set of subject lines, the body block by block, and the trigger that fires it. No signup, nothing gated.
These are shapes we recommend rather than a catalogue of somebody else's production stack, so they are worth adapting rather than pasting. Where one is a flow we run on our own list, its page says so.
Before you launch
The mail you send while people are waiting, and the mail that tells them the wait is over.
Waitlist email
The confirmation that goes out the second somebody joins a waitlist, and the one follow-up that keeps them warm until you can let them in.Product launch email
The email that announces the thing, and the three around it that decide whether anybody notices. A launch is a sequence, not a send.
First run
Everything between the signup form and the moment the product is part of somebody's week.
Welcome email
The first email after signup, and the one with the highest open rate you will ever have. Spend it on one action, not on a tour.Onboarding email template
One email per step of the setup, sent only to the people who have not done that step yet. The condition matters more than the copy.Trial expiration email
Three emails around the end of a trial, and the one that matters is written differently depending on whether they actually used it.Verification email
The confirm your email message a SaaS sends at signup. It is the one email people sit and wait for, so it has one job: arrive at once and take one tap.
Staying useful
Sequences and one-offs that keep a list warm without teaching it to ignore you.
Drip campaign template
A fixed set of emails on a fixed cadence, started by something somebody did. The template is one email; the campaign is the exit condition.Nurture email sequence
For the lead who is interested but not ready. The sequence teaches, the conditions route, and nothing in it asks for a meeting until something has been read.Feedback and survey email
One question, sent close enough to the thing it asks about that the answer is worth having: as a reply, as an NPS score from 0 to 10, or as a satisfaction rating after a support request.Product update email
The regular note to people already using the product. Smaller than a launch, more often, and written for somebody who already knows what the words mean.
Keeping them
The two hardest sends: the one that asks a quiet account to come back, and the one that answers a cancellation.
Win-back email
Two emails to an account that has gone quiet, and a check between them so the second never reaches somebody who already came back.Cancellation email
What to send after somebody cancels, and the one thing that decides whether it works: answering the reason they gave rather than the reason you wish they had given.
Building these
Every blueprint here is portable: the structure works in whatever you send with today. If you want to build them without writing HTML, they can be assembled block by block in the SendHeron template builder, and the conditions described on each page are the same kind a sequence branches on.
Free trial
Lifecycle sequences, drafted from your website
SendHeron reads your site and drafts the lifecycle sequences that fit your product, such as welcome, trial, win-back and cancel-save, in your product's own words and ready to edit. The other emails in this gallery you build in the template editor. Start a trial and run the setup on your own site.
7-day free trial. Pick a plan, add a card, cancel before the trial ends and you won't be charged. 1,000 contacts and 5,000 sends during the trial.