MRR Dashboard: 8 Metrics SaaS Teams Need (2026)

An MRR dashboard should tell you more than the size of your monthly recurring revenue. It should show what changed, why it changed, and which customers require action. A useful dashboard separates new, expansion, contraction, reactivation, and churned MRR instead of hiding every movement inside one headline number.

This guide gives you the eight metrics, formulas, layout, and data checks needed to build an MRR dashboard your founder, finance lead, and customer success team can use. You can build it from Stripe or another billing platform, but your application database is often the better source when plan status, usage, account ownership, or product activity also matters.

What is an MRR dashboard?

An MRR dashboard is a live view of predictable subscription revenue normalized to a monthly amount. It combines the current MRR balance with the movements that created it. For example, a company can finish the month at ₹10 lakh MRR while still having a serious retention problem if new sales are masking ₹2 lakh of churn.

The best dashboard answers three questions in under a minute: What is MRR now? How did it change during the period? Which accounts caused the change? If a chart cannot help answer one of those questions, it probably does not belong on the first screen.

Define MRR before you design the dashboard

Agree on one company-wide definition before building charts. MRR includes recurring subscription charges normalized to one month. A ₹120,000 annual subscription contributes ₹10,000 MRR. A ₹30,000 one-time onboarding fee contributes zero MRR. Discounts should reduce MRR for the period in which they apply.

Decide how to handle usage-based revenue. Include a committed recurring minimum when one exists. Treat variable overages separately unless your finance policy uses a trailing average. Whatever you choose, document it and apply it consistently; changing the definition silently makes trend lines useless.

Use subscription records as the operating source and paid or issued invoices as a reconciliation source. Payment dates alone can distort MRR because an annual prepayment is cash collected today for service delivered across twelve months.

The 8 metrics every MRR dashboard needs

1. Ending MRR

Ending MRR is the recurring monthly value of all active subscriptions on the final day of the period. It is the headline number, but never the whole story. Display it with the absolute and percentage change from the prior month.

Formula: ending MRR = beginning MRR + new MRR + expansion MRR + reactivation MRR − contraction MRR − churned MRR. That bridge must reconcile exactly; if it does not, fix the data before anyone uses the dashboard.

2. New MRR

New MRR is recurring revenue from customers who became paying customers during the period. Do not count upgrades from existing customers here. Keep new business separate so you can judge acquisition performance without confusing it with account growth.

3. Expansion MRR

Expansion MRR is additional recurring revenue from existing customers through upgrades, more seats, higher usage commitments, or add-ons. Track both the total and the accounts behind it. Expansion often reveals which product behaviours precede a larger contract.

4. Contraction MRR

Contraction MRR is recurring revenue lost when a customer remains active but downgrades. It is easy to miss because the logo did not churn. A rising contraction line can expose budget pressure, poor feature adoption, or packaging problems before cancellations rise.

5. Churned MRR

Churned MRR is recurring revenue lost from customers who cancel or fail to renew. Show voluntary and involuntary churn separately when possible. Failed payments need a billing recovery workflow; customers who deliberately leave need product, support, or positioning work.

6. Reactivation MRR

Reactivation MRR comes from previously churned customers who return. Keeping it separate prevents old accounts from inflating new-customer revenue and helps you measure whether win-back campaigns work. Define a minimum inactive period so a same-day billing correction is not mislabeled as reactivation.

7. Net new MRR

Net new MRR combines the movements into one change number: new + expansion + reactivation − contraction − churned MRR. MRR growth rate is net new MRR divided by beginning MRR, multiplied by 100. Show both because a ₹1 lakh gain means something different at ₹5 lakh MRR than at ₹1 crore MRR.

8. Net revenue retention

Net revenue retention, or NRR, measures how the starting customer base changed without counting new customers. Formula: (beginning MRR + expansion + reactivation − contraction − churned MRR) divided by beginning MRR, multiplied by 100.

An NRR above 100% means expansion and reactivation outweighed losses from the starting base. Pair NRR with gross revenue retention, which excludes expansion, when you need a stricter view of leakage.

