Events consume a large fraction of many DevRel budgets and often have a high cost per attendee reached. Choose an event type by the relationships, brand recognition, technical material, or product use it is expected to produce.
Event types and what each is good for
| Event type | Cost | Goal | Risk |
|---|---|---|---|
| Sponsorship at flagship conference | $25K to $1M+ | Brand, lead capture, recruiting | Generic-booth invisibility |
| Speaking slot at flagship | Travel cost only | Authority, awareness | Talk falls flat |
| Speaker bureau (own people speaking everywhere) | Salary + travel | Compound brand | Burnout |
| Hosting your own conference | $500K to $10M+ | Customer ownership, narrative control | Empty seats |
| Workshop / hands-on session | $5K to $50K | Activation | Low scale |
| Local meetup (sponsoring) | $500 to $5K each | Authenticity, local presence | Hard to scale |
| Local meetup (organising your own) | Per-event variable | Community-building | Volunteer-attrition |
| Hackathon (sponsoring) | $10K to $100K | New-developer reach | Variable signal |
| Hackathon (running your own) | $50K to $500K | Lead generation, deep engagement | Operational complexity |
| Webinar | $0 to $5K | Activation, retention | Webinar fatigue |
| AMA / office hours | $0 | Retention, sentiment | Requires staffing |
Choosing what to attend
A short decision checklist for each event:
- Who is in the room? Audience demographic match.
- What is your goal? Awareness, activation, recruiting, retention, customer love?
- What does success look like? Define before the event.
- What is the cost per qualified outcome? Total event cost / qualified DQLs or activations.
- What is the cost of not being there? Sometimes presence is defensive.
- Who else is there? Your competitors, your partners, your customers.
A common failure is to attend an event because “we always do” rather than because the analysis supports it.
Speaker placement
Conference talks can reach an established technical audience without the cost of operating an event. Key practices:
- Submit early, often, to many CFPs. Even strong speakers get accepted at maybe 30 to 40% of submissions.
- Match topic to conference audience. Relevance to attendees matters alongside the quality of the talk.
- Prepare and review the talk. Recordings can remain available for years.
- Build the speaker portfolio over years. Repeated appearances can make the speaker familiar to the event’s audience.
Tools that help:
- Sessionize for tracking CFP submissions.
- Notist for managing speaker portfolios.
- PaperCall (now part of Sessionable) for CFP submission management.
Operating a flagship sponsorship
For a sponsorship costing $250K or more, define the operating plan before purchase:
- Pre-event. Email known attendees who are customers / prospects. Schedule meetings in advance. Set goals for the booth team.
- At-event.
- Booth staffed by people who can answer technical questions, with marketing support where useful.
- Real demos alongside concise slide decks.
- Lead-capture infrastructure (a QR-code-based system; don’t write business cards).
- Side-event (dinner, workshop) for high-value contacts.
- Post-event. Follow up within 48 hours. Segment leads by quality.
Assign post-event follow-up before the event; otherwise conversations and captured contacts may receive no response.
Hosting your own event
When the company has reached a size where customers want to gather, hosting your own conference becomes viable.
Examples by stage:
- Series A / early growth. Quarterly virtual events; small in-person meetups.
- Series B / growth. Annual customer day; small focused customer-summit (~100 to 500 people).
- Mature / public. Flagship multi-day conference (SIGNAL, Sessions, HashiConf, GitHub Universe).
Costs scale rapidly. A 500-person customer summit is in the $500K to $2M range; a 5,000-person flagship is $5M to $15M+. The ROI question is usually pipeline + customer retention + competitive positioning combined.
Side events
At another company’s flagship conference, use side events for curated groups, workshops, customer dinners, and 1:1 meetings:
- After-parties with curated guest lists.
- Workshop tracks at adjacent venues.
- Customer dinners for top-50 prospects in town for re:Invent / KubeCon / Build.
- Quiet rooms for productive 1:1 meetings.
Some DevRel programmes buy a smaller official package and allocate more budget to workshops, dinners, or meeting space.
Measurement
Track per event:
- Direct cost. Sponsorship, travel, swag, side-events.
- Indirect cost. Staff time (often the largest hidden cost).
- Outputs. Talks delivered, hands-on workshop attendees, conversations.
- Qualified leads / DQLs. With proper attribution.
- Post-event activation. How many event-attendee accounts moved through onboarding within 30 days.
- Pipeline-influenced. Revenue attribution where possible.
- Sentiment. Post-event NPS, qualitative debrief.
A useful summary number is cost per activated developer. Comparing it across events supports budget allocation using the same outcome definition.
Pitfalls
- Sponsoring without booth staffing plan. A $100K sponsorship with no team plan is wasted.
- Speaker burnout. Same 3 people on every stage produces diminishing returns; rotate.
- Generic “developer event” attendance. A booth at a Java event when your product is Python.
- Virtual events with no live element. On-demand-only formats are essentially webinars.
- Hosting beyond operating capacity. Set attendance to the venue, staffing, programme, and follow-up capacity available.