324 Meetings in Three Months for a Crypto Accelerator

This Telegram outreach case study follows a crypto accelerator's three-month project: 3172 touches, 324 meetings and $15,728 in client revenue across all channels. Telegram wasn't part of the first stage, though. That stage was built around LinkedIn, so this is a LinkedIn outreach case study too. Here's how the project ran, why most of the resources moved into messengers, and what you can reuse in your own outreach.

The brief: subscribers from the US, Europe and Asia

The client is a crypto accelerator. It offers startups a subscription to its network, which includes venture funds and decision makers at crypto companies. The startups had to come from three regions: the US, Europe and Asia. The goal was to grow the subscriber pool within three months.

That's a tough brief for cold outreach. Three regions mean different time zones, and a message that works in one market may fall flat in another. The offer is also harder to explain than a typical service: you're selling access to people, and the value of that access has to come through in one short message.

Where we started: LinkedIn outreach and 12 scripts

In the first stage we set up the infrastructure and warmed up a C-level LinkedIn account, meaning the profile of a senior executive. Why a C-level account is the usual choice: at a startup, a founder typically makes this kind of call, and a founder is more likely to accept a request from an executive than from a sales rep.

We don't send from any account before it's warmed up. A cold account burns out within a week.

Next came an A/B test across 12 scripts, different versions of the message compared against each other. The project reached a 70% acceptance rate on connection requests. Across our B2B campaigns, 60-70% of LinkedIn requests usually get accepted, so this one landed at the top of that range.

Here's our usual launch order. It's our standard process, not the timeline of this specific project:

1. Discovery and ICP, week 1. Two hours with the client on who buys, who says no and what comes up in meetings. The ICP, or ideal customer profile, turns into segments and selection criteria.
2. Infrastructure, weeks 1-2. Domains and mailboxes, LinkedIn and messenger accounts, warm-up.
3. Database and scripts, week 2. We collect and verify contacts and write first-touch variants for each segment.
4. Launch and A/B tests, weeks 2-6. We review the numbers every week and close a silent segment in week two.
5. Handover. An interested contact lands in the client's CRM with the full conversation history. We book the meeting, the client runs it.

What changed along the way: Telegram and 74% of resources

In the second stage we wrote scripts for Telegram. The channel pulled ahead fast: within a month it passed every other channel in the project on meetings booked, email included.

From there, resources followed the meetings. In the third stage we:

• redirected 74% of the project's resources into messengers
• expanded the team
• tested 11 new hypotheses. In outreach, a hypothesis is an assumption that a specific segment will respond to a specific message or channel

We move resources to where the meetings are, not to where opens and replies look best. In our campaigns, if a segment falls outside the usual range, it shows by week two, and we change the channel instead of waiting. We cover when to add LinkedIn and Telegram to email in our guide to B2B cold email.

Here's an example of a first Telegram message for this kind of segment. It's a template for illustration, not a message from the project:

"Hi [Name], I see [project] is raising right now. We run a crypto accelerator with a subscription that connects startups with venture funds and decision makers at crypto companies. Want me to send the list of funds in our network so you can see if any of them fit?"

The template has three parts: a reason to reach out that comes from the startup's own situation, one line on what the subscription gives, and an easy next step the person can say yes to.

Results in numbers

Run the same numbers and you get roughly one meeting for every ten touches (324 out of 3172). That's the ratio this project produced, not a promise for every segment. Behind those results are 12 scripts in the first test and 11 hypotheses in the third stage.

What to apply to your own outreach

• Run several channels and compare them on meetings. Opens and replies tell you the message gets read. A meeting tells you the person wants the conversation.
• Don't send from accounts that aren't warmed up. A cold account burns out within a week, before the channel can show you any numbers.
• Test several messages at once. This project started with 12 scripts in its first test.
• Make channel decisions early. A silent segment shows by week two, so there's no reason to wait until month three.

If you want to find out which channel works for your segment, start by testing segments in the first weeks. That's how our outsourced SDR service works: Telegram and LinkedIn outreach alongside email, with the list, scripts and conversations on our side, meetings on your calendar and a weekly report in numbers.

Decide before the first touch which number will tell you to switch channels, and who checks it every week. Then you'll spot a channel like Telegram in this project within weeks of adding it, not in the final report.