Owner: Adlet SmykovAdlet Smykov

Motivation: Most of our creator relationships are still transactional: we sponsor content and repeat. In Q4 we want to test what happens when creators become part of the wider PostHog community instead: IRL interactions, getting closer to teams and products, and more ways to work with us without every collab being manually managed.

What we'll ship:

• A creator partner portal, including an application, clear ways to participate, briefs and resources, and content bounties
• Creator-focused IRL activations around the events and conferences we're already attending, and creators brought into PostHog events as guests, hosts, and moderators

Owner: Brittany JoinerBrittany Joiner

Motivation: People across channels are raising their hands, and one community member carries most of the forum replies. Before we formalize naming, tracks, or applications, we want to learn what keeps helpful people helping and what would make them stop.

What we'll ship:

• Perks budget agreed, and every champion receives at least one perk or recognition
• A working, internal definition of "helpful" so we can count it
• Conversations with each champion about why they help and what would make them stop
• One informal leader tried in a channel beyond Discord and the forum
• A written proposal for what a formal program should (or shouldn't) look like in Q1

We'll know we're successful when:

• 10 champions meet the working "helpful" definition
• The top forum replier writes less than 50% of community replies

Owner: Kliment MinchevKliment Minchev

Motivation: Events are how we build relationships with startups, and content from them reaches an audience that isn't restricted to the room. We mostly lean on partners for video and social, and in Q3 content capture was inconsistent. Capture is also part of what makes an event feel high quality, so we want to own it.

What we'll ship:

• One video freelancer on a one-camera, one-mic setup to capture all SF events
• Creators involved in IRL events (e.g. moderating, hosting), starting with SF Tech Week
• Product release themed events (e.g. Replay Vision birdwatching)
• A content capture standard other events can reuse

We'll know we're successful when:

• We can point to BDR stories that started at events (Luma → Clay → PostHog)
• Metrics on carefully crafted hypotheses (e.g. a creator doubles impressions) trend upward

Owner: Kliment MinchevKliment Minchev

Motivation: The program is real: a /students page and campus ambassadors at 6 California schools, with team members excited to speak to students. Before expanding to other high-signal schools we want the hypotheses behind it proven with more than anecdotes.

What we'll ship:

• 2 events per semester (mixer and check-in) at the current schools
• An educational angle (e.g. IRL pocket guides) to test why students engage
• Ambassador and event metrics, written up with a recommendation on whether to expand

We'll know we're successful when:

• Existing schools confirm they want to repeat the program next semester
• Ambassador applications grow in the next semester
• Events stay engaging and attended

Owner: Daniel ZaltsmanDaniel Zaltsman

Motivation: Builders already gather in local groups, collectives, and hacker houses, and we have a long list of applicants we haven't been able to keep up with. We want groups that run on their own energy, with light support from us.

What we'll ship:

• A response to every existing applicant
• Reactivation attempts for all dormant chapters (10+ today)
• A "cool builder groups" page on posthog.com, in the spirit of cool tech jobs
• A lightweight starter kit for organizers (event formats, support and swag, a Luma setup)
• Overlap identified with Brittany's champions work

We'll know we're successful when:

• 10 previously dormant groups are running events again
• Groups run events with no PostHog staff involved in organizing them
• Organizers support each other in onboarding

Owner: Daniel ZaltsmanDaniel Zaltsman

Motivation: We have a product engineer and founder motion but little presence beyond a few hubs. Events are where we can test new markets, but only if each one meets a high bar: premier topics, speakers, and partners, all produced by PostHog.

What we'll ship:

• A short event playbook: principles, 2-3 formats, and a quality bar (food, activations, and content capture included)
• Market selection using where our users are growing
• 12 PostHog-produced events built around premier topics, speakers, and partners
• Content captured at every event, using the capture standard from the content from events objective

We'll know we're successful when:

• 12 events have run and each meets the quality bar
• There is demand to expand the format elsewhere

Owner: Brittany JoinerBrittany Joiner

Motivation: Every channel needs champions on both sides, internal engineers and external leaders. Without both, a channel doesn't work and we should kill it.

What we'll ship:

• A /community hub linking every channel, agreed with website and editorial
• GitHub (priority): a contribution policy in the handbook agreed with product teams, GitHub added to community triage, and named responders
• Reddit: a "people, not the brand" approach in the handbook, with engineers engaging from their own accounts

We'll know we're successful when:

• The new /community hub is shipped
• Product teams have agreed how they handle GitHub contributions
• 90% of community GitHub issues/PRs get a first response within 48h