Email Marketing for SaaS Companies

If you are the first marketer at a SaaS company and someone has asked you to “do email”, the instinct is to write a newsletter. Resist it for eight weeks. The newsletter is the lowest revenue per hour thing on the list, and building it first tends to lock you into a tool that cannot send on product events.

This is the build order I would follow, written for a team of one with a few days of engineering time to spend.

Week one: the data plumbing nobody wants to do

Before you evaluate a single tool, get four things in place. Every problem later in the program traces back to one of them.

Events. A named list of product actions worth emailing about. Keep it to twelve for now. Typical set: signed_up, activated, project_created, invited_teammate, hit_usage_limit, subscription_started, payment_failed, subscription_cancelled, feature_x_used, exported_data, integration_connected, logged_in_after_dormancy. Name them in past tense with snake case and never rename one after launch.

Traits. Attributes that describe the person and the account: plan, seat count, ACV, signup source, role, account created date, last active date. Keep person and account separate from day one, because retrofitting an account object into a tool that only has contacts is the most painful migration in this category.

Identity. One stable user ID from your database, sent with every event, with email as a secondary key. Email as a primary key breaks the moment someone changes theirs, and someone always does.

Sending domains. Marketing on mail.yourdomain.com, transactional on notifications.yourdomain.com, each with SPF, DKIM and a DMARC policy. Google and Yahoo now enforce authentication and one-click unsubscribe for bulk senders, so this is not optional hygiene, it is a delivery requirement.

Which five sequences should you build, and in what order?

Rank by revenue per hour of build time, not by funnel position. That ordering produces a counterintuitive list, and it is correct.

Sequence	Build time	Revenue mechanism	Typical impact	Order
Trial expiry	1-2 days	Converts users already at peak intent	High, fast to read	1
Onboarding and activation	3-5 days	Raises the share of signups reaching first value	High, compounds	2
Dunning	1 day	Recovers revenue already earned	30-50% of involuntary churn	3
Activation nudges	2-3 days	Rescues stalled users mid funnel	Medium	4
Expansion	2-4 days	Seats, tiers, annual upgrades	Medium, high ACV	5
Newsletter	Ongoing forever	Brand and retention, hard to attribute	Low per hour	6

Why dunning comes before the newsletter

A dunning email goes to someone whose card just failed, who already decided to pay you, and who mostly needs to update an expired card. There is no persuasion involved. Recovery rates of 30 to 50 percent of involuntary churn are commonly reported, and involuntary churn is often a third of total churn at self serve companies.

It takes about a day to build: four sends over 14 days, escalating tone, each linking directly to a card update page that does not require a login. Stripe and most billing providers expose the events you need with no custom instrumentation at all.

Compare that to the newsletter. Weeks of ongoing effort, indefinite payback, and a real risk of list fatigue if the cadence outruns your ability to say something useful. I would not write a single issue before the five sequences above are live.

The trial expiry sequence

Highest intent audience in your entire database, and a deadline you control. Five sends: day 3 value check, day 7 mid-trial nudge based on whether they activated, day 11 case or feature relevant to their usage, day 13 expiry warning with the specific things they will lose, day 15 post-expiry recovery with a short extension offer for active users only.

Branch on activation. A user who never created a project needs a different day 11 email than a user who created nine, and sending both the same message wastes the strongest segmentation signal you have.

Which tool at which stage, and what it actually costs

Choose on event volume and data model, not on feature checklists. Every tool in this category can send an email.

A few opinions on the specific tools. Loops is the fastest to get running and the easiest to hand to a non technical founder, with a genuinely simple event API. Userlist was built for SaaS specifically and has the cleanest account-versus-user model at the small end, which matters more than people expect. Encharge sits in between with stronger branching than Loops at a similar price.

Customer.io is where most product-led companies land by Series A, and it is the one I would pick if I expected to still be using the tool in three years. Its pricing scales on profiles and events, so model both before signing. HubSpot makes sense when the same team runs the CRM and marketing email and nobody wants two systems, but its product event handling is weak and the contact tier pricing gets expensive fast. Braze is a genuinely different class of tool with an implementation cost to match, and below roughly $30M ARR it is usually overbuying.

Self hosting is a real option if you have engineering capacity and a data residency constraint, covered in Mautic for SaaS. For a wider field including tools not listed here, see the best email marketing software for SaaS.

What reporting keeps the program funded?

One table, monthly, with revenue in it. Open rates have not been trustworthy since Apple Mail Privacy Protection started prefetching images, and reporting them to a CFO invites a question you cannot answer.

The view that works:

The holdout column is what makes this credible. Hold back 5 to 10 percent of eligible recipients from each triggered sequence and compare. Without it, every number in the revenue column is a claim that a user who was going to convert anyway converted because of your email, and a skeptical finance team will say so.

Revenue per send is the single number to lead with. It ranks sequences honestly, it explains why dunning gets built first, and it survives translation to people who do not care about email. Model your own figures with the SaaS email revenue calculator before you commit to a target, and check your rates against the SaaS email benchmarks rather than against generic cross-industry averages.

The 90 day rollout

What to skip in month one: the newsletter, any preference centre beyond a single unsubscribe, segmentation beyond plan and activation status, and A/B testing. Testing subject lines on 400 sends produces noise, and the time is better spent shipping the next sequence.

Where these programs actually fail

Not on copy. On data.

The most common failure is events that fire inconsistently. A project_created event that also fires on template duplication will send congratulations emails to people who did nothing, and by the time you notice, trust in the whole program is damaged internally. Audit event definitions with the engineer who wrote them, monthly, for the first six months.

Second failure: nobody owns it after launch. Lifecycle email is not a project, it is a surface that decays. Sequences reference features that got renamed, links rot, and a branch that was correct in March is wrong in September. Budget two hours a week forever, and put a review date on every sequence. Common errors worth pre-empting are collected in the SaaS email marketing mistakes write-up.

Third, and most expensive: choosing a tool before the data model exists. Teams pick based on a demo, discover six months later that the tool has no account object or cannot branch on a numeric event property, and migrate. That migration costs roughly six weeks and everyone’s goodwill.

What to do next

Write the twelve event names down today and get them in front of an engineer this week. That single step unblocks everything else, and it is the one most teams postpone because it does not feel like marketing.

Once events exist, build dunning first, then trial expiry, then the rest in order. If your motion is sales-led rather than product-led the emphasis shifts, and B2B SaaS email marketing covers that variant. For the mechanics of firing on product actions, the behavioral email trigger definition is the short version, and drip campaigns for SaaS explains the narrow cases where a fixed schedule still beats an event. Once the five sequences run, expansion is where the next meaningful revenue sits, covered in expansion revenue email campaigns and the wider SaaS email marketing hub.