GTM engineering

Best cold email software and providers in 2026

Cold email tools compared by layer: inbox providers, sending platforms and verification. What each is best for, Google's sender rules, and where LinkedIn fits better.

A deliverability checklist card with SPF, DKIM, DMARC, one-click unsubscribe and spam rate under 0.3 percent ticked, under the headline deliverability first, tool second

The short answer

The best cold email setup has three layers, and the sending tool is only one of them. First, inboxes on secondary domains with SPF, DKIM and DMARC set up. Second, a sending platform such as Instantly, Smartlead, lemlist or Apollo, chosen by how many inboxes you run and whether you need multichannel steps. Third, list verification before every send. Get the first and third right and most mainstream sending tools will work.

On this page
  1. The three layers people mix up
  2. Sending platforms compared
  3. Inbox infrastructure that holds up
  4. The rules your setup has to pass
  5. Verify every list before it sends
  6. Where email stops and LinkedIn starts
  7. Fix the base layers, then pick the tool
  8. FAQ

#The three layers people mix up

“Cold email provider” can mean three different things, and buying the wrong one is the most common setup mistake.

Stack diagram of a cold email setup from bottom to top: domains and inboxes, authentication with SPF DKIM and DMARC, warm-up, list verification, sending platform, and reply handling into the CRM
A cold email setup, bottom to top. Problems in the lower layers can't be fixed by changing the sending tool.
LayerWhat it doesExamples
Inbox infrastructureThe mailboxes and domains messages are sent fromGoogle Workspace, Microsoft 365, dedicated cold email inbox providers
Sending platformSchedules sequences, rotates inboxes, tracks repliesInstantly, Smartlead, lemlist, Apollo, Outreach, Salesloft
Verification and dataChecks addresses exist before you sendMillionVerifier, ZeroBounce, NeverBounce, enrichment waterfalls
The three layers of a cold email setup

#Sending platforms compared

These are the tools GTM engineers mention most. Pricing changes often, so this compares fit rather than cost.

ToolBest forWatch out for
InstantlyTeams running many inboxes who want warm-up and sending in one placeEasy to send too much. Set per-inbox caps yourself
SmartleadAgencies and GTM engineers who want an API, sub-accounts and white-labellingMore settings to get right before the first send
lemlistSmall teams who want email plus LinkedIn steps and personalised imagesMultichannel steps still need LinkedIn's limits respected
ApolloTeams who want the contact database and sequencing in one toolShared data means competitors may contact the same people
Outreach or SalesloftLarger sales teams sending from primary domains with deep CRM syncBuilt for warm and existing pipeline more than high-count cold sending
Cold email sending platforms by fit

#Inbox infrastructure that holds up

  • Use secondary domains. Send cold email from look-alike domains (for example getbrand.com) so your primary domain's reputation stays clean.
  • Keep each inbox light. A few dozen cold emails per inbox per day is a common ceiling among practitioners. Add inboxes rather than pushing one harder.
  • Warm up new inboxes for two to three weeks before cold sending, and keep warm-up running at a low level after.
  • Mix providers if you send at any size. Google and Microsoft inboxes land differently with different recipients.

#The rules your setup has to pass

Google's email sender guidelines set the bar for anyone sending to Gmail, and Yahoo adopted similar rules. For bulk senders, defined by Google as close to 5,000 or more messages a day to Gmail accounts, the requirements include:

  • SPF and DKIM authentication on the sending domain.
  • A DMARC record, with the From domain aligned to SPF or DKIM.
  • One-click unsubscribe for marketing and promotional mail, honoured within two days.
  • A spam complaint rate kept below 0.3%, as reported in Google Postmaster Tools.

Cold sending rarely hits 5,000 a day from one domain, but filters judge everyone by the same signals. Treat these as the minimum.

#Verify every list before it sends

Bounces damage inbox reputation faster than almost anything else. Run each list through a verification service right before sending, not when it was built, since addresses go stale. Handle catch-all domains (which accept any address) separately: send to them from your healthiest inboxes in small batches, or skip them.

#Where email stops and LinkedIn starts

Email is good at carrying proof: a benchmark, a checklist, a teardown. It's weak at establishing that you're a real person worth answering. That's where LinkedIn helps. A profile visit, a follow and a genuine comment before the email arrives make your name familiar when it lands.

awwreach runs that LinkedIn warm-up as a flow, paced 3–9 minutes apart with dry run on by default, and routes replies to your CRM or an n8n webhook next to your email replies.

#Fix the base layers, then pick the tool

Most deliverability problems blamed on a sending tool start in the layers underneath it: unauthenticated domains, overworked inboxes, unverified lists. Get those right and the choice between mainstream platforms comes down to workflow fit. Then spend the time you saved on the part that earns replies, a message worth reading.

Frequently asked questions

It depends on your setup. Instantly and Smartlead suit teams running many inboxes, lemlist suits small multichannel teams, and Apollo suits teams that want data and sequencing in one tool.

Written by The awwreach team

We build awwreach and write about networking on LinkedIn that earns replies: what works, what's safe and what to avoid.

Keep reading

related guides

How GTM teams scale outbound with always-on playbooks
A playbook card showing four stages, signal, segment, proof and send, running in a loop beside the headline pipeline from playbooks, not headcount

How GTM teams scale outbound with always-on playbooks

Why one-off outbound pushes stall, what 486 published signal playbooks have in common, and a four-part system for shipping a new outbound play in days, not quarters.

Read the guide
Clay alternatives for GTM engineers in 2026
A decision card that starts with the question what did you hire Clay for and branches to enrichment, AI research, workflows and signals, under the headline pick the tool by the job

Clay alternatives for GTM engineers in 2026

The right Clay alternative depends on what you use Clay for. Gumloop, n8n, Apollo, Make, signal tools and plain code compared by job, plus GTM engineer vs Clay vs Gumloop.

Read the guide
The lean B2B GTM motion: beat bigger SDR teams
Two lanes compared: ten reps sending generic messages versus two reps and a GTM engineer sending a few precise ones, under the headline fewer reps, sharper aim

The lean B2B GTM motion: beat bigger SDR teams

How a lean sales team hits pipeline targets without adding headcount: where big SDR teams really win, five moves that close the gap, and what to buy before an AI SDR.

Read the guide
your first flow takes about four minutes.

go make someone's inbox nicer.