Cold Email Infrastructure

Most cold email campaigns fail before the first message is even written. The failure is rarely the subject line, the offer, or the call to action, it is the sending infrastructure underneath all of it: a single shared mailbox handling every campaign, DNS records copied from a five-year-old blog post, and zero warmup before the first blast goes out. Cold Email Infrastructure is the foundation every other Advazon service sits on top of, lead generation, LinkedIn outreach, CRM automation, and none of it matters if the domain sending the emails is already flagged, unauthenticated, or burned.

We treat infrastructure as an engineering problem, not a checklist. Every build starts with a target sending volume and works backward to the exact number of domains, mailboxes, and warmup pace that fits, rather than applying a generic template built for a business with a completely different risk profile. A five-person agency sending 2,000 emails a month and a healthcare company sending 500,000 emails a month across twenty domains need architecturally different setups, and treating them the same is how deliverability problems start.

What Breaks Without Proper Infrastructure

When a business tries to run cold outreach on its primary domain, skips authentication records, or fires hundreds of emails a day from a single inbox, three things happen in a predictable sequence. Open rates collapse first, as spam filters quietly route mail to junk instead of bouncing it outright, which means the sender often doesn’t notice until weeks of campaigns have already gone unseen. Next, the primary domain’s sending reputation takes damage that follows the whole company, not just the outreach team, because mailbox providers score reputation at the domain level. Internal email, invoices, and customer support replies can all start landing in spam alongside the cold outreach that caused the problem. Finally, the domain lands on one or more blacklists, and getting removed typically takes anywhere from a few days to several weeks depending on the list and how the delisting request is handled.

None of this is caused by a weak subject line or a poorly worded offer. It is caused by infrastructure that was never designed to carry the volume being pushed through it, in the same way a garden hose fails if you try to run a fire hydrant’s worth of water through it. We have inherited more than one account where the previous vendor’s fix for declining opens was “send more volume” or “try a new subject line formula,” when the actual problem was DNS records that had never been verified, or a domain that had already accumulated months of spam complaints on a shared IP block.

What We Build

Every build follows the same core discipline regardless of company size: isolate risk away from the primary domain, verify every layer of authentication before a single campaign email goes out, and ramp volume in a way that builds sender reputation instead of burning it. The list below is not a generic checklist, it is the sequence we actually execute, in order, for every client engagement.

• Domain acquisition and DNS setup from day one, on secondary domains that never touch your primary brand domain, so a deliverability issue on the outreach side can never spill over into your main company inbox or marketing email program
• SPF, DKIM, and DMARC configured and verified on every sending domain, not just set once and forgotten, we recheck propagation and alignment before a domain is cleared for warmup, not after problems show up
• Dedicated mailboxes, one purpose per domain, so a single flagged inbox never takes down your whole operation, if one mailbox gets a spike in complaints, the rest of your sending keeps running
• A controlled warmup ramp over 3 to 4 weeks that builds sender reputation gradually before any real campaign volume hits, following a curve rather than a fixed daily number, since mailbox providers respond to patterns, not just totals
• Inbox placement testing across Gmail, Outlook, and Yahoo before your first real send, using seed accounts and placement tools so we catch a filtering problem in testing instead of learning about it from a client’s reply rate
• Full connection into Smartlead or Instantly, with rotation, tracking, and unsubscribe handling configured before launch, so compliance and list hygiene are built in from day one rather than patched in after a complaint

The Build Timeline

Setup and authentication are completed within 7 days of kickoff. That means every domain is acquired, every DNS record is verified, and every mailbox is created and connected to your sending platform inside the first week, with no dependency on you providing anything beyond initial approval on domain names and brand guardrails.

• Days 1 to 2: domain research and acquisition, DNS zone setup, mailbox provisioning
• Days 3 to 5: SPF, DKIM, and DMARC configuration and propagation verification, sending platform connection
• Days 6 to 7: inbox placement testing, seed list checks, warmup schedule finalized and started
• Weeks 2 to 4: progressive warmup with daily monitoring, gradually increasing send volume while tracking bounce rate, spam complaints, and inbox placement
• Week 2 onward: low-volume, monitored live sending can begin while warmup continues in parallel, so you are not sitting idle for a month waiting for the all-clear
• End of week 3 or 4: full volume unlocked once warmup benchmarks are met, timing depends on your target send count

