Skip to main content
Gruv Logo
Revenue Analytics

Revenue movement without stitching reports.

Track subscription changes over time, explain MRR movement, monitor churn and recovery, and export to finance, billing, and growth.

MRR movementCohort viewsExportable reports
Revenue · last 12 monthsUpdated · 2m ago
MRR
$682k
+14.2%
ARR
$8.18M
+62.8% YoY
Net retention
113.4%
+3.2pp
NDJFMAMJJASO

How it works

Where subscription reporting breaks.

MRR movement is hard to explain

Teams separate new, expansion, contraction, churned, and recovered revenue manually every cycle.

Churn and recovery split

When failed-payment and churn are not in the same model, teams cannot distinguish voluntary from recoverable.

Growth and finance disagree

Cohorts, daily changes, and exports diverge when every team uses a different source of truth.

Ops and finance disconnected

Billing needs near-term status. Finance needs structured exports and explanations that hold up later.

Analytics around movement, churn, and exports

Turn subscription changes into reporting surfaces for billing, growth, and finance. Better explanations of what changed and why.

  • MRR movement classification

    Break recurring revenue into new, expansion, contraction, churned, and related states.

  • Cohort and retention

    How subscriber groups behave over time. Compare retention and monetization patterns.

  • Churn and recovery

    Separate voluntary churn from failed-payment recovery so problems do not blend.

Analytics around movement, churn, and **exports**
Capabilities

What analytics teams need

MRR tracking

Explain how recurring revenue grows, shrinks, or recovers.

Cohort analysis

Compare retention and monetization across groups.

Churn metrics

Separate voluntary loss from recovery and payment churn.

Operational change views

Daily subscription movement billing and growth act on.

Exports and custom reports

Push metrics into recurring reports or downstream systems.

How it works

From events to decision-ready reporting

Subscription metrics record

A subscription team can review cohort revenue, expansion, contraction, support context, and finance-ready metrics from the same operating record.

Subscription metrics record

Frequently Asked Questions

How is MRR calculated?+
Active subscription value normalized to a monthly view, then classified by movement state. Consistency matters more than the formula.
Can I export analytics data?+
Yes. Reporting is most useful when teams move it into recurring reports, finance, or their own systems. Path depends on rollout.
What cohort views are available?+
Compare retention, monetization, or lifecycle by signup period, plan, channel, or region. The cuts depend on what teams are asking.
Can analytics connect to finance and billing?+
Yes. Revenue analytics is most useful when it connects back to billing outcomes and invoice activity, not as a disconnected dashboard.
How does Gruv AI fit into this feature?+
Gruv AI runs payout automation, compliance gates, exception handling, and an Ask Gruv AI workspace across every product. Each feature inherits the same AI surface, so rules, holds, and reconciliation context stay consistent across the workflow.
Can I start with this feature and add more later?+
Yes. Gruv is modular, you can start with a single workflow and expand to additional modules as your requirements grow.
How do integrations work?+
Integrate via APIs and webhooks, or start with file imports/exports for a fast evaluation. Email ingestion can help with lightweight backfills when needed.
What affects coverage, methods, and timelines?+
Coverage, methods, and timelines vary by market and are subject to compliance and policy checks. Confirm your target corridors and payout methods during evaluation.
Is this tax or legal advice?+
No. Tax and compliance features vary by jurisdiction and customer configuration. This content is for informational purposes and is not tax or legal advice.

Put revenue data to work.

Track subscription changes over time, explain MRR movement, monitor churn and recovery, and export to finance, billing, and growth.

Many teams start with a narrow launch in weeks; timelines depend on scope and integrations.