Email Deliverability Checklist for a First Outbound Domain
Deliverability is the unglamorous half of outbound, and it is where a lot of "we tried cold email" stories actually end. A thread on r/gtmengineering asked, honestly, what the best warmup tool is right now. Another, on r/emaildeliverability, asked about safe volume on pre-warmed inboxes. Underneath both is a plainer observation from r/coldemail: "Cold email scales worse operationally than people admit."
Pramod Kumar, co-founder of Kingdom of Kumar. On X
·
I will not name a winning warmup tool, and I will not invent a safe daily volume. Those answers go stale, and they depend on your domain, your copy, and how you earned the right to send. I will give you a checklist, the public rules that actually bind you, and a way to grow volume that does not treat inboxes as a video game.
The longer setup path is in Cold email infrastructure for startups. How the first month should feel is in Your first outbound motion in 30 days. Replies have their own piece: How to handle cold email replies. The work around this sits on GTM engineer and GTM engineering.
If the product is not ready to sell, do not warm a domain so you can find that out the hard way. Take the App Launch Score first.
The rules that are not folklore
Before a tool recommendation, read the current sender documentation.
Google publishes email sender guidelines and bulk sender requirements. Microsoft publishes guidance on email authentication in Microsoft 365. Those pages change. Read them in the week you set this up, not from a screenshot in a Twitter thread from last year.
In plain language, you should expect to need:
- A domain you control, preferably one you will use for outbound rather than your only corporate domain
- SPF, DKIM, and DMARC actually aligned, not "we ticked a box in the sequencer"
- A way to honour unsubscribe and bounce handling
- Honest identification, not a display name that pretends to be someone else
I am paraphrasing. The vendor documentation is the source, and it wins if this article and the pages disagree later.
A checklist for the first outbound domain
Print this. Tick it in order.
Domain and identity
- [ ] You have chosen a sending domain and you know why it is not (or is) the primary company domain
- [ ] You can log into the registrar and DNS, in the company's name
- [ ] SPF, DKIM, and DMARC are published and pass a real test send to a Gmail and a Microsoft inbox you control
- [ ] The From name and address would look reasonable if the recipient forwarded the mail to a colleague
- [ ] You have a visible way to unsubscribe, and it works
Infrastructure
- [ ] Mailboxes are company-owned, not a freelancer's personal Gmail
- [ ] You know which tool is allowed to send, and it is not three tools at once
- [ ] Bounce handling is on; failed addresses are taken out of the queue
- [ ] You have a place to see complaints and to stop a campaign by hand in minutes
- [ ] Tracking choices (open pixels, wrapped links) are deliberate, not the vendor default you never looked at
The list and the copy
- [ ] You are sending to people you decided were a fit, not to a scraped dump
- [ ] Emails were verified; failed rows did not sneak into the sequencer
- [ ] First lines refer to something you can point at, or they stay plain
- [ ] You would be willing to receive the message
- [ ] Volume for the first days is conservative, even if a vendor dashboard suggests you can "scale"
Operations
- [ ] One person is on the hook for replies the same day
- [ ] A weekly review looks at bounces, complaints, and whether inbox placement still looks sane on test accounts
- [ ] You have written down what you will do if placement drops: stop, inspect, do not add inboxes in a panic
About warmup tools, and pre-warmed inboxes
The warmup question is fair, and I still will not pick a winner in print. Warmup tools can help a new domain look like it has been used, or they can create odd traffic patterns if you treat them as a cheat code. If you use one, watch it the way you would watch any other sending: does it cause strange replies, does it send content you would not associate with your brand, and do you know how to turn it off?
Pre-warmed inboxes, sold as a shortcut, have the same problem as any shortcut that is hard to inspect. You may be buying someone else's reputation, history, and risk. If you cannot see how the mailbox was used, I would not put my company's name on it. I also will not quote a "safe" starting volume for those mailboxes, which was the question in the r/emaildeliverability thread. There is no number I can give you that stays true across providers and weeks.
What I would do instead: set up the domain properly, send a little, to people who should actually get the mail, and grow only when bounces and complaints stay quiet and test placement still looks acceptable. That is slower than a sales page. It is also closer to how this actually works.
"Cold email scales worse operationally than people admit"
This is the line I would pin to the wall. Every new inbox is not just capacity. It is DNS, warmup or careful ramp, a reply path, a place to catch failures, and another thing that can break on a Tuesday. Teams get into trouble when they add inboxes to outrun a copy or list problem, or when they treat "scale" as the goal rather than conversations they can handle.
Operationally, scaling well looks like: a short list of good-fit people, mail that was approved, replies handled by a human, and a domain you are still proud of in month three. It does not look like a dashboard of twenty mailboxes and a model hitting send.
If you already have a placement problem, stop sending, fix authentication and list quality, and only then resume at a lower volume. Adding infrastructure on top of a damaged domain is how a bad week becomes a bad quarter.
A first-two-weeks cadence
Days 1–2: DNS, authentication, test sends to yourself, nothing to strangers.
Days 3–7: a small number of approved, high-fit messages. Watch bounces and test inboxes.
Week 2: slightly more only if week one was clean. Do not add a second domain yet.
Write the actual counts you chose in the Friday note, so you remember them when someone suggests tripling next week.
FAQ
Should I send from my primary domain?
I usually would not start high-volume cold outreach from the only domain that also carries customer and investor mail. A dedicated sending domain, clearly tied to the company, is easier to isolate if something goes wrong. This is judgement, not a regulation.
Do I need a sequencer on day one?
No. A carefully sent batch from a properly set-up mailbox can teach you more than a tool with five steps you have not earned. Add a sequencer when the process is boring in a good way.
What if Google or Microsoft changes the rules?
They will. Recheck the official pages when you change tools, and at least a few times a year. Do not rely on this article as the last word. If you want the boring parts built into a motion you can actually run — domain setup, approvals, a Friday review — Kingdom of Kumar does that for $500 a month, three-month minimum, on Grok and Claude. You own the system and you approve what goes out. We will not promise a placement rate, and we will not sell you a rack of pre-warmed inboxes as a strategy.