Email deliverability for startups and solo founders

A startup's deliverability risk profile differs from an established company's in one specific way: everything starts from zero. No sending history, no established reputation, often a domain registered the same month the first campaign goes out - which is precisely the pattern mailbox providers scrutinize most closely.

Pre-launch: before the first real send

• Register and authenticate the domain early, even before you have anything to send. SPF, DKIM and DMARC published and stable for a few weeks before the first real campaign gives a mailbox provider some baseline to evaluate against, rather than seeing authentication appear the same day as a volume spike.
• Separate transactional from marketing from day one. It's far easier to set up a clean split (a subdomain for transactional mail, the main domain or another subdomain for marketing) before any sending history exists than to untangle it later once reputation has accumulated on a mixed-use domain.
• Don't reuse a previously-used domain without checking its history. A domain that changed hands, or an old company domain being repurposed, can carry prior reputation - good or bad - that affects day-one sending. A quick check before reusing any domain: look it up against the major blocklists (Spamhaus, Barracuda, SpamCop), and search it in the Wayback Machine to see what it was used for previously - a domain that hosted a content farm or sent spam under a prior owner carries that history forward, and the cost of discovering this after launch is a lot higher than the five minutes it takes to check first.

Early customers: the first few hundred to few thousand sends

• Warm up gradually even though the volume feels small. A startup with 200 early users sending a product update to all of them at once, from a domain registered three weeks ago, is still a meaningful volume jump relative to the domain's sending history.
• Prioritize transactional reliability over marketing volume. Password resets, confirmation emails, and onboarding sequences matter disproportionately at this stage - a broken signup-confirmation email is a worse first impression than a skipped marketing send.
• Watch complaint rate closely even at low volume, since a small number of complaints represents a much larger percentage of a small list than the same number would at scale.

Scaling: once volume is growing

• Don't let sending volume outpace mailbox and domain reputation. A sudden growth spurt in users (a product launch, a funding announcement, a viral moment) often brings pressure to send more volume faster than the sending infrastructure has reputation to support.
• Add capacity ahead of need, not reactively. Standing up and warming additional mailboxes or domains takes weeks - starting that process when volume is already straining existing capacity means a gap during exactly the period growth matters most.
• Revisit the transactional/marketing split as team size grows. What worked with one founder sending everything often needs more structure once a dedicated marketing or growth hire starts sending independently. A common failure mode here is a growth hire connecting a new email tool and sending their first campaign through the same domain and mailbox the founder uses for customer support - the two sending patterns look nothing alike to a mailbox provider, and the mismatch itself can read as suspicious even before any content or list-quality issue comes into play.

A startup-stage checklist

What not to do

• Don't wait until the week of launch to set up SPF/DKIM/DMARC - a domain with zero authentication history sending its first campaign is the highest-risk pattern there is.
• Don't mix transactional and marketing mail on one domain to save setup time early - the cost of separating them later, after reputation has accumulated, is higher than setting it up correctly from the start.
• Don't treat low absolute volume as a reason to skip warm-up discipline - the ratio to sending history matters more than the raw number.
• Don't scale sending volume faster than your infrastructure's demonstrated capacity, even when growth pressure is real - a reputation setback during a high-growth moment is expensive precisely because it's the moment you most need reliable delivery.

MailPilot is built for exactly this starting-from-zero problem: it warms new mailboxes gradually over OAuth or SMTP/IMAP, checks SPF/DKIM/DMARC from the first connection, and tracks per-mailbox reputation daily - so a startup's sending infrastructure has a measured track record by the time volume actually matters, instead of guessing at it, and without needing a dedicated deliverability hire before the team is big enough to justify one.