The B2B Crypto Sales Funnel

A B2B crypto sales funnel is the path from a team's first touch with you to its first revenue for you. It has the usual SaaS stages (awareness, interest, evaluation, and contract) plus onchain integration signals that prove adoption: testnet deploy, mainnet deploy, and first volume. The funnel ends at revenue: a signed contract with a paid first invoice, or the first fees the integration earns you.

What are the stages of a B2B crypto sales funnel?

A B2B crypto sales funnel has nine stages: awareness, engaged visitor, developer activation, qualified opportunity, technical evaluation, testnet deploy, mainnet deploy, first volume, and revenue. The early stages live in web analytics, and the middle stages in the CRM. The integration signals live onchain, and revenue lives in the CRM and your billing system. Each stage needs a clear exit rule.

Not every company has every stage. A custody provider may have no testnet stage. A data API may count API calls instead of onchain volume. Remove stages that do not apply, but keep at least one onchain integration signal before revenue.

How is a B2B crypto funnel different from a SaaS funnel?

A B2B crypto funnel differs from a SaaS funnel in the steps before revenue and in how buyers identify themselves. In SaaS, revenue usually follows the signature, and accounts grow by seats. In crypto, an integration often has to ship onchain before it earns, and accounts grow by volume. Buyers often arrive as anonymous wallets or pseudonymous builders, not as named leads with work emails.

Three differences change how you measure:

• Proof is public. You can see a customer's deploy and volume onchain, often before they tell you.

• Identity is mixed. One buyer shows up as an email, a Telegram handle, and two or more wallets.

• Revenue can lag adoption. Fee and usage revenue follow volume, so a signed deal with no volume may earn nothing yet.

What should you measure at each stage?

Measure one volume metric, one conversion metric, and one time metric at each stage. Volume tells you the size of the stage. Conversion tells you how many move on. Time tells you how long they wait. Together they show where deals stall, which matters more than any single headline rate.

Awareness and engaged visitors

• Metrics: visitors by channel, docs page views, returning visitors.

• Conversion question: which channels send visitors who read docs, not only the home page?

• Formo groups traffic into 13 channels, such as Organic Social, Paid Search, AI, and Referrals, using the referrer, UTM parameters, and ad click IDs.

Developer activation

• Metrics: wallet connects, API keys created, quickstarts completed.

• Conversion question: what share of engaged visitors connect a wallet or create a key within their first week?

• The Formo web SDK autocaptures wallet connects, signatures, and transactions by default (in wagmi mode, for calls made through wagmi hooks). Backend milestones such as "API key created" can be sent with the server SDK.

Qualified opportunity and technical evaluation

• Metrics: opportunities created, opportunities by source, days in evaluation.

• Conversion question: what share of qualified opportunities reach a testnet deploy, and which sources convert best?

• These stages live in your CRM. Record the account's wallets here, so the onchain stages can link back.

Testnet and mainnet deploy

• Metrics: deploys per month, days from testnet to mainnet, share of testnet deploys that reach mainnet.

• Conversion question: where do integrations stall between testnet and mainnet: audits, legal, or engineering time?

• Add the relevant contracts in Formo to ingest their events, then use those events as funnel steps. Check the chains page for which networks support contract events.

First volume and revenue

• Metrics: days from mainnet to first volume, days from first volume to first invoice or first fees, revenue per account, share of accounts still paying after 90 days.

• Conversion question: what share of integrations with first volume reach revenue, and which acquisition sources produce accounts that keep paying?

• If integrators tag transactions with ERC-8021 builder codes, Formo parses them from the calldata of the transactions it records and lets you break down wallets, transactions, volume, and revenue by builder code. Contract value and invoices live in your CRM and billing system.

The table sums up one example set of metrics per stage.

How do you instrument onchain milestones in the funnel?

Instrument onchain milestones by linking each customer account to the wallets and contracts that prove progress, then recording those as events. Use web analytics for the visit and connect, contract event ingestion for deploys and volume, and the CRM and billing system for the commercial stages and revenue. The steps below work for most infra, wallet, and protocol teams.

