The growth metrics dashboard: the 6 numbers you need to know every week

Most founders I speak with have a dashboard with 25 to 40 metrics. They rarely look at it. The best operators I know have six. They look at them every week and make decisions based on what they see. The difference is not that the first group is less sophisticated. It is that they made the mistake of building a reporting system instead of a decision-making system. A dashboard with 40 metrics is an archive. A dashboard with six is a tool.

Why fewer metrics is more

The cognitive problem with large dashboards is not that the data is wrong. It is that the human brain cannot hold 40 numbers in working memory, draw a trend across all of them simultaneously, and make a clear decision. When everything is tracked, nothing is prioritized. Teams that track too many metrics often end up in one of two failure modes: they spend their weekly review meeting discussing which metrics matter this week, or they skip the dashboard entirely and operate on gut feel, which defeats the purpose of having data at all.

What makes a good metric in a weekly executive context: it must be directly actionable. If a metric changes and you do not know what to do about it, it does not belong on the executive dashboard. It belongs in a diagnostic layer that you only consult when something triggers further investigation. A good metric is also trend-sensitive: it should move meaningfully within a week or two weeks if something in the business changes. A metric that only changes quarterly tells you nothing useful in a weekly review. And it must have a clear owner: one person who is accountable for its direction and who is responsible for explaining any significant deviation.

The difference between a metric and a KPI is worth clarifying. A metric is any measurable outcome. A KPI, a key performance indicator, is a metric that is directly tied to a strategic objective and has a defined target. Not all metrics should be KPIs. The six metrics in the weekly dashboard should all be KPIs: they have targets, owners, and thresholds that trigger a response.

The 6 metrics that belong in the weekly dashboard

1. Net New MRR

Net New MRR is the single most important weekly number for a growth-stage SaaS company. It is new MRR added from new customers, plus expansion MRR from existing customers, minus churned MRR and contraction MRR. It is the net direction of your revenue base in real time.

What to measure: the current month's net new MRR compared to the same period last month and last year. Track both the absolute number and whether you are on pace to hit your monthly MRR target given the days elapsed.

Who owns it: CEO or VP Sales, with input from CS on the churn and contraction components.

Threshold for action: if net new MRR in the first two weeks of a month is more than 20% below the pace required to hit the monthly target, that is a trigger for an immediate pipeline review and potentially an acceleration of outbound or renewal activity. Waiting until week four to discover a shortfall is too late to course-correct.

2. Pipeline Coverage

Pipeline Coverage is the ratio of total qualified pipeline to your revenue target for the current quarter. A standard benchmark is 3x to 4x: if your quarterly target is 500,000 euros, you need 1.5 to 2 million euros in qualified pipeline to have a high probability of hitting the number, given normal slippage and win rates.

What to measure: qualified pipeline divided by remaining quarterly target, updated weekly as deals close, are added, or are disqualified.

Who owns it: VP Sales or Revenue Operations.

Threshold for action: below 3x coverage with more than six weeks remaining in the quarter is a yellow flag. Below 2x is a red flag requiring immediate pipeline generation activity. Coverage above 5x may indicate that qualification standards are too loose and win rates are about to disappoint.

Pipeline Coverage and Pipeline Velocity are complementary. Coverage tells you whether there is enough volume. Velocity tells you whether the volume is converting fast enough.

3. NRR trailing 12 months

Net Revenue Retention on a trailing twelve-month basis shows you the health of your existing customer base. An NRR above 100% means existing customers are spending more this year than last year, even after accounting for churn. This is the most powerful signal that you have built a product customers genuinely want to expand.

What to measure: MRR from customers who were active twelve months ago, including any expansion and after subtracting churn and contraction, divided by what those same customers were paying twelve months ago.

Who owns it: VP Customer Success, with RevOps producing the calculation.

Threshold for action: NRR below 90% on a trailing twelve-month basis requires an immediate investigation into churn patterns and expansion motion. NRR above 110% is a strong signal to invest more in the existing customer base, potentially through dedicated expansion sales capacity. The article on Net Revenue Retention covers the full calculation methodology.

