Email Marketing for SaaS: Onboarding to Win-Back
Email marketing for SaaS, stage by stage: onboarding emails, trial conversion, product updates and win-back, run by your AI agent and triggered by your app.
Email marketing for SaaS: one email per stage of the customer lifecycle
Email marketing for SaaS is not a newsletter. It is a set of emails tied to what a user does in your product: they sign up, they activate, they convert, they stay, or they drift away. Each stage gets its own message, triggered by an event in your app rather than by a calendar. This guide walks through the five stages, the emails that belong to each, and how to wire them so your AI agent runs the whole thing.Why SaaS email marketing works differently
A shop emails people who might buy. A SaaS emails people who already signed up and now have to use something. The job of most SaaS emails is to move a user one step forward inside the product: connect their first integration, invite a colleague, reach the moment where the tool pays for itself. That changes three things:- The trigger is behavioural. "Day 3 after sign-up, and still no project created" is a better reason to write than "it's Tuesday".
- The clock is per user. Two people who signed up a week apart must each receive their day-3 email on their own day 3.
- The volume is predictable. If you get 2,000 trial sign-ups a month and your onboarding has five emails, you send about 10,000 onboarding emails a month. You can size your plan before you start.
The SaaS customer lifecycle, stage by stage
| Stage | Goal | Email to send | Trigger in AgentsMail |
|---|---|---|---|
| 1. Sign-up | Get the first session right | Welcome + one first action | Contact joins the Trial users list |
| 2. Activation | Reach the "aha" moment | 2–3 tips, one per key feature | Same sequence, wait steps between emails |
| 3. Conversion | Turn the trial into a paid plan | Trial-ending reminder, offer | Tag trial-ending added by your app |
| 4. Retention | Keep paying users informed | Product updates, monthly digest | Campaign to the Customers list, with a topic |
| 5. Win-back | Bring back a cancelled user | Short "what changed since you left" | Tag churned added by your app |
Stage 1 and 2: SaaS onboarding emails
SaaS onboarding emails are the ones with the biggest return, because they reach people while they still remember why they signed up. A good onboarding sequence is short: a welcome email the day of sign-up, then two or three emails spaced a few days apart, each pushing one action. The cleanest way to start it is from your own sign-up code. When a user creates an account, your backend adds them to a list with the single-contact endpoint. That call has side effects on purpose: it enrols the contact in any sequence that listens to that list.json
POST /api/v1/lists/{listId}/contacts
{
"email": "lea@acme.io",
"firstName": "Léa"
}01
Create the sequence on the list trigger
The trigger is
list_joined on your Trial users
list. Creating the sequence also creates its first draft version.02
Add the steps
Welcome email, wait 48 hours, tip #1, wait 72 hours, tip #2. Each send
step carries its own subject and content.
03
Publish, then activate
The graph is validated when you publish. Nothing runs until the sequence
status is
active.{{firstName}}, so plan the sentence for both cases.
Stage 3: converting the trial
Conversion emails depend on a date your app knows and AgentsMail doesn't: the end of the trial. So let your app say it. Three days before the trial ends, your backend tags the contacttrial-ending. A second sequence, triggered on tag_added, sends the reminder and the offer.
Two details make this stage cleaner:
- Use a
remove_tagstep at the end of the conversion sequence, so the tag can be applied again if the user starts a new trial later. - Use a webhook step if your app needs to know the email went out — for example, to show a banner in the product the same day. A webhook step calls a URL of yours as the contact passes.
customer; the next step does not need to guess.
Stage 4: retention and product updates
Paying users want to know what changed, not to be onboarded again. That is campaign territory: one email, one audience — theCustomers list, optionally narrowed by a tag such as plan-pro.
Here, topics matter. A topic is an editorial theme — "Product updates", "Webinars" — that a recipient can turn off without unsubscribing from everything. A customer who does not care about webinars keeps receiving billing-relevant product news. Attach the topic to the campaign and add the {{topicOptOutUrl}} link to the template.
Before you send, two checks are worth the minute they take:
- the spam risk report reads the subject, preview text and body and flags things like a subject that promises more than the body delivers;
- the render endpoint returns the final HTML with warnings, without sending anything.
Stage 5: win-back
Cancelled users are the cheapest to bring back: they know the product. Keep it to one or two emails. Your app tags themchurned on cancellation; a sequence waits a few weeks, then sends a short "here is what shipped since you left".
Respect the exit. If they unsubscribed rather than just cancelled, they stay unsubscribed: an unsubscribed contact is skipped at departure and consumes nothing.
Let your AI agent run it
Every step above is an API call, which means an agent can do it. With the AgentsMail skill installed and an API key, you describe the outcome in plain language:text
Build a 4-email onboarding sequence for the "Trial users" list:
welcome today, then one tip every 3 days about projects, integrations
and invites. Draft the templates, render each one, and show me the
graph before you publish anything.Deliverability before volume
Onboarding emails only work if they arrive. Before your first sequence goes live, verify a sending domain — ideally a subdomain such asmail.yourapp.com — so your marketing reputation stays separate from your password resets. Since 2024, Gmail and Yahoo also require authentication and one-click unsubscribe from bulk senders; our breakdown of the Gmail and Yahoo bulk sender rules lists what they check.
AgentsMail refuses a send that cannot go out cleanly — domain not verified, sender not on a verified domain — and names the reason instead of failing silently.
What it costs for a SaaS
| Your SaaS | Emails per month | AgentsMail plan |
|---|---|---|
| 300 trial sign-ups × 5 onboarding emails + 1 monthly update to 1,000 users | ~2,500 | Free — 3,000 emails, 10,000 contacts, 2 sequences |
| 2,000 sign-ups × 5 emails + updates to 8,000 users | ~18,000 | Pro — €19/month, 50,000 emails, 10 sequences |
| 20,000 sign-ups × 6 emails + updates to 100,000 users | ~220,000 | Enterprise — €200/month, 500,000 emails |
FAQ
What are SaaS onboarding emails?
They are the automated emails a new user receives in the first days after signing up: a welcome, then a few emails that each push one key action in the product. Their goal is activation, not sales. In AgentsMail they live in a sequence that starts when the user joins a list.How many emails should a SaaS onboarding sequence have?
Three to five is a common range: a welcome on day 0, then one email every two to four days. Each email should ask for one action. Stop the sequence, or move the user to another one, as soon as they have done what the emails were pushing.Can my app trigger emails without an integration platform?
Yes. Your backend calls the AgentsMail API directly: adding a contact to a list or tagging them is enough to start a sequence. No middleware is required.Should onboarding emails and password resets use the same sender?
Keep them apart. Send marketing and onboarding from a dedicated subdomain, and keep account emails such as password resets on your application's own transactional setup, so one reputation never drags down the other.01SaaS email is triggered by what users do, not by the calendar.
02Your app adds a contact to a list or tags it; a sequence does the rest.
03Bulk imports enrol nobody — use the single upsert or a tag.
04Product news goes out as campaigns, with topics people can turn off.