Channel 09 / 13 · Start conversations
Webinars, workshops & events
Make the session worth attending even if nobody buys.
Use it when
A technical problem benefits from live explanation, demonstrations or peer examples.
Don't confuse it with
Panel discussions where everyone repeats “AI is changing everything.”
01 / What companies actually did
Harness turned a research report into an event
Its 2025 virtual State of Software Delivery event used the report’s findings to convene engineering leaders, with several distinct technical sessions and on-demand material.
[H2] Harness — State of Software Delivery (2025) ↗[H3] Harness — Software Delivery research event ↗GrafanaCON runs hands-on labs and expert booths
The program includes practical work on OpenTelemetry and dashboards plus community-led talks and expert access. That gives attendees useful reasons to show up.
[G2] Grafana — GrafanaCON 2026 program ↗Supabase builds distribution around its launch events
Its published Launch Week process coordinated community activity, demos, guest participation and follow-on workshops/hackathons.
[S1] Supabase — How we launch ↗[S2] Supabase — Community Day ↗02 / How to do it
- 01Choose one hard problem and a credible technical speaker; use a real project or customer.
- 02Promise a concrete takeaway: working demo, runbook, checklist or live analysis.
- 03Invite 50–100 carefully selected practitioners rather than maximizing generic registrations.
- 04Prepare a workshop-sized demo with fallback screenshots and tested setup.
- 05Send recording + code + relevant next step; route sales follow-up only to people with genuine fit/interest.
Things you can publish or run
03 / What good looks like
Watch this
Target-account attendance, engaged participants, follow-up technical calls, accepted opportunities.
Common trap
Registrations and attendee totals are not pipeline.
04 / Copy the worksheet
COPYABLE WORKSHEET / 09
Webinars, workshops & events template
Replace the brackets. Use this as a starting point, not a rigid formula.
TECHNICAL EVENT RUN OF SHOW Audience: [specific engineering job] Title: [specific outcome, not a trend] Host + practitioner: [...] + [...] Promise: attendees leave with [working thing] 00–05: real problem and setup 05–25: demo / teardown / case 25–35: what failed, trade-offs, lessons 35–45: Q&A, show code/checklist Pre-event: targeted invites + speaker approval + rehearsal Post-event: recording + repo + summary + opt-in follow-up Track: target accounts attended → useful conversations → opportunities
05 / Original sources