4. CAC Payback Period

CAC Payback Period measures how many months it takes to recover the cost of acquiring a new customer from that customer's gross margin contribution. It is the most direct measure of how efficiently you are deploying acquisition capital.

What to measure: total sales and marketing spend for the period divided by net new customers acquired, divided by the average monthly gross margin contribution per new customer. The result is months to payback.

Who owns it: CFO or VP Finance, with input from Sales and Marketing on the spend attribution.

Threshold for action: for a venture-backed growth company, a CAC Payback Period above 24 months is a signal that acquisition economics need review. The best-in-class SaaS companies in 2026 target under 12 months. If payback period is lengthening quarter-over-quarter, that is a trend that requires intervention before it compounds into a capital efficiency problem. The CAC Payback Period article covers the full calculation and common errors.

5. Burn Multiple

Burn Multiple is net burn divided by net new ARR. It tells you how many euros you burn for every euro of new recurring revenue. In 2026, a Burn Multiple below 1.5x is the standard for Series A companies. Above 2x requires explanation.

What to measure: net burn for the current month divided by net new ARR on an annualized basis for the same period. Track on a rolling three-month average to smooth out monthly volatility.

Who owns it: CEO or CFO.

Threshold for action: a Burn Multiple that has increased by more than 0.3x quarter-over-quarter without an explanation grounded in a deliberate investment decision is a warning signal. If Burn Multiple is rising because you hired ahead of growth, that is a planned investment. If it is rising because growth has slowed while burn stayed flat, that is a problem. The article on Burn Multiple and Rule of 40 covers the context and benchmarks in depth.

6. Win Rate

Win rate is the percentage of qualified opportunities that result in closed-won deals. It is the most direct measure of how effectively your sales team converts pipeline into revenue and it is the lever that has the most immediate impact on Pipeline Velocity.

What to measure: closed-won deals divided by all closed deals in the period, excluding no-decisions from the denominator. Track by segment, by rep, and by deal size tier to identify patterns.

Who owns it: VP Sales.

Threshold for action: a win rate drop of more than 5 percentage points over two consecutive months is a red flag. It can signal a competitive shift, a pricing problem, a product positioning issue, or a sales execution weakness. The response depends on root cause analysis. A win rate that drops immediately after a competitor launches a new feature has a different fix than a win rate that drops because your most effective rep left the company.

The dashboard architecture: three levels

The six metrics described above belong to the executive dashboard: the weekly view for founders, CEOs, and the senior leadership team. This is not the only dashboard you need, but it is the one that should drive the most important decisions.

Below the executive dashboard sits the team dashboard, which typically has 12 to 15 metrics reviewed daily or every two to three days. This layer includes metrics like MQL volume, SQL conversion rate, average deal size by segment, rep-level activity metrics, and customer health score distributions. These are operational metrics owned by team leads. They do not all belong in a board conversation, but they are the inputs that drive the six executive metrics.

The third level is the operational or diagnostic dashboard, which is consulted on demand when something in the executive or team dashboard triggers a deeper investigation. If NRR drops by 4 percentage points in a single month, you open the diagnostic layer and look at churn by cohort, by ICP segment, by product tier, and by tenure. This is where the 30-plus metrics that never made it to the executive dashboard live. They are accessible when needed, but they do not compete for attention during the weekly review.

How to build the dashboard

In HubSpot: the six metrics can be assembled using a combination of CRM reports and custom properties. Net New MRR requires either a deal revenue property connected to subscription data or an integration with billing software. Pipeline Coverage is a standard funnel report filtered to the current quarter. Win rate is a deal outcome report. NRR and CAC Payback Period typically require data from multiple systems and are best calculated in a RevOps layer before being pushed back into HubSpot as custom properties. Burn Multiple requires financial data that lives outside HubSpot entirely and is usually maintained in a spreadsheet or financial tool linked to the dashboard.

