The Web3 BD & Partnerships Playbook: From Cold Contact to Signed Deal
Web3 BD is one of the highest-leverage roles in the ecosystem. A single integration partnership can add millions in TVL, thousands of new users, or a critical piece of infrastructure. But most Web3 BD teams are winging it.
Here's a structured playbook based on what actually works.
The Web3 BD Funnel
Unlike traditional B2B sales, Web3 partnerships rarely follow a linear funnel. They're relationship-driven, community-influenced, and often happen in public (on X or in Discord). But you still need a structure:
Stage 1: Identification Who do you want to partner with, and why? Define your ideal partner profile before you start outreach. For most Web3 protocols, this means:
- Complementary but non-competing products
- Shared user base or target market
- Technical compatibility
- Aligned incentives (both sides benefit clearly)
Stage 2: Research Before reaching out, know:
- Their current integration partners (check their docs and announcements)
- Their BD team structure (who actually owns partnerships?)
- Their recent announcements and roadmap
- Any public signals of interest in your category
Stage 3: First Contact The goal of first contact is not to pitch. It's to open a conversation. The best first message is a genuine question or observation, not a partnership proposal.
Stage 4: Qualification After the first response, qualify quickly:
- Do they have the technical capacity to integrate?
- Who is the decision-maker?
- What's their typical integration timeline?
- Have they done similar integrations before?
Stage 5: Proposal Only send a formal proposal after you've had at least one real conversation. A proposal sent cold is almost always ignored.
Stage 6: Close Web3 partnerships often stall at the technical or legal stage. The BD person's job is to keep the momentum going and remove blockers.
The BD Contact Database
Our BD & Partnerships list contains 604 verified Web3 BD professionals — the people who own partnership decisions at protocols, exchanges, wallets, and infrastructure providers.
These are the highest-value contacts for BD outreach because:
- Their job is to evaluate and respond to partnership proposals
- They have decision-making authority or direct access to it
- They're actively looking for integration partners
Response rates for well-targeted BD outreach to this list run 45-55% — the highest of any segment we track.
Templates That Work
Initial outreach to a BD contact:
"Hey [Name] — we're building [one sentence] and I think there's a natural integration with [their protocol]. We already work with [similar partner] and the technical lift is minimal. Would you be open to a quick call to explore? Happy to share a one-pager first if that's easier."
Follow-up after no response:
"Bumping this — we just launched [feature/milestone] that makes the integration even more compelling. Still think there's a fit here if you have 20 mins."
After a positive first call:
"Great talking today. I'll send over the technical spec and a draft integration proposal by [date]. In the meantime, happy to intro you to [relevant contact] if that would be useful."
The Most Common BD Mistakes
- Pitching too early — most partnerships die because the BD person led with a proposal before establishing any relationship
- Wrong contact — going to the CEO when there's a dedicated BD team, or going to a junior BD person when the decision requires C-suite sign-off
- No clear value prop for the partner — "we want to integrate with you" is not a value proposition; "this integration will drive X new users to your protocol" is
- Stalling on technical details — get your engineering team involved early; BD deals die when the technical spec takes 3 months to produce
Measuring BD Success
Track these metrics:
- Outreach to response rate: target 40%+ for BD contacts
- Response to call rate: target 50%+
- Call to proposal rate: target 60%+
- Proposal to close rate: target 30%+ (Web3 partnerships have a high close rate once you get to proposal stage)
- Time to close: target 30-60 days for technical integrations, 60-90 days for deeper partnerships