How to Qualify Crypto Leads With Wallet Data

To qualify crypto leads with wallet data, you define MQL and SQL stages and back each one with onchain fit and intent signals. Fit comes from what a wallet holds and which apps it uses. Intent comes from what the wallet and its owner do on your site and contracts. Clear stage rules then decide when marketing hands a lead to sales.

What is lead qualification in crypto?

Lead qualification in crypto is the process of deciding which wallets, people, and accounts deserve sales or marketing time. It uses the classic stages, such as MQL and SQL, and adds onchain evidence. A wallet's holdings, protocol use, and history show fit. Its connects and transactions on your app show intent.

Two business models use it in different ways.

• Onchain apps (DEXs, lending markets, perpetual futures (perps) exchanges, and wallets) qualify high-value users for a partnerships, VIP, or institutional desk. The lead is a person with one or more wallets.

• B2B crypto (RPC, data, custody, wallet infrastructure, and protocols that sell integrations) qualify teams. The lead is an account: a protocol, a DAO, or a fund. Our guide to account intelligence for crypto explains how to group wallets into those accounts.

What are MQLs and SQLs for onchain apps and B2B crypto?

A marketing-qualified lead is a lead that marketing judges ready for more attention, based on fit and engagement. A sales-qualified lead is one that sales has reviewed and accepted as a real opportunity. Onchain apps and B2B crypto teams use the same two stages, but the evidence behind each is different.

Some teams add a product-qualified lead (PQL): a user who reached a key action in the product, such as a first deposit or a first API call. In crypto, the first onchain transaction is often the best PQL trigger.

Which wallet data signals show fit and intent?

Fit signals show whether a lead looks like your best customers. Intent signals show whether the lead is acting now. Wallet data adds both. Fit comes from net worth, apps used, labels, and wallet age. Intent comes from connects, transactions, visits to high-intent pages, and lifecycle changes on your own app.

Read each signal with care. In Formo, net worth is verified token holdings plus DeFi positions net of debt where available, and Solana wallets include token balances only. Net worth is capacity, not a buying budget. A fund's trading wallet can hold millions and still have no need for your product.

How do you build a lead stage table?

A lead stage table lists each stage with its entry rule, its owner, its exit rule, and a time limit. Marketing and sales agree on it in writing. It stops the two common failures: sales ignoring leads it did not trust, and marketing counting leads that sales never saw.

The numbers are examples. Set yours from your own data: look at the wallets and accounts that became customers last quarter and find the thresholds they share.

How do you qualify crypto leads with wallet data step by step?

To qualify crypto leads with wallet data, first remove the addresses you should never score. Then define a fit segment, add intent rules, route matches to sales, and review the results each month. The process below works for onchain apps and for B2B teams that track their prospects' wallets.

1. Exclude bad addresses. Build an exclusion segment: OFAC Sanctioned label, published sybil list labels, known exchange and custody addresses (tag them with your own custom label), and the Bots device type.

2. Define fit. Study last quarter's best customers. Build a segment from the labels, apps, net worth, and wallet age they share.

3. Define intent. Add behavioural rules, such as "connected and made a transaction 2 or more times in 30 days", or visits to pricing and docs pages.

4. Save the MQL segment. Combine fit and intent, then save it so the whole team uses the same definition.

5. Route to sales. Send new matches to Slack or your CRM through a user alert webhook or a CSV export.

6. Confirm with a person. Sales reaches out and records need, buyer, and timeline. Only then does the lead become an SQL.

7. Review monthly. Compare MQL to SQL and SQL to won rates by segment. Tighten rules that send noise.

Formo supports each step. Segments combine wallet labels, net worth, lifecycle stage, apps, tokens, device, and attribution data, and behavioural segments support AND and NOT logic over events in a time period. User alerts send matching profiles to a webhook or a Slack incoming webhook, and each matching user is notified once per 24 hours. User alerts take profile filters (net worth, labels, lifecycle, apps, tokens, chains, and attribution), not a saved segment or event counts, so copy the fit part of your MQL rule into the alert. You can also export a segment as CSV or query profiles through the Profiles API.

