Web3 B2B Outbound, Run Through Lemlist
If you sell to web3 companies — node infrastructure to exchanges, security audits to protocol teams, chain tooling to fintechs exploring integrations — you face an audience that is uniquely hostile to cold email. Their inboxes are saturated with token shills, airdrop spam, and 'partnership' pitches from anonymous accounts. The bar to be read at all is higher than in almost any other B2B vertical.
That's also the opportunity. Much of web3 deal flow happens in Telegram and Discord, but enterprise and partnership decisions still get made over email — it's the formal channel where a protocol's BD lead, an exchange's infrastructure team, or a fintech's compliance group actually evaluates vendors. Lemlist is where your sequences, liquid-syntax personalization, and LinkedIn touches live. ColdRelay is the infrastructure underneath: the secondary domains, mailboxes, and dedicated IPs that Lemlist actually sends from. This guide covers how to wire the two together for web3 B2B.
Why Run Lemlist on ColdRelay Infrastructure
Lemlist is a sending and personalization platform — liquid syntax variables, personalized images and landing pages, multichannel sequences that mix email with LinkedIn steps. It sends from whatever mailboxes you connect to it; it doesn't provision domains or guarantee the deliverability of the mailboxes themselves. That's the infrastructure layer's job.
That layer matters more in web3 than almost anywhere else. Spam filters are already primed against crypto-adjacent vocabulary — 'token', 'chain', 'wallet', 'protocol' all raise the scrutiny on your sending reputation. A mediocre setup that lands in the inbox for a SaaS audience can land in spam when the copy mentions smart contracts. ColdRelay provides 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 you can send — warmup runs continuously as part of each mailbox's budget.
The pairing is additive, not competitive: ColdRelay is the infrastructure, Lemlist is the sender on top. You keep Lemlist's personalization engine and multichannel sequencing — you just give it mailboxes built to survive the harshest filtering environment in B2B.
Visit Lemlist →Connecting ColdRelay Mailboxes to Lemlist
Provision mailboxes on ColdRelay
Pick secondary domains related to but separate from your primary brand domain — your docs, status page, and customer comms should never share reputation with outbound. ColdRelay supports 100-150 mailboxes per domain; most web3 vendors start with 30-100 mailboxes across 1-2 domains since this is a targeted, high-ACV motion, not a volume play. Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC already configured.
Export credentials and connect in Lemlist
Export your mailbox list with SMTP/IMAP credentials from the ColdRelay dashboard, then in Lemlist go to Settings → Email Accounts and connect each mailbox via 'Other Provider (SMTP/IMAP)'. Each ColdRelay mailbox connects as its own sending identity so Lemlist's inbox rotation can spread sends across the pool.
Set sending limits to match the mailbox budget
In each Lemlist email account's sending settings, cap daily campaign sends at 2 per mailbox. That mirrors ColdRelay's per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup. Skip lemwarm; ColdRelay's warmup network handles warming continuously, and double-warming just burns budget.
Build the sequence with liquid syntax and LinkedIn steps
Create a multichannel campaign in Lemlist: a LinkedIn profile-visit step first (web3 buyers check who's looking), then email steps. Use liquid syntax to branch copy on real research fields — {{ githubRepo }}, {{ protocolName }}, {{ recentAuditOrUpgrade }} — with liquid conditions like {% if chainFocus == 'EVM' %} to swap entire paragraphs per segment instead of sending one generic template.
Add personalized assets and launch
Attach a Lemlist personalized image or personalized landing page to your second or third touch — a one-pager rendered with the prospect's protocol name and logo signals real effort to an audience trained to ignore mass sends. Attach all connected mailboxes to the campaign, launch, and scale mailboxes on ColdRelay as pipeline grows.
The Web3 Lemlist Playbook
Earn credibility in the first line or get deleted
Web3 buyers pattern-match for shills instantly. Open with proof you've actually looked at their work: a specific GitHub repo, a recent governance proposal, a line from their docs, the audit they just published. Feed those into Lemlist liquid variables per prospect — generic 'love what you're building in web3' openers confirm you're spam.
Position email as the formal channel, not a DM substitute
Your prospects live in Telegram and Discord, where anonymous pitches are noise. Lean into email's formality: write like a vendor opening an enterprise or partnership conversation — clear company identity, a concrete integration or audit proposal, a real signature. The contrast with their DM chaos is the advantage.
Never pitch tokens — pitch infrastructure outcomes
Even if your product touches tokens, the cold email shouldn't. Frame around uptime, audit coverage, integration timelines, compliance — the language of an exchange's infrastructure team or a fintech evaluating chain integrations. Token vocabulary triggers both spam filters and human skepticism; save it for the call.
Use LinkedIn steps to verify you're a real company
Skeptical buyers will check whether you exist before replying. Put a Lemlist LinkedIn visit or connection step before the first email and keep the sender's profile congruent with the pitch — real name, real company, real history. A founder or named engineer as sender out-converts a generic SDR identity in this market.
Typical Web3 B2B Outbound Benchmarks (Lemlist + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants matter most where crypto-adjacent copy already draws extra filter scrutiny |
| Reply rate | 1.5-4% | Lower than typical B2B — the audience is hyper-skeptical — but offset by high deal values on audits, infra, and integration contracts |
| 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 sequence and liquid-variable setup in Lemlist |
| Touches to reply | 3-5 | Multichannel sequences (LinkedIn visit + email) outperform email-only against buyers who verify senders before responding |
What It Costs: Lemlist + 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.
Lemlist is billed separately on its own per-seat subscription for sequencing, liquid-syntax personalization, personalized images and landing pages, and multichannel LinkedIn steps — priced per its current plans.
Web3 outbound is a precision motion, so most teams run a smaller mailbox pool than volume-driven verticals — infrastructure cost scales with mailbox count, Lemlist with seats. One bill for sending capacity, one for the personalization software on top.
| 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; Lemlist handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Does ColdRelay replace Lemlist?
No — they're complementary layers. Lemlist handles sequencing, liquid-syntax personalization, personalized images, and LinkedIn steps. ColdRelay provides the underlying domains, mailboxes, and dedicated IPs that Lemlist sends from. You use them together: infrastructure underneath, sending and personalization on top.
Won't cold email just get ignored by web3 teams who live in Telegram and Discord?
DMs are where the noise is — anonymous pitches and token shills have made them nearly unusable for vendor outreach. Email is the formal channel where protocol BD leads, exchange infrastructure teams, and fintech evaluators actually process partnership and enterprise proposals. A well-researched email from a verifiable company stands out precisely because it isn't a DM.
Do crypto-related words hurt deliverability, and does infrastructure fix that?
Crypto-adjacent vocabulary does draw extra filter scrutiny, which makes the sending reputation underneath more important, not less. ColdRelay's isolated Azure tenants with dedicated IPs and pre-configured SPF, DKIM, and DMARC give each mailbox a clean, dedicated reputation — and it still pays to keep token-heavy language out of the copy itself.
Do I need lemwarm 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. Point Lemlist at outbound sending only and skip lemwarm to avoid double-warming.