Cold email infrastructure stack — deliverability-safe outbound at volume

The stack for sending tens of thousands of cold emails a month without spending your primary domain’s reputation to do it. Four layers: isolated sending domains and mailboxes, Clay for list construction and the verification gate, Smartlead or Instantly as the sending and rotation engine, and HubSpot as the destination for anything that replies.

One constraint shapes every choice here. Since February 2024, Gmail and Yahoo have enforced sender requirements on any domain pushing 5,000 or more messages a day: SPF, DKIM, a DMARC record with alignment, RFC 8058 one-click unsubscribe headers, and a Postmaster-reported spam complaint rate held under 0.3%. Microsoft began enforcing its own version on 2025-05-05 for senders at the same 5,000/day threshold into outlook.com, hotmail.com, and live.com, and non-compliant mail is rejected rather than filtered. A program that ignores this does not degrade gradually — it stops arriving, and the domain that carried it stays damaged after you fix the configuration.

How the pieces fit

The domain and mailbox layer

This layer is a provisioning decision rather than a product purchase, and it is the one that determines whether the rest of the stack works. Cold volume never leaves the domain that carries your transactional mail, your invoices, and your marketing list. It leaves a set of registered lookalike domains — yourcompany-hq.com, getyourcompany.com, yourcompany.io — bought at roughly $12/year each, each authenticated independently with its own SPF, DKIM, and DMARC records, and each carrying 2 to 4 mailboxes.

Two ways to buy the mailboxes. Google Workspace Business Starter runs $7/user/month on annual commitment and $8.40 on flexible monthly billing, and caps a user at 2,000 messages and 3,000 external recipients per day over a rolling 24-hour window. Those caps are far above the level that is safe for cold mail — the operating figure is 20 to 40 sends per mailbox per day, which means the platform limit is never the binding constraint and you should not treat it as a target. Dedicated cold-email inbox providers (Maildoso, Mailscale, ScaledMail) sell pre-provisioned mailboxes with DNS already configured at roughly $1.90 to $3.00 per mailbox per month, which is where the math lands once you are past about 30 mailboxes.

The watch-out is that Google Workspace’s acceptable use terms do not contemplate mailbox farms provisioned for unsolicited bulk mail, and accounts bought in bulk against the same billing identity get suspended together. The guard: register and bill each sending domain separately, or use a dedicated inbox provider whose entire product assumes this use.

Clay — list construction and the verification gate

Clay builds and enriches the list, and — more load-bearing — it is where records are killed before they ever reach a mailbox. Waterfall enrichment runs a record through multiple providers until a verified work email is found; AI columns score the account against the ICP rubric and write the personalization variable that the sequence will merge. Clay bills on two meters, Data Credits for provider lookups and Actions for AI runs and table operations, on a Free tier (500 Actions, 100 Data Credits, 200 rows per table), Launch at $185/month monthly or about $167/month billed annually (15,000 Actions, 2,500 Data Credits), Growth at $495/month monthly or about $446/month annually (40,000 Actions, 6,000 Data Credits), and a quote-only Enterprise tier.

The verification gate is the part teams skip and then pay for. A bounce rate above roughly 3% is what converts a warmed domain into a burned one inside a single campaign, so the list passes through a dedicated verifier — MillionVerifier at about $0.0037 per email ($37 per 10,000), ZeroBounce at $8 per 1,000 credits pay-as-you-go and around $0.004 per email at 250,000+ — and anything returning catch-all or risky is held back rather than sent. Verification is cheap relative to what it protects: verifying 50,000 addresses through MillionVerifier costs less than one month of the sending platform.

Smartlead — sending, rotation, and reply detection

Smartlead is the sending engine and the default pick for this stack. Its role is to take a verified, enriched list and distribute the send across every connected mailbox so that no single address carries a volume spike — rotation is the mechanism that makes 40 mailboxes at 30 sends/day behave differently from 1 mailbox at 1,200. Every Smartlead plan includes unlimited email accounts at no per-mailbox cost, which is the specific reason it is the default here: a stack whose whole premise is horizontal mailbox scale should not be billed per mailbox. Plans run $39/month (Base, 6,000 sends), $94/month (Pro, 90,000 sends), $174/month (Unlimited Smart, 150,000 sends), and $379/month (Unlimited Prime, 500,000 sends), with 17% off on annual billing — $32.50, $78.30, $144.50, and $314.60 respectively. API and webhook access and 3 dedicated SmartServers land on Prime.

