Web3 Partnership BD, Run Through Instantly
For a web3 infrastructure company — an RPC provider, an oracle network, a custody layer, an indexing service — growth often isn't a thousand small customers. It's integrations. Every exchange that lists through your rails, every wallet that adds your network, every protocol that builds on your API compounds the moat. The problem is that most teams chase these partnerships opportunistically: a conference intro here, a warm Telegram referral there. The partner map is finite and knowable, which means it can be worked systematically.
That's a pipeline problem, and pipeline problems are what cold email solves. Instantly is where the motion runs — campaigns per partnership type, sends rotated across a large mailbox pool, replies pooled into one inbox. ColdRelay is the infrastructure underneath: the secondary domains, mailboxes, and dedicated IPs that Instantly actually sends from. This guide covers how to wire the two together and run BD outreach like a coverage exercise instead of a lottery.
Why Run Instantly on ColdRelay Infrastructure
Instantly's pitch is scale: unlimited email accounts on paid plans, bulk import, simple campaign building, and a unified inbox built for teams running many mailboxes at once. But 'unlimited accounts' only describes what the software will accept — it doesn't conjure the accounts themselves. Someone still has to provision the domains, configure DNS, and put real deliverability under every address you connect. That's the infrastructure layer, and it's the part Instantly explicitly leaves to you.
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 — warmup runs continuously as part of each mailbox's daily budget. For a web3 sender that matters doubly: filters already scrutinize crypto-adjacent mail harder, so the reputation under each mailbox has to be clean and dedicated, not borrowed from a shared pool.
The pairing is additive, not competitive: ColdRelay is the infrastructure, Instantly is the sender on top. You keep Instantly's campaign builder, A/Z testing, and Unibox — you just feed its appetite for accounts with mailboxes built to land.
Visit Instantly →Connecting ColdRelay Mailboxes to Instantly
Size the mailbox pool against your partner map
Start from the BD math, not a default number. Count the targets: every exchange, wallet, bridge, and protocol that fits your integration thesis, times roughly 3-4 contacts each (BD lead, head of ecosystem, a technical counterpart). At 2 outbound sends/day per mailbox — each mailbox sends 4 emails/day total, 2 outbound + 2 warmup — a pool of 40 mailboxes works about 1,200 first-touches a month with follow-ups. ColdRelay supports 100-150 mailboxes per domain, so even a large pool fits on one or two secondary domains, provisioned on isolated Azure tenants with dedicated IPs in about an hour.
Bulk-import the pool into Instantly via CSV
Export your mailbox list with SMTP/IMAP credentials from the ColdRelay dashboard. In Instantly, go to Email Accounts → Add New → Bulk Import via CSV and upload the file — every mailbox connects in one pass instead of one-by-one OAuth dances. Instantly's unlimited-accounts model means the whole ColdRelay pool attaches without per-seat penalties.
Set sending limits and skip Instantly's warmup
In each account's settings (or in bulk), set the daily campaign limit to 2 emails per mailbox, mirroring the ColdRelay budget of 4 sends/day total — 2 outbound + 2 warmup. Leave Instantly's warmup toggle off for these accounts: ColdRelay's network warms each mailbox continuously, and stacking a second warmup layer just spends budget twice.
Build one campaign per partnership type
In Instantly's campaign builder, create separate campaigns for each integration motion — exchange listings, wallet integrations, protocol/dApp builds — rather than one mega-campaign. Each gets its own lead list, its own sequence, and its own slice of the shared mailbox pool. Use A/Z testing within each campaign to run plain-subject variants against each other ('Integration: [their product] + [your network]' vs. a question-form subject) and let volume settle the argument.
Route every reply through Unibox and launch
Turn on Unibox so replies from all 40+ mailboxes land in one queue your BD lead actually works. Tag replies by campaign so you can see which partnership type is converting, then launch. From first ColdRelay order to first send is same-day: about an hour of provisioning plus campaign setup in Instantly.
The Web3 Instantly Playbook
Treat the partner universe as a finite list, not a feed
Unlike selling SaaS into an endless TAM, your integration targets are countable — there are only so many exchanges, wallets, and L2s that fit your thesis. Build the full list once, load it into Instantly campaigns by type, and measure coverage: what percentage of the map has been touched this quarter. The goal is that no plausible partner can say they never heard from you.
Write like an integration proposal, not a pitch
Crypto inboxes are trained to delete hype, so be the email that reads like internal correspondence: what the integration is, what it takes from their side (an endpoint, a listing review, an SDK install), what it does for their users, and a named technical contact. Plain, specific, boring-on-purpose copy survives the skepticism that kills anything resembling a shill.
Segment campaigns by what the partner has to do, not who they are
An exchange evaluating a listing, a wallet adding a network, and a protocol consuming your API have completely different effort profiles and approval chains. Keep them in separate Instantly campaigns with sequences paced to match — exchange listings need longer gaps and more touches because legal and listing committees move slowly; wallet integrations can move on a two-week cadence with the right engineer cc'd.
Plan capacity for a motion that never ends
Partnership BD isn't a quarterly blitz — new protocols launch monthly and your partner map keeps growing. Budget mailboxes for steady-state, not burst: at 2 outbound/day per mailbox (within the 4/day total alongside 2 warmup sends), a stable 40-60 mailbox pool sustains continuous coverage plus re-approach cycles on targets that went quiet, and you add capacity on ColdRelay as the map expands rather than spiking volume on existing mailboxes.
Typical Web3 Partnership BD Benchmarks (Instantly + 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 on integration outreach | 2-6% | Higher than generic web3 cold email — a concrete integration proposal with mutual upside out-converts a sales pitch |
| Partner-map coverage per quarter | 60-90% | With a 40-60 mailbox pool, most teams can touch nearly the full target universe each quarter, including follow-ups |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| First reply to signed integration | 6-16 weeks | Exchange listings sit at the long end (committees, legal); wallet and protocol integrations close faster |
What It Costs: Instantly + 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.
Instantly is billed separately on its own subscription for the campaign builder, A/Z testing, Unibox, and analytics — its paid plans allow unlimited connected email accounts, priced per its current plans.
The combination is built for sustained coverage: Instantly's flat software cost doesn't grow as you connect more accounts, so total spend scales almost entirely with the ColdRelay mailbox count — which you size to your partner map, not to a software tier.
| 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; Instantly handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Does ColdRelay replace Instantly?
No — they're complementary layers. Instantly handles campaigns, sequencing, A/Z testing, and the Unibox where replies land. ColdRelay provides the underlying domains, mailboxes, and dedicated IPs that Instantly sends from. Instantly's unlimited-accounts model and ColdRelay's per-mailbox infrastructure fit together by design: one supplies the capacity, the other manages the sending.
How many mailboxes does a web3 BD team actually need?
Work backwards from the partner map. Each mailbox sends 4 emails/day total — 2 outbound + 2 warmup — so 40 mailboxes yields 80 outbound sends/day, enough to run first-touches and follow-ups across a universe of a few thousand contacts each quarter. Teams targeting only top-50 exchanges might run 15-20 mailboxes; teams covering every wallet and L2 ecosystem typically settle at 40-60 and grow from there.
Should I use Instantly's built-in warmup with ColdRelay mailboxes?
No. ColdRelay mailboxes warm continuously as part of their built-in budget — 2 warmup sends/day alongside 2 outbound, with no waiting period before your first campaign. Leave Instantly'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.
Won't partnership emails from a crypto company just get filtered as spam?
The category does draw extra scrutiny, which is exactly why the infrastructure layer matters. ColdRelay's isolated Azure tenants with dedicated IPs and pre-configured SPF, DKIM, and DMARC give every mailbox its own clean reputation, delivering 95%+ inbox placement. Pair that with plain, proposal-style copy — what the integration is and what it takes — and you avoid both the filter patterns and the human reflex that deletes anything reading like a token promotion.