1. Install the SDK on site, docs, and app. Use one Formo project and one write key across them.

2. Identify builders. Call identify when a builder connects a wallet or signs in, and pass your user ID. Wallets that share a device cookie or a user ID are linked.

3. Store deploy wallets on the CRM account. Ask for them at technical evaluation. Without them, the onchain stages cannot link back.

4. Ingest contract events. Add your contracts, or the customer's, in project settings and select the events that mark a deploy or a transaction. A deploy shows up only as an event, for example from your own factory or registry contract, because Formo ingests events from contracts you add, not contract creation.

5. Build the funnel. Use page views, custom events, and contract events as steps. The default conversion window is 2 hours, so set it in days or weeks for integration journeys, or use an any-order funnel.

6. Send stages both ways. Push CRM stages, including revenue, to wallet profiles as labels with the API, and export Formo data to the warehouse as CSV, or through data sync once Formo support enables it.

Which tools cover which stages of the funnel?

Most B2B crypto teams use four kinds of tools: product analytics for web and wallet behaviour, a CRM for deals and revenue, chain data tools for onchain proof, and a warehouse to join them. No single tool covers all nine stages well. Pick the system of record for each stage, then decide where the joined report lives.

Formo data sync exports events, users, wallet profiles, and SQL results to Google Cloud Storage or Amazon S3, on a cron schedule or on demand, in CSV, NDJSON, or Parquet. Data sync is in development; contact Formo support for access.

What conversion rates should you expect?

You should expect your own rates, not an industry average. Public, dated benchmarks for B2B crypto stages such as testnet to mainnet do not exist in a reliable form, and deal sizes vary too much between an RPC plan and a custody contract. Build a baseline from your own cohorts, then improve against it.

How to build a baseline:

• Cohort by quarter of entry. Group opportunities by the quarter they were created.

• Measure each step separately. Opportunity to testnet, testnet to mainnet, mainnet to first volume, and first volume to revenue.

• Track time, not only rate. A 60 day median from testnet to mainnet tells you more than a single percentage.

• Split by source. Compare conference, partner, inbound, and hackathon cohorts.

• Wait for cohorts to mature. Do not judge a cohort before its median deal could finish.

See conversion rate and funnel analytics in the glossary.

Frequently asked questions

What is the most important stage in a B2B crypto sales funnel?

Revenue, because the funnel ends there. Before revenue, mainnet deploy matters most. A signed contract with no deploy is not adoption, and a deploy with no volume rarely earns fees. Most teams find their biggest leak between testnet and mainnet, so measure that step first.

How long is a typical B2B crypto sales cycle?

It varies too much to give one number. A self-serve API plan can close in days. A custody or protocol integration with audits can take many months. Measure the median time per stage for your own deals and report it each quarter.

Can I track a customer's onchain progress without asking them?

Partly. Deploys and transactions are public, so if you know the customer's contracts or wallets, you can watch them. Most teams still ask for deploy wallets during evaluation, because guessing which wallets belong to which customer is error-prone.

How do I connect CRM stages to onchain data?

Store the customer's wallets and contracts on the CRM account. Then join on those addresses in a warehouse, or push the CRM stage into your analytics tool. In Formo you can add CRM stages to wallet profiles as labels through the API.

Do anonymous developers belong in the funnel?

Yes. Developers who read docs and connect a wallet are often the first sign of a future deal. Track them as engaged visitors and activated developers. When the account later becomes an opportunity, their earlier activity shows how the deal started.

Which funnel conversion window should I use for integrations?

Use a window that matches your cycle, such as several weeks for testnet to mainnet. Formo funnels default to 2 hours and accept windows from minutes to months. An any-order funnel matches steps across the selected date range, with no window between steps.

Related articles

• The DeFi growth funnel

• Crypto acquisition funnel tracking guide

• Dapp funnel analytics

• How to measure crypto marketing ROI

• Crypto marketing tactics, metrics and tools