Event driven outreach skill
Builds outbound sequences around conference and event attendance: pre-event research and meeting booking, on-site plays, and post-event follow-up.
by LeadMagic·MIT license·★ 62 Stars on the repo·GitHub ↗
npx degit LeadMagic/gtm-skills/skills/events/event-driven-outreach#main ~/.claude/skills/event-driven-outreachChecked ·commit main
Inside this skill
SKILL.md · the author's own words# Event-Driven Outreach ## Overview Conferences and events are concentrated buying intent — attendees have budget, are actively evaluating, and are reachable in a compressed time window. This skill covers the pre-event, on-site, and post-event outbound motion. ## Authoritative Foundations - **Josh Braun — Relevance-first outreach** — Lead with the specific event context and a low-pressure question; skip the generic 'will you… - **Winning by Design — SPICED** — Discovery framework — Situation, Pain, Impact, Critical Event, Decision; use it to qualify event convers… - **Forrester (SiriusDecisions) — Demand Waterfall** — Tag event-sourced and event-influenced leads so follow-up conversion is measured by… ## When to Use - "Outreach around [conference]"
Word-for-word excerpt, not a result. Read the full SKILL.md ↓
Files of Event driven outreach
Show the full text161 lines
Event-Driven Outreach
Overview
Conferences and events are concentrated buying intent — attendees have budget, are actively evaluating, and are reachable in a compressed time window. This skill covers the pre-event, on-site, and post-event outbound motion.
Authoritative Foundations
- Josh Braun — Relevance-first outreach — Lead with the specific event context and a low-pressure question; skip the generic 'will you be at the booth?' pitch.
- Winning by Design — SPICED — Discovery framework — Situation, Pain, Impact, Critical Event, Decision; use it to qualify event conversations before handoff.
- Forrester (SiriusDecisions) — Demand Waterfall — Tag event-sourced and event-influenced leads so follow-up conversion is measured by stage.
When to Use
- "Outreach around [conference]"
- "Conference prospecting"
- "Event follow-up sequence"
- "Trade show outbound play"
Step-by-Step Process
Phase 1: Pre-Event (2-3 weeks before)
- Attendee list sourcing: Scrape attendee lists, speaker lists, sponsor lists, LinkedIn event RSVPs, hashtag engagers
- Account research: For each target, determine: are they speaking? sponsoring? attending? Which sessions are relevant?
- Pre-event outreach: "Saw you're attending [Event]. I'll be there too — would love to grab 15 minutes to share what we're seeing in [their domain]." This books meetings before you arrive.
- Speaker outreach: "Your talk on [topic] at [Event] — quick question." Speakers are flattered by pre-event engagement.
Phase 2: On-Site (During the event)
- Real-time engagement: Monitor event hashtag. Engage with prospect posts.
- Session targeting: Attend sessions your prospects attend. Sit near them. Ask good questions during Q&A (with your name + company intro).
- Expo hall: If exhibiting, qualify booth visitors fast. Badge scan + 1-question qualifier + "I'll follow up with [specific thing]."
- Evening events: Happy hours, dinners, after-parties. Best networking happens outside the conference center.
Phase 3: Post-Event (1-7 days after)
Day 1: "Great meeting you at [Event]" — personalized, reference your conversation. Day 2-3: LinkedIn connection + "Enjoyed [specific conversation topic] at [Event]" Day 5-7: Value-add follow-up: "Following up on our conversation about [topic], here's [specific resource/data]"
Phase 4: Non-Attendee Outreach
"I wasn't at [Event] but I noticed [topic] was big. Teams I work with are seeing [related trend]." You can reference conference themes without having attended.
Phase 5: ROI Measurement
Track: meetings booked from event outreach, pipeline created, deals closed. Cost per meeting = (event cost + outreach time) / meetings booked. This lets you compare events objectively — kill the ones that don't convert.
Output Format
Event outreach playbook with: attendee sourcing method, pre-event sequence, on-site playbook, post-event templates, and ROI measurement framework.
Quality Check
Before delivering, verify:
- All required sections are complete
- Output matches the user's stated need
- Named frameworks are cited for key recommendations
- No vague claims — every recommendation has a specific action
- Deliverable is ready for operational use, not just conceptual
Common Pitfalls
- No pre-event outreach. Showing up to a conference without booked meetings wastes the investment. Fix: scrape attendee lists, research targets, and book meetings 2-3 weeks before.
- Booth staff without training. Untrained staff give generic demos and fail to qualify. Fix: train on qualification questions, demo flow, and data entry before the event.
- No post-event follow-up system. Leads go cold within 48 hours. Fix: Day 1 personalized follow-up, Day 3 value-add, Day 7 soft CTA.
Execution Artifacts
references/framework-notes.md— named frameworks, citation anchors, and operating assumptionstemplates/output-template.md— copy-paste deliverable structure for the userscripts/check-output.py— local checklist validator for required sections This skill includes lightweight artifacts the agent can load on demand: Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.
Implementation Depth
Use this section when the user asks for a finished asset, not a high-level explanation.
Diagnostic Questions
- What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
- Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
- What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
- What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
- What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?
Framework Application
Map the recommendation explicitly to the named frameworks in this skill:
- Event-Led Growth: apply only the part that directly improves the requested deliverable.
- B2B Event Marketing Framework: apply only the part that directly improves the requested deliverable.
- Bizzabo — Event Experience Framework: apply only the part that directly improves the requested deliverable.
Deliverable Standard
A strong output from this skill includes:
- A crisp diagnosis of the current situation
- A recommended path with tradeoffs, not a generic list
- A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
- A measurement plan with leading and lagging indicators
- Risks and edge cases called out before execution
Adaptation Rules
- For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
- For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
- For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.
Related Skills
- cold-email-strategy, cold-email-copywriting, multi-channel-outreach, social-selling, pipeline-management
| 1 | |
| 2 | name event-driven-outreach |
| 3 | description >- |
| 4 | Builds outbound sequences around conference and event attendance: pre-event |
| 5 | research and meeting booking, on-site plays, and post-event follow-up. Use |
| 6 | when the user is prospecting around a specific conference or trade show, or |
| 7 | needs an event follow-up sequence. Triggers on: "event outreach", "conference |
| 8 | prospecting", "trade show follow-up", "event outbound". |
| 9 | license MIT |
| 10 | compatibility Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed |
| 11 | metadata |
| 12 | version "1.0.0" |
| 13 | author LeadMagic |
| 14 | category events |
| 15 | tags [events, conferences, outbound, trade-shows, prospecting] |
| 16 | frameworks |
| 17 | - "Josh Braun — Relevance-first outreach" |
| 18 | - "Winning by Design — SPICED" |
| 19 | - "Forrester (SiriusDecisions) — Demand Waterfall" |
| 20 | related_skills |
| 21 | [ |
| 22 | cold-email-strategy, |
| 23 | cold-email-copywriting, |
| 24 | multi-channel-outreach, |
| 25 | social-selling, |
| 26 | pipeline-management, |
| 27 | ] |
| 28 | |
| 29 | |
| 30 | # Event-Driven Outreach |
| 31 | |
| 32 | ## Overview |
| 33 | |
| 34 | Conferences and events are concentrated buying intent — attendees have budget, |
| 35 | are actively evaluating, and are reachable in a compressed time window. This |
| 36 | skill covers the pre-event, on-site, and post-event outbound motion. |
| 37 | |
| 38 | ## Authoritative Foundations |
| 39 | **Josh Braun — Relevance-first outreach** — Lead with the specific event context and a low-pressure question; skip the generic 'will you be at the booth?' pitch. |
| 40 | **Winning by Design — SPICED** — Discovery framework — Situation, Pain, Impact, Critical Event, Decision; use it to qualify event conversations before handoff. |
| 41 | **Forrester (SiriusDecisions) — Demand Waterfall** — Tag event-sourced and event-influenced leads so follow-up conversion is measured by stage. |
| 42 | |
| 43 | ## When to Use |
| 44 | |
| 45 | "Outreach around [conference]" |
| 46 | "Conference prospecting" |
| 47 | "Event follow-up sequence" |
| 48 | "Trade show outbound play" |
| 49 | |
| 50 | ## Step-by-Step Process |
| 51 | |
| 52 | ### Phase 1: Pre-Event (2-3 weeks before) |
| 53 | |
| 54 | **Attendee list sourcing:** Scrape attendee lists, speaker lists, sponsor lists, |
| 55 | LinkedIn event RSVPs, hashtag engagers |
| 56 | **Account research:** For each target, determine: are they speaking? sponsoring? |
| 57 | attending? Which sessions are relevant? |
| 58 | **Pre-event outreach:** "Saw you're attending [Event]. I'll be there too — |
| 59 | would love to grab 15 minutes to share what we're seeing in [their domain]." |
| 60 | This books meetings before you arrive. |
| 61 | **Speaker outreach:** "Your talk on [topic] at [Event] — quick question." |
| 62 | Speakers are flattered by pre-event engagement. |
| 63 | |
| 64 | ### Phase 2: On-Site (During the event) |
| 65 | |
| 66 | **Real-time engagement:** Monitor event hashtag. Engage with prospect posts. |
| 67 | **Session targeting:** Attend sessions your prospects attend. Sit near them. |
| 68 | Ask good questions during Q&A (with your name + company intro). |
| 69 | **Expo hall:** If exhibiting, qualify booth visitors fast. Badge scan + 1-question |
| 70 | qualifier + "I'll follow up with [specific thing]." |
| 71 | **Evening events:** Happy hours, dinners, after-parties. Best networking happens |
| 72 | outside the conference center. |
| 73 | |
| 74 | ### Phase 3: Post-Event (1-7 days after) |
| 75 | |
| 76 | Day 1: "Great meeting you at [Event]" — personalized, reference your conversation. |
| 77 | Day 2-3: LinkedIn connection + "Enjoyed [specific conversation topic] at [Event]" |
| 78 | Day 5-7: Value-add follow-up: "Following up on our conversation about [topic], |
| 79 | here's [specific resource/data]" |
| 80 | |
| 81 | ### Phase 4: Non-Attendee Outreach |
| 82 | |
| 83 | "I wasn't at [Event] but I noticed [topic] was big. Teams I work with are |
| 84 | seeing [related trend]." You can reference conference themes without having |
| 85 | attended. |
| 86 | |
| 87 | ### Phase 5: ROI Measurement |
| 88 | |
| 89 | Track: meetings booked from event outreach, pipeline created, deals closed. |
| 90 | Cost per meeting = (event cost + outreach time) / meetings booked. |
| 91 | This lets you compare events objectively — kill the ones that don't convert. |
| 92 | |
| 93 | ## Output Format |
| 94 | |
| 95 | Event outreach playbook with: attendee sourcing method, pre-event sequence, |
| 96 | on-site playbook, post-event templates, and ROI measurement framework. |
| 97 | |
| 98 | ## Quality Check |
| 99 | |
| 100 | Before delivering, verify: |
| 101 | |
| 102 | [ ] All required sections are complete |
| 103 | [ ] Output matches the user's stated need |
| 104 | [ ] Named frameworks are cited for key recommendations |
| 105 | [ ] No vague claims — every recommendation has a specific action |
| 106 | [ ] Deliverable is ready for operational use, not just conceptual |
| 107 | |
| 108 | ## Common Pitfalls |
| 109 | |
| 110 | **No pre-event outreach.** Showing up to a conference without booked meetings wastes the investment. Fix: scrape attendee lists, research targets, and book meetings 2-3 weeks before. |
| 111 | **Booth staff without training.** Untrained staff give generic demos and fail to qualify. Fix: train on qualification questions, demo flow, and data entry before the event. |
| 112 | **No post-event follow-up system.** Leads go cold within 48 hours. Fix: Day 1 personalized follow-up, Day 3 value-add, Day 7 soft CTA. |
| 113 | |
| 114 | ## Execution Artifacts |
| 115 | |
| 116 | `references/framework-notes.md` — named frameworks, citation anchors, and operating assumptions |
| 117 | `templates/output-template.md` — copy-paste deliverable structure for the user |
| 118 | `scripts/check-output.py` — local checklist validator for required sections |
| 119 | This skill includes lightweight artifacts the agent can load on demand: |
| 120 | Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice. |
| 121 | |
| 122 | ## Implementation Depth |
| 123 | |
| 124 | Use this section when the user asks for a finished asset, not a high-level explanation. |
| 125 | |
| 126 | ### Diagnostic Questions |
| 127 | |
| 128 | What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led? |
| 129 | Which ICP tier is the output for: small business, mid-market, enterprise, or mixed? |
| 130 | What proof is available today: customer stories, usage data, third-party validation, screenshots, or none? |
| 131 | What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow? |
| 132 | What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure? |
| 133 | |
| 134 | ### Framework Application |
| 135 | |
| 136 | Map the recommendation explicitly to the named frameworks in this skill: |
| 137 | |
| 138 | Event-Led Growth: apply only the part that directly improves the requested deliverable. |
| 139 | B2B Event Marketing Framework: apply only the part that directly improves the requested deliverable. |
| 140 | Bizzabo — Event Experience Framework: apply only the part that directly improves the requested deliverable. |
| 141 | |
| 142 | ### Deliverable Standard |
| 143 | |
| 144 | A strong output from this skill includes: |
| 145 | |
| 146 | A crisp diagnosis of the current situation |
| 147 | A recommended path with tradeoffs, not a generic list |
| 148 | A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan |
| 149 | A measurement plan with leading and lagging indicators |
| 150 | Risks and edge cases called out before execution |
| 151 | |
| 152 | ### Adaptation Rules |
| 153 | |
| 154 | For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity. |
| 155 | For mid-market: include workflow ownership, handoffs, integrations, and enablement assets. |
| 156 | For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements. |
| 157 | |
| 158 | ## Related Skills |
| 159 | |
| 160 | cold-email-strategy, cold-email-copywriting, multi-channel-outreach, social-selling, pipeline-management |
| 161 |
Discussion
Alternatives
Browse more free Claude skills or everything in Sales.