Apollo (and peers) excel at contacts, sequences, and scale. They fail when your message is generic - because nobody captured which accounts discuss painful migrations, or which phrases show budget urgency in plain language.
Order matters:
- Public intent and language
- Account selection (ICP + trigger)
- Contact paths (Apollo / LinkedIn / warm intro)
- CRM and follow-up
Step 1: Hypotheses from public posts
Search patterns like:
"evaluating {{category}}"on Reddit / HN"moving off {{competitor}}""alternatives to {{incumbent}}""frustrated with {{vendor}}"
Save URLs; tag themes: security, pricing, integration, support.
Use alternatives mining guide for query families. Search ranks results by intent when you repeat weekly.
Step 2: Map themes to accounts (carefully)
Public posts rarely equal permission to email. Use threads to:
- Improve website copy and case studies
- Identify accounts to research when company is identifiable and outreach is appropriate
- Train AEs on objection language
Never scrape emails from profiles or DMs without consent.
Step 3: Build small Apollo lists
One angle per segment - the angle came from Step 1.
| Segment | Hook source | List size |
|---|---|---|
| Competitor switchers | Thread quotes | 50–100 |
| Greenfield category | Problem phrases | 50–100 |
Start small; measure reply rate before scaling sends.
Step 4: CRM truth (template)
Account: Acme Corp
Trigger: HN thread 2026-06-01 - SOC2 export gap
Quote: "We can't get audit logs out of X"
Hypothesis: Compliance mid-market
Sequence: compliance-angle-v2
Status: Replied / meeting booked
Future you - and your AE - will thank you.
Minimum stack by stage
| Stage | Stack |
|---|---|
| 0–10 customers | Spreadsheet + manual search + email |
| 10–50 | CRM + Apollo + research workflow |
| 50+ | Add enrichment, dedicated SDR, playbooks |
See B2B GTM tools map.
What not to do
- Blast scraped lists with AI mail-merge fluff
- Ignore unsubscribes and bounces
- Confuse "they mentioned pain" with "they want cold email"
- Same sequence for every thread theme