Cold Email Infrastructure for Startups: What to Set Up Before You Send
A recurring post in r/coldemail is titled, almost word for word, "I need help in setting up a cold email infrastructure". Nearby threads ask Instantly vs Smartlead, what the best warmup tool is right now, and whether cold email scales worse operationally than people admit.
Pramod Kumar, co-founder of Kingdom of Kumar. On X
·
Aaron Shepherd's joke on X, from 23 October 2026, is the same point in three lines: "2024: i need a great offer and good infra to fix my outbound / 2026: i need Claude Code and a GTM engineer / 2028: i need a great offer and good infra." Tools rotate. Infrastructure and the offer keep coming back.
This article is the setup work to do before you send, not a promise that you will "land in the inbox." I will not invent a safe daily volume or a warmup vendor ranking. I will point you at the mailbox providers' own rules, which are the only rules that matter, and at a conservative build order. A longer operational checklist is in Email deliverability checklist for startups. Sequencer choice is in Instantly vs Smartlead.
"I need help in setting up a cold email infrastructure"
Start with the job, not the logo. Infrastructure, here, means: the domains you send from, the DNS that proves you are allowed to send, the mailboxes, the way you warm and ramp, the way you suppress bounces and complaints, and the person who watches those numbers. A sequencer is one piece of that. It is not the system.
If you do not yet have an offer that has earned a conversation when a real buyer hears it, stop. Good infrastructure will not fix a weak offer. If you are still launching, use the App Launch Score and talk to users first.
What to set up, in order
1. A sending domain that is not your primary domain.
If your company site is `example.com`, do not start cold outreach from `hello@example.com`. Use a close variant you actually control, and put a simple site or redirect on it so it does not look like a shell. Keep the primary domain for people who already know you. I will not prescribe an exact number of domains. Start smaller than you think, because each domain is something you have to authenticate, warm and watch.
2. Authentication: SPF, DKIM and DMARC.
These are not optional decorations. Google publishes current email sender guidelines and bulk sender requirements. Microsoft publishes current guidance on email authentication in Microsoft 365. Read the pages on the day you set this up. Requirements have already tightened once in the last few years, and I will not paste a snapshot that will go stale.
In plain language: SPF says which servers may send for the domain, DKIM signs the message, DMARC says what to do when a message fails. All three should be in place before you send anything you care about. Use a unique alignment setup your provider documents, and then send yourself test messages to confirm the headers look right.
3. Mailboxes that look like people, used like people.
Create real mailboxes, with a real name, a real reply path, and a signature that matches the company. Do not share one mailbox across a team as a firehose. Decide who reads replies. A mailbox nobody checks is how you miss an unsubscribe and a buying question on the same afternoon.
4. A warmup and a ramp, not a blast.
Warmup means the mailbox sends and receives ordinary mail, gradually, before (and usually while) you do outreach, so it does not go from zero to a campaign on day one. There are tools for this. I will not name a winner; that r/gtmengineering thread is full of competing claims, and the honest ones say the sending platform, list quality and authentication matter more than the warmup brand. Ramp means you increase outreach slowly and you stop if bounces or complaints jump. If a vendor sells you "pre-warmed inboxes" as a shortcut around this, be sceptical and read the deliverability checklist.
5. List quality in front of the send button.
Verify emails. Suppress role addresses you do not intend to write to. Remove known bounces. A beautiful domain will not survive a dirty list. See How to build a B2B list without paying for bad data.
6. A sequencer that you can take data out of.
Instantly, Smartlead and others can all send. Pick one you can authenticate, monitor, and export. Do not lock a list in a tool you cannot leave. Set complaint and bounce thresholds so sending pauses when something is wrong.
7. A weekly watch.
Look at bounce rate, complaint rate, and whether mail is being rejected. Look at replies that say "unsubscribe" or "how did you get my address." Fix the list or pause. This is the "scales worse operationally than people admit" problem: the work does not end at setup.
What I would not do in week one
- Buy twenty domains and twenty mailboxes "for scale"
- Send from your primary corporate domain "just to test"
- Skip DMARC because a YouTube video said it can wait
- Import a 20,000-row file you have not sampled
- Let an AI SDR send on a domain you have not ramped
- Pay for a deliverability miracle service that will not show you the headers
A first outbound motion can be small and still be professional. Your first outbound motion in 30 days assumes this setup is in place, not the other way around.
A simple pre-flight checklist
- [ ] Secondary sending domain(s) purchased and DNS under your control
- [ ] SPF, DKIM, DMARC published; test messages confirm them
- [ ] Mailboxes named, signatures set, replies go to a person
- [ ] Warmup underway; outreach not blasted on day one
- [ ] First list verified; sample of 20 checked by a human
- [ ] Sequencer connected; opt-outs and bounces will stop the send
- [ ] You have read Google's and Microsoft's current sender pages this week
- [ ] You know who pauses sending if the numbers move the wrong way
How this fits with GTM engineering
This is unglamorous work, and it is part of the job. A GTM engineer who only talks about agents and Clay, and cannot tell you how mail is authenticated, is not ready to run outbound. At Kingdom of Kumar we build and run the wider system on Grok and Claude for $500 a month, with a three-month minimum, and we treat infrastructure as a precondition, not a footnote. You own the domains and you approve what goes out. If you want someone to "just hit send," we are the wrong team. More on the practice is on GTM engineering.
FAQ
How many emails can I send per mailbox per day?
I will not invent a number. It depends on the domain's age, the provider, the list, and current enforcement. Start lower than the figure you will hear in a sales call, and follow the mailbox provider's own guidance.
Can I use Google Workspace or Microsoft 365 for cold outreach?
Read their current terms and sender rules before you do. Some teams use them for replies and a specialist sending setup for first-touch outreach. Do not assume a paid seat is a licence to run a campaign.
Do I need a warmup tool if my sequencer has warmup built in?
Often the built-in one is enough to start, if authentication and list quality are right. A second tool is not a substitute for those.
When is infrastructure "done"?
It is never done. It is ready enough to send a small, verified, approved batch when authentication is in place, warmup has started, and someone is watching bounces. Then you keep watching.