Outbound Campaign Launch Checklist: 20 Checks Before You Hit Send

Most outbound campaigns do not fail in week three — they fail before the first email leaves the outbox. A misconfigured DMARC record, a list with 8% bad addresses or a broken merge tag can sink deliverability and burn a domain in days. Pilots run pre-flight checklists precisely because the cost of a missed item is catastrophic and the fix is cheap. This outbound campaign launch checklist gives you the same discipline: 20 checks across infrastructure, list, copy and tracking, run in order, before you hit send.

Infrastructure Checks (1–6)

1. Sending domains are secondary, not primary. Cold volume should never run on the domain your company lives on. Confirm every sending inbox sits on a lookalike domain that redirects to your main site.
2. SPF, DKIM and DMARC all pass. Send a test to a checker (or use your ESP’s validator) and confirm all three authenticate. One failing record is enough to route you to spam — our SPF, DKIM & DMARC setup guide covers the records line by line.
3. Domains and inboxes are warmed. New inboxes need 2–4 weeks of gradual email warmup before campaign volume. Check warmup dashboards show healthy inbox placement, not just sends.
4. Daily sending limits are conservative. Cap each inbox at 20–40 cold emails per day with randomized intervals. Verify the sequencer settings match the plan — defaults are often higher.
5. No blacklist entries. Check sending domains and IPs against major blacklists before launch, not after replies dry up.
6. Custom tracking domain is set. If you track opens or clicks, the tracking domain must be your own subdomain, not the sequencer’s shared default.

List Checks (7–11)

7. Every address is verified. Run the full list through email verification within the last 30 days. Remove invalids entirely and decide deliberately what to do with catch-alls.
8. The list matches the ICP. Spot-check 20 random records against your targeting criteria. If more than one or two miss, the list needs rebuilding, not sending.
9. Suppression lists are loaded. Current customers, open opportunities, competitors, past opt-outs and partner accounts must be excluded. Nothing damages trust internally like cold-emailing a paying customer.
10. Duplicates and colleagues are handled. De-dupe by email and by company; decide how many contacts per account you will touch at once.
11. Merge fields are clean. Sort the sheet by each personalization column and scan for blanks, ALL CAPS names, “LinkedIn” in the company field and similar landmines.

Copy Checks (12–16)

12. Send a live test to yourself and a colleague. Read it on mobile. Check formatting, links, signature and that the merge tags actually merged.
13. Spam triggers are scrubbed. No link-heavy signatures, attachments, image loads or pitch-slap phrasing on the first touch.
14. The subject line earns the open without tricking it. Test it against the rules in our cold email subject lines guide — misleading subjects buy opens and spam complaints together.
15. Every email has one clear ask. One CTA per message. Follow-ups add value (a proof point, a resource) rather than repeating “bumping this up.”
16. Opt-out is present and works. A plain-text opt-out line satisfies compliance and reduces spam complaints. Click it in your test to confirm it functions.

Tracking & Process Checks (17–20)

17. Reply detection is on and routed. Confirm replies stop the sequence automatically and land in a queue someone owns, with an agreed response-time SLA.
18. CRM sync is verified. Send one test lead through and confirm the contact, activity and status update appear correctly.
19. Baseline metrics are defined. Write down the reply rate, positive-reply rate and meetings target you expect before launch, so week-two results are judged against a plan instead of a mood.
20. A kill criterion exists. Decide now what triggers a pause — for example, bounce rate above 3% or a spam-complaint spike — and who has authority to pull the cord.

Make the Checklist a Ritual, Not a Rescue

Run the full list before every new campaign and the infrastructure section weekly, because records drift, blacklists happen and warmup decays when tools change. Teams that treat the pre-launch check as a fixed ritual spend their optimization energy on copy and targeting — the parts that actually win replies — instead of firefighting deliverability. Twenty minutes of checking beats four weeks of rebuilding a burned domain.