GrowthStackAdvisory
Book 30 min

GrowthStack Advisory / Resources / Cold email infrastructure setup

Cold email infrastructure: my playbook for US, EMEA and APAC

The short answer

Protect your domain, start with low volumes, and scale based on positive replies, not the number of emails sent. For a new outbound program, start with 2–3 secondary domains that clearly represent your business and 2–3 mailboxes per domain on Google Workspace or Microsoft 365, and keep your primary company domain for regular business communication. Set up SPF, DKIM and DMARC before any campaign. Start at 5–10 cold emails per mailbox per day and work up to 20–30 per mailbox per working day while deliverability and engagement stay healthy. Three domains with two mailboxes each can eventually support around 120–180 cold emails per working day.

Infrastructure gets your email accepted. Relevance gets your email answered.

Shobhit Gupta, founder of GrowthStack Advisory

By Shobhit Gupta

Founder, GrowthStack Advisory. Has built and managed SDR teams across the US, Europe, the Middle East and Asia, at Locus, GoComet and Landmark Group. LinkedIn.

· Updated · 14 min read

Cold email performance starts before the first email is sent

Having built and managed SDR teams across the US, Europe, the Middle East and Asia, one thing I’ve learned is that cold email performance starts long before the first email is sent.

Most teams spend too much time discussing subject lines, AI personalization and sending tools. Very few spend enough time getting their email infrastructure right.

My approach is simple: protect your domain, start with low volumes, and scale based on positive replies, not the number of emails sent.

The sequence that fails is familiar. Somebody buys a sequencing tool, connects a mailbox, uploads a list and starts sending. Replies are thin, so volume goes up. Deliverability degrades quietly, because nothing announces it, and by the time anyone notices the pattern the domain has a reputation problem that takes longer to repair than it took to create. Everything below is the specification GrowthStack works to when a company is opening a new market, most recently for a diagnostics equipment manufacturer entering the United States.

1. How I set up domains and mailboxes

For a new outbound program, I generally recommend:

My preferred steady-state volume is 20–30 cold emails per mailbox per working day, provided deliverability and engagement remain healthy.

These are my conservative operating benchmarks, not email provider limits or guarantees.

A starting sending estate: the primary company domain kept for regular business email, and three secondary sending domains with two mailboxes each, every mailbox at 20 to 30 cold emails a day, about 120 to 180 a day in total
Three secondary domains with two mailboxes each. The primary domain carries no cold outreach. Domain names are examples.

Why the primary domain stays out of it

Cold outbound generates spam complaints even when it is done carefully. If you send from your primary domain, the reputation damage attaches to the domain that also sends invoices, contracts, support replies and password resets, and the first sign is often the finance team’s email going to spam. Secondary sending domains are consumable assets: if one is damaged beyond repair, it gets retired and replaced, which is a manageable event for a sending domain and a serious one for the company’s.

Google Workspace or Microsoft 365

Either works when it is configured properly. The one real consideration is where your buyers read their mail, since provider-to-provider delivery is the path being tested, and running a mix across the domains avoids concentrating the whole sending reputation with one provider. Either way, these are properly licensed business mailboxes on domains you control, with authentication configured per domain.

2. SPF, DKIM and DMARC are non-negotiable

Before launching any campaign, I check three things.

SPF: Identifies which email servers are authorized to send emails for your domain.

Example for a Google Workspace-only setup:

v=spf1 include:_spf.google.com ~all

DKIM: Digitally signs your emails so receiving servers can verify authenticity. I prefer 2048-bit DKIM keys where supported. Generate the record through your email provider.

DMARC: Tells receiving servers how to handle messages that fail authentication and alignment checks.

A monitoring-stage example:

v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

The reporting address must be configured. Once legitimate senders are verified, I move toward p=quarantine and eventually p=reject.

Also check MX records, TLS, domain alignment, and any required sending-provider DNS settings. Never blindly copy SPF records across multiple providers.

SPF, DKIM and DMARC set up before any campaign, then DMARC tightened from p=none to p=quarantine to p=reject once every legitimate sender is verified
The three records come first. DMARC then moves from monitoring to enforcement in two steps.

Google documents each record for Workspace: SPF, DKIM and DMARC. Microsoft 365 uses a different SPF include and two DKIM CNAME records, and both setups, with the three SPF mistakes that cause silent failures, are in the cold email deliverability checklist.

3. How many emails should you send?

StageCold emails per mailbox/day
Week 15–10
Week 210–15
Week 315–20
Week 4 onward20–30

This is a starting framework, not a fixed ramp. If the mailbox is new, the recipient data is weak, or delivery errors appear, slow down.

Cold emails per mailbox per day: 5 to 10 in week 1, 10 to 15 in week 2, 15 to 20 in week 3, and 20 to 30 from week 4 onward
The four-week ramp per mailbox.

With three domains and two mailboxes per domain, a healthy setup could eventually support around 120–180 cold emails per working day.

I’d rather send 120 relevant emails than 1,000 generic ones.

That is also why the mailbox count follows from the volume the motion needs, divided by a conservative rate per mailbox. Volume per mailbox is the most common self-inflicted deliverability wound, and more mailboxes exist to keep the volume on each one low.

