What problem does it solve?
Revenue metrics like MRR, ARR, churn, and LTV are easy to compute inconsistently — raw Stripe tables require deferred-revenue recognition, currency conversion, and subscription logic that teams repeatedly re-derive and get wrong. This Skill provides canonical metric definitions and tested recipes so every model computes the same number.
Core Features & Use Cases
- Managed-view modeling on PostHog: Build HogQL views on the auto-generated
revenue_analytics_* views (revenue_item, mrr, customer, subscription, charge, product) fed by Stripe or custom revenue events, with currency handled via convertCurrency().
- dbt marts: Stage billing sources into
fct_revenue_item, fct_mrr, and dim_customer models with deferred-revenue recognition, a dense customer-month spine, and schema tests.
- Canonical metric definitions: Precise formulas for gross revenue, MRR, ARR, new/expansion/contraction/churn MRR, churn rate, ARPU, and LTV, plus the MRR movement bridge identity for validation.
- Use Case: A data analyst connects Stripe to PostHog and needs monthly MRR over time. The Skill explains that the managed
mrr view is only a live snapshot, then provides a HogQL recipe summing recurring revenue_item amounts per month, ready to materialize as a scheduled view.
Quick Start
Ask the assistant to build a monthly MRR and ARR model from your PostHog Stripe revenue data using the managed revenue_analytics views.