Crypto BD Is Displacement Sales: A Field Guide for the 99% Problem

If you’ve been hired as a crypto BDR, you are doing displacement sales. Almost all of it.

The greenfield motion in crypto runs on founder bandwidth, not BD headcount. Greenfield deals tend to be small, the prospect doesn’t yet know they have the problem, and the close happens in DMs between two founders who’ve known each other for three cycles. By the time a company has scaled enough to hire a BD team, it’s selling into accounts that already have a vendor. Often two or three. Frequently a vendor whose scope quietly grew until they’re sort-of doing the thing you do.

The two clearest illustrations are the hardest products in the category: security audits and market making. Roughly 99% of audit prospects already have an audit firm in rotation, whether that’s a named-tier firm or someone from the long tail behind them. Roughly 99% of token-issuing prospects already have a market-making relationship in place.

The same dynamic holds for custody, RPC, indexers, oracles, bridges, MEV protection, intent solvers, and most of the infrastructure stack. The exceptions are pre-launch projects (small budget, free options) and post-incident projects (rare, short window). Everything else has an incumbent, even when “incumbent” means “the firm we used 18 months ago and will probably renew with.”

If your motion isn’t built around displacing an incumbent, your motion is wrong. The list is wrong, the pitch is wrong, the timeline forecast is wrong, and the pricing is wrong. The rest of this post is the playbook.

(There’s a field guide to BANT for crypto BDRs alongside this one for the qualification side. This is the targeting-and-close side.)

Why crypto displacement is different from SaaS displacement

The general displacement playbook from B2B SaaS gets you most of the way: longer cycles, more stakeholders, incumbent counter-moves, champion-led migration plans. Crypto adds vectors in both directions.

Harder than SaaS:

Trust networks are the actual sales channel. Founders introduce founders to vendors. “Who do you use for X?” in a Telegram chat is the highest-converting top-of-funnel in the industry, and you don’t show up in it unless someone vouches.
Switching is socially visible. A new audit logo on a release post or a new MM partner in a token announcement is read by investors and competitors. Some prospects don’t switch because the optics look like the previous vendor failed, even when they did.
Loyalty inertia compounds. “They helped us when we were small” is a real reason a now-scaled-up team won’t switch off the auditor that did their original $20K engagement.

Easier than SaaS:

Incumbents are often genuinely weak in specific accounts. Audit firms have finite senior bench, and senior-reviewer time gets allocated to the contracts that pay for it. The public post-mortem record makes that allocation visible after the fact. Market makers running dozens of books simultaneously have limited attention per book, and spread and depth data during volatility events makes that visible in real time.
Engagement cycles are short. Most audits are per-project, not multi-year ARR. Most MM agreements are renewable in 6-12 month cycles or terminable on 30-day notice. There is no enterprise-grade switching cost in the contract.
Failures are public. Exploits, post-mortem threads, governance forum complaints, and on-chain spread/depth data are open. You can identify a weak incumbent without ever being introduced to the account.
Founder migration is fast. Once one prominent client switches, peer projects watch. A single high-profile displacement tends to unlock a wave of warm conversations in the same sub-segment over the following quarter.

Net: crypto displacement is winnable, but on a different vector than SaaS. You’re not playing the long enterprise procurement game; you’re playing the public-failure-and-founder-network game.

Find the weakest incumbent, not the best prospect

Conventional BD ranks prospects by ICP fit, fundraise stage, logo prestige. Displacement BD ranks by incumbent weakness in this specific account.

For each name on the list, before sending the DM, gather four things:

Who is the current vendor? For audits, the most recent published audit report names the firm. For MMs, the listed market maker is on the project’s tokenomics page or the exchange’s market-maker disclosures.
What is the public failure signal? Audits: post-mortems of exploits in their codebase; bug bounty disclosures that name the original auditor; gaps between what the audit report flagged and what later went wrong. MMs: spread widening during the Q4 2025 deleveraging, depth shortfalls during exchange listings, “neutrality” complaints on governance forums, on-chain volume that looks like wash-trading.
What’s the network signal? Conversations in your Telegram and Signal threads, recent X complaints, anonymous Warpcast posts, governance forum posts where the team commented on vendor performance.
What’s the contract signal? Renewal windows, contract-end events visible on-chain (multisig signatures, token unlocks tied to MM agreements), recent tweets that mention “evaluating options.”

The list isn’t “top 50 by raise.” It’s “top 15 where the current vendor is most exposed.” The wedge, meaning the one capability you should lead with, is whatever specifically failed in those four signals. Not “we’re 10% better at finding bugs.” Not “we have more capital.” A wedge that sounds like the prospect’s last week.

If a prospect has a strong incumbent with a clean public scorecard, walk away unless you have a personal-network signal that contradicts the public picture. Walking away is also a positioning move: you’re the firm that doesn’t take displacement deals just to take them. Founders notice.

Multi-thread, in parallel, or die

The incumbent already has multiple relationships in the account. You’re behind from the first DM.

Three personas matter in every displacement deal:

Technical. The person who feels the pain. Smart-contract engineers in audits, heads of trading or quant leads in MMs.
Economic. The person who pays. Engineering managers or CTOs in audits, CFOs or COOs in MMs.
Executive. The person who decides on vendor-of-record changes. Founder, CEO, or sometimes the head of security for audits at larger orgs.

