Good founder outbound starts with a public evidence snippet (link + quote), one crisp hypothesis, and a low-pressure ask. If you cannot explain why this person in two sentences, skip the send.
Best for: founder-led B2B with visible technical buyers - not spray-and-pray consumer blasts.
Go / no-go checklist
Before DM or email:
- You helped publicly in-thread OR they asked for solutions
- You can cite their constraint (team size, stack, timeline)
- You disclosed affiliation if mentioning product
- Platform rules allow the channel (see Reddit checklist)
- You are under your weekly cap (suggest 5–10 touches)
The five-field handoff note
| Field | Example |
|---|---|
| Source URL | Link to thread or issue |
| Quote | "Export to CSV broke our audit" |
| ICP fit | 50-person fintech, SOC2 |
| Risk | May be student project |
| Ask | 15-min call or async doc review |
Paste into CRM before you send - not after.
Message skeleton (ethical)
Public reply first (preferred):
[Helpful tip addressing their constraint - no link]
(Disclosure: I'm building [product] in this space - happy to share more if useful.)
DM/email (only after value or invite):
Hi [name] - saw your point about [specific pain] on [platform].
We built [one sentence] for teams dealing with [constraint].
[One proof point - customer type or doc]
If you're still exploring options, open to a 15-min chat this week?
Either way, hope [tip] helps.
Avoid: fake familiarity, multi-paragraph pitches, scraped personal emails.
Volume and spam thresholds
| Signal | Action |
|---|---|
| 0 replies after 20 sends | Fix message or ICP - not "send more" |
| Mod warning | Stop promotional pattern immediately |
| Unsubscribe / block | Remove from sequence; review targeting |
Motion fit
| Motion | Use this SOP |
|---|---|
| Design partner hunt | Yes - high touch |
| Transactional SMB PLG | Partial - prefer in-product |
| Enterprise ABM | Threads = intel; warm intros = close |
Pair with intent before Apollo when scaling beyond founder sends.