Email Marketing for SaaS Companies: Deliverability First

Email marketing for SaaS companies is structurally different from ecommerce or newsletter email. The use cases span transactional (system mail), product communication (feature announcements, lifecycle nurture), and traditional marketing (newsletters, promotional sends). Each has different deliverability requirements, different platforms, and different success metrics.

Most SaaS deliverability problems I diagnose come from treating these as a single program — sending marketing volume through transactional infrastructure or vice versa. This guide covers the separation that matters and the platforms that handle each layer correctly.

The Core Separation: Transactional vs. Marketing

A SaaS company sends two distinct categories of email:

Transactional Email

• Password reset, email verification, magic link login
• Receipts, invoice notifications, payment failure
• Account changes, security alerts
• System notifications triggered by user action

These must deliver fast and reliably. Recipients are actively waiting for them. Complaint rates are essentially zero because users requested the action.

Marketing / Lifecycle Email

• Welcome and onboarding sequences
• Feature announcements, product updates
• Newsletter, blog digest
• Promotional sends (rare in SaaS)
• Re-engagement, win-back, churn prevention

These have higher complaint risk because users didn't immediately request them. Delivery speed matters less; engagement matters more.

Why Separation Matters

Mix them on the same infrastructure and you get cascading problems:

• Marketing complaints damage reputation for transactional mail
• Transactional throughput requirements constrain marketing send patterns
• Sender authentication and reputation tuning becomes confused
• Compliance handling diverges (transactional doesn't need unsubscribe; marketing does)

The fix is separate sending subdomains, often with separate ESPs:

transactional.yourdomain.com → Postmark or AWS SES (transactional ESP)
email.yourdomain.com → Customer.io or Iterable (marketing ESP)

Practitioner note: I've consulted with SaaS companies where transactional reputation collapsed because marketing complaints damaged the sending subdomain. The fix takes weeks — you have to migrate transactional to a clean subdomain, warm it up properly, then update every internal service to use the new domain. The split should happen on day one of any SaaS email setup. Retrofitting it later is painful.

ESP Selection by Use Case

Layer	Recommended ESPs	Best For
Transactional	Postmark	Best deliverability; small/mid-market
Transactional	AWS SES	Cheapest; high-volume API
Transactional	SendGrid	Mature; ok deliverability
Marketing / Lifecycle	Customer.io	Mid-market SaaS, strong behavioral
Marketing / Lifecycle	Iterable	Mid to enterprise SaaS
Marketing / Lifecycle	Braze	Mobile-first SaaS, enterprise
Marketing / Lifecycle	Loops	Early-stage SaaS, simple flows
Marketing / Lifecycle	Resend	Developer-focused, modern
Marketing / Lifecycle	Klaviyo	Don't use for non-ecommerce SaaS

For most early-stage SaaS, the right setup is Postmark (or AWS SES) for transactional, and Loops or Customer.io for marketing. As you scale, Iterable becomes the standard mid-market marketing ESP.

Lifecycle Programs That Drive SaaS Revenue

The marketing layer of SaaS email is primarily lifecycle automation tied to product behavior signals:

Activation Sequence (Days 0-14)

Welcome → Setup → First-value moment → Habit formation

Trigger emails based on what users have and haven't done in the product. A user who completes onboarding gets a different email path than one who hasn't logged in since day 1.

Adoption Sequence (Days 15-90)

Feature education → Advanced use cases → Integration awareness → Community

Surface product capabilities based on use patterns. Users who only use the basic features get pointers to advanced ones; power users get integration and community content.

Retention Sequence (Ongoing)

Health-score-based outreach → Churn risk intervention → Win-back

Identify users showing churn signals (login decline, feature usage drop) and trigger targeted re-engagement.

Expansion Sequence (Customer Stage)

Upgrade triggers → Cross-sell to relevant teams → Renewal prep

Identify expansion opportunities based on usage patterns and trigger sales-assisted email when threshold conditions hit.

Authentication Configuration

For each sending subdomain, configure separately:

# Transactional subdomain
transactional.yourdomain.com TXT "v=spf1 include:_spf.postmark.app -all"
selector1._domainkey.transactional.yourdomain.com TXT "..." # Postmark DKIM
_dmarc.transactional.yourdomain.com TXT "v=DMARC1; p=reject; rua=mailto:[email protected]"

# Marketing subdomain  
email.yourdomain.com TXT "v=spf1 include:_spf.customer.io ~all"
cio1._domainkey.email.yourdomain.com TXT "..." # Customer.io DKIM
_dmarc.email.yourdomain.com TXT "v=DMARC1; p=quarantine; rua=mailto:[email protected]"

Note the different DMARC policies — transactional should be p=reject (you're confident in alignment), marketing can be p=quarantine (less aggressive in case of ESP misconfiguration).

Metrics That Matter for SaaS Email

Transactional Metrics

• Delivery rate: target 99.5%+
• Time-to-inbox: target under 30 seconds for security-sensitive mail
• Bounce rate: target under 0.5% (transactional should hit valid addresses)
• Inbox placement: target 98%+

Marketing/Lifecycle Metrics

• Activation rate from welcome series (users who hit value moment within 14 days)
• Feature adoption rate from product education emails
• Time-to-second-value acceleration from onboarding emails
• Churn rate reduction from retention sequences
• Expansion-attributed revenue from upgrade flows

Don't optimize SaaS marketing email for open rates. Optimize for the product behavior the email is meant to drive.

Common SaaS Email Problems

"Our transactional email goes to spam"

Usual causes:

• Marketing complaints damaging shared subdomain reputation
• Authentication issues on transactional subdomain
• Transactional ESP with shared IPs to other senders

Fix: separate subdomains, audit authentication, possibly migrate transactional to Postmark for deliverability.

"We have a 200K email list and 8% open rate"

Usual causes:

• Old list with no engagement-based sunset
• Mixed transactional + marketing on same subdomain
• Sending broadcast email instead of behavior-triggered

Fix: aggressive list cleaning, shift to behavior-triggered sequences, separate sending domains.

"Our welcome series doesn't drive activation"

Usual causes:

• Emails too generic, not tied to user behavior
• No conditional logic on what users have/haven't done
• Wrong send timing relative to user actions

Fix: redesign as behavior-triggered with conditional logic. Send "complete setup" emails only to users who haven't, "first feature" emails based on what they have completed.

Practitioner note: Most SaaS welcome series I audit send the same five emails to every new user regardless of what they've done in the product. The result: users who already activated get nagged to do things they did, and users who didn't activate get generic content instead of specific help with their blocker. Behavior-driven sequences dramatically outperform calendar-based ones in SaaS. The infrastructure is the same; the conditional logic is what separates good from bad.

Compliance Considerations for SaaS

SaaS email compliance is mostly the same as other email marketing with a few SaaS-specific gotchas:

• Transactional doesn't need unsubscribe, but the line is blurry. "Receipt with promo at bottom" is marketing, not transactional.
• Account notifications need a way to control preferences even if they don't need unsubscribe
• GDPR consent for marketing emails to EU users, even if they're paying customers
• Soft opt-in under PECR (UK) covers existing customers for related services

A practical pattern: separate "system notifications" from "product updates" with separate preferences in your account settings UI. Users can opt out of product updates without losing critical account notifications.

When to Build vs. Buy

For most SaaS companies, buying ESPs (Postmark + Customer.io) is correct. Building custom email infrastructure rarely makes sense unless:

• You have very high volume (10M+ emails/month)
• You have specific compliance requirements no ESP meets
• You have a strong engineering team with email expertise

The build-vs-buy threshold for SaaS email is high. Most "we should build it" decisions are mistakes that consume engineering time without improving the product.

If you're setting up email infrastructure for a SaaS company or need help diagnosing deliverability problems specific to SaaS workloads, book a consultation. I work with SaaS companies on transactional/marketing separation and lifecycle program design.

Sources

• Postmark: Transactional Email Best Practices
• Customer.io: Behavioral Email Documentation
• Iterable: Documentation
• Google: Email Sender Guidelines
• M3AAWG: Sender Best Common Practices

---

v1.0 · May 2026