Smartlead also owns reply classification: it detects a human reply, pulls that thread out of the sequence, and categorizes it before handing it onward. That categorization is the trigger for the CRM handoff below.

Instantly — the alternative sending engine

Instantly occupies the same layer as Smartlead and you run one or the other, never both. Its role in this stack is the swap for teams that want a lead database and an AI reply agent in the same subscription rather than assembled from parts, and for teams whose deliverability problem is IP-level rather than mailbox-level. Instantly’s Outreach-only Growth plan is $47/month with unlimited email accounts, unlimited warmup, and 5,000 sends/month; the bundles run $94/month Starter ($85 annual), $194/month Scale ($175 annual, 100,000 sends and 25,000 uploaded contacts), and $555/month Agency ($500 annual, 500,000 sends), with the SISR system — sharded, rotating dedicated IP pools that isolate a flagged IP from the rest — appearing at the Agency tier.

The rule for picking it: choose Instantly when you want its 450M-record B2B database to replace part of the Clay data spend, or when you are sending from dedicated IP pools rather than shared infrastructure. Choose Smartlead when you already own the data layer, want the cheapest path to unlimited mailboxes, and want API access without buying an agency-tier plan.

HubSpot — where a reply becomes pipeline

HubSpot is the system of record and the point at which the outbound program stops being a sending exercise. A positive reply classified in Smartlead creates or updates a HubSpot contact, attaches the enriched Clay context to the record, opens a deal at the first stage, and assigns an owner. Everything before this point is infrastructure; this is where measurement starts, because reply rate is not a business number and pipeline created per sending mailbox is. HubSpot’s core CRM is free, Sales Hub Starter is $15/seat/month billed annually (about $20 monthly), and Sales Hub Professional is $90/seat/month annually with a one-time $1,500 onboarding fee.

Named handoffs

1. List built → verified: Clay table completes waterfall enrichment → rows export to the verifier → only valid rows return to the sending list; catch-all and risky rows are held.
2. Verified list → sequence: verified rows with personalization variables push from Clay into the Smartlead campaign, which assigns them across the mailbox pool at the configured per-mailbox daily cap.
3. Reply detected → sequence stopped: Smartlead classifies an inbound reply as human → removes the thread from the sequence → fires a webhook.
4. Positive reply → pipeline: the webhook creates or updates the HubSpot contact with Clay’s enrichment attached, opens a deal, and assigns the owner.
5. Spam rate breach → send paused: Postmaster Tools reports a domain crossing the complaint threshold → that domain’s mailboxes are pulled from the rotation pool before the platform-level reputation follows. The email deliverability monitor workflow automates this check.

Why this combination

The load-bearing reason is blast-radius isolation. Every expensive failure in cold email is a shared-fate failure — one bad list burns the domain, one burned domain drags the IP, one shared IP drags every other sender on it. This stack is built so each layer fails alone: domains are independent so a burned one is replaced for $12 and a two-week warmup; mailboxes rotate so no single address accumulates the complaint history; the verification gate stops the bad list at Clay rather than at the recipient’s spam button; and the CRM sits outside the sending infrastructure entirely, so replacing the whole sending layer costs you nothing in pipeline data.

The alternative is running cold volume through the marketing automation platform you already own, and it fails specifically rather than vaguely. HubSpot’s own sending domain is shared with your nurture and lifecycle mail, so a cold-list complaint spike degrades the email your existing customers receive; there is no mailbox rotation primitive; and the 0.3% Postmaster threshold is computed per domain, which means the two programs share one budget for complaints. Running them together is not a cost saving — it is a decision to spend your marketing deliverability on prospecting.

The cost asymmetry supports the same conclusion. The sending layer here is $2,000 or less per year. The infrastructure it protects — a primary domain with years of accumulated sender reputation — has no purchase price and a replacement cost measured in quarters.

Cost reality

Annual bands for a program running 40 mailboxes across 12 domains, roughly 30,000 to 50,000 sends per month:

