Members

Goals

Q2 2026 goals

• PostHog = AI First (James)

  • Every product should be usable by an MCP and/or have useful signals implemented (James)
  • Launch PostHog Code (James)
  • Positioning (James)

• Hit our ARR target (Tim)

  • Launch managed warehouse with pricing (Raquel)
  • Launch PostHog Code with pricing (James)
  • Ongoing margin + cost work (Tim)

• Increase reliability (Ben)

  • Set up better limits/boundaries/guidance where relevant (Ben)
  • Figure out, across the various use cases, what are the root problems of reliability and what do the product teams need to do (Ben)
  • We understand the root causes of and assign owners to get to X nine’s (depending on product - part of the goal is figuring out what this number should be) (Ben)

• Query performance (Paul)

  • significantly reduce the count of slow queries per day
  • significantly reduce p95 of seconds users spend waiting for results

• Make sure we’re marketing and cross selling every product the right amount, to keep moving us away from being seen as analytics++ (Charles)

• Charles: Sales & demand gen, customer success, onboarding, marketing & content, support, and billing

• James:

  
  Website Team
  
  Website Team, and core AI products

• Raquel: data stack, and PMs

• Paul: Product analtyics, Web analytics, Analytics platform, Customer analytics, Client libraries, Session replay, Platform UX

• Tim: growth, devex, sales/CS/ops/finance/people

• Ben: Infra, ClickHouse, & various product teams

Working together

The

Blitzscale Team

Blitzscale Team meets once a week to check in on immediate changes and unblock anything that needs to move fast. These meetings work best when the group stays lean, though sometimes we'll invite people outside the core team to contribute if they are working more closely on a specific area. This is particularly useful for deeper context or a new perspective on an ad-hoc basis.

A smaller meeting helps us move quickly and prevents us from overcollaborating. We've learnt that once the meeting gets too big, people become less likely to raise issues in their area and decision making slows down as a bigger group pushes for consensus instead of quick decisions.

To keep the group focused:

• Blitzscale should be a small team, just like any other team at PostHog. We aim to keep it to fewer than six people.
• As PostHog grows, we will add more director-level leaders but they will not necessarily join all meetings. If everyone joins the weekly meetings, the group will quickly become too large to be effective.
• We will review who is in the weekly meeting every three months and adjust as needed.
• Not being in the meeting does not mean your work is not important. It usually means you are doing a great job communicating everything the team might need to be aware about, so staying focused on your area is more important.

Notes are posted in #team-blitzscale later in the week.

Handbook