Skip to content

Sprint - April 20 to May 3 #54405

Closed
Closed
Sprint - April 20 to May 3#54405
Labels
sprintSprint planning

Description

@dustinbyrne
dustinbyrne
opened on Apr 14, 2026

Sprint Planning

List of incidents + any action items that haven't been scheduled yet

Team sprint planning

For your team sprint planning copy this template into a comment below for each team.

# Team ___

**Support hero:** ___
**Off during the sprint:** ___

## Quarter goals

1. Quarter goals, status (red/yellow/green) and action points if yellow/red

## Retro

### Tasks

<!-- Grab the high and low priority items from last time and add whether that item was completed or not -->

## Plan

### High priority

-

### Low priority / side quests

-

### Are any other teams impacted by this plan? If so, tag them here

-

Activity

  1. dustinbyrne
    added
    sprintSprint planning
    on Apr 14, 2026

  2. dustinbyrne commented on Apr 14, 2026

    @dustinbyrne
    dustinbyrne
    on Apr 14, 2026
    ContributorAuthor

    Team Client Libraries

    Support hero: @dustinbyrne then @marandaneto
    OOO: @marandaneto @ioannisj 1 day

    Quarter goals

    • ⚪ Goal 1: What makes PostHog more tailored to how you actually use it
      • ⚪ Discover SDK + default gaps
      • ⚪ Proactive user research (interviews, surveys, mobile/backend focus)
      • ⚪ AI-assisted SDK setup + usage improvements
    • ⚪ Goal 2: PostHog libraries vNext
      • ⚪ Offline-first / async-first posthog-js
      • ⚪ Distributed tracing headers + remote config support
      • ⚪ More framework-specific wrappers
      • ⚪ Framework expansion (e.g. Angular wrappers)
      • 🟡 Mobile session replay (triggers, min duration, RN/Flutter/macOS, perf)
      • 🟡 Mobile error tracking (iOS improvements, RN support & restructuring, breadcrumbs)
      • ⚪ Flutter desktop support (Windows/Linux)
    • 🟡 Goal 3: Maintaining the SDKs
      • ⚪ SDK test harness + CI integration
      • 🟢 SDK rotation ownership
      • ⚪ Config standardization (API key/token)
      • ⚪ Ingestion rate limiting support
      • 🟢 Unified remote config endpoint (/static/token/config)
      • ⚪ SDK design guidelines and best practices
    • ⚪ Goal 4: Log for Mobile
      • ⚪ Add support for collecting and sending app-side logs from Android
      • ⚪ Add support for collecting and sending app-side logs from iOS
      • ⚪ Add support for collecting and sending app-side logs from Flutter
      • ⚪ Add support for collecting and sending app-side logs from React Native

    Retro

    Details

    High priority

    Low priority / side quests

    Plan

    High priority

    Low priority / side quests

    🟢 =finished 🟡=in progress 🔴=won't finish ⚪=not started

  3. marandaneto
    pinned this issue on Apr 15, 2026

  4. MichaelKutsch-ph commented on Apr 15, 2026

    @MichaelKutsch-ph
    MichaelKutsch-ph
    on Apr 15, 2026
    Contributor

    Team Infra

    Support hero: @danielxnj @MichaelKutsch-ph

    Retro

    High Prio

    • 🟡 migrate more apps to The Application™
      • django stack
      • admin api
      • web and worker still outstanding, needs some work still
    • 🟡 more network things (tailscale setup cleanup) @MichaelKutsch-ph - standardized ECS done, in rollout
    • ✅ Cilium: own nodepools with cilium only, route percentage of traffic to it on dev - let it sit for a while and then progress @danielxnj
    • ✅ improve argoCD notifications - increase transparency about appHealth and deployments @Z3r0Sum - rollout per teams for team-based notifcations, feature flags, managed warehouse...
    • ⚪ use bigger node sizes to reduce overall node count / lighten EKS API load @langesven
    • 🟡 VictoriaMetrics:
      • Upgrade VM to latest @MichaelKutsch-ph
      • Node optimization VM: @danielxnj
        • Move vm to own nodepools (noisy neighbour)
        • More beefy nodes?
        • Tackle noisy neighbour (guaranteed QoS)
      • 🟡 Analyze expensive queries @langesven
    • 🟡 Dev env: argo test env with actual dev environment -> long term goal immutable infrastructure @Z3r0Sum - PoC with agent-based orchestration
    • 🟡 smokescreen rollout @Daesgar - rollout to some services in prod, e.g. capture, temporal.... -> golden chart integration

    side quest

    • GitHub secret terraform provider, start using it again @-support-hero
    • Alerting / Monitoring for our gh actions

    ✅=finished 🟡=in progress 🔴=won't finish ⚪=not started

    OKR Infra

    High Prio

    • MSK with kafka 4 @MichaelKutsch-ph
      • dev first plus switch-over
      • identify things for better automation
      • prod-* too once everything is clear
    • more network things (tailscale setup cleanup) @MichaelKutsch-ph
    • smokescreen rollout @Daesgar + golden chart integration-
    • migrate more apps to The Application™
      • django stack
      • admin api
      • web and worker still outstanding, needs some work still
    • Cilium: starting EU rollout @danielxnj
    • argo notifications: rollout to teams @Z3r0Sum
    • VictoriaMetrics:
      • Upgrade VM to latest @MichaelKutsch-ph
      • Node optimization VM: @danielxnj
        • Move vm to own nodepools (noisy neighbour)
        • More beefy nodes?
        • Tackle noisy neighbour (guaranteed QoS)
      • Analyze expensive queries @langesven

    side quest

    • GitHub secret terraform provider, start using it again @-support-hero
    • Alerting / Monitoring for our gh actions
    • argoCD appset templating

  5. tomasfarias commented on Apr 15, 2026

    @tomasfarias
    tomasfarias
    on Apr 15, 2026
    Contributor

    Team Batch Exports

    Support hero: @tomasfarias / @rossgray

    Quarter goals

    • Objective 1: Unify batch exports and real-time destinations
    • Objective 2: Reduce pipeline architecture technical debt
    • Objective 3: Self-serve debugging

    Retro

    Details

    High priority

    ✅ Display for realtime destination backfills failed/successful runs @rossgray

    • Now displaying partial errors
    • Now supporting an error threshold that, when reached, fails the run.
      • Currently, not configurable, but we may open this up for users to configure in the future.
    • Other enhancements to logs/runs view.
      ✅ Add concurrency for workflows batch export @tomasfarias
      🟡 With load testing
      • Need to take a look at configuration.
      • Seeing connection timeout errors.
        🟡 Review metrics and alarms
    • backlog_count
    • Building a new grafana dashboard
    • Next sprint: Resource based allocator + auto-scaler

    Low priority

    🟡 Add documentation/tooltip for table setup for BigQuery

    • Add query to create the table

    • Would be nice if this was available via the API

    • Improve debugging tools
      🟡 Enable MCP integration

      • Check status, and try to get it over the line
      • Partially already completed: System tables & Integrations MCP.
        ✅ Improve backfill script

    🔴 Refactor logging library

    ✅=finished 🟡=in progress 🔴=won't finish ⚪=not started

    High priority

    • Split up S3 destination into supported destinations into:

      • S3-compatible (catch-all)
      • AWS S3
      • Cloudflare R2
      • GCS

    • Integration for AWS S3 with support for no-credentials authentication

    • Integration for PostgreSQL

    • Resource based allocator + auto-scaler for batch export workers

    Low priority

    • Add new snowflake inserted_at column

    • Explore retryable/non-retryable in response body of CDP API

      • So that batch export can retry the request

  6. frankh commented on Apr 15, 2026

    @frankh
    frankh
    on Apr 15, 2026
    Contributor

    Team Logs

    Write more bytes somehow

    Retro

    Details

    High priority

    Low priority / side quests]

    • 🟡 services overview @jonmcwest
    • ⚪ investigate ways to make PostHog be willing to pay for PostHog logs
    • ⚪ server side settings/filters
    • 🟡 merge in ben's metric stuff

    High priority

    • PII scrubbing / server side settings/filters / ingestion pipeline @DanielVisca
    • traces out for posthog internal use in prod @frankh
    • finish up backups @frankh
    • column configurations in saved views @jonmcwest
    • have real internal users for alerts @jonmcwest
    • Add alerting to MCP, and get claude to create a bunch of alerts to stress test @DanielVisca

    Low priority / side quests

    • Get metrics MVP running in dev

    🟢 =finished 🟡=in progress 🔴=won't finish ⚪=not started

  7. meikelmosby commented on Apr 15, 2026

    @meikelmosby
    meikelmosby
    on Apr 15, 2026
    Collaborator

    Team Workflows

    Time Off

    • Abe (24th of April until 27th)
    • @havenbarnes put in your PTO if you have any :)

    Retro

    High priority

    • Rolling out postgres-v2 to team 2 / all services @dmarchuk
    • Email delivery throttle @meikelmosby
    • Solve memory problem on hog-worker @meikelmosby
    • Solve auto-scaling issues (oscillating a lot) for hog-worker @meikelmosby
    • Solve problem around runaway partition lag for consumers @meikelmosby
    • "Wait until event" workflow action / conversion goal @dmarchuk
    • Push Notifications for android / ios @havenbarnes
      • Look into GDPR
      • Look into just storing device tokens in person props
    • Roll out recurring workflows @dmarchuk
    • Move all services to /apps in charts repo @meikelmosby

    Low priority

    This Sprint

    High priority

    Low priority

    • Reminder: cleanup for cyclotron migration @havenbarnes
      • spin down legacy workers once the final delayed workflows have executed
      • clean up legacy code as well once it's no longer in hot path

  8. rafaeelaudibert commented on Apr 15, 2026

    @rafaeelaudibert
    rafaeelaudibert
    on Apr 15, 2026
    Member

    Team Growth

    Support hero: @rafaeelaudibert and @MattBro
    Off during the sprint: Rafa's honeymoon 2nd week of the sprint, Pipa, Rio Grande do Norte, Brazil

    Quarter goals

    1. Make agentic sign ups first-citizen of PostHog 🟡 (@MattBro @fercgomes )
    2. Allow anyone to integrate/provision an org + project in PostHog 🟡 (@rafaeelaudibert @MattBro)
    3. Activation rate across all onboarding experiences should be 60%+ 🟡 (@fercgomes @MattBro @rafaeelaudibert)
    4. Shape the external interface for Signals ⚪ (@fercgomes @MattBro @rafaeelaudibert )
    Details ⚪ = Not Started 🟡 = In Progress 🟢 = Completed 🔴 = Won't complete 🔵 = Abandoned

    Plan

    High priority

    Low priority / side quests

    Retro

    Details
    • SPT for Stripe Projects @MattBro 🚧 (broken on Stripe-side)
    • Stripe OAuth in DWH @rafaeelaudibert ✅
    • Stripe Workflows @rafaeelaudibert 🚧
    • Stripe Full Screen app @rafaeelaudibert ✅
    • Make Agentic Provisioning generic enough to work with the wizard @MattBro ✅
    • Allow the wizard to provision accounts programatically 🚧
    • Clean up OAuth management page @MattBro :constr
      • Seeing the existing OAuthApplication ✅
      • Seeing existing OAuthAccessToken issued for your account, revoke them. ✅
      • Change the scopes + email asking for permissions 🚫
    • VSCode extension ready to market @fercgomes @rafaeelaudibert ✅
    • Keep up with all of the experiments @fercgomes @MattBro ✅ @rafaeelaudibert 🚫
    • Solve/figure out what agentic onboarding is/means @fercgomes 🚧

    Low priority / side quests

    • Call with Cline to figure out if there's something we can do here @rafaeelaudibert ✅
    • Foster Cmd K adoption with some UI changes to the sidebar @rafaeelaudibert 🚧
    • Keep digging more on the Vercel integration, possibly Edge FF resolution @MattBro 🚫
    • Finish survey support for toolbar @fercgomes 🚧
    • Support vision for PostHog AI via the toolbar @fercgomes 🚧

    What else did we do?

    • Cross-sell on the sidebar is much smarter, using weighted selector @rafaeelaudibert
    • Improved billing/project notice component @rafaeelaudibert
    • Deployed mcpcat @rafaeelaudibert
    • Adding Activated intent event for all products available during onboarding @fercgomes
    • Worked on general posthog activation (ingested event + something from product, correlated to 3-month retention) @fercgomes
    • POC Claude Managed Agents @MattBro
    • In-person talk in NYC @MattBro

  9. mariusandra commented on Apr 15, 2026

    @mariusandra
    mariusandra
    on Apr 15, 2026
    Collaborator

    Data Team Tools

    Q2 2026 objectives

    Objective 1 - Build a BI experience that feels competitive and joyful (Marius)

    • ⚪ New chart types, prioritizing the most-requested visualizations
    • 🟡 SQL editor reliability and UX improvements
    • ⚪ Better variables, including multiselect, query-backed and time-based variables (e.g. for dashboards)
    • ⚪ Easier schema exploration and an alternate “no-sql” query building interface (manual controls + AI integration).
    • ⚪ Ability to click in and out of rows to explore deeper.

    Objective 2 - Make notebooks the default way to analyze data (Anna)

    • ⚪ Python notebooks for customers
    • ⚪ Core notebook UX and stability improvements
    • ⚪ Better integration between notebooks, HogQL, DuckDB, and external databases
    • 🟡 Initial collaboration improvements for notebooks (lock nodes if someone is editing, etc)
    • ⚪ A clearer default analysis flow centered on notebooks

    Objective 3 - Build a first-class querying and DuckDB experience (George)

    • ⚪ First-class DuckDB support (not treated as “just Postgres”)
    • ⚪ Better query errors so failures are understandable and actionable
    • ⚪ Improvements to the HogQL type system to support earlier errors
    • ⚪ Calculated properties and lambdas on top of HogQL tables
    • ⚪ Improved UX for connecting to databases

    Retro

    • Could we release direct postgres queries? @annaszell
    • Gather (and fix?) notebook papercuts @annaszell
    • Splitting up postgres/duckdb (not "just postgres"), quality of life improvements from this @georgemunyoro
    • Calculated properties (clearing the way for it) @georgemunyoro
    • SQL editor papercuts @mariusandra
    • Whatever is most important for SQL/BI when I'm back one week later @mariusandra

    Plan

    Support rota: George then Marius

    High priority

    • Projections / schema editing
    • SQL editor to notebooks (Filters, AI chat?)
    • Notebook papercuts and vibeation @annaszell

    Low priority / side quests

    Are any other teams impacted by this plan? If so, tag them here

    • N/A

  10. rorylshanks commented on Apr 15, 2026

    @rorylshanks
    rorylshanks
    on Apr 15, 2026
    Contributor

    Team ClickHouse

    AKA Team Read Fewer Bytes Please

    Retro

    High priority

    Low priority / side quests]

    🟢 =finished 🟡=in progress 🔴=won't finish ⚪=not started

  11. andrewjmcgehee commented on Apr 15, 2026

    @andrewjmcgehee
    andrewjmcgehee
    on Apr 15, 2026
    Contributor

    Team Data Modeling

    OOO

    • no one

    Retro

    High priority

    • get materialized insight endpoint results to parity with non-materialized @sakce 👈
    • remove cache age from endpoints in favor of data freshness @sakce 👈
    • remove the beta label from endpoints (includes any work to get us "there") @sakce 👈
    • improve error handling ui/ux surfaced to customers for models @andrewjmcgehee 👈
      • errors not displaying in EU 👈
      • show logs on syncs so customers can self-diagnose 👈
    • team 2 billing models runs against duckgres completely successfully @andrewjmcgehee
    • smooth transition into models backed/synced by GitHub @andrewjmcgehee 👈

    Low priority

    • explore & implement modeling team isolated CI / DB stuff @andrewjmcgehee
    • project secret API keys @sakce 👈
    • MCP for endpoints @sakce 👈
    • write a persona map (check experiments for example) @andrewjmcgehee 👈

    👈 = WIP

    This Sprint

    High priority

    • remove the beta label from endpoints @sakce 🚧 chore(endpoints): remove BETA label #54808
    • smooth transition into models backed/synced by GitHub @andrewjmcgehee 👈
    • remove beta label for modeling if error rates below 3% @andrewjmcgehee
    • allow required/optional vars on endpoint execution (filtering and grouping) @sakce 🚧
    • make duckgres work properly for endpoint execution @sakce
      • todo: come up with a set of endpoints to verify this
    • plan migration / deprecation of /query api @sakce
    • think about skills / ai and schedule customer interviews @andrewjmcgehee
      • write a rfc following guidelines
      • write first skills PR

    Low priority

    Q2 Goals

    Let's review them

  12. joshsny commented on Apr 17, 2026

    @joshsny
    joshsny
    on Apr 17, 2026
    Contributor

    Team PostHog AI

    Support hero: @cvolzer3, ?
    Off during the sprint: @joshsny - 1.5 days 💒, @tatoalo - 1 day

    Retro

    Tasks

    🟢=finished 🟡=in progress 🔴=won't finish ⚪=not started

    High priority

    • 🟢 @tatoalo @VojtechBartos test and improve ux of cloud runs in posthog code - working through issues in canvas in order
    • 🟡 @skoob13 @cvolzer3 migrate CI evals to sandboxes
    • 🔴 @skoob13 start posthog ai migration
    • 🟢 @skoob13 finish experiment with cli tools mcp, we should ship this
    • 🟢 @ryans-posthog ship structured output to production
    • 🔴 @ryans-posthog understand why our agent is much slower than claude code directly
    • 🟢 @ryans-posthog get a better understanding of current sandbox infra
    • 🟡 @ryans-posthog babysitting PRs
    • 🟢 @cvolzer3 keep improving UI/UX papercuts of PostHog AI
    • 🟡 @cvolzer3 expand the surface of the MCP store
    • 🟢 @cvolzer3 get MCPs working in the sandbox
    • 🟢 @cvolzer3 regional support for bedrock in the gateway

    Side quests

    Plan

    High priority

    • @skoob13 release single-tool mcp server that works with haiku
    • @skoob13 start working on context for sandbox agents, injecting context from current UI / insight
    • @skoob13 write docs for evals
    • @skoob13 make sure skills docs are 😘
    • @VojtechBartos @tatoalo continue working through the cloud run ux in posthog code
    • @VojtechBartos @tatoalo try get to parity with local runs (terminal, bash commands from message)
    • @cvolzer3 ship the MCP store, make it a great experience in PostHog Code
    • @cvolzer3 support hero
    • @tatoalo ship the full version of cloud attachments
    • @tatoalo github repo cache + refresh api
    • @tatoalo full parity for codex in cloud
    • @ryans-posthog babysitting PRs
    • @ryans-posthog improve how our temporal workflow manages sandbox lifecycle
    • @ryans-posthog multi repo support for task runs in sandboxes
    • @ryans-posthog take a look at sandbox setup ux
    • @joshsny look into the modal sandbox snapshot situation
    • @joshsny BAA with OpenAI / checking if we need any legal things in PostHog Code

    Side quests

    Are any other teams impacted by this plan? If so, tag them here

  13. hpouillot commented on Apr 17, 2026

    @hpouillot
    hpouillot
    on Apr 17, 2026
    Contributor

    Team Error Tracking

    @hpouillot OOO 3 days

    Retro 🟢 🔴 🟡 🚫

    @cat-ph - add error tracking MCP tools 🟡 Few tools remaining
    @cat-ph - stretch: agent usage instrumentation 🟢

    @ablaszkiewicz - issue migration follow-up 🟢 Done, investigation on the performance. Sync has delays
    @ablaszkiewicz - design recommendation center 🟢
    @ablaszkiewicz - stretch: integration with feature flags / experiments 🔴

    @fivestarspicy - conduct ET usage interview 🟡 Power users list collected + outreach messages ready.
    @fivestarspicy - cost analysis 🚫 Delayed
    @fivestarspicy - market research AI / ET 🟢 Need to create a Slack canvas with the findings

    @hpouillot - architecture diagram for cost analysis 🔴
    @hpouillot - breadcrumbs 🟡 UI is ready, PR for JS SDK
    @hpouillot - code owners usage for assignment rules 🔴 -> Replace with cymbal metrics, symbol set sticky routing inside cymbal.

    OKR

    Recommendations - Setup & Priorities
    Grouping - Grouping
    Agent experience - MCP & Wizard
    Pricing exploration - Value alignment
    Issue Report - Signal integration
    Search query - Migration & Performance

    High priority

    @hpouillot - code owners usage for assignment rules
    @hpouillot - breadcrumbs web SDK
    @hpouillot - architecture schema for cost analysis
    @hpouillot - stretch: react and node SDK for breadcrumbs

    @cat-ph - Remaining MCP Tools
    @cat-ph - Skills for the wizard inside context mill

    @fivestarspicy - send outreach to ET users
    @fivestarspicy - pitch with Christophe for issue rate limiting

    @ablaszkiewicz - issue migration sync, clickhouse union with dirty issues
    @ablaszkiewicz - add recommendations to center (alerts, weekly digest, ingestion issues, cross-sell)
    @ablaszkiewicz - issue rate limiting

  14. lucasheriques commented on Apr 17, 2026

    @lucasheriques
    lucasheriques
    on Apr 17, 2026
    Contributor

    Team Surveys

    Support hero: @lucasheriques

    Quarterly goals

    🟡 Goal 1: Surveys research & pricing exploration
    🟡 Goal 2: Surveys MCP & skills
    ⚪ Goal 3: MCP analytics

    Retro

    High priority

    • Work on Surveys' skills to make it simpler for people to create them without leaving PostHog AI/Claude Code/Codex @lucasheriques
    • Have at least 5 calls during this sprint to discuss surveys' pricing @lucasheriques
    • Look into adoption by medium and large customers @fivestarspicy

    Side quests

    • Finish dashboard for surveys' o11y

  15. vdekrijger commented on Apr 20, 2026

    @vdekrijger
    vdekrijger
    on Apr 20, 2026
    Contributor

    Team Analytics Platform

    Support hero: @vdekrijger
    Off during the sprint:

    Quarter goals
    Dashboard stability and enhancements @MattPua
    • New and expanded tests to prevent unexpected failures
    • Collection of UI/UX changes that make working with dashboards a smoother experience
    • Better controls and components beyond showing just graphs
    Improve platform stability and reliability @vdekrijger
    • A clear definition of "success" for alert checks, subscriptions, exports, and query service
    • Stability improvements to better deal with degraded infrastructure
    • A 99.95% success rate for our background jobs over the last 28 days rolling
    • Anomaly detection to proactively spot regressions
    • Add sensible usage limits to everything we own @andyzzhao
    AI-first support for our owned components @vdekrijger
    • Signal integration for specific alerts
    • AI suggestions during creation
    • Improved AI onboarding
    • Investigate ways to deal with adjusted usage patterns from AI
    Revenue analytics as a platform @arthurdedeus
    • Opinionated way of linking revenue data to customers (persons/groups)
    • Fix major accuracy issues (figures not matching Stripe)
    • Build insights from revenue analytics data
    Reposition group analytics @arthurdedeus & @mjwarren3
    • Pricing RFC and actionables (e.g. change billing metric, adjust unit price)
    • Update docs to reflect the product key value driver
    • Announce new pricing (with marketing)
    Query performance Improvements @robbie-c
    • Finish backfilling sessions v3 on the new cluster
    • Fix the gaps in our query tagging
    • Ensure that new teams are created with an internal/test user cohort and help big customers migrate onto this
    • Explore person ID sharding and help other teams use preaggregation
    • Improve custom query performance with DMAT columns / and EAV table @aspicer
    • Improve the query codebase @aspicer
    Event schema @aspicer
    • Continue improving this feature
    • Add support for blocking events that don't match the schema
    Event schema @andyzzhao
    • Expand properties-rs to capture property values as well as property names
    • Ensure that posthog-ai has access to a good quality taxonomy

    Retro

    Tasks

    @MattPua

    • 🟢 Start working on dashboard templates (e.g. make it possible for our customers)

    @vdekrijger

    • 🟡 Continue with improving reliability and tackling issues that are surfaced in the new dashboard
    • 🟢 Investigate the alert issue raised by the customer
    • 🟢 Tackle the papercuts I've accumulated over the last few days

    Plan

    High priority

    @MattPua

    • 🟢 Finish work related to dashbboard templates for copying templates between projects
    • 🟢 Finish up new alerts chart from Lisbon Hackathon
    • 🟢 Finish setup for new machine
    • 🟡 New Dashboards for Alerts/Subscriptions Metrics

    @vdekrijger

    • Migrate alerts from Celery to Temporal
    • Tackle a few outstanding resiliency improvements for our owned components
    • Investigate possibilities for adding SLOs for the query service
    • Tidy up the hackathon into separate PR's
    • Start on integrating AI as a first class citizen.

    Low priority / side quests

    Are any other teams impacted by this plan? If so, tag them here

  16. TueHaulund commented on Apr 20, 2026

    @TueHaulund
    TueHaulund
    on Apr 20, 2026
    Contributor

    Team Session Replay

    Support hero:
    @fasyy612

    OKRs

    Details
    • 🧠 Goal 1: Nail single-session on-demand summaries
    • 🎬 Goal 2: Scale video export pipeline
    • 🏷️ Goal 3: Build session categorizer
    • 📡 Goal 4: Replay as a Signal source
    • 🖥️ Goal 5: Build new AI-native frontend for Replay
    • 🔌 Goal 6: Basic MCP for Session Replay
    • 💰 Goal 7: Business model for AI features
    • 🔒 Goal 8: Map out PII, data retention, and IP concerns
    • 🗂️ Goal 9: Set up data labelling system for replays

    Retro

    Details

    ✅ @ksvat Test V2 triggers with select customers
    🟡 @ksvat Start planning effort for new AI-centric Replay Home

    🟡 @fasyy612 POC for custom summarization preamble/prompt

    🟡 @nicowaltz First version of labelling suite
    ✅ @nicowaltz Finalize and merge feature collection PRs

    ✅ @TueHaulund Fully retire old video exporter
    ✅ @TueHaulund Gradual release of on-demand single-session summaries

    ✅ @fivestarspicy Figure out early-access cohort for single-session summaries
    🟡 @fivestarspicy Start looking into reliability metrics

    High priority

    @fasyy612 Custom summarization preamble/prompt + custom tags

    @ksvat Become MCP master and get an overview of current MCP

    @nicowaltz Wrap up labelling suite initial version
    @nicowaltz Coordinate data training efforts

    @fivestarspicy FinOps - figure out cost per active minute
    @fivestarspicy Beta learnings doc (session summarization)

    @TueHaulund Implement continuously sweeping summarization job to even out rasterizer load
    @TueHaulund Clean up feature flags and discontinued summarization types

  17. Radu-Raicea commented on Apr 20, 2026

    @Radu-Raicea
    Radu-Raicea
    on Apr 20, 2026
    Member

    Team LLM Analytics

    Time off

    Quarter goals

    Goal 1: Agent-first LLM Analytics @richardsolomou @brandonleung @carlos-marchal-ph
    Goal 2: Proactive LLM Analytics @andrewm4894
    Goal 3: Full evals stack @andrewm4894
    Goal 4: Product glue @brandonleung @richardsolomou
    Goal 5: Reliability and performance @Radu-Raicea @carlos-marchal-ph
    Goal 6: Trace and session UI @richardsolomou
    Goal 7: Ingestion pipeline and migration @carlos-marchal-ph @Radu-Raicea

    Retro

    Details

    High priority

    Low priority / side quests

    Plan (W17, W18)

    High priority

    Low priority / side quests

    Mid-sprint check-up

  18. pl commented on Apr 20, 2026

    @pl
    pl
    on Apr 20, 2026
    Contributor

    Team Ingestion

    Retro

    Details

    High priority

    • Isolate ingestion kafka topics
      • 🟢 Finish outputs refactoring @pl
      • 🟢 Test Kafka 4 @pl
      • 🟡 Break out the ingestion MSK cluster @pl
    • PersonHog
    • Expand first point of capture to support better processing tooling
    • Set ingestion SLAs and metrics and commit to them
    • Improve per-partition ingestion throughput
      • 🟢 Implement batching pipelines @pl
      • 🟢 Stretch: Prototype the Kafka consumer @jose-sequeira
      • 🟢 Figure out how to deploy with sidecars @jose-sequeira
    • Deduplicator
    • Event Filtering
      • 🟡 Implement more efficient event filtering based on the RFC @pl
    • Error Tracking Ingestion
      • 🟢 Validate correctness in production @z0br0wn
      • 🟢 Add alerting, etc for ingestion-errortracking @z0br0wn
      • 🟢 Switch over to ingestion-errortracking @z0br0wn
      • 🟢 Clean up the testing infrastructure @z0br0wn
    • WarpStream

    Incident follow-up

    • Implement circuit breakers for error tracking @z0br0wn

    Support follow-up

    None

    Side quests

    OKRs

    • 🟢 Isolate ingestion kafka topics
    • 🟢 PersonHog
    • 🟢 Expand first point of capture to support better processing tooling
    • 🟢 Set ingestion SLAs and metrics and commit to them
    • 🟢 Improve per-partition ingestion throughput

    Projects

    TODO

    High priority

    • Isolate ingestion kafka topics
      • Break out the ingestion MSK cluster @pl
    • PersonHog
    • Expand first point of capture to support better processing tooling
    • Set ingestion SLAs and metrics and commit to them
    • Improve per-partition ingestion throughput
    • Deduplicator
    • Event Filtering
      • Implement more efficient event filtering based on the RFC @pl
    • WarpStream
      • Test capture-mirror in US without S3 Express One Zone @eli-r-ph
      • Migrate ingestion outputs to WarpStream @jose-sequeira

    Incident follow-up

    • Repartition Session Replay in prod-us, rename topics in all envs @z0br0wn
    • Error Tracking Ingestion
      • Implement circuit breakers for error tracking @z0br0wn
      • Tune the alerts to use ingestion lag @z0br0wn

    Support follow-up

  19. adamleithp commented on Apr 21, 2026

    @adamleithp
    adamleithp
    on Apr 21, 2026
    Contributor

    Team Plaform UX

    Off during the sprint: N/A

    Legend

    ⚪ = Not Started 🟡 = In Progress 🟢 = Completed 🔴 = Won't complete 🔵 = Abandoned 🟣 = Ongoing

    Q2 2026 Quarter goals

    1. "Posthog is confusing" - reduce visual complexity of PostHog and try to ease the label "confusing" or "space ship dashboard"
    2. Continue to own platform UI/UX
      • Comb through platform and fix issues/spark joy wherever possible

    Retro

    High priority

    1. 🟢 Ai first homepage

      • 🟢 Release to 100% users
        • 🟢 Handle feedback

    2. 🟡 PostHog Code help

      • 🟢 Going to help with small stuff before the launch
        • 🟢 Rebuild their navbar
        • 🟢 Rebuild their prompt input + menus
          • 🟢 Rebuild their tip tap UX (chips)

    3. 🟣 Continue to own platform UI/UX

      • Comb through platform and fix issues/spark joy wherever possible

    Low priority / side quests

    1. 🟢 Fix search algo with re-ranking (this is working nicely!)

    Plan

    High priority

    1. 🟡 Continue to develop Quill (for MCP/Code)

      • 🟢 Phase 1 (basic primitives)
      • ⚪ Top class agents.md/skill file for devs to use

    2. 🟡 Rebuild date time picker

      • 🟢 Build it in quill
      • 🟢 Add quill to posthog/frontend
      • ⚪ Experiment/Release

    3. 🟣 Continue to own platform UI/UX

      • Comb through platform and fix issues/spark joy wherever possible

  20. jurajmajerik commented on Apr 22, 2026

    @jurajmajerik
    jurajmajerik
    on Apr 22, 2026
    Contributor

    Q2 Goals

    ⚪ = Not Started 🟡 = In Progress 🟢 = Completed 🔴 = Won't complete 🔵 = Abandoned

    AI

    • 🟡 API layer - get the API ready for agents
    • ⚪ Skills - create experiment skills so PostHog AI knows how to use MCP tools effectively.
    • 🟡 MCP - supports all main operations.
    • ⚪ Signals - ship our first signal

    🟡 Feature flags - make it possible to run multiple experiments per feature flag
    🟡 Query performance - extend precomputation to the main subquery of all metric types.
    ⚪ Loading experience - consolidate fetching and set better expectations in the UI.

    Retro

    Anders

    • Feature flag stuff

      • Got the initial SDK harness test for flags out, will continue with PR’s for the SDKs (I plan to test out an “agent fleet” on this as there are some many SDKs …). This will make it a lot easier to make sure that SDK’s are comp
      • fix(compliance): declare capabilities in health endpoint
      • chore(experiments): clean up FLAG_BUCKETING_IDENTIFIER feature flag

    • Q2 goal

      • Have started to research / doddle on the Q2 goal, no deliverables yet, just deep thinking. Will result in an RFC

    • Performance (which came up in support)

      • Optimized the funnel query. Testing on our funnel queries was promising. Running in prod now.
      • feat(experiments): allow disabling expensive funnel steps data in query
      • feat(experiments): skip session_id column when funnel steps data disabled
      • feat(experiments): optimize funnel query to single events table scan

    • Copy experiment feature

      • feat(experiments): add copy experiment to another project
      • feat(experiments): track creation mode in experiment created analytics

    • Support, bugfixes, etc

      • fix(experiments): cast non-numeric HOGQL aggregation results to Float64 for winsorization
      • fix(experiments): use correct app label in admin URL reverses
      • fix(security): add semgrep audit exclusions for experiment query builder
      • feat(experiments): show timeseries click hint in metric tooltip
      • fix(experiments): increase hypothesis char limit and add live validation
      • fix(devex): recreate hogli symlink when target is dangling

    Marcel

    Rodrigo

    Juraj

    Sprint Goals

    Anders

    • Get RFC out on the changes required to feature flags to support “multiple experiments per feature flag”
    • Set up feature flag SDK harness tests for python, posthog-js, posthog-node and posthog-go (more if time)
    • Fix inconsistencies if revealed
    • Implement CUPED for mean and funnel queries

    Marcel

    • Release current AI iteration (New MCP approach and one skill), if feature flag integration is released

    Rodrigo

    • Release DW funnels and actors query. Update documentation and add to the changelog.
    • Start working on the metric load/reloads. Preserve results while loading and queued reload.

    Juraj

    • Continue on main subquery precomputation
    • Monitor existing query and make sure numbers match up
    • Extend subquery precomputation to other metric types
    • Query performance tooling
      • Ability to re-run direct path and precomputation side by side to compare

  21. haacked commented on Apr 22, 2026

    @haacked
    haacked
    on Apr 22, 2026
    Contributor

    Team Feature Flags Platform

    Support hero:

    Off during the sprint: Nobody!

    Quarter goals

    Link to goals

    1. Isolated flags-specific infra 🟡
    2. Load testing framework ⚪
    3. Sub-100ms P99, consistent response 🟡
    4. Decouple flag evaluation from persons DB 🟡
    5. Delete all /decide code 🟢
    6. Split remote_config from /flags 🟢
    7. Get /local_evaluation in a good state 🟡
    Details ⚪ = Not Started 🟡 = In Progress 🟢 = Completed 🔴 = Won't complete 🔵 = Abandoned

    Retro

    Big sprint for the performance and infrastructure goals. Patricio drove the /local_evaluation Rust rollout to 100% (EU included) with a clean revert/recover loop, plus pinned down high-cardinality metric labels on Victoria Metrics. Matheus landed real perf wins with the double-deserialization fix, a GIN index benchmark, and header-based deterministic routing, alongside IP-based rate limiting on the charts side. Haack shipped the flag version history reconstruction endpoint and the Rust dependency cache builder, cleaned up noisy SDK event properties in posthog-js, and kept Rust crates and ClickHouse query sizes under control.

    Details

    @haacked

    Feature flag event property cleanup (posthog-js):

    Flag version history & dependency cache:

    Infra & maintenance:

    @matheus-vb

    Performance & deserialization:

    Rate limiting:

    Other:

    @patricio-posthog

    local_evaluation Rust migration:

    Metrics cardinality:

    Other:

    Plan

    Project Board

    High priority

    @haacked

    @matheus-vb

    @patricio-posthog

    Side quests

    • Reduce the size of $feature_flag_called events
    • Add support for blocking specific IP addresses and specific users
    • Add dev load testing with rollout deployments

  22. burakhoca commented on Apr 24, 2026

    @burakhoca
    burakhoca
    on Apr 24, 2026

    Harika iş 🥳🥳

  23. dmarticus commented on Apr 27, 2026

    @dmarticus
    dmarticus
    on Apr 27, 2026
    Contributor

    Team Feature Flags

    Support hero:

    Off during the sprint: Nobody!

    👋 Welcome @rubychilds, joining the team as PM this sprint!

    Quarter goals

    Link to goals

    1. AI-first flag management (for PostHog employees) 🟡
    2. Real-time cohorts 🟡
    3. Close the targeting functionality gap (user + group targeting) 🟡
    Details ⚪ = Not Started 🟡 = In Progress 🟢 = Completed 🔴 = Won't complete 🔵 = Abandoned

    Retro

    A backfill-and-targeting sprint. @dmarticus stood up the temporal workflow scaffolding for event-property backfill on cohort save — coordinator + child workflow + behavioral event filter extraction — and continued grinding through the user+group mixed-targeting backlog with a stack of correctness and UX fixes (preserving conditions when switching modes, activity logging for evaluation context changes, surfacing person results over skipped group conditions). @gustavohstrassburger landed automatic person-property backfill on cohort save and pushed cohort backfill performance hard — debouncing the trigger by 5 minutes, extending cached filter TTL to 7 days, scaling temporal-worker-messaging to 100 pods in prod-US, and improving error isolation in resave_cohorts. On the side, the team rolled out device bucketing across iOS, Android, react-native, and Node SDKs, polished static cohort UX (create-from-criteria, between-input dates, duplication fixes), shipped a redesigned Match-by selector, and refreshed targeting + scheduled changes docs.

    Details

    @dmarticus

    Event property backfill on cohort save:

    User + group targeting:

    Static cohorts UX:

    Mobile SDK device bucketing:

    Browser SDK fixes:

    Docs & policy:

    Recruiting:

    @gustavohstrassburger

    Person property backfill on cohort save:

    Long-tail backfill performance:

    Remote config & flags UX:

    HogVM & test fixes:

    Plan

    Project Board

    High priority

    @dmarticus

    @gustavohstrassburger

    • Behavioral cohorts on team 2 (internal testing)
    • Wire up event-property backfill on cohort save end-to-end (taking over from @dmarticus — coordinator + child + filter extraction landed last sprint, integration + rollout next)
    • Continue chipping at long-tail expensive cohort backfills (bring 99th-percentile orgs down from ~31h significantly)

    @rubychilds

    • Onboarding to the team — get up to speed on Q2 goals and current state of targeting + cohorts work

    Side quests

    @dmarticus

    @gustavohstrassburger

  24. Gilbert09 commented on May 1, 2026

    @Gilbert09
    Gilbert09
    on May 1, 2026
    Member

    Team Warehouse Sources

    Support hero: @danielcarletti then @estefaniarabadan
    OOO:

    • Tom (week before Barbados - bank holiday + pto)
    • Daniel (05/1 - local holiday = Labor day)

    Quarter goals

    • ⚪ Goal 1: Improve pipeline stability and reliability (Estefania)
    • ⚪ Goal 2: Add warehouse data integrations with other PostHog products (Tom)
    • ⚪ Goal 3: Add more sources (Marcus)
    • ⚪ Goal 4: Improved source config (Daniel)
    • ⚪ Goal 5: Bonus objective
      • User error notifications (including disabled due to errors) (Anyone)
      • Activation, retention metrics (stretch goal) (Anna)

    Retro

    Details
    • [Daniel] Unexpectedly had a difficult time finding one of our Postgres DB to serve as Logical Replication test. Basically the same problem we usually have for sources: how do you get a real example of the source to test?
      • The solution might be heavy payload mocking. Maybe we could start a payload database? Like having payload examples for all endpoints/schemas we are able to sync, and get that to auto update with real data. Won't help for plain DBs but for REST/GraphQL/etc it would be awesome
      • For databases, I've been generating a lot of scripts that create tables and feed data, as well as long running scripts that just run DML ops on them.
    • 🟢 [Tom] Have a handle on #alerts-warehouse-sources with pods
    • 🟡 [Tom] Get existing stripe users migrated over to webhooks
    • 🔴 [Tom] Get back onto working on Warehouse => CDP integration
    • 🟢 [Marcus] Support
      • add FORCE INDEX fallback for MySQL bad-plan timeouts
      • add read and session timeouts to MySQL sync connection
      • probe actual scale for unconstrained postgres numeric columns
      • fix capturing logs within the iterator
      • normalize corrupted vitally region in job_inputs
      • return 400 instead of crashing when Stripe webhook signing secret is missing
      • fix postgres failing because of invalid startup options
      • add management command to re-enable schemas disabled by error
    • 🔴 [Marcus] Slack webhook support
    • 🔴 Marcus] More sources (priority)
    • 🟢 [Marcus] first iteration of MCP tools
    • 🟢 [Marcus] add TLS opt-out toggle for Postgres sources with SSH tunnels
    • 🟢 [Marcus] allow users to specify custom primary key for schema syncs
    • 🟡 [Estefania] Rollout pipelines V3 to beta sources to more teams and monitor
    • 🟢 [Estefania] Start the work on writing to DuckDB/DuckLake

    High priority

    • 🟢 [Tom] Have a handle on #alerts-warehouse-sources with pods
    • 🟡 [Tom] Get existing stripe users migrated over to webhooks
    • 🔴 [Tom] Get back onto working on Warehouse => CDP integration
    • 🟡 [Daniel] Release Postgres Logical Replication, fix bugs and implement improvements from initial user feedback. Validate scalability and safety net
    • ⚪ [Daniel] If the logical replication is working perfectly, the next step is test other Postgres backed dbs (specially Supabase)
    • 🟢 [Daniel] Frontend updates to Postgres source setup (push users towards CDC, have more details and explain things better for non-technical users)
    • 🟢 [Daniel] Validate and release ClickHouse as a source
    • 🟢 [Marcus] Support
      • add FORCE INDEX fallback for MySQL bad-plan timeouts
      • add read and session timeouts to MySQL sync connection
      • probe actual scale for unconstrained postgres numeric columns
      • fix capturing logs within the iterator
      • normalize corrupted vitally region in job_inputs
      • return 400 instead of crashing when Stripe webhook signing secret is missing
      • fix postgres failing because of invalid startup options
      • add management command to re-enable schemas disabled by error
    • ⚪ [Marcus] Slack webhook support
    • ⚪ Marcus] More sources ([priority)
    • 🟢 [Marcus] first iteration of MCP tools
    • 🟢 [Marcus] add TLS opt-out toggle for Postgres sources with SSH tunnels
    • 🟢 [Marcus] allow users to specify custom primary key for schema syncs
    • 🟡 [Estefania] Rollout pipelines V3 to beta sources to more teams and monitor
    • 🟢 [Estefania] Start the work on writing to DuckDB/DuckLake

    Low priority / side quests

    • ⚪ [Daniel] Improve observability: make it easier to find and read logs, perhaps with a script so even AI can quickly fetch logs from temporal workflows
    • ⚪ [Estefania] Add re-sync schema option to django admin

    Plan

    High priority

    • [Marcus] mcp improvements
      • update backend to have correct openapi types
      • remove custom handlers in the mcp
    • [Marcus] release slack with webhooks
    • [Marcus] show warning when selecting an incremental field without an index
    • [Tom] Get started on some Skills
    • [Tom] Get back onto working on Warehouse => CDP integration
    • [Estefania] Investigate alternatives to Kafka for PipelinesV3 and decide based on it
    • [Estefania] Continue the work on writing to DuckDB/DuckLake
    • [Daniel] Get Postgres CDC over the line: finalize prod tests and release to a few customers. If it goes well, release to general pop under a early Beta flag
    • [Daniel] Extend Postgres CDC to other compatible sources (Supabase mainly)
    • [Daniel][Stretch] Database sources: multi-database/schema support
      • Define structure and raise requirements
    • [Daniel][Stretch] Configure columns to import from the source

    Low priority / side quests

    🟢 =finished 🟡=in progress 🔴=won't finish ⚪=not started

  25. pawel-cebula commented on May 4, 2026

    @pawel-cebula
    pawel-cebula
    on May 4, 2026
    Contributor

    Team Billing

    Retro

    Retro items

    @minekansu

    • 🟡 exploratory analysis for defining active user and active org - started working on this but got distracted by other tasks, mainly quota calculations
    • 🟡 data quality checks for revenue model
    • sales ops tasks
      • ✅ fix ooo logic
      • 🔴 fix issues with sfdc ownership assignments - leaving this to Abhischek with custom object migration
      • ✅ automation around data surfacing and collection for contract setup
      • ✅ review customers on coupa/ramp etc to help finance decide if we want to take over process from sales
    • ✅ sales growth review
    • ✅ quota calculation numbers required lots of manual fixes
    • ✅ commercial AE role data analysis
    • ✅ trigger to auto set AE owners in vitally post opp close
    • ✅ forecasting review and brainstorming with Fraser
    • ✅ customer dinner with Tim
    • ✅ Updated onboarding team revenue retention numbers
    • ✅ clean up and round robin Cam's lead and accounts
    • ✅ automation for contacts to collect info from sales team proactively

    @pawel-cebula

    • In-house credit ledger
      • ✅ Implement creating credit model records for last remaining customer balance transactions - #1838, #1847, #1849
      • 🟡 Core ledger implementation - stack of 3 PRs so far: #1859, #1860, #1861
      • 🔴 Start integrating it into existing customer balance transactions to prepare for running it as a shadow ledger
    • PostHog Code - remaining steps ahead of planned public beta launch (27.04)
      • 🟡 Billing page, usage and spend dashboards support
        • Billing page implemented by PostHog Code (I reviewed)
        • Usage and spend not a must for launch since billing page will have seats overview
      • ✅ Triggering credit top-ups or removals or limit resets on upgrades/downgrades
        • Clarified how it's going to work
    • 🔴 Logs pricing - 30 and 90 day retention
      • Will try to pick it up this sprint
    • 🔴 Investigate an issue with limits incorrectly toggling back after being removed (e.g. after free to paid upgrade)
      • Will try to pick it up this sprint
    • Other (not planned initially)
      • Revenue model / IWA fixes based in things flagged by Mine in #revenue-issues:
        • ✅ Use revenue recognition MRR for annual plan customers in org properties - #1831
        • ✅ Defensive timestamp parsing for IWA view and org properties - #1842
        • ✅ Handle unpaid invoices with applied customer balance - #1840
        • ✅ Stop applying credit discount after annual credits are exhausted - #1853
        • ✅ Annual invoices contribute 0 MRR, centralize monthly-period check - #1852
        • ✅ Matview instead of view for IWA forecast query - fixed slow IWA alert, forecast 773s → 0.35s - #1858
        • ✅ Perf: rewrite effective_credit_discount_pct as LANGUAGE sql - #1854
        • ✅ OOM fix in update_all_org_properties via iterator() - #1846
        • 🟡 Use invoice snapshot metadata for completed IWA rows - #1855
      • PostHog Code:
        • ✅ Post-merge fix for seat-based subscriptions (activate KeyError) - #1848
      • Org group properties / admin tooling:
        • ✅ Add billing_plan and startup_program_label as org group properties - #1844
        • ✅ Use MetadataKeys enum for startup plan period check - #1843
        • ✅ Align public API yc_merch_count max with frontend - #1856
      • Alerts / infra:
        • ✅ Increase Stripe Celery worker max replicas 2→4 - charts#9815
        • ✅ Investigated BillingUpstreamConnectFailure alerts - chronic HPA flapping on billing-web
        • ✅ Opt managed orgs into spike emails via feature flag - #1857
      • Docs / planning:
        • ✅ Updated billing team Q2 2026 objectives - posthog.com#16202
        • 🟡 Collections RFC - follow-up questions sent to vendors
      • Support & cross-team:
        • Covered support hero for Ele on Apr 10 - handled refund policy questions, Zendesk triage, sanctions guidance, ingestion filtering
        • Every.to partnership coordination with Cleo/Annika
        • Flagged platform addon reorder issue to platform-features team
      • Reviews: charts#10067 (HPA flapping), quotehog#356, quotehog#355, posthog#54697 (admin emails), posthog#54938 (pagination), posthog#54447 (Salesforce sync), posthog#53517 (Code seat billing UI), charts#10033 (duckgres), RFC#1011 (compute pricing), RFC#1070 (batch exports pricing), posthog#53001/billing#1832 (Stripe Shared Payment Tokens), billing#1834 (uninstall idempotency)

    @mcoll-posthog

    • Revenue Recognition Model - still ongoing, this is going to be the trend for some weeks
    • Fix admin emails not being properly updated to billing
    • Finish initial version of Stripe simulator
    • Write Antithesis RFC

    @abhischekt

    • ✅ build 2 Claygents to automate outbound pipeline for:
      • ✅ Stripe Propensity Leads
      • ✅ Warmbound Leads
    • 🟡 Create a Dashboard for Weekly leads checkin
    • ✅ Sync stripe_customer_id and billing_address to SFDC accounts
    • Unplanned side-quests:
      • ✅ QuoteHog bugs and perf improvements

    Q2 2026 Objectives

    ✅=finished 🟡=in progress 🔴=won't finish ⚪=not started

    1. Complete the transition to the new revenue model (eng lead: @mcoll-posthog , revops lead: @minekansu)

      • 🟡 Initial implementation
      • Discrepancy hunting and fixing - all understood and fixed or explicitly accepted
      • All internal dashboards re-implemented on the new model
      • Investor reporting migrated
      • Model understood and trusted across the team
        • Finance signs off on model documentation
        • Zero revops escalations for routine ARR/MRR questions for 4 weeks after launch
        • Bonus: self-serve (finance can pull monthly data they need to close the books without billing/revops in the loop)
      • Stretch goal: revenue model data flowing into Campfire

    2. Migrate all credits to an in-house ledger (lead: @pawel-cebula)

      • 🟡 Implement a double-entry credit ledger
      • Deploy and run the shadow ledger
      • Fix unexpected discrepancies
      • Migrate from customer balance to the ledger

    3. Ship all expected pricing launches and changes (lead: @pawel-cebula)

      • PostHog Code
        • 🟡 Seat-based subscriptions (free and paid)
        • Seat-based subscriptions (free and multiple paid)
        • Overages and background agents
      • Storage and compute
        • Data warehouse
        • Endpoints
      • Workflows
        • Channels: Push, SMS
        • Per-workflow limit exclusion
      • Batch exports
        • Higher frequency exports
      • Logs
        • 30 and 90 day retention

    4. Reduce tech debt and improve developer experience (lead: @mcoll-posthog)

      • Improve async task observability and reliability
      • Upgrade to PostgreSQL 17/18
      • Switch from Nginx to Granian

    5. Complete the Salesforce org object rollout (lead: @abhischekt)

      • Deploy deduplication workflow and scripts to production
      • Complete historical migration to custom org object
      • Migrate all integrations and lead triggers to new object
      • Confirm Vitally and Salesforce sync works under the new setup
      • Document all scripts and workflows in PostHog-owned GitHub repo

    6. Build customer health score v1 in Vitally (lead: @minekansu)

      • Define "active user" per product
      • Define org-level "active customer" rollup logic
      • Validate definitions against known accounts (healthy, churned, at-risk)
      • Implement health scores in Vitally

    7. Implement fully automated outbound pipelines (lead: @abhischekt )

      • Source and score additional leads (LinkedIn followers, Appfigures.com targets, Stripe Propensity Leads)
      • Generate outbound sequence content using LLM in Clay
      • Sequence highest scoring targets automatically using Lemlist

    This sprint

    @minekansu

    • MIS 2Q26 update
    • techstars workshop
    • weekly revenue updates
    • active user and org for product analytics, session replay, flags
    • set up contract setup rotation
    • sales hiring model scenario for layered coverage

    @pawel-cebula

    • In-house credit ledger
      • Core ledger implementation
      • Integrate it into existing customer balance transactions to prepare for running it as a shadow ledger
      • Start running shadow ledger
        - Ambitious given integration scope and likely PostHog Code launch during this sprint
    • PostHog Code - remaining steps ahead of planned public beta launch
      • Add billing period and plan details to seats APIs
      • Usage and spend dashboards support
    • Logs pricing - 30 and 90 day retention
    • Investigate an issue with limits incorrectly toggling back after being removed (e.g. after free to paid upgrade)

    @mcoll-posthog

    • Revrec baseline and revenue discrepancies reduction
      • Improved ledger explorer
    • S3 parquet export
    • Admin email backfill

    @abhischekt

    Time off:

  26. marandaneto
    closed this as completedon May 4, 2026
  27. marandaneto
    unpinned this issue on May 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    sprintSprint planning

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions