Goals

Q4 2026 objectives

Make revenue reporting trustworthy

Theme: Finish reconciling discrepancies so we can use the new model for reporting and closing the books.

1. Finish the move to the new revenue model (lead: Marce Coll)

• Close out the remaining material discrepancies, fixing them or explicitly accepting them.
• Get Finance sign-off on the model.
• Work with Mine and Finance to move routine ARR/MRR and investor reporting onto the model, and get its data flowing into Campfire.

Make billing the source of truth

Theme: Own credits, products, prices, and subscription behavior so billing can support PostHog's needs with fewer constraints from external providers.

2. Migrate all credits to the in-house ledger (lead: Pawel Cebula)

• Seed credit pools from the new revenue model and reconcile them with customer balances. Fix or explicitly accept differences before cutover.
• Move all credits onto live ledger, applying promotional credits through discounts and prepurchased credits through customer balance, with the correct tax treatment.
• Rebuild refunds around ledger transactions and ship the operational tooling needed to manage live credits.
• Integrate credit ledger transactions into the new revenue model so credit usage and refunds are reflected correctly in revenue reporting.

3. Make the new product catalog the source of truth for products and prices (lead: Roy Cohen)

• Build a catalog with at least parity with today's product and pricing setup, with requirements checked with the teams that need it.
• Sync the catalog to Stripe and integrate it wherever billing currently uses the old catalog.
• Run existing pricing configurations through it in production without changing customers' billing unexpectedly. Integration with existing subscriptions can ship before the new subscription engine is ready.

4. Run our own subscriptions in shadow mode for all Stripe subscriptions (lead: Daniel Snitkovskiy)

• Compare recurring billing, prorations, and invoice outcomes against Stripe for all subscriptions.
• Define a migration plan, whether and how old and new subscriptions can coexist, and the cutover criteria.

Make usage reporting and limiting accurate and near real time

Theme: Help PostHog and customers understand usage and control spend, with accurate reporting and limits that take effect in real time.

5. Make limiting correct and consistent (lead: Marce Coll)

• Put money-domain limiting into production.
• Keep limiting decisions in billing, with posthog consuming the resulting state through the new endpoint.

Rollout needs v2 or equivalent usage data to avoid a latency regression. Alex's reporting work supplies and improves that foundation. Real-time enforcement via counters is a separate objective under objective 6.

6. Ship real-time usage reporting and limiting (lead: Alexander Mays)

• Real-time usage reporting: Put the new usage feed into production and move reporting consumers to it. This also provides the usage-data foundation for Marce's money-domain limiting work.
• Migrate existing consumers and define how the old reporting path will be retired.
• Real-time limiting: Implement limit enforcement using Valkey counters and a new real-time usage service, and integrate it with the products that need it.
• Disambiguate caps, limits, allowances, and allocations.

Control abuse and unpaid usage

Theme: Prevent abuse across AI products, and automate restrictions and recovery for unpaid invoices.

7. Enable credit reservations for AI workloads (lead: Alexander Mays)

• Reserve eligible credit before AI work starts so concurrent jobs cannot spend the same reserved credit while usage counters catch up.
• Settle against actual usage and return unused or expired reservations to the available balance.

8. Automate collections enforcement and recovery (lead: Daniel Snitkovskiy)

• Ship collections automation to restrict access for unpaid invoices and restore it when payment status permits.
• Make decisions and actions inspectable, with the debugging and recovery support needed to explain and recover failed actions.

Make billing more reliable

Theme: Prevent, detect, and act on failures.

9. Detect and investigate billing failures before customers report them (lead: Roy Cohen)

• Add tracing across billing
• Add actionable alerts for critical failures

Handbook

What the Billing team does ... anything billing:

• Billing infrastructure
• Pricing & self-serve revenue (in collaboration with each product team)
• Revenue reporting
• Usage reports
• Quota limiting
• Usage and spend dashboards
• Limits and alerts