PlaysbyMoat8
Back to the library
The workflow guideSales

Build a prospect shortlist from industry event speakers

A sales team used public event pages to identify relevant people and companies, enrich available contact information, and prepare tailored outreach. The described process still involved manual weekly exports.

6 implementation stepsIntermediate

How this works

A sales team used public event pages to identify relevant people and companies, enrich available contact information, and prepare tailored outreach. The described process still involved manual weekly exports.

Use event participation as a professional relevance signal, preserving the exact talk and affiliation. An event page can support a reason to connect, but it does not prove current employment, attendance by the sender or permission for a bulk campaign.

Before you start

Defined operating scope

Relevant event speakers provide a public starting point for account and contact research.

Required source material

Obtain Relevant public event pages; Ideal customer criteria; Permitted business contact data. If connectors are unavailable, use authorized files with the same fields.

Decision and exception rules

The event affiliation is outdated. Use current verified information and keep the historical event affiliation separately.

Prepare the inputs

event_pages
Required

Public event and session records

Record event date and page retrieval date.

speaker_records
Required

Names, affiliations and talk titles

Keep the source page for each field.

customer_criteria
Required

Company and role fit rules

Define exclusions before enrichment.

contact_data
Required

Permitted business contact references

Honor restrictions and uncertain identity matches.

Implementation, step by step

  1. Establish the working record

    • Confirm the selected records, effective versions and responsible owner.
    • Check event_pages, speaker_records, customer_criteria, contact_data before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.

    Checkpoint: The input record identifies the selected event_pages and any missing required fields.

  2. Extract speaker names and company affiliations

    • Extract speakers, affiliations and session topics, distinguishing moderators and sponsors from speakers when relevant.
    • Verify talk titles, event dates and current identity matches.

    Checkpoint: A saved intermediate result for: Extract speaker names and company affiliations.

  3. Check company fit and available business contacts

    • Verify company fit and current professional identity before linking permitted contact records.
    • Check messages do not imply attendance, familiarity or outcomes unsupported by the evidence.

    Checkpoint: A saved intermediate result for: Check company fit and available business contacts.

  4. Draft an introduction tied to a verifiable talk or business topic

    • Draft an introduction referencing a specific public talk or topic honestly; avoid pretending to have attended or met the person.
    • Verify talk titles, event dates and current identity matches.

    Checkpoint: A saved intermediate result for: Draft an introduction tied to a verifiable talk or business topic.

  5. Review the list and messages before outreach

    • Review duplicates, dates, exclusions and message facts, then save the prospect list and unsent drafts.
    • Check messages do not imply attendance, familiarity or outcomes unsupported by the evidence.

    Checkpoint: A saved intermediate result for: Review the list and messages before outreach.

  6. Package the result and unresolved work

    • Check contact permissions and source accuracy. Refer honestly to public talks; do not claim a prior meeting that never happened.
    • Use permitted public and professional information only.

    Checkpoint: A reviewed prospect list with personalized email drafts. Unresolved items remain visible in the review record.

Decisions along the way

The event affiliation is outdated.

Use current verified information and keep the historical event affiliation separately.

Two speakers share a name.

Resolve identity through organization and session context before enrichment.

No permitted contact route is available.

Keep the research record without inventing an email or bypassing restrictions.

What you will produce

find-sales-prospects-from-event-speakers-result.json

JSON

A reviewed prospect list with personalized email drafts. Label proposed and completed states separately.

Include: event_id · speaker_reference · talk_topic · historical_affiliation · current_company · fit_reason · message_draft · status · evidence_reference · review_note

find-sales-prospects-from-event-speakers-review.md

Markdown

Keep the evidence and unresolved decisions needed to apply this result, including exceptions involving contact_data.

Include: source_reference · question · owner · next_action

Check the result

  • Verify talk titles, event dates and current identity matches.
  • Check messages do not imply attendance, familiarity or outcomes unsupported by the evidence.
  • Inspect event_pages and speaker_records in both the original and output; confirm that record identity and interpretation survived the transformation.
  • Check contact permissions and source accuracy. Refer honestly to public talks; do not claim a prior meeting that never happened.

When something goes wrong

The event affiliation is outdated.

Use current verified information and keep the historical event affiliation separately. Retain the affected evidence and recovery status.

Two speakers share a name.

Resolve identity through organization and session context before enrichment. Retain the affected evidence and recovery status.

No permitted contact route is available.

Keep the research record without inventing an email or bypassing restrictions. Retain the affected evidence and recovery status.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Build a prospect shortlist from industry event speakers for the following bounded example; prepare the result for review.

Inputs

Synthetic example: Event E-4 lists speaker S-8 on supply-chain forecasting in 2024. A current official profile shows a different employer.

Expected result

Synthetic expected result: Retain the 2024 talk as topic evidence, use the current employer for fit review and draft an honest reference to the public session, not a claimed meeting.

Run a small pilot

Start small

Trial a representative batch containing the ordinary case and the exception demonstrated above.

Record the baseline

Record current preparation time, review effort and correction types for the same records.

Agree success criteria

Agree acceptable review and error limits; measure human-confirmed account fit; accurate contact records and relevant outreach replies.

Stop or revise

No permitted contact route is available. Pause affected records and apply this recovery: Keep the research record without inventing an email or bypassing restrictions.

Keep the scope clear

  • Use permitted public and professional information only.
  • Research and draft preparation do not authorize bulk outreach.

Check before using

Check contact permissions and source accuracy. Refer honestly to public talks; do not claim a prior meeting that never happened.

Business activities

  • Find and approach prospects

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Relevant public event pages · Ideal customer criteria · Permitted business contact data

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