Event Presence Prospecting
free skill · signal-research
Find which conferences a company sponsors, exhibits at, or speaks at, and use that as a budget and audience signal.
/plugin marketplace add mambalabsdev/mamba-labs-skillsWhat it does
Event presence is an unusually honest signal because it costs money and it is public. A company that buys a booth has both budget and a stated audience. This skill finds the events, separates sponsorship from attendance from speaking, and builds outreach that is timed to the event rather than generic.
When to use it
- which conferences do they sponsor
- event based prospecting
- will this company be at the show
- conference outreach
- who exhibits at this event
What it needs from you
- domain: the company domain
- years: which years to look at
- event: a specific event, if the question is about one
Live data it reads
Event presence is read from public sponsor, exhibitor and speaker listings for the years requested. - event-presence-index: conference sponsorship, booth and speaker presence for a company Store page: https://apify.com/mambalabs/event-presence-index Runnable example input:
How it works
- Separate the three presence types. Sponsoring is a budget signal, exhibiting is a pipeline signal, and speaking is a positioning signal. They imply different things.
- Check whether the company runs its own events. A company with its own conference has a different marketing posture than one that buys booths at other people's.
- Read the audience of the events, not just the names. Which events a company buys is a statement about who it thinks its buyer is.
- Time the outreach. Before the event is about planning, during is crowded, and two weeks after is when the follow up backlog is being worked and a relevant message lands.
- Write the angle from the specific event and the specific presence type, never from the fact of attendance.
- Note the events they stopped attending, where the data supports it. A dropped sponsorship is a signal too.
What you get back
The event list by year with presence type, the audience read, the timing recommendation, and the angle.
The quality bar
- Presence types are separated and each one is interpreted differently
- Own events are distinguished from third party events
- The timing recommendation is tied to a date relative to the event
- The angle names the specific event
Where it runs
- Claude Code
- Codex CLI
- Cursor
- MCP-compatible agents
Get the skill
We will email you the install command and a link to the skill. No account, no purchase.