MRR and churn differ between teams
Finance calculates revenue from invoices, while the growth team uses product or CRM status, so the metrics do not match.
Impact: Arguments about numbers replace decisions.
SaaS and subscription analytics
Unify Subscription, Product Usage and Billing Data for Reliable SaaS Metrics
SaaS metrics such as MRR, churn, retention and activation depend on billing, product and CRM data that are rarely aligned. We build a governed analytics layer so revenue, product and customer teams report the same numbers and can act on usage signals early.
The metrics problem
Two teams, two MRR figures
For a subscription business, the most important numbers are MRR, churn, retention and activation. These depend on billing data, product usage events and CRM records, which are held by different tools and updated at different times. Finance may report a different MRR from the growth team, and customer success often learns that an account is at risk only after the renewal date has passed.
We build an account-level layer with agreed definitions and reconciliation to billing totals. Usage trends are linked to renewal dates, which is the starting point for customer churn prediction and for machine learning models on subscription data. The governed data also supports the wider data warehousing and analytics work we deliver for growing software businesses.
Metrics that matter
MRR, retention and activation, defined once
Each measure is baselined before the project starts, so improvement is shown against your own starting point.
| Measure | How it is calculated | Why it matters |
|---|---|---|
| MRR reconciliation gap | Difference between analytics MRR and billing totals, each period | Shows whether revenue reporting can be trusted |
| Gross and net revenue retention | Retained and expanded revenue as a share of starting revenue, by cohort | Shows the health of the existing customer base |
| Churn flagged in advance | Share of churned revenue that was flagged as at risk before renewal | Shows whether the early-warning view works |
| Activation rate | Share of new accounts reaching the agreed activation event within a set period | Shows the effect of onboarding changes |
| Dashboard breakage | Number of dashboards affected by schema changes without warning | Shows whether change control is effective |
Account-level design
Subscriptions, plans and usage in one account model
Ingestion
Scheduled loads from billing and CRM, and event streams or frequent batches from product analytics.
Storage and modelling
An account-level model with subscription history, plan changes and usage aggregates, versioned for schema changes.
Calculations
MRR, churn, retention and activation definitions implemented once, with reconciliation to billing totals.
Serving
Executive metrics, cohort analysis for product teams, and renewal-risk views for customer success.
Where numbers disagree
Problems that undermine trust in SaaS metrics
Product usage is not linked to revenue
Event data is stored separately from accounts and plans, so usage cannot be compared with renewal risk.
Impact: Churn is noticed after the customer has left.
Cohort analysis is slow
Retention cohorts need manual joins between billing and product tables.
Impact: Pricing and onboarding changes are assessed too slowly.
Data model changes break dashboards
New plans, tracking events or billing providers change the data, and reports stop working without warning.
Impact: Loss of confidence in the analytics team.
Source systems
Billing, product and CRM data brought together
We confirm what each system exposes, how often it can be refreshed and who owns the data, before the design is final.
Billing platform
Subscriptions, invoices, plans and payments
Product analytics events
Feature use, sessions and activation events
CRM
Accounts, owners, deals and support context
Support tools
Tickets and satisfaction data
Finance and ERP
Revenue recognition and cost data
Dashboards
Executive, product and customer success views
- Account-level subscription and usage data model
- Certified MRR, churn and retention dashboards
- Cohort and activation analysis
- Renewal-risk view combining usage and support signals
- Schema change monitoring to protect dashboards
Delivery
From definition workshop to monitored platform
Each phase ends with a defined output. Timelines are estimated after the assessment, once sources and scope are confirmed.
- 1
Metric and source audit
We review billing, product and CRM sources, and agree the definitions of MRR, churn, retention and activation with finance and product.
Output: Metric dictionary and source inventory
- 2
Account model design
We design the account-level model with subscription history, plan changes and usage aggregates, versioned for future change.
Output: Account data model
- 3
Pipeline and reconciliation
We build the billing, product and CRM loads, and set up reconciliation to billing totals each period.
Output: Pipelines and reconciliation checks
- 4
Dashboards and renewal views
We publish executive metrics, cohort analysis and renewal-risk views for customer success.
Output: Executive, product and customer success dashboards
- 5
Monitoring and change control
We monitor schema and data changes, and review metric definitions when plans or products change.
Output: Monitoring and change log
Change control
Schema changes that do not break dashboards
Controls are agreed for each project, based on the sensitivity of the data and the rules that apply to your organisation.
- Single definition of each SaaS metric, owned by a named team
- Reconciliation of revenue metrics to billing totals every period
- Access control for customer and pricing data
- Documentation of event tracking changes
- Retention rules for product event data
Illustrative scenario
Churn early-warning view: illustrative
This is an illustrative scenario, not a verified client result. Measured outcomes are shared only from real projects, with their baseline and method.
The challenge
A subscription business sees churn in monthly reports, but the product and customer success teams cannot see which accounts are losing usage before renewal.
The approach
- Join subscriptions, plan changes and product usage at account level
- Define a usage trend per account and a renewal window
- Publish a renewal-risk view to customer success
- Compare outcomes against the predicted risk each quarter
What we measure: Share of churned revenue that was flagged in advance, reconciliation gaps to billing, and time to build a cohort analysis. Measured against a baseline.
SaaS questions
SaaS and subscription analytics: FAQs
Which SaaS metrics do you define?+
Typically MRR, net revenue retention, gross churn, activation and cohort retention. We agree each definition with finance and product before building the dashboards.
Can you connect our billing platform and product analytics tool?+
Usually, through their APIs, exports or warehouse connectors. We confirm the options and refresh frequency during the assessment.
What happens when we change plans or tracking events?+
The data model is versioned and schema changes are monitored, so dashboards are flagged before they break rather than failing silently.
Can usage data predict churn?+
Usage trends can highlight accounts that need attention, but prediction quality depends on your data history. Any model is evaluated before it is used for decisions.
Can you help us agree one definition of churn?+
Yes. We run the definition workshop with finance, product and customer success, and document the result so it is applied the same way in every report.
What product analytics tools can you connect to?+
We connect through their exports, APIs or warehouse connectors where available. The options are confirmed during the assessment.
Find out where your reporting delays come from
A data platform assessment maps your systems, the reports that matter and the decisions they support, then gives you a practical first step.