1000 Leads in a Week: How to Read Such Cases Without Fooling Yourself
"1000 leads in a week" headlines sell. Most hide the math that matters. We published our own such case here: https://www.24go.site/blog/kays-1000-lidov-za-nedelyu?locale=en - and this is the honest guide to reading it, and any case like it.
Ask for the denominator
1000 leads from how many messages, groups, accounts, and days? A thousand leads from 200,000 scanned messages is a 0.5% hit rate - solid infrastructure, average targeting. The same thousand from 10,000 messages is elite targeting worth studying. Without the denominator, the headline is decoration.
Leads are not deals
Separate the funnel publicly: scanned → replies → qualified → calls → closed. Our case reports all five stages. Any case reporting only stage one ("we collected N contacts") tells you about parsing speed, nothing about business. Contacts are inventory. Deals are revenue.
Check what was excluded
Setup time, warm-up period, proxy and tooling costs, manager hours answering replies. A case that counts only software spend and ignores three weeks of warm-up understates true cost per lead by multiples. Honest cases list full inputs.
Reproduce one slice
Do not copy the whole machine. Take one repeatable slice - group selection criteria, first-message template, follow-up timing - and test it on your audience for a week. If the slice works standalone, adopt it. The full case is inspiration; the slice is the asset. Starting template if you run your own test: https://www.24go.site/blog/poshagovaya-instruktsiya-lidogeneratsiya-za-30-minut?locale=en
Honest limits
Survivorship bias is real: you read the case that worked, not the nine configurations that failed first. Ask authors what they tried that flopped. Their failures section is usually more valuable than the headline number.
And markets move. A tactic from six months ago meets burned-out audiences and tightened admin rules today. Date-stamp every case you act on.
What is the most inflated case study you almost acted on?
Top comments (1)
"Ask for the denominator" is the one I would put first. For list building the denominator is the count before the pull: if 22,000 people match the filter and the case shows 1,000, the interesting question is which 1,000 and why, not the thousand itself. The other number I look for in a case like this is the hit rate of a small random sample before the full run, because the first page of a sorted result usually lies about the rest. A case that reports both is one you can reproduce; a case that reports only the thousand is a headline.