Multi-Product Web3 BD, Run Through Smartlead
Most web3 companies that survive past their first cycle end up selling more than one thing. The node infrastructure business adds an API suite; the API suite spins up an audit or advisory arm. Each product line sells to a different buyer — DevOps leads at exchanges evaluate node infra, dApp engineers evaluate APIs, protocol founders and security leads evaluate audits — and a single blended outbound motion serves none of them well. The buyer who wants your RPC endpoints does not want to hear about your audit practice in the same thread.
Smartlead is built for running several distinct motions side by side: separate campaigns with their own mailbox rotation, a Master Inbox that pools replies across all of them, and an API with webhooks that pushes outcomes wherever your pipeline lives. ColdRelay is the infrastructure underneath: the secondary domains, mailboxes, and dedicated IPs that Smartlead actually sends from. This guide covers how a multi-product web3 team wires the two together so each product line gets its own campaign, its own slice of sending capacity, and its own line in the revenue report.
Why Run Smartlead on ColdRelay Infrastructure
Smartlead is a sending and orchestration platform — campaign-level mailbox rotation, spintax, a Master Inbox, and an API built for reporting. It sends from whatever mailboxes you connect to it; it doesn't provision domains or put deliverability under the addresses themselves. That layer is the infrastructure's job, and for a multi-product web3 sender it carries extra weight: you're running several campaigns in parallel against an audience whose filters already scrutinize crypto-adjacent mail harder than almost any other category, so the reputation under every mailbox has to be clean, dedicated, and yours alone.
ColdRelay fills that layer. You order dedicated mailboxes on isolated Azure tenants with dedicated IPs, fully DNS-configured (SPF, DKIM, DMARC) and ready in about an hour, with no warmup waiting period before your first campaign — warmup runs continuously as part of each mailbox's daily budget. ColdRelay supports 100-150 mailboxes per domain, so even a pool split across three product lines usually fits on one or two secondary domains.
The pairing is additive, not competitive: ColdRelay is the infrastructure, Smartlead is the sender on top. You keep Smartlead's per-campaign rotation, Master Inbox, and webhook reporting — you just give every campaign mailboxes built to land in a hostile filtering environment.
Visit Smartlead →Connecting ColdRelay Mailboxes to Smartlead
Size one mailbox slice per product line on ColdRelay
Don't provision one undifferentiated pool. Budget capacity per product line based on each line's target list: a node-infra motion aimed at exchanges and validators might need 15-20 mailboxes, an API motion aimed at dApp teams 20-30, an audit motion aimed at protocol founders 10-15. At 2 outbound sends/day per mailbox — each mailbox sends 4 emails/day total, 2 outbound + 2 warmup — those slices translate directly into per-line daily capacity. ColdRelay supports 100-150 mailboxes per domain, and the whole pool provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC already configured.
Bulk-import the pool under Email Accounts
Export your mailbox list with SMTP/IMAP credentials from the ColdRelay dashboard. In Smartlead, go to Email Accounts and use the bulk CSV import to connect the entire pool in one upload. Use a tagging convention in the mailbox names or sender identities (e.g., infra-, api-, audit- prefixes) so each slice is easy to find when you assign mailboxes to campaigns.
Set sending limits and skip Smartlead's warmup
Set each account's daily campaign limit to 2 emails per mailbox, mirroring ColdRelay's per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup. Leave Smartlead's warmup off for these accounts: ColdRelay's network warms every mailbox continuously, and running a second warmup layer just spends the same budget twice. The conservative cap matters more in web3 than elsewhere — a skeptical, heavily filtered audience punishes volume spikes fastest.
Build one campaign per product line and assign its mailbox slice
Create a separate Smartlead campaign for each product — node infra, API suite, audit services — each with its own lead list and sequence written for that buyer. Use Smartlead's campaign-level mailbox rotation to attach only that line's mailbox slice to its campaign, so an aggressive test on the API motion can never drag down the sender reputation the audit motion depends on. Use spintax sparingly: light variation in greetings and connectors keeps fingerprints diverse, but heavy spinning reads as automation to an audience trained to spot it.
Wire the Master Inbox and webhooks, then launch
Turn on the Master Inbox so replies from all campaigns pool into one queue, and use its campaign filters to route each product line's replies to the BD lead who owns that line — the infra BD lead should never be triaging audit inquiries. Then configure Smartlead's webhooks (reply received, lead categorized) to push events into your CRM or deals pipeline, tagged by campaign, so every opportunity is attributed to a product line from the first reply. From ColdRelay order to first send is same-day: about an hour of provisioning plus campaign setup.
The Multi-Product Web3 Smartlead Playbook
One campaign per product line, one buyer per campaign
The DevOps lead evaluating node infrastructure, the engineer evaluating your API, and the founder commissioning an audit are different people with different vocabularies and different approval chains. Keep them in separate Smartlead campaigns with sequences written for one buyer each — and never cross-pitch a second product inside a sequence. The fastest way to look like spam to a web3 buyer is to pitch them something adjacent to what they actually evaluate.
Isolate sending slices so one product's experiments can't burn another's reputation
Campaign-level mailbox rotation is the quiet superpower here: each product line sends only from its own ColdRelay mailbox slice. If the API team wants to test new messaging on a colder list, any bounce or complaint blast stays contained to that slice — the audit motion's carefully built sender reputation is untouched. Treat the slices like blast doors, and resist the temptation to 'borrow' capacity across lines when one campaign runs hot.
Route the Master Inbox to owners, not to a shared queue
In a multi-product company, an unrouted reply queue is where deals go to die — the infra lead skims past audit inquiries and vice versa. Use the Master Inbox's campaign filters and lead categories to give each BD lead a view of only their line's replies, and hold them to same-day responses. A web3 buyer who replied to a specific product pitch expects the person who answers to actually own that product.
Make every product line earn its pipeline with webhook attribution
Push reply and category events from Smartlead's webhooks into your deals pipeline, tagged by campaign, from day one. After a quarter you'll know each line's true cost-per-opportunity — which mailbox slice to grow, which sequence to rewrite, and whether the audit arm's outbound deserves its capacity or should hand it to the API motion. Multi-product BD without per-line attribution is just three opinions arguing over one budget.
Typical Multi-Product Web3 BD Benchmarks (Smartlead + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants carry the load where crypto-adjacent mail already draws extra filter scrutiny |
| Reply rate by product line | 1.5-5% | Audit and security offers typically reply highest; node infra to exchanges sits lower but carries larger contract values |
| Mailbox slice per product line | 10-30 | Sized to each line's target list; slices stay isolated via Smartlead's campaign-level rotation |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Time to first campaign | Same day | ~60 minutes to provision on ColdRelay, plus per-line campaign setup in Smartlead |
What It Costs: Smartlead + ColdRelay
You pay per mailbox per month for the infrastructure, with volume tiers that drop as you scale (see the table below). DNS, dedicated IPs, and isolated Azure tenants are included — and a pool split across several product lines still prices as one combined mailbox count, so the slices benefit from the same volume tier.
Smartlead is billed separately on its own subscription for campaigns, mailbox rotation, the Master Inbox, spintax, and API/webhook access — priced per its current plans.
Total spend scales with the combined mailbox pool on ColdRelay plus one Smartlead subscription covering all product lines. Because attribution flows through webhooks per campaign, each line's share of the infrastructure cost can be weighed against the pipeline it actually produces.
| Mailboxes | ColdRelay price / mailbox / month |
|---|---|
| 1–199 | $1.00 |
| 200–999 | $0.85 |
| 1,000–4,999 | $0.70 |
| 5,000+ | $0.55 |
Each mailbox sends 4 emails per day — 2 outbound to prospects + 2 warmup. ColdRelay provisions mailboxes on isolated Azure tenants with dedicated IPs; Smartlead handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Does ColdRelay replace Smartlead?
No — they're complementary layers. Smartlead handles campaigns, mailbox rotation, the Master Inbox, and webhook reporting. ColdRelay provides the underlying domains, mailboxes, and dedicated IPs that Smartlead sends from. You use them together: infrastructure underneath, sending and orchestration on top.
Should each product line get its own domains and mailboxes?
Each line should get its own mailbox slice, assigned to its campaign via Smartlead's campaign-level rotation, so reputation stays contained per line. Whether the slices share a domain is a sizing question: ColdRelay supports 100-150 mailboxes per domain, so a three-line pool of 50-70 mailboxes comfortably fits on one or two secondary domains while staying fully separated at the campaign level.
Should we use Smartlead's client sub-accounts to separate product lines?
Usually not. Sub-accounts are designed for agencies managing separate clients with white-label reporting. For one company with several products, separate campaigns inside a single account give you the isolation you need — distinct mailbox slices, sequences, and webhook tags — while keeping the Master Inbox and analytics unified. Reach for sub-accounts only if product lines run as genuinely separate business units with their own teams.
Do I need Smartlead's warmup if my mailboxes come from ColdRelay?
No. Each ColdRelay mailbox warms continuously as part of its built-in budget — 2 warmup sends/day alongside 2 outbound, for 4 sends/day total — with no waiting period before your first campaign. Leave Smartlead's warmup off for these accounts and point its daily limits at outbound only, so the two systems don't double-spend the same budget.