24 Hours in the Life of a Top Web3 BD: How He Manages 50 Telegram Groups
A Web3 market maker's BD sits on 50 Telegram groups and wakes up to 999+ unread messages. This is his full daily loop: filtering candidate leads in the morning, reading a month of an ID's past messages before deciding on an opener, writing every lead's status back into the system before leaving, and leaving monitoring running overnight.
Signals to watch
- A founder complains in a group that testnet TPS will not climb and is urgently looking for an experienced market maker to help optimise
- Two weeks earlier the same ID discussed ZK-Rollup data availability schemes in depth in another group
- The same ID has publicly dismissed the pure capital injection model used by some top-tier market makers
- Three leads followed up today carry new statuses in the system: Term Sheet sent / not a target / initial contact with a reminder
In Web3, Telegram is essential infrastructure. A competent business developer (BD) may have only a handful of contacts on WeChat, but on Telegram they are almost certainly sitting in dozens or even hundreds of industry groups.
What does “Web3 BD daily work” actually look like? To many outsiders it means posting the company PR in groups every day, adding contacts, and sending mass DMs. But to a genuinely top-tier BD, it is a drawn-out campaign of information processing, timing and deep background checks.
We documented a day with Alex, a senior Web3 market maker (MM) BD, to reconstruct how an efficient “Telegram lead generation workflow” actually runs.
09:00 AM: Morning filtering, from 999+ down to 15 high-priority leads
The first thing Alex does at the office is not open Telegram and crawl through the “999+” unread messages his 50 groups piled up overnight. Doing that by eye would eat the whole morning, and it is very easy to miss the one message that matters.
He opens his laptop and logs straight into Top Prospect.
The monitoring keywords he set the night before — “TGE”, “liquidity”, “urgently seeking MM”, “mainnet delay” — have already filtered the noise out of all 50 groups. In Top Prospect’s “candidate leads” list sit 15 high-priority discussions, lined up neatly.
Alex scans the context quickly. One of them catches his attention: a project founder is complaining in a group that “testnet TPS won’t climb, urgently looking for an experienced MM to help optimise”. Under that message there are none of the usual “we’ll pump your token” spam ads — instead, a few people who clearly know the space are discussing the technical side.
Alex clicks “mark as high priority” and sets the status to “focus for today”. These 15 leads are his battlefield for the day.
Diagram: the thousand-plus overnight group messages go through the monitoring keywords first — the noise stays outside the sieve and only a dozen or so items are actually left to handle today; the bubbles and quantities shown are illustrative, not a real record.
14:00 PM: Deep background check — let the bullet fly a while
In the afternoon, Alex gets ready to follow up with the project founder he locked onto in the morning.
A junior BD would probably have already rushed in with: “Hello, we’re XX market maker, we deploy a lot of capital, DM?” But Alex knows that with a technical founder like this, that opener is very likely to be read and ignored.
He does not rush into a DM. Instead he uses Top Prospect’s “source analysis” feature to trace this ID’s messages over the past month.
From the context the system pulls out, Alex discovers: two weeks earlier this founder had discussed “ZK-Rollup data availability schemes” in depth in another group, and had openly dismissed the “pure capital injection” model some top-tier MMs rely on.
“So he’s a technical geek who dislikes pure capital plays.” Alex now had his footing.
He reworked his approach for the afternoon. In the DM he did not mention capital at all. He said: “I saw you discussing TPS optimisation in the group. We’ve helped a few ZK projects with liquidity market making before, and we have some experience with order book depth and on-chain interaction latency. Is the bottleneck on your testnet at the consensus layer or at the execution layer?”
Ten minutes later, the reply came: “Finally someone who actually understands the tech. Let’s talk.”
Diagram: before sending a DM, lay out a month of that person’s past messages to work out what the first line should say — the opener skips capital and asks about the technical bottleneck instead; the conversation shown is illustrative, not a real record.
18:00 PM: Lead handoff and status tagging — saying goodbye to the black box
As the day wound down, Alex finished his first round of conversations with three projects.
In the past, a BD’s follow-up notes lived inside their own head, or were scattered across various DM threads. The moment they took leave or left the company, these assets in the “Telegram lead generation workflow” were gone for good.
Alex opens Top Prospect and updates the status of the 3 leads he followed today:
- Project A: moved from “to verify” to “Term Sheet sent”.
- Project B: tagged “not a target / grey industry”, with a note on the reason (refused to provide a code audit).
- Project C: status stays “initial contact”, with a follow-up reminder set for next Wednesday.
With this kind of structured status management, Alex not only knows exactly where he stands today; his team lead can also see how the whole business development SOP is being executed in the backend, which effectively stops the team from colliding on the same lead.
Diagram: every lead followed up today is written into its own status column, so progress stays in the system whether or not the person is at their desk; the status labels shown are illustrative, not a real record.
22:00 PM: Bedtime review and “idle” monitoring
At 10 p.m., Alex gets ready to rest.
Web3 is a market that never sleeps, 24 hours a day — many important discussions happen late at night in Asian time, which is daytime in Europe and the US. Alex does not need to stay up watching the screen.
Before bed he does one final check of his Top Prospect monitoring settings, making sure core words like “market making”, “listing” and “liquidity” stay active through the night.
“When I wake up tomorrow morning, the system will tell me who sent a real signal in a group tonight.” Alex puts his phone down and goes to sleep with an easy mind.
Diagram: late night in Asian time is daytime in Europe and the US — the person is asleep while the monitoring keywords keep watch in the groups on their behalf; the bubbles shown are illustrative, not a real record.
BD notes
People often ask: isn’t managing 50 Telegram groups exhausting?
Alex’s answer: “If you’re fighting the information stream with physical effort, of course it is. But if you treat the tool as your external brain, letting the system handle the noise and the human brain handle judgement and conversation, then it is just focused mental work.”
In a space that shifts as fast as Web3, the information gap is the profit. And efficient business development is, at heart, an arms race over how information is acquired and processed.
This article is human-authored. TOP Prospect processes only Telegram groups the user has explicitly authorized and connected. Its output supports human sales judgement; it does not replace human decisions and does not automatically contact or message group members.
How a Signal worth attention is found
See how Top Prospect finds and organizes Signals worth checking, keeps the original Telegram context, removes duplicates, and helps you decide what to review first. You decide whether to follow up and what to do next.
