Email, SMS and Lifecycle · Cold email infrastructure setup (domains, inboxes, warmup)
Separate sending domains, mailboxes, authentication and a four-week warm-up, built to keep cold outbound off the domain your customers rely on.
About this service
We build cold sending on separately registered domains, never on a subdomain of the one your customers, your invoices and your password resets come from. And we do not send into Israel, Canada or Germany. Israel's Amendment 40 to the Communications Law makes commercial email opt-in, with statutory damages of up to one thousand shekels per message and no requirement to prove loss; CASL and German competition law arrive at similar places by different routes. If your target list lives there, this is not the engagement, and you will hear that before you pay rather than after.
The build:
Two to four registered domains, chosen to be pronounceable rather than clever near-misses of your brand — a lookalike domain is exactly what gets reported to a brand protection service, sometimes your own. DNS at Cloudflare or your registrar, mailboxes on Google Workspace or Microsoft 365, three per domain. SPF, DKIM at 2048 bits, and DMARC published at p=reject on every cold domain from the first day, because these domains have no legitimate third-party senders and no reason to run permissive.
Volume, and why it is low:
Twenty to thirty messages per mailbox per day, and held there. Workspace will permit far more and every vendor selling you volume will encourage it. The binding constraint is not the provider's limit, it is the complaint rate a cold list produces, and mailbox count is the only variable that scales without raising it. We build the number of mailboxes your target list justifies, and we will tell you when your list is too small to need any of them.
Tracking:
Open tracking off. The pixel introduces a redirect host whose reputation you now inherit, it inflates every number that touches it, and on cold mail it correlates with filtering. Click tracking, where you want it, runs on a domain you own that is neither your primary nor the sending domain. Reply detection happens over IMAP rather than through a tracking host.
Warm-up:
Four weeks minimum before the first real send, on a warming network, with the ramp visible to you rather than reported after the fact. We seed against Gmail, Outlook.com and a genuine corporate Microsoft 365 tenant, because placement at a business receiver behaves nothing like consumer Gmail and only one of those is your buyer.
What we refuse:
Spintax. Bulk AI-written opening lines, which land in the same folder as every other tool running the identical trick this quarter. Catch-all domains left in the target list. Scraped contact data from EU sources. Sending from a mailbox on your primary domain for the important accounts, which is where every burned primary domain we have been called to fix began. And we will not hand over infrastructure we have not warmed, because unwarmed domains fail in week one and the failure will look like your copy.
Not included:
Sequence copy, list building, prospect research, and running campaigns. We are infrastructure and deliverability; the outbound motion belongs to you or your agency. We resell no seats and take no commission from any tool we recommend, which is why the recommendation is worth reading.
Who should not buy this:
Teams with nobody actually committed to sending — idle infrastructure degrades, and cold domains left dormant for a quarter are worse than fresh ones. Anyone whose deal size makes a single reply worth a few hundred dollars or less, where the arithmetic does not carry the setup. Anyone pointing this at consumers rather than businesses.
Handover:
Credentials, DNS records, the warm-up log, and a written runbook for the day a domain starts deferring: which one to retire, how to replace it, and the volumes to restart at. One deliverability review thirty days after your first live send.