• Domains: ~$150/year (12 domains at ~$12 each). Buy one or two spares.
• Mailboxes: ~$900 to $1,450/year with a dedicated inbox provider at $1.90-$3.00/mailbox/month, or ~$3,400/year on Google Workspace Business Starter at $7/user/month annual. The gap widens with every mailbox added.
• Sending platform: ~$1,750/year (Smartlead Unlimited Smart at $144.50/month billed annually) or ~$2,100/year (Instantly Scale at $175/month annual). Smartlead Base at $32.50/month annual covers only 6,000 sends and does not fit this volume.
• Clay: ~$2,000 to $5,400/year (Launch at ~$167/month annual, Growth at ~$446/month annual). Enrichment volume, not seat count, decides the tier.
• Verification: ~$150 to $250/year at 50,000 addresses/month through MillionVerifier.
• HubSpot: $0 on the free CRM, or ~$540/year for 3 Sales Hub Starter seats at $15/seat/month annual.

Total annual range: ~$5,000 to $10,000 for a 40-mailbox program, with Clay as the largest and most volume-sensitive line.

The hidden costs are the ones that decide whether the program works. Domain warmup is 2 to 4 weeks per new domain before it carries campaign volume, and that is calendar time you cannot buy back. Ongoing operation is 5 to 10 hours per week of a real person’s attention — replying to threads the classifier routed wrong, retiring domains whose complaint rate drifted, and rebuilding lists as the ICP definition sharpens. Copy and offer development sits outside this budget entirely and is the variable that actually moves reply rate.

Match rules

Use this stack when:

• Outbound email is a primary pipeline source rather than a supplement, and you are sending at least 10,000 messages a month. Below that, the infrastructure overhead exceeds what rotation buys you.
• You sell into a defined ICP with a verifiable work-email pattern. Clay’s enrichment and scoring are only as good as the rubric they run against.
• Someone owns deliverability as a named responsibility — reading Postmaster Tools weekly, rotating domains, watching bounce and complaint rates. This stack degrades quietly without that person.
• Your legal position on unsolicited B2B email is settled for the geographies you send to, and the sequence carries a physical address and a working opt-out on every message.

Do not use this stack when:

• You are sending primarily into the EU or UK, where GDPR and PECR make unsolicited B2B email to individually-identifiable addresses a consent question rather than an opt-out question. The infrastructure works; the motion may not be lawful for your list. Get that answered before provisioning, not after.
• Your total addressable market is under a few thousand accounts. At that size, mailbox rotation is machinery for a problem you do not have, and a researched 200-account list sent from your real domain outperforms it.
• You have no differentiated offer. This stack raises deliverable volume; it does not make an undifferentiated message convert, and volume against a weak offer produces complaints faster than meetings.
• Your motion is inbound-led or partner-led and outbound is an experiment. Run the experiment from a single mailbox first.

Common variations

• Swap Smartlead for Instantly. The right swap when you want the lead database and AI reply agent bundled rather than buying data separately through Clay, or when your deliverability problem is IP-level and you need SISR’s sharded dedicated pools. Expect a modest cost increase at equivalent volume, and expect to keep Clay anyway if your ICP needs enrichment depth beyond a single database.
• Add n8n between the sending platform and the CRM. Native integrations handle the positive-reply case; they do not handle the interesting ones — routing an out-of-office to a re-send queue dated after the return, pulling a domain from rotation on a complaint-rate breach, or suppressing an entire account when any contact at it replies negatively. Add n8n when your handoff logic outgrows a single webhook, at roughly $300-$800/year on cloud or a $20-40/month VPS self-hosted.
• Replace HubSpot with Salesforce. Correct when Salesforce is already the source of truth. It changes nothing about the sending layers and adds integration work at the handoff, since the reply-to-record path becomes an API write rather than a native connector.
• Drop the dedicated inbox provider and stay on Google Workspace. Reasonable under roughly 15 mailboxes, where the per-mailbox premium is small and you would rather keep the mailboxes inside an admin console your IT team already runs.

What this stack does NOT replace

• A message worth reading. Nothing in this stack improves reply rate; every layer here protects the ability to send at all.
• Legal review of your outbound motion. CAN-SPAM in the US is an opt-out regime; GDPR and PECR in Europe are not, and CASL in Canada is stricter than both. The stack enforces none of this for you.
• A list strategy. Clay executes an ICP definition and will build an expensive, well-enriched list of the wrong accounts just as reliably as the right ones.
• Conversation intelligence and downstream sales process. Once a reply becomes a meeting, this stack is finished; Gong and the CRM’s deal workflow own everything after.
• The deliverability fundamentals themselves — authentication records, warmup discipline, complaint monitoring. The tooling automates the execution, not the understanding. Start with how to keep cold email out of spam before provisioning anything.