The SaaS event landscape
- Ecosystem conferences (e.g. Dreamforce, INBOUND): partners, integrations, and platform customers
- Vertical industry shows: where your buyers gather by industry
- Functional events: marketing, sales, RevOps, security, data
- Regional and community events: smaller but often higher-intent
Defining a SaaS event ICP
SaaS ICPs often hinge on technology stack, company stage, and team structure. For events, add: ecosystem role (customer, partner, competitor), functional fit of likely attendees, and proof points you can reference for that segment.
| Attribute | Example criteria |
|---|---|
| Technology stack | Uses a platform you integrate with |
| Company stage | Series B+ or 200–2,000 employees |
| Team | Has a dedicated RevOps or data team |
| Ecosystem role | Customer vs partner vs competitor |
Mapping the buying committee
SaaS purchases usually involve several stakeholders. Before the event, identify the economic buyer, champion, and technical evaluator at Tier 1 accounts, and note the source of each record.
Pre-show workflow for SaaS teams
- Step 1
Choose events
Prioritize events by ICP density, not attendance numbers.
- Step 2
Prioritize accounts
Tier exhibitors and event-related companies by fit and ecosystem role.
- Step 3
Validate people
Confirm roles and check source context.
- Step 4
Prepare outreach
Lead with use cases and integrations rather than event greetings.
Tools that can help
Many SaaS teams already use a contact database such as Apollo; pair it with the event's exhibitor list to add event context. See event intelligence vs general contact databases.