Choosing a Transactional Email Provider for a New SaaS
The unglamorous decision that quietly breaks products. How to pick a sender, warm a domain, and stop landing in spam.
Email is the single most underrated part of a SaaS. Users can't sign up without it. Passwords can't reset without it. Enterprise buyers can't get invoices without it. And half the startups we work with have a transactional email setup that's one DNS misconfiguration away from landing in spam.
Choosing a transactional email provider for a new SaaS isn't just a vendor decision. It's the beginning of a series of small technical choices that add up to deliverability. Get it right early and it's invisible infrastructure. Get it wrong and you'll spend a year debugging why customers didn't get their verification emails.
What "transactional email" actually means
Transactional emails are the ones triggered by user actions or system events. Password resets, welcome emails, receipts, notifications. As opposed to marketing emails, which are broadcasted to lists.
The distinction matters because different providers handle each better. Some are optimized for transactional volume and deliverability; some are optimized for marketing volume and features. Mixing them up costs you deliverability on both.
The providers worth considering
Four providers cover most of the market for a new SaaS.
Postmark
The specialist. Focused entirely on transactional email with very high deliverability. Pricier per email than the alternatives, but not by much for a startup's volume. If you can only pick one provider without thinking, this is the safe bet.
Resend
Newer entrant with strong developer experience. Clean API, decent React email templates, straightforward pricing. Rising quickly among startups because the setup is genuinely quick. Deliverability is now competitive with Postmark for typical use.
SendGrid
The old default. Owned by Twilio. Handles very high volumes and both transactional and marketing email. The developer experience is dated, the docs are a maze, and deliverability on the free tier has a mixed reputation. Fine if you're already there; not our recommendation for a new project.
Amazon SES
Raw and cheap. If you send a million emails a month and have engineers who want to own the pipeline, SES is the best per-email deal. If you're a two-person startup sending 5,000 emails a month, the setup and maintenance aren't worth the savings.
What we usually pick
For a new SaaS shipping in the next few weeks, we pick between Postmark and Resend based on team preference. Both work, both are cheap enough at low volume, both handle deliverability well when set up correctly.
Deliverability isn't the provider's job alone
A great provider doesn't save you from a bad setup. Deliverability comes from four pieces working together.
1. SPF, DKIM, and DMARC records
Three DNS records that tell mailbox providers your emails are legitimate. SPF says "these servers can send for us." DKIM cryptographically signs each email. DMARC ties them together and tells receivers what to do when the check fails.
All three are non-optional in 2026. Gmail and Yahoo now reject bulk email that fails DMARC. Set them up before your first email lands in a real inbox.
2. A dedicated sending domain
Send from a subdomain of your main domain — usually mail.yourapp.com or something similar. This isolates your email reputation from your marketing team's Mailchimp campaigns and from your engineers' personal Gmail forwarding.
Sending straight from your root domain is fine for small volumes but limits your options later. A subdomain gives you flexibility.
3. A real "from" address that receives replies
Don't send from noreply@yourapp.com. It signals "we don't care about you" and hurts engagement, which hurts deliverability. Send from support@ or a specific human's address, and make sure someone reads it.
4. Warming the domain
New domains have no reputation. Sending 10,000 emails from a brand-new domain on day one is a fast path to being marked as spam. Ramp up: start with 100 emails a day, double every few days, watch the bounce and complaint rates. Most providers offer automated warming.
The setup that catches new SaaS off-guard
Three things that consistently break in the first month.
The first user's email lands in spam
Domain isn't warmed. Records aren't set. The provider is fine; the setup isn't. Do a test send to your own Gmail, Outlook, and Yahoo addresses before launching. Use a tool like mail-tester.com to check the score.
Verification emails don't arrive at all
Usually a DKIM signing issue or an SPF alignment problem. The provider's dashboard will show bounces and blocks; look at them within the first hour of going live.
Corporate spam filters block everything
Enterprise buyers on Microsoft 365 or Google Workspace have aggressive filters. Even a well-set-up email can end up in a corporate junk folder. Ask your first enterprise customer to whitelist your sending domain during onboarding. It saves a lot of "did you get my email" back-and-forth.
Templates and content
The provider handles delivery. You handle content.
Keep it simple
Plain HTML with minimal styling gets through filters more reliably than heavy branded templates. If your welcome email looks like a marketing blast, some filters treat it like one.
Include a plain text version
Every provider generates one automatically; make sure it's not empty. Filters weight the presence of a real text version.
Unsubscribe links, even for transactional email
New Gmail and Yahoo requirements ask for unsubscribe headers on bulk email. Even for transactional email, having a way for users to opt out of specific notification types is good practice and helps deliverability signals.
Common misconceptions
"If Postmark says it delivered, it's in the inbox." "Delivered" means the receiving server accepted it. It doesn't mean the mailbox provider showed it to the user. Inbox placement is a separate metric that providers approximate but don't guarantee.
"Cheap email providers are fine at low volume." The per-email price difference is trivial at low volume. The deliverability difference isn't. Pay $10-30 a month for a provider with good deliverability. It's the best-value spend on your stack.
"We can add SPF and DKIM later." Gmail and Yahoo now reject bulk email without them. "Later" means "we're okay with our verification emails going to spam." Set them up before you send email one.
What to do the day you set this up
The checklist. All of this should happen before your first real user gets an email.
- Pick a provider — Postmark or Resend for most cases.
- Create a sending subdomain, e.g. mail.yourapp.com.
- Add SPF, DKIM, and DMARC records to your DNS.
- Verify all three in the provider dashboard.
- Send test emails to Gmail, Outlook, and Yahoo addresses. Check inbox placement.
- Run one email through mail-tester.com and fix anything below 9/10.
- Set a bounce and complaint threshold that pages you if it spikes.
A morning of work. It's the difference between a product that reliably delivers email and one that quietly loses customers to spam folders.
How this ties into the rest of your stack
Transactional email is only one email surface. Marketing email lives elsewhere — Customer.io, Loops, Mailchimp — and should send from a different subdomain to isolate reputation.
Notifications inside your product benefit from the same discipline: batched digest emails, opt-out controls per notification type, and clear from-addresses.
Our onboarding post covers how welcome emails fit into the broader onboarding flow.
Frequently asked questions
Final take
Email is old, fussy infrastructure that's easy to underinvest in until it breaks. Choosing a good transactional email provider is the smallest part of getting deliverability right. The DNS setup, warming, and content decisions do most of the work.
If you're setting up email for a new SaaS and want a review of the provider choice, DNS records, and templates before your first send, book a call. We'll walk through it and tell you what to fix first.
FAQ
Frequently asked questions
What's the best transactional email provider for a new SaaS?+
For most new SaaS, Postmark or Resend. Postmark is the deliverability specialist; Resend has the best developer experience. Both are cheap at low volume and set up quickly. SendGrid and Amazon SES exist for higher-volume or highly custom setups but rarely make sense for a small new project.
What are SPF, DKIM, and DMARC?+
Three DNS records that tell mailbox providers your emails are legitimate. SPF authorizes sending servers. DKIM cryptographically signs messages. DMARC ties them together and tells receivers what to do when a check fails. All three are effectively required — Gmail and Yahoo reject bulk email without them.
Why do my verification emails land in spam?+
Usually one of three reasons: missing or misconfigured SPF/DKIM/DMARC records, a brand-new sending domain with no reputation, or content that pattern-matches to spam. Fix DNS first, warm the domain with gradual volume, and run a test through mail-tester.com to catch content issues.
Should I send email from my main domain or a subdomain?+
A dedicated subdomain like mail.yourapp.com. It isolates your transactional email reputation from marketing sends and personal forwarding on the same root domain. Sending from the root works at small volumes but limits your options later, so start on a subdomain from day one.
Is Amazon SES worth the savings for a small SaaS?+
Rarely. The per-email price advantage is real at high volumes but insignificant at typical startup volumes. SES requires more setup, more monitoring, and more knowledge of email fundamentals than managed providers. Save it for when your monthly volume makes the math actually work.
Building something similar?
Let's talk in 30 minutes.