The crypto-specific wrinkle: in many smart-contract orgs, the technical persona has more decision power than they would at a typical enterprise. A senior engineer can kill a vendor change unilaterally if they’re not bought in, even if the founder wants to switch. Prioritize the technical persona for depth, but reach economic and executive in the same week. Not after the technical call goes well.

The single most common multi-threading failure I’ve watched in crypto BD: the BDR books a great call with the technical lead, gets enthusiastic feedback, and goes back to outbound to find the economic and executive contacts. By the time those calls are scheduled three weeks later, the incumbent has caught wind and offered the technical lead a senior engineer for the next engagement. Deal dead, never officially. Reach all three personas in parallel, in the same week, with personalized outreach to each. The slowest persona to respond determines deal velocity.

Wait for the trigger

Random outreach lands when the prospect has no buying window. Most of the time, the right move is to hold a prospect on a slow drip until a trigger fires, then move fast.

Audit triggers worth watching:

New release or new feature shipping
New chain deployment
New fundraise (investor diligence demands a fresh audit)
Exploit in their codebase or in a closely related one
Public competitor incident (investors and the team get nervous and re-evaluate)
Bug-bounty report that the team disclosed as severe

Market-making triggers worth watching:

Token launch or major TGE event
New CEX listing or DEX pool deployment
Drawdown or liquidity event (Q4 2025 was an instructive case)
Governance proposal to renegotiate the MM agreement
Exchange delisting threats or low-volume warnings

Universal triggers:

Incumbent failure (security incident, missed deliverable, public post-mortem)
Team change (new CFO, new CTO, new head of engineering)
Competitive announcement (their incumbent works with their direct competitor and they didn’t know)
Your own recent win (if you displaced a peer auditor or MM, every comparable project on that peer’s book just became a warm prospect)

Build a watchlist that fires on triggers. Don’t outbound the cold list weekly.

Inoculate the champion, then put the migration plan on the table

Two moves win the close stage. Both happen before the final pricing conversation.

Inoculate the champion. The moment your incumbent senses the deal slipping, they will respond. Discount, expedited timeline, a senior name dropped onto the team, a roadmap promise. Your champion will be the one who hears it. They need to know what’s coming and what to say back, before it lands.

Lines that work, given to the champion in the second meeting:

“Why didn’t they offer this six months ago when we asked?”
“Is the senior they’re staffing the one who’ll actually do the work, or just join the kickoff call?”
“What happens after this engagement, when the discount rolls off?”
“If their roadmap promise is real, why isn’t it in the contract?”

This is champion-enablement, not objection-handling. Hand the lines over as an asset. Treat the incumbent’s counter-move as a deal stage you plan for, not an event you react to.

Migration plan in the room. Displacement deals stall when the buyer can’t visualize the transition. Bring a one-page migration plan named for the prospect, before they ask for it.

For an audit displacement: review of the prior audit’s open issues, regression risk in re-running, scope split between green-area review and red-area deep-dive, timeline to a clean engagement, named partners on the team. For a market-maker displacement: the inventory transition mechanic, the overlap window where the incumbent ramps down while you seed, the exchanges and pairs covered from day one, spread and depth commitments by week, and integration milestones with the project’s smart-contract team.

The migration plan also exposes the displacement work the incumbent will demand to gate: final-audit completion, MM tail-management, fee reconciliation. Name those concretely so the buyer knows you’ve thought about them. The plan that anticipates the incumbent’s friction is the plan that closes.

Pricing is commitment, not discount

Don’t burn margin on the first deal. Burn it on the second.

For audits, the right structure is a multi-engagement bundle: two or three engagements at locked-in pricing, with each subsequent engagement at a slight discount. The buyer gets predictable cost. You get something more valuable: by the time the bundle ends, the buyer has done two engagements with you, and the incumbent has no foothold left to renew from. The switching cost back to the old vendor has gone up, not down.

For market making, the right structure is performance-gated: spread, depth, and uptime commitments tied to the fee structure, with explicit clawbacks if you miss them. This is the displacement-pricing version of “we won’t do what your last MM did during the Q4 deleveraging.” Writing it into the contract makes the inoculation real.

What backfires across both:

Free first audit (or first month of MM service free) is a common displacement gambit. It loses on three axes: it signals you don’t believe in your own pricing; it teaches the buyer that your output is worth zero on the margin; and it commits you to economically irrational work that you’ll resent and quietly under-invest in. The buyer notices.
Flat percentage on volume for MM displacement is a race to zero. Floors and SLAs hold. The same logic applies to any aggregator-shaped buyer in the broader stack.
Heavy discount on a first engagement without a second-engagement structure means you’ve trained the buyer to expect that price. The next renewal is a confrontation about why the number went up, not a renewal.

Think pricing as a commitment you make to the buyer, gated to performance the incumbent failed to deliver. Discount is the lazy version. Commitment is the real one.

References compound

The greenfield reference says “this product solved a problem we had.” The displacement reference says “we ran on Vendor X for 18 months and switched. Here’s what changed.” The buyer who switched is the buyer your competitor’s prospects will believe.

One displacement reference, named on stage at a conference or quoted in a public post, tends to unlock a wave of warm conversations in the same sub-segment. Get the case study locked in the contract. Ask the new client for a quote inside the first 90 days, while the contrast with the prior vendor is still fresh.

If your pipeline review opens with “who’s their current vendor?” and “what’s broken with them?”, you’re running the right motion. If it opens with “how big was their last raise?”, you’re running founder-led-style outbound with an AE-level hire.

Crypto BD is displacement sales. Plan the motion accordingly.