Cold Email Infra Setup: The 30-Day Plan We Use for Every New Client

Every outbound program starts with infrastructure. Skip this step and nothing that follows matters -- your emails land in spam, your domains get burned, and you waste months troubleshooting what should have been prevented. We have onboarded dozens of clients over the past two years. The infrastructure build is the same every time.

Here is the exact 30-day plan we execute for every new client, day by day. Not theory. Not best practices. The actual steps, in order, with the exact timing that works.

What Is the Infrastructure Math?

Before buying anything, figure out how much email you need to send. The formula is simple. Take your target emails per day. Divide by 30 -- that is the maximum sends per mailbox per day. That gives you the number of mailboxes. Divide mailboxes by 3 -- that is how many you run per domain. Now you have your domain count.

Example: you want to send 1,000 emails per day. 1,000 divided by 30 equals 34 mailboxes. 34 divided by 3 equals 12 domains. That is 12 domains and 34 mailboxes to hit 1,000 daily sends without burning anything.

Monthly cost includes Google Workspace at $6/mailbox/month plus domain registration amortized over 12 months. It does not include your sending platform (Instantly, SmartLead, or similar), which runs $30-200/month depending on tier and volume.

Days 1-3: How Do You Choose and Buy Sending Domains?

Never send cold email from your primary domain. This is the single most common mistake we see. If your company domain gets flagged for spam, your entire organization's email -- including client communication, invoices, and support -- goes down with it. Alternate sending domains protect your primary domain completely.

Buy domains that look related to your brand but are clearly separate. The pattern we use: {brand}hq.com, get{brand}.com, {brand}team.com, try{brand}.com, use{brand}.com, {brand}app.com. For a company called Acme, that would be acmehq.com, getacme.com, acmeteam.com, and so on. Buy 10-15 at once. They cost $10-15 each on Namecheap, Cloudflare, or Porkbun.

Days 2-4: What DNS Records Do You Need?

DNS authentication is what tells receiving mail servers that your emails are legitimate. Without it, Gmail, Outlook, and every corporate mail server will treat your messages as suspicious. Three records are mandatory: SPF, DKIM, and DMARC. A fourth -- a custom tracking domain -- is required if you want open or click tracking without damaging reputation.

DNS propagation takes 24-48 hours. Set records on day 2 and verify them on day 4. Do not skip the verification step. We check every domain's DNS with mail-tester.com and Google's Postmaster Tools before moving forward. One misconfigured record can tank deliverability for the entire domain.

Days 3-5: How Do You Provision Mailboxes?

Google Workspace is the standard for cold email infrastructure. $6 per mailbox per month. You get Google's sending reputation, native DKIM support, and compatibility with every sending platform. Microsoft 365 works too, but Google Workspace has better deliverability in our testing across 100+ domains.

Create 3 mailboxes per domain. Use real-looking names that match your team or plausible variations: firstname@, first.last@, first@ -- something like sarah@acmehq.com, sarah.chen@acmehq.com, alex@acmehq.com. Avoid names that scream automation: sales@, outreach@, team@. Spam filters pattern-match on these.

1. 1Set a profile photo on each Google account. Blank profile photos are a spam signal and reduce reply rates. Use professional headshots -- stock photos are fine.
2. 2Add an email signature with name, title, company name, and a link to a real website. Keep it simple. No banners, no social icons, no images.
3. 3Put a basic one-page website on each sending domain. A simple landing page with your company name, a sentence about what you do, and a contact form. Spam filters check whether the sending domain resolves to a live website.
4. 4Enable two-factor authentication on every mailbox. Google flags accounts without 2FA as higher risk for abuse.

Days 4-7: How Do You Connect to a Sending Platform?

Your sending platform -- Instantly, SmartLead, EmailBison, or similar -- is the engine that actually sends campaign emails and manages warmup. On days 4-7, connect all provisioned mailboxes and verify everything shows green before enabling warmup.

1. 1Add each mailbox to your sending platform via SMTP/IMAP credentials or OAuth connection. OAuth is preferred where supported -- fewer connection issues.
2. 2Verify DNS records show green in the platform's health check dashboard. Every platform has one. Red SPF or DKIM means your DNS is misconfigured or has not propagated yet.
3. 3Set the daily campaign send limit to 0 on every mailbox. During warmup, you send zero campaign emails. The platform only sends warmup emails. This is critical -- do not skip it.
4. 4Enable warmup on every connected mailbox immediately after verification passes.

If any mailbox shows a red health check, do not proceed. Fix the DNS or reconnect the account. Sending from a misconfigured mailbox during warmup poisons that mailbox's reputation from day one. It is faster to fix it now than to recover a damaged sender reputation later.

Days 4-21: How Does Warmup Work?

Warmup is the process of building sender reputation before sending campaign emails. Your sending platform sends emails between your mailboxes and a pool of other warmup accounts. These emails get opened, replied to, and marked as important -- all signals that train Gmail and Outlook to trust your mailbox.

The ramp is gradual. Days 1-7: the platform sends 5-10 warmup emails per mailbox per day. Days 8-14: it ramps to 15-20 per day. Days 14-21: it hits 25-30 per day. By the end of week 3, each mailbox has sent and received hundreds of positive-signal emails. Its sender reputation is established.

