LeadAITelegram bases

Telegram audience mining

Ten thousand people are talking.
We hand you the nine hundred who matter.

And next to every one of them, the sentence explaining why they made the list, quoted from what they said themselves.

@minh_••••KEEP

“vào lệnh long BTC x10, ăn non r… tuần trước cháy tài khoản”

why Posts his own leveraged entries and a liquidation last week. Trades his own capital, daily.

@kate_••••KEEP

“looking for influencers and traders to bring onto our exchange, DM open”

why Exchange BD stating the need out loud. Buys audience as a job.

@vip_signal_••DROP

“VIP room 99$/mo — 87% winrate, limited slots, DM now”

why Sells signals to the same people you want. A competitor, not a lead.

Three rows out of a chat with eighteen thousand members. The other 17,997 were read too, which is the part nobody else does and the only reason the three above can be trusted.

Collection

How a base is actually built.

Seven passes, and the order is the point. Each one throws away work the next would otherwise waste money on.

01

Brief

Who counts, and who does not. Exchange affiliates but not signal sellers. Traders with capital but not airdrop farmers. This sentence is what the classifier is judged against later, word for word.

02

Discovery

A keyword grid built in the language your audience types in, crossed with city and community patterns. Twenty seed terms become a hundred queries.

03

Audit

Search results lie. Every chat is sampled for messages a day, unique authors and spam share. Half to two thirds are dropped before one contact is harvested.

04

Harvest

Participants plus what they themselves wrote. A handle with no history can only be guessed at. Accounts without a username are dropped, since nothing can reach them.

05

Qualify

Each candidate read against your brief in the original language. Back comes a verdict, a reason quoting their own behaviour, and a summary. Rejects ship too.

06

Dedup

Every handle ever classified sits in one index. Nobody in your base was messaged for another client, and nobody known is paid for twice.

07

Write

One message per person, built from their own stated need. Where data is thin it stays general instead of inventing a detail.

• conference windows

The cheapest week of the year to mine.

Before an event, its chat fills with people introducing themselves: who they are, what they sell, who they want. That is a filled-in questionnaire nobody had to ask for, and it expires. We run those chats on the event calendar, two weeks out and one week after.

Who we find

Quoted by how rare it is, not averaged.

Audiences are not equally dense. Traders are everywhere once you know which chats to read. Serious affiliates are not. Each is quoted on its own instead of blended into one flattering number.

Traders and retail usersspot & futures, by geography, active 30d
5,000–10,000 / mo
Players and product usersgamefi, socialfi, tap2earn, testnet
5,000–10,000 / mo
KOLs, group admins, community leadspeople who already hold an audience
400–600 / mo
Investor sidefunds, angels, family offices
100–200 / mo

Ranges, not guarantees. A tighter brief lowers the count and raises the quality, and that trade is better agreed before the first invoice than after it.

Delivery

One row per person, rejects included.

Shipped columns: handle, name, company, role, segment, source chat, what they want, what they offer, summary, verdict, reasoning.

HandleVerdictReasoning
@lan_•••• KEEP Accumulating monthly since 2023 and asking how to move funds off the exchange into a wallet. A long horizon holder with real capital.
@marcel_••• KEEP Runs affiliate partnerships for an exchange and asks the room for partners. States the need himself, so no inference required.
@tuan_•••• THIN Three messages, all one word reactions. No evidence of trading anything, so the brief cannot be confirmed either way.
@airdrop_••• DROP Only ever posts referral links and farms testnet tasks. No capital behind the account, so volume without value.

Sending

Slow on purpose. A burned account costs more than a day of volume.

Delivery is an infrastructure problem, not a copy problem. Accounts belong to your campaign alone, are warmed before they carry anything, and run well under the ceiling rather than at it.

Per account / day
35 messages, hard capped in the sender rather than left to judgement.
Interval
Randomised 60–120s between sends, floor of 2s between any two API calls on a session.
Isolation
Dedicated accounts and sessions per client. One problem stays one problem.
Warmup
Accounts are aged and given a real profile before the first campaign message leaves them.
Replacement
A restricted account is replaced and the sequence continues. Included, not billed as an extra.
Start
A campaign begins when a human picks the base and launches it. Nothing sends itself.

Throughput

Capacity is accounts times the cap. That is the whole formula.

Scaling means adding warmed accounts, never pushing existing ones harder.

3 accountsstarting setup, enough to test scripts properly
105 / day · ~3,100 / mo
6 accountsonce a winning script is established
210 / day · ~6,300 / mo
12 accountsfull rate on a proven flow
420 / day · ~12,600 / mo
24 accountswhere the base, not the sender, becomes the limit
840 / day · ~25,000 / mo

Size this against how many replies your team can answer. Sending more than you can handle is how a good base gets wasted.

Measured

Numbers from our own runs.

737qualified profiles from one pass over 50 chats
90,883handles in the index every base is deduped against
21.5%reply rate on our own outbound in this niche

Ours, from campaigns we ran ourselves. Your reply rate depends on your offer, and showing you the mechanism beats quoting someone else's conversion.

Next

Tell us who you need. We will tell you how many exist.

Send the profile you are after. Back comes the realistic monthly number for that audience, the chats it would come from, and a sample of qualified rows with their reasoning, so the targeting can be judged before anything is agreed.

Message us on Telegram