Email marketing for SaaS is mostly not marketing. The campaigns that move revenue in a subscription business are triggered by what someone does inside the product — signed up and did nothing, hit a limit, invited a teammate, stopped logging in — and they are closer to product than to promotion.
That reframing matters because a SaaS company that runs a monthly newsletter and calls it email marketing is leaving the actual money untouched. Here are the sequences that matter, roughly in order of what they are worth.
1. Onboarding to first value
The single highest-leverage email a SaaS company sends is the one that gets a new signup to the moment the product becomes useful. Not a feature tour. The specific action that makes someone a user rather than a signup — sent their first campaign, connected their first repository, imported their first list.
Identify that action, then build a short sequence that exists only to produce it. Three or four emails over the first week, each with one instruction and one link, each stopping the moment the user completes the action. That last part is the one teams get wrong: an onboarding sequence that keeps sending after the user has already done the thing is actively annoying.
Trigger it on signup, exit it on activation. Everything else is decoration. Welcome email examples covers the copy side.
2. Trial conversion
If you run a trial, the emails around days 3, 7 and the day before expiry do more for conversion than your pricing page. The structure that works:
- Early trial: here is the thing to try first. Same activation logic as onboarding.
- Mid trial: here is what you have done so far, and here is what you have not tried yet. Use their real usage data; a mid-trial email with actual numbers in it converts far better than a generic one.
- Expiry: a plain, unembellished note about what happens to their data and their account. Not a discount. Discounts at expiry train people to wait for discounts.
Branch this on usage. Someone who used the product heavily needs a different email than someone who signed up and never returned, and sending both the same "your trial ends tomorrow" wastes the highest-intent moment you get.
3. Activation rescue
Some proportion of signups never reach first value, and that proportion is usually larger than founders expect. A rescue sequence targets exactly that group: signed up, did not activate, still opening email.
Keep it short and make it about the obstacle rather than the product. Ask what got in the way. Genuine replies to a plain-text "what stopped you?" from a real person at the company are among the most useful research a SaaS company can collect, and the reply rate on a properly targeted version of this is high enough to be worth reading personally.
4. Expansion
Usage-triggered upgrade prompts convert several times better than a pricing email to your whole base, because they arrive at the moment the limit is actually felt. Approaching a seat limit, hitting a volume cap, using a feature that a higher tier does more of — each is a trigger.
The tone that works is informational rather than promotional. Tell them where they are against the limit and what happens when they cross it. The upgrade link is a detail, not the message.
5. Churn prevention
Declining usage is the earliest reliable signal of a cancellation, and it is visible weeks before the billing event. A sequence triggered on a meaningful usage drop — sessions down, seats idle, a workflow that stopped running — reaches people while the decision is still reversible.
Failed payments deserve their own flow and are often the most underrated revenue recovery in the business. Involuntary churn from expired cards is a meaningful share of total churn at most SaaS companies, and a three-email dunning sequence with clear instructions recovers a large fraction of it. Pair it with renewal reminder emails.
The part that is genuinely marketing
Beyond the lifecycle, a product newsletter is worth running if you actually have something to say. Changelogs sent as email work when the changes are user-visible and the writing is specific. "We shipped X, here is the problem it solves" is a good email. "Exciting improvements this month" is not.
For B2B acquisition rather than retention, the mechanics are different enough that they belong in B2B email marketing.
The technical piece nobody enjoys
SaaS email has an unusual problem: your marketing email and your transactional email share a domain, and transactional email is the one that must never fail. A password reset in the spam folder is a support ticket; a newsletter in the spam folder is a bad Tuesday.
The standard answer is a subdomain split — marketing from one subdomain, transactional from another — so a reputation problem on one does not sink the other. Both need SPF, DKIM and DMARC of their own, which our SPF DKIM DMARC generator will produce. The trade-off, and it is real, is that splitting means warming two reputations instead of one. See transactional vs marketing email for when the split is worth it.
If you would rather run both through one account and one authenticated domain, that is what our SMTP relay is built to do — and for early-stage products, unlimited contacts on the paid plans means your bill tracks how much you send rather than how many accounts have ever signed up — which matches how a SaaS list actually grows.
Frequently asked questions
How many onboarding emails should a SaaS send?
Three to five over the first week or two, each with a single action, and the sequence should stop as soon as the user completes the activation event. Length matters less than the exit condition — a four-email sequence that keeps sending after activation performs worse than a three-email one that stops.
Should SaaS marketing and transactional email use the same domain?
Use the same root domain for brand consistency, but separate subdomains for sending. That way a marketing reputation problem does not put password resets in spam. The cost is warming two sending reputations rather than one, so very small senders sometimes reasonably choose to keep them together.
What is the highest-ROI email a SaaS company can build?
The failed-payment dunning sequence, because involuntary churn is revenue you have already earned and it recovers with three emails and no persuasion. After that, the onboarding-to-activation sequence, because everything downstream depends on users reaching first value.
How do I trigger emails from product usage?
Send product events to your email platform through its API or a webhook, store them on the subscriber record, and build automations that fire on those fields. Our MCP server and API both accept custom fields and tags for exactly this, so a usage event in your app can update a subscriber and start a flow without a separate integration layer.