Do not send campaign emails during warmup. This is the hardest advice to follow because it means 2-3 weeks of waiting with nothing to show. But teams that skip or shorten warmup pay for it immediately. Spam rates triple. Mailboxes get flagged. Domains get burned. Then you are starting over from scratch, except now your domains carry negative reputation.

Days 7-14: What Should You Build While Waiting?

Warmup is dead time for infrastructure but productive time for everything else. Two weeks is enough to build your entire campaign foundation so you are ready to send the moment warmup completes.

• Define your ICP with signal-based filters, not just job titles and company size. What event or behavior makes someone a good prospect right now?
• Build your target account list. 500-1,000 accounts is a solid starting point for month one.
• Run contact enrichment and email verification. Every contact needs a verified email (BounceBan score 97+, deliverable result) before it touches a campaign.
• Write 2-3 copy variants for A/B testing. Situation-naming openers, not generic questions. 70 words max for the first email.
• Set up CRM integration so replies and meetings flow directly into your pipeline without manual entry.
• Build your unsubscribe process. CAN-SPAM compliance is not optional.

By day 14, you should have a verified contact list, approved copy variants, CRM connected, and warmup scores climbing past 70. When warmup finishes on day 21, you can move to test sends immediately instead of scrambling to build lists and write copy.

Days 21-25: How Do You Run Test Sends?

Before sending to real prospects, send 10-20 test emails from each mailbox to seed accounts you control. Use personal Gmail, Outlook, and Yahoo accounts. Also test with corporate Google Workspace and Microsoft 365 accounts if you have access -- corporate filters behave differently than consumer ones.

1. 1Send test emails that match your actual campaign copy -- not 'test 123' but the real first-touch email with real personalization variables.
2. 2Check every test in the recipient's inbox. Did it land in Primary, Promotions, or Spam? If any land in Promotions or Spam, do not proceed.
3. 3Run your sending domain through mail-tester.com. Score should be 9+ out of 10. Below 8 means something is misconfigured.
4. 4Check Google Postmaster Tools for any domain reputation warnings. New domains should show 'None' (not enough data) -- that is fine. 'Low' or 'Bad' means a problem.

If anything lands in spam: stop. Debug before proceeding. The most common causes are a missing DMARC record, warmup scores below 90, the sending domain having no website, or the copy containing spam trigger words (free, guarantee, limited time). Fix the issue, wait 48 hours, and retest.

Days 25-30: How Do You Ramp to Production Volume?

Production ramp is gradual, not a switch. Start at one-third of your target volume and step up over five days. This gives receiving mail servers time to adjust to your new sending patterns without flagging you as sudden bulk sender.

If your bounce rate exceeds 2% at any point during the ramp, pause immediately. High bounces mean your contact data has quality issues -- run every remaining contact through BounceBan verification before resuming. A 5%+ bounce rate can damage domain reputation in a single day.

What Does Ongoing Maintenance Look Like?

Infrastructure is not set-and-forget. Domains degrade over time. Mailboxes accumulate negative signals. Sending platforms change their warmup algorithms. Weekly maintenance is what separates programs that sustain results from programs that peak in month 2 and crash in month 4.

We manage 100+ sending domains across our client base. Every domain gets a weekly health check. When a domain starts showing declining inbox placement -- even if it has not been blacklisted -- we retire it and rotate in a fresh one. The replacement takes 3-4 weeks to warm up, which is why you always want 10-15% more domains than you strictly need. Redundancy is not waste. It is continuity.

How Much Does This All Cost?

The total infrastructure cost surprises most people -- it is lower than they expect. The expensive part of outbound is not the infrastructure. It is the data, the copy, and the time to manage campaigns. Infrastructure is a fixed cost that scales predictably.

That is $270-470 per month to send 20,000+ verified cold emails. If you book even 5 meetings from that volume, your cost per meeting from infrastructure alone is $55-95. The rest of your cost per meeting comes from data enrichment, copy generation, and campaign management time -- which is where most teams either invest heavily or hire an agency.

What Are the Most Common Infrastructure Mistakes?

We have audited dozens of cold email setups that were underperforming. The same mistakes show up repeatedly. Avoid these and you are ahead of 80% of teams running outbound.

1. 1Sending from your primary domain. One spam flag and your entire company email goes down. Use alternate sending domains exclusively.
2. 2Skipping warmup or cutting it short. 14 days minimum, 21 recommended. Every day you skip costs you weeks of recovery later.
3. 3Running more than 30 emails per mailbox per day. The math is tempting -- why not 50? Because spam filters are watching volume per sender, and 30 is the threshold where things break.
4. 4No website on the sending domain. Spam filters check this. A domain that resolves to nothing looks like a throwaway spam domain. Put up a one-page site.
5. 5Ignoring bounce rates. A 5% bounce rate seems small until it gets your domain blacklisted. Monitor after every batch and hard-stop at 2%.
6. 6Using generic mailbox names like sales@, team@, or outreach@. These pattern-match to known spam senders. Use real human names.
7. 7Setting DMARC to p=reject on a new domain. Start with p=none to monitor, then move to p=quarantine after 30 days of clean data.

What Does the Full 30-Day Timeline Look Like?

Here is every step compressed into one view. Print this out or save it as a checklist. Every new client engagement at our agency starts with this exact timeline.

Thirty days from kickoff to production volume. It is not fast. But every team we have seen try to compress this timeline has paid for it in burned domains, blacklisted IPs, and months of recovery time that far exceeded the weeks they tried to save. Do it right once.