How to Find Conference Speaker Emails
A practical playbook for getting the verified work email of any conference speaker, what works manually, what scales, and what to never do. Updated for 2026.
Why speaker emails are worth the effort
Conference speakers are pre-qualified prospects. They self-select as decision-makers, they care about a topic specific enough to talk about it publicly, and they just spent real money and time to be in the room. A relevant cold email referencing their actual talk replies at 8-15%, versus 1-3% for a generic outreach. The juice is worth the squeeze.
The manual method (works for 5-20 speakers)
Step 1. Open the conference's public speaker page. Copy each speaker's name + current company.
Step 2. For each one, open Hunter.io, Apollo, or RocketReach and search by name + domain. You'll get a verified email or a likely pattern (e.g. first.last@company.com).
Step 3. Verify the email with a real-time check (NeverBounce, ZeroBounce) before sending. Bouncing 30% of your sends will torch your sender reputation in a week.
Step 4. Build the personalized opener, read their talk title and abstract on the conference site, then reference it specifically in line one.
Time per speaker: 4-7 minutes. Tolerable for a small event. For SaaStr-scale (800 speakers), this is a 50+ hour week of pure busywork.
The automated method (works for 50-1000 speakers)
Step 1. Paste the speaker page URL into a tool that extracts the full roster, names, talk titles, companies, headshots. Most generic scrapers choke on JS-rendered agendas; you want one built for conference layouts.
Step 2. Enrich each row against a B2B data provider (Apollo, Lusha, Clearbit) to confirm current employer and pull the verified work email. Speakers change jobs constantly; the company on the conference site is often months stale.
Step 3. Pre-qualify against your ICP before revealing emails. Email-reveal credits are the expensive part, filtering out wrong-industry or wrong-seniority speakers on raw scraped data first cuts spend by 60-70%.
Step 4. Generate a personalized opener per speaker that quotes their actual talk. This is where most automation fails, they generate template-spam. The opener should reference the talk title and the speaker's angle on it; if it could be sent to anyone, it's worthless.
Time on 800 speakers: 5-10 minutes end-to-end with SayIntel, a couple hours stitching it together yourself with raw tools.
Email-finding tools: what they actually do
Apollo: 275M-contact database, reveals work emails per credit. Best raw coverage for North American B2B.
Hunter.io: domain-based pattern matching plus a database. Good for ad-hoc lookups.
RocketReach: similar to Apollo, often catches contacts Apollo misses (especially older execs).
Lusha / Cognism: Europe-strong; better for EU contacts than Apollo's coverage.
Clay: a workflow tool that orchestrates several of the above providers in sequence (waterfall enrichment) so you maximize hit rate.
None of these tools start from a conference signal, they all start from a name you already had. That's the gap purpose-built tools fill.
What never to do
Don't use someone's personal Gmail or LinkedIn-default email for B2B outreach. Even if you find it, you're outside any legitimate-interest defense and your reply rate will be worse than work email anyway.
Don't blast unverified emails. A single bad campaign with 30% bounces drops your sending domain into spam folders for weeks. Always run a real-time verifier before send.
Don't use templates with {first_name} as your only personalization. Speakers see hundreds of those. Reference the actual talk or don't send at all.
Don't ignore opt-outs. Honor every "please remove me" within 10 business days. CAN-SPAM, GDPR, and CASL all require it; your inbox placement requires it more.
Is this legal?
Short answer: yes, in the US, EU, UK, and Canada, with the right lawful basis and opt-out flow. Long answer with case law and country-specific rules: Event outreach legality (full guide).
Putting it together
For under 25 speakers, do it manually with Apollo + a verifier, you'll learn the motion. For anything bigger, automate the boring parts (extraction, enrichment, pre-qualification, draft generation) and keep the human in the approve-or-edit loop. That's the workflow SayIntel is built around, full breakdown in the scraping & personalization FAQ.