Interactive tool

Cold email sending capacity planner

Enter the cold emails you need each working day and the region. It works out the mailboxes and secondary domains, using Shobhit’s steady-state ranges, and what the setup can send in each week of the ramp.

Steady-state ranges and the ramp are Shobhit Gupta’s conservative operating benchmarks from the playbook above. Slow down if the mailbox is new, the data is weak or delivery errors appear.

4. What if you don’t have an email warm-up tool?

I don’t believe automated warm-up tools are mandatory.

My preferred approach is to build legitimate sending history:

Avoid fake conversations, automated warm-up networks and sudden volume spikes.

A simple way to test authentication before the first send is to email a Gmail address and open Show original: SPF, DKIM and DMARC should each show PASS. What to watch each week while the history builds is in the weekly monitoring checks.

5. Regional differences: US vs EMEA vs APAC

The technical infrastructure remains broadly the same. What changes is the regulatory environment, buyer behavior and outreach strategy.

RegionMy starting volume per mailbox/dayMy approach
US20–30Direct, problem-led messaging with a clear business reason
EMEA10–20More targeted outreach, stronger privacy checks and country-specific segmentation
APAC10–25Localized messaging, careful market selection and more relationship-led follow-up

These volumes are my suggested testing ranges, not regional sending limits.

Suggested starting volume per mailbox per day by region: US 20 to 30, EMEA 10 to 20, APAC 10 to 25
Starting ranges by region, with the approach that goes with each.

US: Cold B2B email can work well when the targeting is specific and the offer is relevant. Follow CAN-SPAM requirements, including truthful identification and a functioning opt-out. The FTC’s CAN-SPAM compliance guide is explicit on the point: “The law makes no exception for business-to-business email.”

EMEA: Don’t treat Europe and the Middle East as one regulatory market. GDPR, UK PECR and national marketing rules need to be checked by country. B2B does not automatically mean unrestricted cold emailing.

APAC: Singapore, Australia, India and Southeast Asian markets have different privacy and electronic marketing rules. Check consent requirements, local exemptions and unsubscribe obligations before launching. Singapore’s rules sit in the Spam Control Act 2007, and Australia’s regulator sets out sender obligations under the Spam Act 2003 in avoid sending spam.

Across all three regions, I prefer sending during the prospect’s local business hours and using locally relevant examples.

How this plays out market by market is in B2B lead generation for the US, B2B lead generation in the UAE and go-to-market for logistics in Southeast Asia.

6. Metrics I monitor

I don’t use open rates as the primary performance metric. Privacy features and automated email scanning make them unreliable.

Cold email metrics in order: hard bounces below 2 percent and ideally below 1 percent, spam complaints near zero, positive replies by ICP, region and angle, qualified meetings, and pipeline. Open rate is not a primary metric.
The five numbers, from accepted to pipeline.

For spam complaints, Google’s email sender guidelines ask senders to keep the rate reported in Postmaster Tools below 0.3%, ideally below 0.1%. Laying these numbers out for SDRs, managers and leadership is covered in how to build a go-to-market reporting dashboard.

7. What doesn’t work anymore

My rule is straightforward: Infrastructure gets your email accepted. Relevance gets your email answered.

If your cold email engine isn’t performing, don’t immediately buy another sending tool. Audit your domains, data, targeting, messaging and reply handling first.

A pipeline audit covers that review end to end. Where AI fits, and where a person still reviews every message, is in how AI BDR tools can streamline your SDR process.

Data, verification and the suppression list nobody builds

Three components, and the third is the one routinely skipped.

Suppression is the least interesting item on any infrastructure list and the one whose absence causes the most avoidable damage. Build it before the first send, because retrofitting it means reconciling records across several tools after the fact.

One product, several motions

This is the part of the build that is strategy rather than plumbing, and it is where most infrastructure-first programs still fail.

The manufacturer above sells the same imaging equipment into markets that have almost nothing in common. Clinical and veterinary buyers care about throughput, image quality and patient workflow. Industrial inspection buyers care about detecting defects in components, compliance and inspection cycle time. And a third group is neither: the existing installed base, who already own the equipment and are candidates for upgrades or a service contract, and who need a completely different conversation because they are already customers.

The tempting approach is one campaign describing the equipment, sent to everybody. It underperforms with all three, because a message written to work for a vet clinic and an industrial inspection lab is necessarily written about the product rather than about either buyer's situation.

So the outbound is separated into distinct motions from the start: different lists, different messaging, different sequences, tracked separately. The infrastructure supports this directly, because separate mailboxes and domains make it straightforward to keep motions isolated and to see which one is producing replies and which one is producing complaints. That is also why segmentation appears in the setup phase rather than being treated as an optimization to do later. Deciding it afterwards means rebuilding the lists.

The general method for defining those segments is in ICP, persona and messaging and the B2B ICP framework.

Reply routing and reporting

Two things that get postponed until the first campaign is live, at which point they are urgent.