A practical MRR dashboard layout

Keep the first screen executive-friendly and make account-level details available through filters or a second view. A sensible layout has four rows:

Use monthly reporting for board and finance reviews, but refresh the underlying dashboard daily. Daily refreshes let customer success and billing teams act on a downgrade, failed payment, or unusual account change while it is still recoverable.

How to build an MRR dashboard from your database

Step 1: Map the minimum data model

Start with customers, subscriptions, plans, subscription events, and invoices. You need stable customer and subscription IDs, start and end dates, billing interval, quantity, recurring price, currency, discount, and status. Add account owner and product-usage fields only after the revenue bridge reconciles.

Step 2: Create monthly subscription snapshots

Calculate each subscription's normalized MRR at the end of every reporting period. Snapshots make historical numbers reproducible even after a customer changes plan. Comparing consecutive snapshots lets you classify each account movement as new, expansion, contraction, reactivation, unchanged, or churned.

Step 3: Reconcile the MRR bridge

Check that beginning MRR plus all positive movements minus all negative movements equals ending MRR. Then compare the underlying contract values with your billing system and investigate differences. Test upgrades, downgrades, coupons, annual plans, pauses, refunds, currency conversion, and mid-month cancellations.

Step 4: Build views for decisions, not decoration

Create the four-row layout, then give each team a useful drill-down. Finance needs reconciliation and forecasts. Customer success needs upcoming renewals, contractions, and risk signals. Product needs plan and feature-usage segments. The metric definition stays shared even when the views differ.

Step 5: Add alerts tied to an owner

A dashboard explains what happened; an alert helps someone change the outcome. Trigger an email, Slack message, or webhook when a high-value account downgrades, a payment fails, NRR falls below your threshold, or projected churn exceeds the month's expansion. Every alert needs an owner and a next action.

Common MRR dashboard mistakes

Build it without becoming the reporting bottleneck

A spreadsheet works for an early snapshot, but manual exports break as plans and account movements multiply. A traditional BI tool can handle the model but may leave non-technical teams waiting for an analyst whenever the question changes. The right setup depends on whether you need a one-off report or a shared operating system.

With AI for Database, you connect your PostgreSQL, MySQL, Supabase, MongoDB, SQL Server, BigQuery, or another supported database and ask questions in plain English. You can turn the answers into a self-refreshing MRR dashboard, drill into the accounts behind a movement, and trigger emails, Slack messages, or webhooks when revenue conditions change.

Start with: 'Show ending MRR, new MRR, expansion, contraction, reactivation, churned MRR, net new MRR, and NRR by month for the last year.' Then validate the first two months against billing records. Once the bridge reconciles, save the view and add only the alerts your team will actually act on.

Questions teams ask about MRR dashboards

What should an MRR dashboard include?

Include ending MRR, new, expansion, contraction, churned and reactivation MRR, net new MRR, and NRR. Add account-level drill-downs so your team can explain every material movement.

How often should an MRR dashboard refresh?

Refresh it daily for operational use and lock monthly snapshots for finance and board reporting. Real-time refresh is rarely necessary; consistent definitions and reliable daily data matter more.

Can a non-technical team build an MRR dashboard without SQL?

Yes. A natural-language database tool can calculate the metrics and create live charts without requiring your operators to write SQL. An engineer or finance owner should still approve the initial MRR definition and reconciliation rules.

What is the most important chart on an MRR dashboard?

The MRR movement bridge is the most useful chart because it explains how beginning MRR became ending MRR. It shows whether growth came from new sales or expansion and whether contraction or churn is eroding it.

Turn the dashboard into a weekly operating habit

Review the MRR bridge weekly, assign owners to material losses, and examine definitions monthly. Your dashboard succeeds when a team can spot a change, find the accounts behind it, and act without waiting for a custom report.

Connect your database at aifordatabase.com, ask for the eight-metric view, and validate it against your billing total. Chalo, one trusted revenue dashboard is enough; you do not need another spreadsheet nobody owns.