# Conference speaker outreach: find an event's speakers and write notes about their talks

Source: https://mcpforgtm.com/recipes/conference-speaker-outreach (StackMCP, independent directory of official MCP servers)

## Goal

SDRs and marketers who want to reach the people speaking at an industry event with a note that refers to their actual talk, not a generic 'saw you're speaking'. Exa can be swapped for Tavily or Perplexity, Firecrawl for Apify, and Hunter for Findymail, Prospeo or Snov.io.

## Connected tools

- Exa: https://mcp.exa.ai/mcp (setup: https://mcpforgtm.com/tools/exa)
- Firecrawl: https://mcp.firecrawl.dev/v2/mcp-oauth (setup: https://mcpforgtm.com/tools/firecrawl)
- Hunter: https://mcp.hunter.io/mcp (setup: https://mcpforgtm.com/tools/hunter)

## Guardrails

- Only quote what the event page says about the talk. Show the source line under each note.
- Don't guess what a speaker will say, and don't mention anything about them that isn't on the event page.
- Tell me how many Hunter lookups a step needs, and run them only after I approve it.
- Write notes as text only. Never send email, save Hunter leads or start a Hunter sequence.

## Steps

1. Use Exa to search for the speaker or agenda page for {event name} {year}. Show me the top results with title and URL, and tell me which one is the official speaker page and what year and dates it shows. Don't open anything else yet.
2. Use Firecrawl to scrape {speaker page URL} with JSON extraction. For each speaker, pull name, job title, company, talk title, session date and the talk description exactly as the page writes it. Scrape only that page. Show me a table, the speaker count, and flag anyone with no talk description.
3. Keep the speakers who match {target titles or company types} and have a talk description. Use Exa to find each company's website domain. Tell me how many Hunter Email Finder searches that is, and run them only after I approve it. Then, after I approve it, verify each email found with Hunter Email Verifier.
4. Write a short note to each speaker with a verified email. Refer to their talk using only what the event page says, and put the exact source line under each note. Ask one question about the talk and suggest {meeting ask}. Show me the text only. Don't send anything.

## Expected output

Speaker table, email lookups and one draft note. Example (all names fictional):

```
Event: Northbank RevOps Summit 2026 (fictional), Nov 12–13
Speaker page: https://northbank-summit.example/2026/speakers (dated 2026 on the page)
Scraped: 1 page, 18 speakers. Kept 4 that match 'RevOps or sales ops leaders at B2B software companies'.

| Speaker | Title | Company | Talk | Email (Hunter) |
|---|---|---|---|---|
| Dana Okafor | VP Revenue Operations | Fernhill Software (fictional) | "Retiring the Friday forecast spreadsheet" | dana.okafor@fernhill.example (verified) |
| Sam Whitlock | Head of Sales Ops | Quarry Lane Analytics (fictional) | "Territory planning with half the data" | Not found |
| Priya Raman | Director, GTM Systems | Mossgate Labs (fictional) | "One CRM after three acquisitions" | priya@mossgate.example (accept-all, not confirmed) |
| Alex Rivera | RevOps Lead | Larkspur Freightworks (fictional) | Title only, no description on the page | Not looked up. Skipped |

Hunter usage this run: 3 Email Finder searches, 2 verifications.

Draft note to Dana (text only, not sent):
Subject: Your forecast spreadsheet talk at Northbank

Hi Dana,

Saw you're speaking on day two at Northbank about retiring the Friday forecast spreadsheet. The session description says Fernhill moved its weekly forecast out of a shared sheet in one quarter. I'd like to hear how you got managers to stop keeping their own copy.

If you're open to it, I'd be glad to grab 15 minutes at the event.

Jordan

Source line from the page: "How Fernhill moved its weekly forecast out of a shared sheet in one quarter, and what broke along the way."

Nothing has been sent, and no Hunter leads or sequences were created.
```

## Watch for

- Last year's speaker page: Search results often surface an older edition of the same event. Before scraping, have it show the year and event dates printed on the page, and stop if they don't match the event you asked for.
- A note that claims more than the page says: The model may guess what a speaker will cover or invent a result. Require the exact source line from the page under each note, and cut any sentence about the talk that the source line doesn't support.
- Only part of the speaker list was scraped: Some events list speakers across several pages or behind a 'load more' button. Compare the speaker count in the table with what the page shows. If each speaker has a separate page, map the site first and scrape only the pages you pick.
- An email at a company the speaker has left: Speaker bios can be out of date. Check that the email's domain matches the company on the page, verify every email before drafting, and skip anyone where the two disagree.