Multi threading in sales means building a relationship with several people at 1 account, so a deal does not rest on a single contact who can leave or go quiet. NAUT tracks 67 live crypto project teams that list a founder or CEO, a BD or partnerships lead and a marketing, growth or community lead on file as of 14 November 2026, and 145 that list at least a founder plus a BD lead.
How this was counted: on 14 November 2026 NAUT read every live project company in its database (6,974) and every person attached to one by their own company record. 3,719 projects have at least 1 person on file. Each person was sorted into a role by their job title alone: founder or CEO, BD or partnerships, and marketing, growth or community. A team counts when it has at least 1 person in each role. 63 of the 67 hold the 3 roles in 3 different people; at the other 4, 1 person's title covers 2 roles. 5 claims behind this piece were put to outside pages: 3 were confirmed and used, and 2 (the Oasis titles in the worked example) were not confirmed by any page that could be read, so those titles appear here as NAUT lists them. Every count is NAUT's record on that day, which is not the whole market.
What is multi threading in sales?
Sales multithreading is the practice of reaching more than 1 person at the account you are selling to. Dock's guide puts it as "Sales multithreading focuses on creating, nurturing, and building relationships with multiple people" (Dock). The risk it covers is the single threaded deal: the same guide warns about what happens "if that point of contact or buyer champion leaves or is no longer involved in the decision-making process" (Dock).
In crypto BD the 3 threads that matter at a project are usually these:
- The founder or CEO, who signs off on budget, token allocations and anything strategic.
- The BD or partnerships lead, who runs integrations, listings and partner deals day to day.
- The marketing, growth or community lead, who owns campaigns, co-marketing and the community that will use what you sell.
How many crypto teams can you multi thread on NAUT?
67 live project teams on NAUT have all 3 roles on file, and 145 have at least a founder plus a BD lead. The table counts teams with each mix of roles; a team with all 3 also counts in each pair above it.
| Roles | Teams | Threads |
|---|---|---|
| All 3 | 67 | 3 |
| Founder, BD | 145 | 2, deal |
| Founder, mktg | 422 | 2, growth |
| BD, mktg | 89 | 2, no founder |
| Founder only | 1,908 | 1 |
The largest group is the last one: 1,908 teams list a founder and nobody in BD or marketing, so at those teams the founder is the 1 thread on NAUT's record today.
Oasis Network
Centrifuge
Cardano
LayerZero
KaiaEach of these 5 teams lists 10 to 12 people on NAUT's record, so the 3 threads come with backups if 1 person does not answer. Beside Oasis Network, the 4 others are Centrifuge, Cardano, LayerZero and Kaia.
How do you do multi threading in sales at a crypto team, in 4 steps?
Pick the 3 roles, order the touches, change the angle for each role, and know when to stop.
- Pick the 3 rolesOpen the team on the project's NAUT page and pick 1 founder, 1 BD lead and 1 marketing or community lead.
- Order the touchesStart with the BD lead, then the founder, then marketing, a few working days apart.
- Vary the angleGive each role the part of your pitch that is their job: budget, the deal, the campaign.
- Set stop rulesStop a thread after 2 follow-ups with no reply, and stop all 3 on a clear no.
Step 1: pick the 3 roles
Open the project's NAUT page and read the team list. Choose 1 person per role, and prefer a "Head of" title over a "Manager" when both sit in the same role. If a role is empty, use the table above: at the 145 teams with a founder and a BD lead you can still run 2 threads.
Step 2: order the touches
Lead with the person whose daily job your offer touches, which for most BD offers is the partnerships lead. Reach the founder next with a shorter note that names the BD conversation, then marketing. Telling each person who else you are talking to keeps the threads from looking like a blast.
Step 3: vary the angle by role
The same pitch sent 3 times reads as spam. Give the founder the outcome and the cost, the BD lead the integration or deal terms, and the marketing lead the audience or campaign. Each note should still stand alone if it is the only one read.
Step 4: set stop rules
Decide the stop rules before you send. A sensible default: 2 follow-ups per thread, then stop that thread; a clear no from any of the 3 ends the sequence; a reply from 1 pauses the other 2 while you follow up.
Multi threading in sales, worked on Oasis Network
Oasis Network is 1 of the 63 teams, with 12 people on file. Its own docs call it "a Layer 1 decentralized blockchain network designed to be uniquely scalable, privacy-first and versatile" (Oasis docs). Its team on NAUT holds 2 people in the founder role, 1 in BD and 7 in community roles, so the 3 threads are there.
| Role | Person on NAUT | Channels | Touch |
|---|---|---|---|
| BD | Head of Ecosystem / BD Manager (team list) | Telegram, LinkedIn | 1st |
| Founder |  Dawn Song, Founder |
X | 2nd |
| Backup |  Jernej Kos, Co-founder |
Telegram, X | 2nd, if no reply |
| Community | Head of Community (team list) | Telegram, LinkedIn | 3rd |
The 2 founder titles are as NAUT lists them; no outside page NAUT could read confirmed either, so read each person's own bio before you write. The BD and community leads sit on the Oasis Network team list without a page of their own. Anyone listed can ask NAUT to remove their page at https://naut.so/legal/data-deletion.
A crypto BD sequence here would open with the ecosystem lead on Telegram, reach Jernej Kos on Telegram a few days later with a note that names the ecosystem conversation, and close the loop with the community lead once 1 thread has replied.
Related reading on NAUT: How to find decision makers in a company: 5 steps for crypto and Crypto BD leads: 11 names at 10 teams that raised in 2026.
Can you pull this data through the NAUT API?
Yes: GET https://api.naut.so/v1/projects/oasis-network with the header Authorization: Bearer $NAUT_KEY returns 1 company with its team, which is the list you pick the 3 threads from, for 5 credits a call. To find people by role across teams, GET https://api.naut.so/v1/people?q=business development searches names, handles and titles, also 5 credits; the full reference is at naut.so/docs/api and plans at naut.so/pricing. Verified Telegram, email and LinkedIn unlock on any paid NAUT plan, so start a 7-day trial to reach all 3 threads.
Multi threading in sales FAQ
What is multi threading in sales?
Multi threading in sales is building relationships with several people at 1 account, so a deal survives when 1 contact leaves or goes quiet. At a crypto project the 3 usual threads are the founder or CEO, the BD or partnerships lead and the marketing, growth or community lead.
How many crypto teams have all 3 roles on file?
NAUT's data shows 67 live crypto project teams with a founder or CEO, a BD or partnerships lead and a marketing, growth or community lead on file as of 14 November 2026, 63 of them with the 3 roles held by 3 different people. Another view: 145 teams list at least a founder plus a BD lead.
Where can I find a crypto team's founder, BD lead and marketing lead with their contact channels?
Each project's NAUT page lists its team with titles, and GET https://api.naut.so/v1/projects/<slug> returns the same team through the NAUT API; NAUT counted 67 teams with all 3 roles on 14 November 2026. Verified Telegram, email and LinkedIn unlock on any paid NAUT plan, so start a 7-day trial to reach them.
When should I stop a multi-threaded sequence?
A workable rule is 2 follow-ups per thread before that thread stops, and a clear no from any of the 3 people ends the whole sequence. A reply from 1 person should pause the other 2 threads while you follow up.
Sources
- NAUT's own database of live crypto projects and the people on each team, read on 14 November 2026: 6,974 projects, 3,719 with at least 1 person, roles matched on each person's job title.
- Dock, Sales multithreading: the definition and the single-contact risk.
- Oasis docs, Oasis Network overview: how Oasis describes its network.