Skip to content
Back to Growth & Acquisition

Community Events

Run meetups, office hours, and conferences that give the community a reason to gather on a schedule and produce reusable content.

Why

Events create a deadline that forces the community to produce — a meetup speaker prepares a talk, which becomes a video, which becomes a blog post, which becomes docs; one event seeds months of content. The recurring rhythm (first Thursday of every month) gives members a reason to re-engage and brings lapsed users back, which no async channel achieves. Events are also the highest-trust acquisition: an attendee who saw a live demo converts at 3-5x a cold landing-page visitor because they saw the product work and met the people behind it. The cost (organizer time, pizza) is low relative to the content and relationships produced, and the recordings compound as an evergreen content library.

When

When the community has 100+ active members and asks for in-person or live interaction. Start with monthly virtual office hours, scale to meetups.

How

1. Start with a low-cost recurring format: monthly 60-min virtual office hours, same day/time, always recorded
2. Pick a host who is a team engineer (not a marketer) — the community wants technical depth, not a sales pitch
3. Structure each session: 10min demo/news, 40min live Q&A or build, 10min 'what's next' + community shoutouts
4. Record and post within 24h to YouTube + a blog-post summary with timestamps; the recording is the evergreen asset
5. After 3 months of office hours, pilot a local meetup: venue = a sponsor office, format = 2 talks + pizza + networking
6. For meetups, recruit 1 external speaker (broadens audience, shares prep load) and 1 internal (showcases product)
7. Once a year, run a 1-day virtual conference: 6 talks, 200+ attendees, free, recorded — the flagship content asset
8. Track: attendance, recording views at 30/90 days, signups attributed to events, talks that became docs

Example

# Monthly office hours (recurring, virtual)
When:  first Thursday, 14:00 UTC, 60 min
Host:  @lead-engineer (not marketing)
Agenda:
  0-10   demo new feature + release notes
  10-50  live build: "let's write a plugin together"
  50-60  Q&A + next month's theme + community shoutouts
Record → YouTube within 24h → blog post with timestamps

# Quarterly local meetup (São Paulo)
Venue:  sponsor office (free)
Talks:  1 external (AWS engineer) + 1 internal (our plugin SDK)
Budget: $200 (pizza + drinks)
RSVP:   40 → 28 show → 8 sign up → 3 activate

# Annual virtual conference
6 talks, 240 attendees, 0 cost (virtual)
→ 4 talks become docs sections
→ 1 talk becomes a 5-part blog series
→ 90d recording views: 12,000

Common Problems

  • ⚠Hosting events with a marketer instead of an engineer — the community smells the sales pitch and doesn't return.
  • ⚠Not recording, or recording and never posting — the evergreen content asset (the recording) is the highest-ROI part and it's lost.
  • ⚠Inconsistent cadence — 'an event when we have time' means the community forgets the series exists between events.
  • ⚠No attribution from event attendees to signups, so events look like a cost center and get defunded.

Best Practices

  • ✓Have a team engineer host, not a marketer; the community comes for technical depth and stays for the relationship.
  • ✓Record every event and post within 24h with a timestamped summary; the recording outlives the event 100x in reach.
  • ✓Pick a recurring day/time and never deviate for the first year; the rhythm is what builds the habit.
  • ✓Attribute signups to events with a unique link or code so events are funded by data, not vibes.