Event Prospecting
Turn an event page into a ranked, person-first pipeline map with company fit, speaker context, outreach hooks, proof links, and CRM-ready handoff.
Give Opulent your ICP and connect the outreach stack
Connect Apollo to find and enrich the people behind each company, and Salesloft for outreach and live revenue signals. Add Zoom and Calendly if you want Opulent to book the meetings it earns, not just list the names.
Write your ICP down as a playbook (a reusable set of steps Opulent reuses on every event: the sectors, sizes, and roles that count, and what disqualifies a company) so the ranking reflects your definition of a fit, not a generic one.
Playbook: !event-prospect Given an event page: 1. Extract the event graph: companies, speakers, sessions, sponsors. Note each company's role at the event. 2. Triage companies first against the ICP: [sector], [size], [geo]. Drop non-fits before spending research on people. 3. Research each fit (funding, product, recent news) and write a one-line reason it matters to us. 4. Find the right person: the role we sell to, not the loudest speaker. Enrich with Apollo (title, email, LinkedIn). 5. Ship a ranked list: person, company, fit score, an outreach hook tied to the event, and a proof link per claim.
Feed Opulent two or three accounts you already won from events. It learns the fit pattern and the hook style that worked, and applies both to the new list.
Kick it off with the event page
This workflow is on-demand: send the event URL when a conference agenda or attendee list goes live. Paste the message from the top of this page with the real link, and Opulent starts from the event graph.
For a recurring series (a monthly meetup, a quarterly summit) put it on a schedule instead so each new agenda is prospected the day it publishes.
The sharp edge: event pages mix speakers, sponsors, and exhibitors, and they are not equally valuable. Tell Opulent which roles matter, or it ranks a headline speaker above a sponsor who is a far better fit.
Watch one event become a ranked list
Take a fintech infrastructure summit with 60 companies on the agenda:
Opulent triages before it researches, so it never burns effort enriching people at companies that were never a fit.
Event: FinInfra Summit 2026 (agenda, 60 companies)
Run actions:
- Extracted 60 companies, 74 speakers, 21 sessions.
- Triaged to 12 ICP fits (B2B payments infra, 50-500 staff);
dropped 48 non-fits before any people research.
- Researched the 12: flagged Northwind Pay (just launched a
ledger API) and Tessera (hiring a Head of Risk).
- Found the buyer at each, VP Eng or Head of Payments, not the
keynote speaker, and enriched with Apollo.
- Shipped a 12-row list: person, hook ("your ledger API launch"),
and a proof link to the session or announcement.What ships
You get a ranked, person-first list a rep could work this afternoon, each row verifiable:
One row per person: name, title, company, fit score, and an outreach hook tied to something real at the event, a session they ran, a launch they announced. A proof link per hook so the rep sees the context before writing. Contact fields enriched from Apollo, ready to sync.
If you connected Salesloft, the list lands as a ready-to-load cadence; if you connected Calendly, the hook can carry a booking link so a warm reply turns into a meeting in one step.
Sharpen the list quality
When a rep flags rows as bad fits, tell Opulent which and why; write the pattern into the !event-prospect playbook or into memory (the notes a run recalls next time), like "drop companies already in our CRM as customers", so the next event skips them.
Tighten the person-selection rule as you learn who actually replies (title, seniority, function) so the buyer, not the speaker, keeps rising to the top.
The natural chain: once the list is trustworthy, pass it to Stand Up a CRM and Outreach Pipeline in One Run so the ranked people become CRM records and sequences without a second pass.