The exact pace flexes with volume and domain count. We would rather extend a warmup schedule by a few days than launch a client into a campaign on a domain that is not ready, because the cost of a burned domain is always higher than the cost of a slower start.

Why This Is Built In-House, Not Templated

Generic “cold email setup” guides assume every business sends the same way. We do not. A healthcare company sending 500,000 emails a month across 20 domains needs a completely different domain architecture, mailbox count, and compliance posture than a five-person agency sending 2,000 emails a month from two domains. Applying the same template to both is how one of them ends up either overpaying for infrastructure they do not need, or under-provisioned and blacklisted within the first month.

Every infrastructure build starts with three questions: what is the target volume, who is the ICP you are emailing, and what compliance requirements apply to your industry, since healthcare, finance, and recruiting all carry different list hygiene and consent expectations than a typical B2B software company. We work backward from those answers to the exact number of domains, mailboxes, and warmup pace that fits, rather than starting from a template and hoping it is close enough.

Common Mistakes We Fix

Most of the infrastructure problems we inherit from previous vendors or in-house attempts fall into a short list of repeat offenders:

• Sending from the primary company domain, which puts the domain’s entire reputation, including internal email deliverability, at risk for the sake of a cold outreach campaign
• Skipping DMARC because it seems optional, when in reality an unverified or missing DMARC record is one of the fastest ways to get flagged under Gmail and Yahoo’s bulk sender requirements
• Warming up too fast, sending real campaign volume within days of setting up a new domain instead of letting sender reputation build gradually
• Running every campaign through a single mailbox, so one bad list or one aggressive send schedule can take down all outreach instead of a fraction of it
• Never testing inbox placement before launch, finding out a domain is landing in spam only after a client asks why reply rates are at zero

Most of these are not hard to fix individually, the problem is that they compound. A domain with no DMARC record, warmed up too fast, sending from a single mailbox, is essentially guaranteed to land in spam or get blacklisted within the first month, and by the time that is diagnosed, the client has usually already lost weeks of pipeline.

Who This Is For

This service fits any B2B company that depends on cold email for pipeline and does not want that channel exposed to a single point of failure. That includes sales teams launching outbound for the first time who need infrastructure built correctly from zero, agencies and consultancies managing outreach on behalf of multiple clients who need isolation between accounts, and established companies whose current sending setup has already run into deliverability problems and needs to be rebuilt rather than patched. It also fits businesses in regulated or reputation-sensitive industries, healthcare, finance, recruiting, where a compliance misstep in list handling or consent can create real risk beyond just a weak open rate.

If you are not sure whether your current setup qualifies as proper infrastructure or a liability waiting to surface, the fastest way to find out is the Email Deliverability Audit, which tells you exactly where you stand before you commit to a full rebuild.

Frequently Asked Questions

How long does it take before I can start sending real campaigns?

Authentication and setup finish within 7 days. Low-volume, monitored sending can begin as early as week two while warmup continues in the background, with full volume unlocked by the end of week three or four depending on your target send count.

Will this affect my company’s main email domain?

No. Every campaign runs on secondary domains built specifically for outreach, so nothing that happens during warmup, testing, or live sending ever touches the domain your company uses for regular business email.

What sending platforms do you support?

We connect infrastructure into Smartlead and Instantly by default, since both give us the rotation, tracking, and unsubscribe handling we need to keep sending compliant. If you are already using a different platform, tell us during kickoff and we will scope compatibility before the build starts.

How many domains and mailboxes will I need?

It depends entirely on your target volume. Each mailbox can safely send a limited daily volume during full warmup, so higher volume targets need proportionally more domains and mailboxes. We calculate the exact number during the kickoff call based on your goals, not a fixed package size.

What happens if a domain gets flagged after launch?

Because mailboxes are isolated by domain, a flag on one domain does not take down the rest of your sending. We monitor bounce rate, spam complaints, and inbox placement continuously after launch, and if a domain needs to be paused, rotated, or rebuilt, that happens without interrupting the rest of your campaign.

Outcome