SaaS metrics dashboard: what to track and how to build one.
It works fine at $50,000 in MRR with forty customers. It works less fine at $200,000, with three price changes and a discount someone approved in a sales call six weeks ago.
Almost every subscription business tracks its numbers in a spreadsheet first. Someone pulls charges from Stripe, pastes them into a tab, and builds a formula for MRR. It works fine at $50,000 in monthly recurring revenue with forty customers. It works less fine at $200,000 with a mix of monthly and annual plans, three price changes, three churned accounts, two upgrades, and a discount someone approved in a sales call six weeks ago. By the time a board meeting or an investor update is due, the person who owns that spreadsheet is reconciling numbers instead of explaining them.
Quick answer
A SaaS metrics dashboard should track five things at minimum: monthly recurring revenue (MRR) broken into its new, expansion, contraction, and churned components, annual recurring revenue (ARR), net revenue retention (NRR), gross revenue retention (GRR) or logo churn, and cash collected versus revenue recognized. The dashboard is only as reliable as the billing data feeding it, which is why most spreadsheet and generic BI versions drift out of sync with what actually happened in the billing system.
What a SaaS metrics dashboard actually needs to do
A metrics dashboard is not a reporting nicety, it is the mechanism a founder or RevOps lead uses to answer three recurring questions: is revenue actually growing or just top-line bookings, where is that growth coming from, and how much of it is at risk. Those three questions map almost directly to MRR, MRR movements, and retention. A dashboard that only shows a single top-line revenue number answers none of them well, because a business can hit its revenue target for a month while quietly losing more existing customers than it's replacing, and a single number won't show that.
The distinction matters most at the moment a company moves from being small enough that one person can hold the whole picture in their head to large enough that they can't. That transition tends to happen well before $1M in ARR, and it is exactly when spreadsheet-based tracking starts producing numbers that don't match what finance, the board, or a diligence process expects.
The core metrics a SaaS dashboard should include
MRR and its movements
Monthly recurring revenue is the baseline, but the single MRR number hides more than it reveals. ChartMogul, which tracks recurring revenue data across thousands of subscription businesses, breaks MRR into five components: new business MRR, expansion MRR, reactivation MRR, contraction MRR, and churned MRR. A business can show flat or growing headline MRR while expansion is quietly propping up a churn problem, and a dashboard that doesn't separate these movements will not surface that. This is a common blind spot behind what looks like a simple MRR reporting gap between what a spreadsheet shows and what the billing system actually processed.
ARR
Annual recurring revenue is simply MRR multiplied by twelve, used for board reporting, valuation conversations, and annual planning rather than day-to-day operating decisions. The two numbers serve different audiences: MRR for the operating team making weekly and monthly calls, ARR for external or forward-looking conversations. A dashboard that only shows ARR hides the month-to-month movement that actually explains why the number changed.
Net revenue retention (NRR)
NRR measures the percentage of recurring revenue retained from an existing customer base over a period, including expansion, and is calculated as (starting MRR plus expansion MRR, minus contraction MRR, minus churned MRR) divided by starting MRR. According to SaaS Capital's 2026 survey of more than 1,000 private B2B SaaS companies, bootstrapped companies with $3M to $20M in ARR reported a median NRR of 103%, with the 90th percentile reaching 117.9%. For context on how this figure actually accumulates or erodes over time and why small monthly differences compound, see how NRR compounds across a customer base.
Median net revenue retention among bootstrapped B2B SaaS companies with $3M to $20M in ARR, per SaaS Capital's 2026 survey of more than 1,000 companies.
Gross revenue retention (GRR) and logo churn
GRR strips out expansion and measures only what's retained from contraction and churn, calculated as (starting MRR minus contraction MRR minus churned MRR) divided by starting MRR. The same SaaS Capital survey put median GRR for bootstrapped companies in that ARR range at 91%. GRR and logo churn (the percentage of customers, not revenue, who cancel) matter because a business can have healthy NRR from a handful of large expansions while quietly losing smaller accounts every month, a pattern that a revenue-only view won't catch.
Cash collected versus revenue recognized
A dashboard limited to recurring revenue metrics misses the gap between what a business has billed, what it has actually collected, and what accounting recognizes as revenue in a given period. That gap widens with failed payments, dunning delays, and proration errors, and it is one of the more common reasons a subscription business's bank balance doesn't match its reported growth. The distinction between bookings, billings, and recognized revenue is worth understanding on its own before building a dashboard that conflates the three.
Why spreadsheets and generic BI dashboards break down at scale
None of the metrics above are hard to define. What breaks is the plumbing behind them. A spreadsheet MRR calculation depends on someone manually pulling and categorizing every new charge, cancellation, upgrade, downgrade, and proration, every month, without missing one. A generic BI tool connected to a data warehouse is more automated, but it is still only as accurate as the billing export feeding it, and most exports don't distinguish MRR movement types without custom logic someone has to build and maintain.
The result is a familiar failure mode: the dashboard is accurate the month it's built, and progressively less accurate every month after as pricing changes, new plan types, and edge cases in proration accumulate faster than anyone has time to update the underlying formulas. This is the same root problem behind a fragmented revenue stack, where billing lives in one tool, the CRM has a different customer count, and finance reconciles the two by hand before every board meeting.
Build vs. buy: what to evaluate
For a subscription business deciding whether to keep building this in spreadsheets, wire together a generic BI tool, or adopt a dedicated subscription analytics platform, the honest evaluation criteria are:
- Does it read directly from the billing system, or from a periodic export? A dashboard fed by a stale CSV export is only ever as current as the last import.
- Does it separate MRR movements automatically, or does someone have to categorize each transaction? Manual categorization is where spreadsheet dashboards quietly go wrong first.
- Does it handle the pricing models actually in use? Usage-based, tiered, and bundled pricing all affect MRR and proration differently, and a dashboard built for flat-rate subscriptions will misreport usage-based revenue.
- Can finance export the underlying data for close and audit? A dashboard that can't produce a clean CSV or Excel export for reconciliation just moves the manual work downstream instead of removing it.
- Does NRR and GRR calculate the same way every month? If the formula changes depending on who built it that quarter, the trend line isn't trustworthy.
Categories of tools that solve this
Subscription businesses generally land in one of a few categories once they outgrow a hand-built spreadsheet. Spreadsheet-native FP&A tools keep the familiar interface of Excel or Google Sheets while adding some automation on top, which lowers the learning curve but doesn't fully solve the manual-categorization problem. Standalone subscription analytics tools, such as Baremetrics or ChartMogul, connect directly to a billing provider and calculate MRR, NRR, and churn automatically, though they typically sit alongside a separate billing and CRM system rather than replacing them. Modular subscription intelligence platforms, a category that includes Revvly, combine the billing and pricing engine with the analytics layer directly, so the dashboard is reading from the same system that actually processes the charge, upgrade, or cancellation, rather than from a downstream export. Each category trades off differently between setup effort, cost, and how tightly the dashboard stays synced to the billing source of truth, and the right one depends on how complex the pricing model already is and how much manual reconciliation the team is willing to keep doing.
The real cost of a dashboard nobody trusts
The quiet cost of an unreliable metrics dashboard isn't the time spent rebuilding it every month, it's the decisions made on numbers that turn out to be wrong. A founder who thinks NRR is 105% when it's actually 95% is making hiring and fundraising decisions on a number that doesn't exist. A RevOps lead who can't separate expansion from new business can't tell whether the sales team or the existing customer base is driving growth, which makes it impossible to know where to invest the next quarter's effort. The dashboard's job isn't to look good in a board deck, it's to be the thing everyone in the company actually believes when they open it.
Frequently asked questions
What should a SaaS metrics dashboard include at minimum?
At minimum, it should show MRR broken into new, expansion, contraction, and churned components, ARR, NRR, GRR or logo churn, and the gap between billed and collected revenue. A single top-line revenue number without these components hides where growth or risk is coming from.
What is the difference between MRR and ARR?
MRR is monthly recurring revenue, the operating metric used for month-to-month decisions. ARR is MRR multiplied by twelve, used for board reporting, valuation, and annual planning. They describe the same underlying revenue at different time scales.
What is a good NRR for a SaaS company?
It depends heavily on company stage and segment. SaaS Capital's 2026 survey found a median NRR of 103% among bootstrapped companies with $3M to $20M in ARR, with top performers reaching 117.9%. Enterprise-focused companies with larger deal sizes typically report higher medians than SMB-focused ones.
Can a spreadsheet handle SaaS metrics tracking?
A spreadsheet can handle it at very early stages with simple, flat-rate pricing and few customers. It becomes unreliable once a business introduces usage-based or tiered pricing, multiple billing cycles, or enough transaction volume that manual categorization of MRR movements can't keep up without errors.
Why do NRR and GRR both matter if they're related?
NRR includes expansion revenue, so it can look healthy even while a business is losing individual customers, as long as the remaining accounts are expanding enough to offset that loss. GRR excludes expansion and shows the retention picture without that offset, which is why tracking both prevents either number from telling a misleading story on its own.
How often should a SaaS metrics dashboard update?
It should reflect billing activity in near real time, or at minimum daily, rather than being rebuilt monthly from an export. Metrics that are only as current as the last manual pull tend to be stale by the time they inform a decision.
Does a metrics dashboard replace the need for accounting close?
No. A metrics dashboard tracks operating metrics like MRR and NRR for day-to-day decisions; it doesn't replace the accounting close process that reconciles billed, collected, and recognized revenue for financial statements. The two should be consistent with each other, but they serve different purposes.
Alain spent a decade building and scaling subscription businesses before founding Revvly. He writes about the infrastructure gap between what SaaS companies report and what they actually earn.