What handoff rules should marketing and sales agree on?

Handoff rules say when a lead moves from marketing to sales, how fast sales must act, and what happens when sales says no. Without them, good leads go stale and both teams argue about lead quality. Write the rules down and review them each quarter.

• One definition. The MQL is a saved segment, not a judgment call. Everyone reads the same list.

• Response time. Sales accepts or rejects each MQL within an agreed time, for example 2 business days.

• Reason codes. Every rejection gets a reason: no fit, wrong person, too early, already a customer, or bad address.

• Recycle path. "Not now" leads go back to nurture with a date to check again, not to the bin.

• Account rule for B2B. When a lead belongs to an account that already has an open opportunity, attach it to that opportunity. Do not create a new MQL.

• Feedback loop. Marketing reviews reason codes monthly and changes the segment rules.

What pitfalls should you avoid when you qualify leads with wallet data?

The main pitfalls are fake or shared wallets, reading too much into one number, and careless use of personal data. Each one can fill your pipeline with leads that look strong on paper and never convert. Check for them before the first handoff.

• Sybils and farmers. Airdrop farmers can create wallets that look active. Formo labels wallets named on published sybil lists from LayerZero, Hop, and Optimism. These lists are historical snapshots, so treat them as one signal. Human Passport scores add a second check. Read more about sybil attacks.

• Exchange and custody addresses. Pooled deposit and hot wallets hold large balances for many users. They are not leads. Keep a list and exclude them.

• Sanctions. Formo's OFAC Sanctioned label comes from Chainalysis's onchain sanctions oracle, which covers EVM addresses. Exclude sanctioned wallets and ask your compliance team about the rest.

• Bots. Formo labels known crawlers and automated clients as the device type Bots. They stay in visitor counts, so filter them out.

• Net worth as budget. A large balance shows capacity, not need or authority to buy.

• Missing data. Solana wallets have token balances but no DeFi positions in net worth, so DeFi rules will not match them.

• Privacy. European regulators can treat wallet addresses as personal data. The EDPB Guidelines 02/2025 on processing of personal data through blockchain technologies (version 2.0, adopted 7 July 2026) say that public keys and wallet addresses qualify as personal data when they can identify a natural person by means reasonably likely to be used. Tell users what you collect, use it for a stated purpose, and ask your legal team before you join wallets to emails.

Frequently asked questions

What is an MQL in crypto?

An MQL in crypto is a lead that matches your ideal customer profile and shows early intent. Fit can come from wallet data such as net worth, apps used, and labels. Intent can come from connects, transactions, and visits to high-intent pages.

What is the difference between an MQL and an SQL?

Marketing qualifies an MQL with data and rules. Sales qualifies an SQL by talking to a person and confirming need, buyer, and timeline. An MQL is a candidate. An SQL is a real sales conversation.

Can wallet data replace a sales call?

No. Wallet data shows fit and activity. It cannot show need, authority, or timing. Use it to choose who to call and what to say, then confirm with a person.

How do I stop sybil wallets from becoming MQLs?

Build an exclusion segment and apply it before any other rule. Include sybil list labels, low Human Passport scores, sanctioned wallets, bots, and pooled exchange addresses. Then review leads that sales rejects for bad addresses.

Is a wallet address personal data?

It can be. European regulators can treat a wallet address as personal data, especially when you can link it to a person. Handle wallet data with the same care as other customer data, and get legal advice for your case.

Does Formo have a built-in MQL field?

No. You build MQL rules as saved segments from labels, lifecycle, net worth, apps, and behavioural filters, then route matches with user alerts or exports.

Related articles

• Account intelligence for crypto

• Crypto user segmentation

• What is wallet intelligence

• Wallet profiles growth playbook

• What are sybil attacks in crypto and how to prevent them

Glossary: wallet labels, sybil wallet, high-value wallet.