Cold outreach
Why your cold emails land in spam, and what it takes to fix itLinks to tools are affiliate links — we may earn a commission at no extra cost to you.
Almost everyone who thinks their cold email copy is the problem has a deliverability problem instead.
You wrote a decent email. You sent it to 200 people. You got no replies — not rejections, no replies. That's the signature of mail that never reached an inbox. Bad copy gets ignored; undelivered mail gets silence.
Here's what's actually happening, and what fixing it properly involves.
The mistake that kills accounts on day one
Sending cold email from your main business domain.
If you send from the same domain you use for customer support, invoices and signed contracts, and your cold campaign gets marked as spam a few dozen times, that reputation damage applies to every email from that domain. Your invoices start landing in junk. Your reply to a warm lead disappears.
The damage is slow to appear and slow to undo, which is why people don't connect cause and effect until months later.
Cold outreach goes out from a separate domain. Usually a close variant of your real one, so it still looks legitimate. Your primary domain never touches a cold campaign.
The three DNS records that decide whether you exist
Mail providers assume an unknown sender is a spammer until proven otherwise. Three records do the proving.
SPF lists which servers are allowed to send mail for your domain. Without it, anyone can forge your address, so providers distrust it.
DKIM signs each message cryptographically, letting the receiver confirm it really came from you and wasn't altered.
DMARC tells providers what to do when SPF or DKIM fails — and gives you reports on who's sending mail as you.
These are DNS entries at your domain registrar. Not difficult, but if any one of them is missing or wrong, your mail is suspect before the subject line is read. Google and Microsoft both tightened their bulk sender rules in 2024, and authentication went from advisable to mandatory. Gmail now expects senders to keep spam complaints below roughly 0.3% — which is about three complaints in a thousand emails.
Warmup is not optional and it is not fast
A brand new domain sending 500 emails on its first day looks exactly like a spammer, because that is what spammers do.
New domains and new inboxes have to earn sending volume gradually — a handful of emails a day, climbing over two to four weeks, with real engagement along the way. Skip it and the domain is burned before your first campaign finishes.
This is also why serious senders use multiple inboxes. Each mailbox carries a low daily limit, so volume comes from having several, not from pushing one harder. Which means multiple inboxes, each individually warmed.
What the do-it-yourself version actually costs
Lay out the real stack:
- A secondary domain
- Several mailboxes on it, each a paid seat with your email provider
- SPF, DKIM and DMARC configured correctly on that domain
- A warmup tool, or two to four weeks of patience
- A sending platform to run sequences and follow-ups
- An email verification tool so bounces don't undo the work
- A list, from somewhere
That's four or five separate subscriptions, a DNS configuration session, and a month before the first real campaign goes out. Every one of those steps is learnable. Together they're the reason most people's cold email never starts — they stall somewhere around DKIM and quietly give up.
None of it is the part you actually wanted to do, which was talk to prospects.
The other half: follow-ups and personalization
Two more things that decide outcomes, both unrelated to infrastructure.
Most replies come from follow-ups, not first emails. A single send is the most common reason a campaign with good deliverability still produces nothing. Sequences are where the results are, and manual follow-up is where discipline collapses.
Generic templates get generic results. A merge field with someone's first name isn't personalization and everyone recognizes it. Real relevance — something specific to that business — is what earns a reply, and doing it by hand across hundreds of prospects is not sustainable.
Where Squibb fits
Squibb exists to delete the entire infrastructure section above.
You tell it who you want to reach. It finds the prospects, verifies the contacts, writes a personalized email for each one, sends, and handles follow-ups. The sending side — domains, mailboxes, authentication, warmup, volume ramping — belongs to the platform. You never buy a domain, never touch a DNS record, never wait out a warmup period.
That's the trade: you give up ownership of the sending layer, and in return you skip the month of setup and the four subscriptions that most people never get past.
The honest limitation: you don't control the sending infrastructure, which cuts both ways. You can't tune per-inbox volume, rotate domains on your own schedule, or build up a sending reputation that belongs to you as a long-term asset. If you already run warmed domains and know your way around deliverability, Squibb takes away the control you've earned and you should stay where you are. It's built for the person who hasn't started, not the person who has already solved this.
The overlap worth knowing: Squibb also finds leads, which means it covers ground that a dedicated list-building tool covers. If you want to own and control your lists, or you need follower scraping and content research, that's a different tool — see how to find business emails from Google Maps, Instagram and LinkedIn. Squibb's argument is that you shouldn't have to assemble the pieces at all.
Next: once replies start coming in, you need somewhere to send people who say yes. That's how to add checkout to a sales page you built with AI.