Goals
Q2 2026 objectives
These are the primary goals the team is prioritizing this quarter.
Build event planning systems to double event volume and quality
Owner:
Daniel Zaltsman
Daniel Zaltsman
Kliment Minchev
Kliment Minchev
Motivation: We did 25–30 events in Q1 and it already stretched our capacity. Doubling volume requires removing rote work so the team can focus on the creative, product-driven, and relational work that makes events impactful.
What we'll ship:
- Event description, promo email, merch order, and audience segmentation generators
- Speaker picker and preparer app
- Events CRM poster/parser (for partners, venues, and vendors)
- Event recap capture app
- Public-facing event list for partners
- Tracking mechanism linking event attendance (Luma or equivalent) to PostHog activation data, check-ins
- Universal feedback form
- Clay integration for increasing pipeline for demand gen
We'll know we're successful when:
- Planning time per event is reduced by half
- Able to say yes to more opportunistic events
- We see an increase in inbound interest from preferred partners
Create a repeatable playbook for conferences, 1>n hackathons, and product-specific events
Owner:
Daniel Zaltsman
Daniel Zaltsman
Motivation: We want to make sure that PostHog events are never stale and always aligned with the quickly evolving needs of our ICP. We’ll keep introducing new formats and retiring ones that are no longer delivering value.
What we'll ship:
- Conference playbook covering: booth setup and staffing, pre-event outreach, on-the-ground sales and community motions, lead capture process, and post-event follow-up. Playbook executed at both Stripe Sessions and AI Engineer Europe
- 1>n hackathon format to compliment incoming AI products
- New formats introduced to support priority products: AI Observability, Error Tracking, MCP, Wizard, Data Stack
- City drop-in template (dinners, meetups, conferences) and at least one city take-over executed against the template
- Event format for testing a Student program
We'll know we're successful when:
- Any organizer (internal or external) could run these events to perfection
- City drop-in generates stronger local engagement than a standalone event in the same city
- Sales see positive impact from conferences
- Events are helping users learn about and try specific products
Test Discord as an online channel for builder community engagement
Owner:
Kliment Minchev
Kliment Minchev
Daniel Zaltsman
Daniel Zaltsman
Motivation: Before committing to a broader community strategy or hire, we'll be running disciplined experiments to learn whether Discord generates genuine, durable participation — not just sign-ups — and whether PostHog can sustain it without over-investing upfront.
What we'll ship:
- Server structure and channel architecture (purpose-built, not default Discord layout)
- Onboarding flow that clearly sets expectations on what the space is and isn't for
- Handbook bot for self-serve answers
- PostHog API integration to link Discord handles to PostHog user accounts where possible
- Bi-weekly virtual events (session replay parties, product demos, mini talks) to give members a reason to show up
- Pulse survey cadence for members who stick around past week 2
- Lightweight moderation playbook and role system based on engagement level
We'll know we're successful when:
- DAU/MAU ratio reaches or exceeds 20% (the benchmark for a default-alive community)
- At least 25% of new members send 3 or more messages within their first two weeks
- We can point to at least one meaningful signal we couldn't have gotten elsewhere — a product insight, a super-user, a cross-user collaboration, or a partner co-event lead
- The team feels like it's worth continuing, not just maintaining
Build a global, self-sustaining builder groups network
Owner:
Kliment Minchev
Kliment Minchev
Motivation: Scaling to many global chapters requires organizers who run independently, connect with each other, and attract our ICP without hand-holding. Shift the trajectory so builder groups don’t depend on us to thrive.
What we'll ship:
- Builder groups v2 playbook: application, vetting, and onboarding automation
- Online space connecting builder group organizers globally (Slack or equivalent)
- Cross-border online builder group pilot and at least one cross-border event
- Templatized event series (e.g. demo night collab) tested in at least two new cities
We'll know we're successful when:
- Time to first builder group decreases by 50%
- Builder group organizers are actively communicating with each other, not just with us
- The event series template is replicable by a new city organizer without starting from scratch
Sidequests
Sidequests are important areas of focus or things the team cares a lot about, but which aren't their primary goal.
Activate Student pilot
Owner:
Kliment Minchev
Kliment Minchev
Motivation: We're already supporting student builders and future founders in a small capacity. We'd like to expand this into a controlled experiment that delivers more data on what a student program might look like.
Explore live streaming
Owner:
Daniel Zaltsman
Daniel Zaltsman
Motivation: Live streaming allows us to connect to a broader subset of our users than IRL events.
Handbook
Slack channel
What we do
IRL Events is the team that organizes and runs PostHog's in-person events and community gatherings.
We bring PostHog users together in real life through events, meetups, and community incubators.