Email deliverability is infrastructure work, not campaign work, and it routinely adds two to four weeks to a launch timeline. The pre-send checklist covers five items: SPF/DKIM/DMARC authentication, list validation, dedicated IP warmup, CNAME records, and a consent field audit. IT and DNS teams own most of it, which is why marketing teams keep getting blindsided. Confirm the infrastructure is ready before you commit a go-live date.
Email deliverability infrastructure takes two to four weeks to set up, and most marketing teams don't scope it into their project plan. That's the gap. The campaign is built, the audience is segmented, the send date is on the calendar, and then IT comes back with a timeline nobody budgeted for.
This happened in five customer conversations this week. Same pattern every time: a launch date was committed to stakeholders before anyone confirmed the sending infrastructure was ready. By the time the gap surfaced, the date was already public.
The work itself isn't complicated. It's just owned by people outside the marketing workflow, which is why it keeps getting missed.
Marketing teams scope campaign build time. They estimate design, copywriting, segmentation, and testing. They don't estimate the sending infrastructure that has to exist before any of that matters.
Deliverability sits with IT and DNS, not marketing operations. Marketing assumes the infrastructure is ready. IT assumes marketing knows what's required. The launch date slips while both sides wait for the other to raise their hand.
The same pattern shows up in HubSpot migration data quality issues and in HubSpot-Salesforce sync projects. Foundational work gets skipped until it blocks something visible.
Here's what needs to happen before your first email ships, in roughly the order it has to happen.
Domain authentication proves to receiving mail servers that you actually sent the email from your domain. Three DNS records do the work:
SPF (Sender Policy Framework) lists the IP addresses allowed to send mail from your domain. Mail from any other IP looks suspicious to the receiving server.
DKIM (DomainKeys Identified Mail) attaches a cryptographic signature to every message. If the content changes in transit, the signature breaks and the receiving server knows.
DMARC (Domain-based Message Authentication, Reporting and Conformance) sits on top of SPF and DKIM. It tells receiving servers what to do when a message fails authentication, and it sends you reports so you can see what's happening across your domain.
Setup needs DNS access and coordination with your email service provider. The work isn't hard, but ticket queues and approval workflows add days.
For more depth on this, see HubSpot's email authentication guide.
Timeline: 3 to 5 business days.
Validate your list before you import it into your email platform. That means checking for:
A dirty import tanks your sender reputation on the first send. Bounces, complaints, and spam trap hits tell ISPs you aren't managing your list, and that reputation damage follows every email you send after.
Third-party validation services catch these issues before they cost you. The extra step is far cheaper than recovering a damaged sender reputation, and it fits inside the quarterly CRM maintenance that keeps your data clean.
Timeline: 2 to 5 business days.
If your volume justifies a dedicated sending IP, warm it up before you push real volume through it. A new IP has no reputation. ISPs treat it with suspicion by default.
Warmup means ramping sending volume gradually, starting small and building daily. The pattern builds a positive sending history that ISPs recognize and trust.
Skip warmup, and ISPs will throttle or block your mail. You hit delivery problems the moment you need deliverability most.
A typical warmup schedule:
That schedule assumes a clean list and solid content. If either is weak, warmup takes longer.
Timeline: 2 to 4 weeks.
Your email platform needs to send from your domain, not from its own. CNAME records route your email subdomain to your email service provider's infrastructure.
This is more DNS work, which means more coordination with IT. If you're running multiple email platforms or integrations, this step gets harder. Our guide to avoiding integration traps covers how to keep this manageable.
Timeline: 2 to 3 business days.
Audit your consent fields before you send, because opt-in records and subscription-status records often disagree.
One customer this week found that their universal double opt-in rule had cut their marketable database in half. Another found contacts marked as opted in on one system and opted out on another.
Before you send, answer four questions:
This is the kind of problem CRM workflow automation prevents going forward. If you find gaps today, your two options are to fix the data before sending or to run a re-engagement campaign that re-collects consent from the unclear contacts.
Timeline: 3 to 7 business days.
Consent problems surface during the pre-launch audit and need their own plan.
If a meaningful share of your list has unclear or conflicting consent, sending anyway creates compliance risk and damages your sender reputation. Plan a re-engagement campaign instead:
This adds time, but it protects your reputation and keeps you aligned with CAN-SPAM and GDPR.
The full checklist runs two to four weeks, depending on where you start and what the audit uncovers.
Here's a realistic shape for a launch:
Clean list, authenticated domain, and clear consent data can compress this to one or two weeks. Starting from scratch or finding major data issues can push it to four to six weeks.
The point is knowing which path you're on before you set a date. Confirm the infrastructure before you commit, the same way teams should verify HubSpot-Salesforce syncs before assuming data will flow.
The disconnect lives here. The ownership map:
Marketing can't launch until IT finishes DNS work. IT can't finish DNS work until marketing confirms which records are needed. The email service provider can't start warmup until the domain is authenticated.
Make the dependencies explicit. Assign owners. Set deadlines. Treat nothing as ready until someone confirms it, the same way successful workflow automation projects earn buy-in from every department before anyone starts building.
Hand this to your IT team and your stakeholders.
Pre-Launch Deliverability Checklist
Share this with your team to set realistic expectations.
| Task | Owner | Start Date | End Date | Dependencies |
|---|---|---|---|---|
| Consent audit | Marketing Ops |
[Date] |
[Date] |
None |
| Domain authentication | IT |
[Date] |
[Date] |
Consent audit complete |
| List validation | Marketing Ops |
[Date] |
[Date] |
None |
| CNAME configuration | IT |
[Date] |
[Date] |
Domain authentication complete |
| IP warmup (if needed) | Email Provider |
[Date] |
[Date] |
Domain authentication complete |
| Re-engagement campaign (if needed) | Marketing Ops |
[Date] |
[Date] |
Consent audit complete |
| Final testing | Marketing Ops |
[Date] |
[Date] |
All above complete |
| Launch | Marketing Ops |
[Date] |
[Date] |
Final testing approved |
How long does email deliverability setup take before a campaign launch?
Email deliverability setup usually takes two to four weeks. Domain authentication runs 3 to 5 business days, list validation 2 to 5 business days, CNAME records 2 to 3 business days, consent audits 3 to 7 business days, and dedicated IP warmup 2 to 4 weeks. Starting from scratch or finding major data issues can push the total to six weeks.
What are SPF, DKIM, and DMARC, and do I need all three?
SPF, DKIM, and DMARC are the three DNS records that authenticate your email. SPF names the IP addresses allowed to send from your domain. DKIM signs each message so the receiving server can confirm it wasn't altered. DMARC tells receiving servers what to do when a message fails SPF or DKIM. You need all three. Modern inbox providers like Gmail and Yahoo require them for bulk senders.
What is dedicated IP warmup and when do I need it?
Dedicated IP warmup is the gradual ramp-up of sending volume on a new IP address, usually over two to four weeks. You need it any time you move to a dedicated IP, because ISPs treat new IPs with suspicion until they build a sending history. Shared IPs don't need warmup because they already have reputation from other senders.
Why does list validation matter before a campaign launch?
List validation matters because a dirty import damages your sender reputation on the first send. Duplicate addresses, typos, spam traps, and inactive contacts drive bounces and complaints, which signal to ISPs that you aren't managing your list. That reputation hit follows every email you send after, so validating before the first bulk import is far cheaper than recovering later.
Who owns email deliverability in a marketing campaign?
Email deliverability is a shared responsibility. Marketing operations owns the consent audit, list validation, and timeline. IT and the DNS team own the SPF, DKIM, DMARC, and CNAME records. The email service provider configures IP warmup and provides technical guidance. Compliance and legal review the consent strategy. Launch delays almost always come from an unassigned dependency between these groups.
The next time someone asks for a go-live date, hold the answer until you can confirm the infrastructure. Run through five questions:
Any "I don't know" or "not yet" adds two to four weeks to your timeline. That isn't pessimism. That's planning.
Teams that build this into their process stop getting surprised by delays. They set realistic timelines, communicate them, and launch on schedule. If you're coordinating multiple systems or platforms, the same thinking applies to connected apps and integrations across your stack.
Need help building a sustainable CRM and email operations process? Talk to Concept's CRM consulting team about preventing infrastructure delays from derailing your next launch.