How to Hire a Web3 BD Lead (And What Most Founders Get Wrong)

I've been the BD hire. I've made BD hires. I've watched dozens of crypto projects make their first BD hire and get it catastrophically wrong. The pattern is so consistent it's almost predictable: founder raises money, founder realizes they need revenue, founder hires someone with "Web3 BD" in their LinkedIn title, 6 months later the pipeline is empty and the hire is gone.

The problem isn't that good BD people don't exist. The problem is that founders don't know what they're actually hiring for.

The Three Types of "BD" in Web3

Before you write a job description, understand that "business development" means three completely different things in crypto:

Type 1: Partnership BD — Relationship-driven. This person's job is to get your protocol integrated with other protocols, listed on aggregators, and mentioned in ecosystem reports. They're measured by integrations shipped, not revenue. This is the most common BD role in crypto and the least likely to generate direct revenue.

Type 2: Revenue BD — Sales-driven. This person closes deals that generate revenue — enterprise contracts, ecosystem-wide agreements, service engagements. They're measured by ARR, deal size, and pipeline velocity. This is what most founders actually need but rarely hire for.

Type 3: Ecosystem BD — Community and developer-driven. This person builds the ecosystem around your protocol — sourcing projects, running grants programs, organizing hackathons. They're measured by developer adoption, TVL growth, and ecosystem health.

Most founders write a job description that blends all three, interview candidates who specialize in one, and then wonder why the hire isn't performing across all three dimensions.

The Hiring Framework

Step 1: Define Your BD Problem

Before hiring anyone, answer these questions:

What is the primary revenue model? (Protocol fees, enterprise contracts, grants, token appreciation)

What does a "closed deal" look like? (Integration live, contract signed, grant distributed)

What's the average deal cycle? (Weeks for integrations, months for enterprise)

Who is the decision-maker on the other side? (Developer, BD lead, foundation, C-suite)

Your answers determine which type of BD person you need.

Step 2: Source for Track Record, Not Rolodex

The biggest mistake: hiring for network instead of execution. "I know everyone in crypto" is not a qualification. Networks decay fast in Web3 — the person who was connected in 2023 may have irrelevant contacts in 2026.

What to look for:

Closed deals with metrics. Not "I was involved in" — "I personally closed $X in Y timeline." Ask for specifics: deal size, sales cycle, who the decision-maker was, what the competitive situation was.

Process orientation. Can they describe their BD process step by step? If they can't articulate how they take a cold lead to a signed agreement, they're winging it.

Technical fluency. They don't need to write Solidity, but they need to understand your protocol well enough to have credible technical conversations. Test this in the interview — have your CTO ask questions.

Written communication. 80% of BD in crypto happens over Telegram, email, and Twitter DMs. Ask for writing samples. If their written communication is sloppy, their outreach is sloppy.

Step 3: Compensation Structure

Benchmarks for 2026 (US market, fully remote):

Level	Base	OTE (with commission)	Token/Equity
BD Associate (0-2 yrs)	$80K–$120K	$120K–$180K	0.1–0.25%
BD Lead (3-5 yrs)	$130K–$180K	$200K–$300K	0.25–0.75%
VP/Head of BD (5+ yrs)	$180K–$250K	$300K–$500K	0.5–2%

Critical: structure the commission to incentivize what you actually want. If you want integrations, commission on integrations shipped. If you want revenue, commission on revenue closed. If you commission on "partnerships announced," you'll get a lot of press releases and no pipeline.

Step 4: The 90-Day Test

Don't evaluate BD hires on revenue in the first 90 days. Evaluate on:

Day 30: Do they have a target list, outreach system, and CRM set up?

Day 60: Are they generating qualified conversations? (Not deals — conversations with the right people)

Day 90: Is there a pipeline with clear stages, timelines, and next steps?

If they can't show you a structured pipeline at 90 days, the problem is capability, not timing.

Red Flags

"My network will close deals." Networks open doors. Process closes deals. If their strategy is "I'll text my friends," you're hiring an expensive Rolodex.

Can't name specific numbers. Vague answers like "I helped grow revenue significantly" mean they were adjacent to revenue, not responsible for it.

No CRM discipline. If they don't use a CRM or can't show you their pipeline management process, they're running BD from memory and Telegram. This doesn't scale.

Overemphasis on events. "I'll go to every conference" is not a BD strategy. Events are a tool, not a strategy.

"I need 6 months to ramp." In Web3, markets move too fast for 6-month ramps. A good BD person should be generating qualified pipeline within 60 days.

The Alternative: Fractional BD

Here's the honest truth — most early-stage crypto projects don't need a full-time BD hire. They need a BD system operated by someone experienced for 3–6 months to build the pipeline foundation, then a junior hire to maintain and expand it.

This is exactly what Cracked Labs' Pipeline Sprint and Retainer models are designed for. We come in, build the system, close the first deals, and either hand it off to your hire or continue operating it on a fractional basis.

The math: a full-time BD lead costs $200K–$300K all-in annually. A Pipeline Sprint costs $10K for two weeks. A Retainer is custom monthly. You get senior-level BD without the commitment until you've validated the pipeline and know exactly what full-time hire to make.