Email deliverability for founders: the first 90 days
TL;DR: Founders often treat deliverability as a writing problem: if the subject line is good enough, mail will arrive. Mailbox providers disagree. They evaluate whether you authenticate your domain, whether recipients want your mail, and whether your sending patterns look like a legitimate business rather than a burst spam campaign.
Deliverability is infrastructure, not copy
Founders often treat deliverability as a writing problem: if the subject line is good enough, mail will arrive. Mailbox providers disagree. They evaluate whether you authenticate your domain, whether recipients want your mail, and whether your sending patterns look like a legitimate business rather than a burst spam campaign.
The good news is that defaults improved. Modern ESPs, including Brew, Resend, Klaviyo, and Loops, guide you through domain verification and publish DNS records for SPF and DKIM. You still own list quality and volume discipline. No vendor can opt-in your users for you.
This guide covers the first ninety days: enough to launch product mail, a small newsletter, and lifecycle onboarding without landing in spam folders you never knew existed.
Week one: authenticate before you scale
Add a dedicated sending subdomain such as mail.yourdomain.com or hello.yourdomain.com. Publish SPF, DKIM, and DMARC records your ESP generates. Verify alignment so the domain in the From header matches the signing domain. Gmail and Yahoo bulk sender rules treat authentication as mandatory for serious programs.
Turn on DMARC reporting with a p=none policy first. Reports look noisy, but they reveal shadow sending you forgot about: old SaaS tools, support desks, calendar invites. Clean those up before you tighten policy to quarantine or reject.
Configure a visible unsubscribe link on marketing mail and honor removals within two days. One-click unsubscribe headers are required for bulk marketing to Gmail and Yahoo above their volume thresholds.
List quality beats list size
Your first five hundred recipients should be people who explicitly asked for mail: beta users, customers, hand-raised newsletter signups. Imported LinkedIn contacts and purchased lists destroy reputation before you send a second campaign.
Use double opt-in when growth is not urgent. Single opt-in is fine for transactional contexts, but marketing lists benefit from the extra confirmation step because it filters typos and malicious signups.
Track spam complaint rate in Google Postmaster Tools and Yahoo sender hub if you qualify. Stay well under 0.3% and aim for under 0.1%. One angry blast to an unengaged segment can suppress delivery for weeks.
Warming is gradual, not optional
A brand-new domain has no reputation. Providers expect volume to ramp. Start with transactional mail to engaged users: receipts, password resets, onboarding steps people trigger themselves. Add marketing broadcasts only after those messages show healthy open and low bounce rates.
A simple warm-up schedule for a startup might look like: week one, under five hundred messages per day; week two, one thousand; week three, two thousand; adjust based on bounces and complaints. There is no universal chart because audience quality matters more than the numbers.
If you change ESPs, treat the migration as a partial warm-up even if the domain is old. New IP pools and signing infrastructure still need to establish trust.
Operational habits that stick
Segment engagement monthly. Suppress or sunset contacts who have not opened in ninety to one hundred eighty days depending on send frequency. Re-engagement campaigns are fine; infinite mail to ghosts is not.
Separate transactional and marketing streams when possible. Different subdomains isolate reputation so a promotional experiment cannot throttle password resets.
When metrics dip, check authentication first, then content classification (Promotions versus Primary in Gmail), then list source. Most founder issues trace to DNS or hygiene, not ESP choice.
Add a dedicated sending subdomain such as mail.yourdomain.com or hello.yourdomain.com. Publish SPF, DKIM, and DMARC records your ESP generates. Verify alignment so the domain in the From header matches the signing domain. Gmail and Yahoo bulk sender rules treat authentication as mandatory for serious programs.Sources
FAQ
Do I need a dedicated IP as a startup?
Usually no. Shared pools from reputable ESPs are appropriate until you send high enough volume that providers recommend dedicated infrastructure. Focus on domain authentication and list quality first.
Can AI writing hurt deliverability?
Only if it causes you to send more mail people do not want. Providers measure engagement and complaints, not whether copy was AI-generated. Relevance and permission still rule.
What is a realistic complaint rate target?
Stay under 0.1% if possible and never approach 0.3%, which Gmail cites as a danger zone for bulk senders.