A readiness checklist before a cold email campaign goes out

Cold outreach campaigns that underperform usually had a visible, checkable problem before the first message went out — a domain that wasn't warmed up, a list with questionable consent, authentication that was never verified. This is the checklist to run through before launch, not the diagnosis to run after.

List consent and quality

Before anything else, confirm the list was built with real consent appropriate to how you're using it, and that it's been verified recently:

• Addresses came from a legitimate source — not purchased, not scraped without basis
• The list has been run through a verification pass within the last month, removing invalid and risky addresses
• Role addresses and obvious non-responders have been filtered out
• You can account for where each segment of the list came from, in case a recipient asks

Domain and mailbox warm-up status

• The sending domain has real sending history, not a registration date with no actual mail sent
• If the domain or mailbox is new, warm-up has been running for at least the planned two-to-four-week minimum before full-volume outreach begins
• Daily volume ramped gradually, not jumped straight to campaign-scale sending

Authentication

• SPF record resolves correctly and includes the sending platform
• DKIM is configured and actively signing outgoing mail
• DMARC is published, even at a permissive p=none policy, so you're collecting alignment data

Sending platform limits and settings

Content and sequencing

• First message doesn't read as templated boilerplate to an obvious degree — genuine personalization beyond a swapped first name
• Follow-up sequence timing is spaced reasonably, not sent in rapid succession
• Content avoids patterns likely to trip spam-keyword filters (excessive urgency language, suspicious link structures)

A pre-launch checklist in one place

[ ] List consent verified and recently checked for validity
[ ] Domain/mailbox has real sending history or completed warm-up
[ ] SPF, DKIM, DMARC all passing
[ ] Sending platform limits confirmed, not assumed
[ ] Reply handling and unsubscribe path configured
[ ] Tracking/link domain checked separately from sending domain
[ ] First message and follow-ups reviewed for templated-boilerplate feel

What happens when this gets skipped

A campaign launched without this checklist often looks, in the first results, like a content or targeting problem — low open rates, no replies — and teams spend time rewriting subject lines and messaging before checking whether the mail was actually reaching inboxes at all. Running through domain and authentication status first rules out the structural causes before spending time on the content causes, which are genuinely harder to diagnose and easier to misdiagnose when a structural issue is the real cause.

Why this is a deliverability checklist, not just a sales one

Everything on this list affects whether mail reaches an inbox, independent of how good the outreach strategy itself is. A well-targeted, well-written campaign sent from an unwarmed domain with broken DKIM will underperform for reasons that have nothing to do with the strategy, and no amount of message-level iteration fixes a structural sending problem.

Running this checklist as a recurring habit, not a one-time gate

Treat this list as something to run before every new campaign on a given domain, not just the first one. A domain that passed every check at launch can still develop a problem weeks later — a DNS change that broke DKIM, a sending platform limit that changed, a list segment that went stale — and re-running the structural checks before each major send catches that drift before it shows up as a mysteriously underperforming campaign.

Keeping the checklist with the team that owns content, not just the one that owns infrastructure

A common failure mode is the checklist living with whoever manages the domain and sending infrastructure, while the team writing campaigns and hitting send has no visibility into whether it was actually run. Sharing a simple pass/fail status on this checklist with whoever is about to launch a campaign — not just the technical owner — closes that gap and avoids a launch happening on the assumption that someone else already checked.

MailPilot handles the domain and mailbox readiness side of this checklist directly — ramping volume, checking SPF, DKIM, and DMARC, and tracking real per-provider placement — so that if a campaign underperforms, the structural causes have already been ruled out before you start debugging content.