In Salesforce: use the dashboard builder to assemble report components for each metric. Salesforce's report type flexibility makes it possible to create most of these calculations natively, though NRR and Burn Multiple will again require external data inputs. The Einstein Analytics layer is useful for more complex trend visualizations if your team has the capacity to maintain it.

In spreadsheets: for pre-product-market-fit companies or companies below 1 million euros in ARR, a well-structured Google Sheet or Excel workbook with manual data inputs updated weekly is entirely adequate. The discipline of reviewing six numbers every week matters more than the sophistication of the tool that displays them. Start simple and add tooling as the data complexity justifies it.

External tools worth knowing: ChartMogul and Baremetrics are purpose-built for SaaS revenue metrics and handle NRR, MRR, churn, and ARR calculations automatically from billing data. Klipfolio and Databox are general dashboarding tools that can pull from multiple sources and display all six metrics on a single screen. The right choice depends on your data maturity and what systems you already have connected.

The weekly review: how it works

The weekly dashboard review is most effective as a fixed 30-minute meeting, same time every week, with a defined agenda. Ad hoc reviews when something looks interesting tend to collapse into data discussions without conclusions. A fixed cadence builds the habit of systematic decision-making.

Who should be in the room: the CEO or founder, VP Sales, and either the Head of RevOps or the CFO. Customer Success leadership joins when the NRR or churn components require discussion. Marketing joins when pipeline coverage is below target and the root cause involves pipeline generation rather than conversion. Keep the list short. More participants slows decision velocity without improving the quality of the decisions.

For each of the six metrics, the review should answer three questions: is the current value above or below target, is the trend improving or deteriorating, and what is the one action that would most move this metric in the right direction over the next two weeks? The third question is the most important. Without a concrete next action assigned to a specific owner, the review is a reporting session. With it, it becomes a decision session.

When a metric triggers an action, close the loop the following week: did the action happen, and did the metric respond? This feedback loop is what separates a dashboard that drives execution from a dashboard that documents it.

Common dashboard-building mistakes

Adding more metrics because someone asked for them is the most common way dashboards grow beyond usefulness. Every time a board member asks a question about a metric that is not on the dashboard, there is a temptation to add it. Resist this unless the metric meets the criteria for an executive dashboard metric: actionable, trend-sensitive, and owned. If it does not, it belongs in the diagnostic layer.

No owner per metric produces a dashboard that everyone looks at and nobody is responsible for. When NRR declines and the question is "whose problem is this?", the answer should be immediate and unambiguous. If it is not, you do not have a metrics problem, you have an accountability structure problem.

Metrics without historical trend are almost useless for decision-making. A single data point tells you a value. A trend across eight quarters tells you a direction. Direction is what enables decisions. Every metric on the executive dashboard should show at minimum four to six historical data points so that the current value can be interpreted in context.

A dashboard nobody opens is often the result of building the dashboard in a tool that requires a login, lacks mobile access, or takes too long to load. The best dashboard is the one that gets opened. If the weekly review meeting starts with someone sharing their screen and navigating a slow BI tool, consider whether a simpler format would produce more consistent engagement.

When to update the dashboard

The composition of the weekly dashboard should be reviewed at each major growth stage transition. Moving from seed to Series A, from Series A to Series B, or from founder-led sales to a team-led sales motion each changes the operational reality enough that some metrics become less relevant and others become more critical.

A metric loses its relevance when it becomes consistently above target with minimal variance. If your CAC Payback Period has been stable at 11 months for six consecutive quarters and there are no planned changes to your acquisition model, it does not need weekly review. Move it to the team layer and bring it back to the executive level only if something structural changes.

When the team grows and responsibilities shift, metric ownership may need to transfer. A Burn Multiple that was owned by the founder in the early stage may transfer to a CFO once that role exists. Win rate that was owned by the founder may transfer to a VP Sales. The ownership change should be explicit and documented, not assumed.

For the broader context of what these six metrics connect to, the article on startup growth metrics provides the foundational framework, while what is RevOps explains the operational infrastructure that makes reliable metric calculation possible at scale.