We Sent 25 AI-Personalized Cold Emails and Got 0 Replies — Here's Why

We built Drumroll to do cold email right: research each prospect, write something genuinely tailored, skip the spray-and-pray. So when we decided to eat our own cooking and run a real outbound campaign, we expected to learn something about messaging. We didn't expect to learn almost nothing about messaging — and everything about infrastructure.

Here's what happened.

The Campaign Setup

We identified 25 prospects. Good fits — B2B SaaS founders and heads of sales at companies between 10–100 people, actively hiring SDRs (a signal they were investing in outbound). We ran each prospect through Drumroll's own pipeline: scraped their LinkedIn, pulled recent company news, generated personalized subject lines and openers.

The output was solid. Not obviously AI-written. Specific references to their company, their hiring patterns, the kind of thing you'd write if you actually spent 10 minutes researching someone. We felt good about it.

Zero replies isn't just disappointing — it's a signal. Getting low replies from a cold campaign is normal. Getting zero opens is a deliverability problem, not a messaging problem.

The Deliverability Audit

We ran the sending domain through mail-tester.com and MXToolbox. The results were ugly.

SPF: Failing

Our SPF record either didn't exist or wasn't aligned with the sending IP. SPF (Sender Policy Framework) tells recipient mail servers which IPs are authorized to send on behalf of your domain. Without a passing SPF record, Gmail and Outlook treat your email as unauthenticated — and unauthenticated email goes to spam or gets silently dropped.

DKIM: Not configured

DKIM (DomainKeys Identified Mail) adds a cryptographic signature to outbound emails that lets recipients verify the message wasn't tampered with in transit. No DKIM signature means no authentication signal — which, combined with no SPF, puts you firmly in "suspicious sender" territory.

DMARC: Missing entirely

DMARC (Domain-based Message Authentication, Reporting, and Conformance) builds on SPF and DKIM to give receiving servers a policy: what should they do when authentication fails? p=none (monitor), p=quarantine (spam folder), or p=reject (block entirely). Without a DMARC record, you're sending a signal to ISPs that you haven't even thought about authentication. Google and Yahoo now require DMARC for bulk senders.

Domain Age and Warmup

The sending domain was relatively new — under 60 days old. Spam filters weight domain reputation heavily, and new domains have no history. Even with perfect authentication records, sending 25 cold emails from a fresh domain without a warmup period is pushing your luck. Sending from one with broken auth records is asking to be filtered.

What We Got Wrong

We optimized the thing we could see — the email copy — and ignored the infrastructure layer underneath it. This is the most common mistake in cold email, and we made it ourselves while building a tool specifically designed to fix cold email.

The lesson isn't nuanced: if your emails don't land in the inbox, nothing else matters. The best subject line in the world doesn't help if Gmail drops the message before the recipient ever sees it. Deliverability is the floor. Everything else — personalization, timing, sequence, subject line testing — is furniture. You need the floor first.

What We're Fixing

This is what a proper sending infrastructure looks like, in order of priority:

1. Set SPF. Add a TXT record to your DNS that authorizes your sending provider's IP ranges. Most ESPs (email service providers) give you the exact record to add. Do this first.
2. Configure DKIM. Your ESP generates a public/private key pair. You add the public key to DNS as a TXT record. Done. Your sending provider handles signing.
3. Add a DMARC record. Start with p=none and an rua address so you get reports. Tighten to p=quarantine once you've confirmed your legitimate sending streams are aligned.
4. Warm up the domain. Start with 5–10 emails per day to people who will open and reply (colleagues, customers who know you). Ramp up over 4–6 weeks. This builds a reputation history that makes spam filters treat you as a legitimate sender.
5. Use a subdomain for outbound. Send cold email from outbound.yourcompany.com instead of your root domain. If it gets flagged or blacklisted, your primary domain's reputation is protected.

The Real Lesson

We got 0 replies from 25 emails, and it had almost nothing to do with our copy. The AI personalization worked. The research was real. The messaging was on point. The emails never arrived.

Infrastructure beats messaging. Every time. Before you think about subject lines, before you A/B test openers, before you hire a copywriter — fix your DNS records. They take 20 minutes to configure and they're the difference between landing in the inbox and landing nowhere.

We're building these checks directly into Drumroll. Before a campaign sends, it'll verify your SPF, DKIM, and DMARC configuration and warn you if anything's broken. Because we'd rather surface this problem before you waste good research on emails that never land.