Reply routing decides what happens when someone answers. Across six mailboxes on three domains, replies arrive in six places. Without a defined route into one inbox with one owner, the interested replies sit unread next to the out-of-offices, which wastes the only outcome the whole build exists to produce. The standard worth holding is a first response within one business hour, measured in the buyer's working day, which is covered in speed to lead.

Reporting has to run per mailbox and per domain, not only per campaign. Campaign-level reporting tells you whether the message is working. Mailbox-level reporting tells you whether the infrastructure is degrading, and those fail independently. A campaign with a healthy reply rate on five mailboxes and a quiet problem on the sixth looks fine in aggregate right up until it does not.

What it costs to run, and whose name it is in

For a build of this shape, third-party costs come to roughly $250 a month: domains, mailbox licenses, a sequencing tool, a data source and email verification. The exact figure moves with the final mailbox count and how much data the program consumes.

The more important point is whose name those accounts are in. At GrowthStack, third-party software, data, domains and email infrastructure are paid for by the client and stay with the client. The reason is not administrative. A sending estate takes weeks to build and accumulates reputation over months, and if it is registered to whoever ran your outbound then ending that relationship means starting the warm-up clock again from zero. Infrastructure held in the client's name is the difference between changing supplier and rebuilding.

That is separate from the cost of the work itself, which is set out on the pricing page and on the cold email infrastructure setup service page.

Why this splits into two phases

The build and the running of it are different jobs with different shapes, and combining them into one commitment obscures both.

Phase one is the setup above: domains, mailboxes, authentication, warm-up, data, verification, suppression, segmentation, the first messaging architecture, reply routing and reporting. It has a defined end, and the output is an asset the client owns whatever happens next.

Phase two is running it: account and contact research against the agreed ICPs, list building and hygiene, copywriting and sequencing, execution and optimization, mailbox and deliverability monitoring, reply management, follow up, qualification, handing over meetings, and reporting on what is working.

A ninety day initial engagement is the recommendation, and warm-up is the reason. The configuration takes days. The reputation-building cannot be compressed, because it is observed by mailbox providers rather than completed by you. Ninety days leaves enough room to build correctly, test the market properly, find which segment and message actually work, and then put volume behind the one that does. Anything shorter tests the infrastructure rather than the market.

References

The rules this build has to satisfy, including the Google, Yahoo and Outlook bulk sender requirements, are in the cold email deliverability checklist. What goes into the sequences once the domains are ready is in outbound sequence structure, and the full ninety day shape is in the outbound 90 day plan.

For the engine this sits inside, see B2B lead generation services, and for having it built, cold email infrastructure setup as a service.

Frequently asked questions

How many domains and mailboxes do you need for cold email?+

For a new outbound program, Shobhit Gupta starts with 2 to 3 secondary domains that clearly represent the business and 2 to 3 mailboxes per domain, on Google Workspace or Microsoft 365. The primary company domain stays for regular business communication. Three domains with two mailboxes each can eventually support around 120 to 180 cold emails per working day.

How many cold emails can you send per mailbox per day?+

Start at 5 to 10 a day in week 1, then 10 to 15 in week 2, 15 to 20 in week 3, and 20 to 30 from week 4 onward, provided deliverability and engagement remain healthy. These are conservative operating benchmarks, not provider limits. Slow down if the mailbox is new, the data is weak or delivery errors appear.

Do you need an email warm-up tool?+

Shobhit Gupta does not consider automated warm-up tools mandatory. He builds legitimate sending history instead: test authentication before outreach, start with real, relevant conversations at low volume, and increase volume only while bounces, complaints and delivery errors stay low. Avoid fake conversations, automated warm-up networks and sudden volume spikes.

What SPF, DKIM and DMARC records do you need for cold email?+

An SPF record listing the servers allowed to send for the domain, such as v=spf1 include:_spf.google.com ~all for a Google Workspace-only setup; a DKIM key generated by your email provider, 2048-bit where supported; and a DMARC record starting at v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com, moving to p=quarantine and then p=reject once legitimate senders are verified.

Is cold email different in the US, EMEA and APAC?+

The infrastructure is broadly the same. The rules and buyer behavior change. In the US, follow CAN-SPAM, which covers business-to-business email. In Europe and the Middle East, check GDPR, UK PECR and national rules country by country. In APAC, Singapore, Australia, India and Southeast Asian markets each have their own privacy and electronic marketing rules. Shobhit tests 20 to 30 emails per mailbox per day in the US, 10 to 20 in EMEA and 10 to 25 in APAC.

Should you send cold email from your main company domain?+

No. Keep the primary company domain for regular business communication and send cold email from secondary domains that are legitimate, recognisable variations of your brand. Cold outbound generates spam complaints even when it is done well, and reputation damage on the primary domain affects invoices, support replies, contracts and everything else the business sends.

What does cold email infrastructure cost to run?+

For a setup of this shape, roughly $250 a month in third-party costs covering domains, mailbox licenses, a sequencing tool, a data source and email verification. The exact figure moves with the final mailbox count and data requirements. At GrowthStack these are bought in the client’s name and stay with the client.

Written with AI assistance from Shobhit Gupta’s notes and client work, then reviewed and edited by Shobhit Gupta on .