The seven SaaS metrics a finance leader should own outright.

VISIBILITY — JULY 24, 2026 —

A finance team at a Series B SaaS company opens its board deck and finds thirty-one metrics. Magic number, net dollar retention, logo churn, quick ratio, ARR per FTE, weighted pipeline coverage, expansion rate, contraction rate, gross churn, ARR waterfall by cohort. The list scrolls. Somewhere in that catalog are the SaaS metrics a finance leader should own outright — the five to seven that actually change a decision. The rest are decoration, generated because the dashboard has a slot for them.

The distinction matters because most of those metrics are never wrong in a way anyone can catch. They live in a spreadsheet that pulls from Salesforce, gets massaged in a tab nobody has opened since the last raise, and arrives on a slide with no path back to the general ledger. When the board asks a follow-up question, the answer is a reconciliation exercise that takes four days.

Ownership means something narrower and harder: the number the board sees is the number that ties to the books. It is generated off live data, not stitched together after the fact. This is the short list, organized by what it decides — growth, retention, efficiency — and where each one breaks when it lives in a separate file instead of alongside the ledger.

Growth: two numbers, not twelve

ARR / MRR

Annual and monthly recurring revenue are the base of the pyramid, and the most quietly mishandled. The problem is not the arithmetic. It is that ARR is a management metric with no GAAP definition, and recognized revenue is a GAAP figure with strict ASC 606 rules about when it hits the income statement. The two are computed differently, on purpose, and they will not tie.

Practitioners on r/FPandA surface this constantly: a controller books deferred revenue on a signed annual contract, an RevOps analyst reports ARR the day the deal closes, and the two numbers diverge by a full billing period. Neither is wrong. But if the finance leader cannot explain the gap in one sentence, the ARR number is not owned — it is borrowed from a system of record that finance does not control. The mechanics of that divergence, and how to keep both figures defensible, are worth reading in full: why ARR and recognized revenue never tie out.

What it decides: the growth rate the board underwrites the next plan against, and the top line every efficiency ratio below divides into.

Where it breaks: when ARR lives in a CRM export and recognized revenue lives in the accounting system, and no one reconciles them until the audit. The bookings-to-billings-to-revenue bridge is the single most common source of a restated board number.

Net revenue retention

Net revenue retention (NRR) measures what a cohort of customers is worth twelve months later — expansion and price increases minus contraction and churn, before any new logos. It is the closest thing SaaS has to a single measure of whether the product compounds.

The benchmark is public and stable. SaaS Capital puts median NRR for private B2B SaaS around 100%, with top-quartile companies clearing 110% or better; Bessemer Venture Partners treats sustained NRR above 120% as the mark of a best-in-class expansion motion. Below 100% and the business is leaking value it has to refill with sales spend every quarter.

What it decides: whether growth can come from the existing base or must be bought. An NRR of 118% means the company grows ~18% a year with zero new customers — that changes how much the board is willing to spend on new logo acquisition.

Where it breaks: NRR requires clean cohort tracking — same customers, same period, one year apart. When that calculation lives in a spreadsheet fed by a monthly CRM dump, cohort definitions drift, mid-period upgrades get double-counted, and the number the board sees in Q3 was computed on a different logic than Q1. The Visibility desk has covered how cohort drift compounds; the short version is that a retention number is only as trustworthy as the customer-level data feeding it.

Retention: the floor and the engine

NRR gets the attention because it can exceed 100%, which flatters the deck. But NRR alone hides the thing that kills companies.

Gross revenue retention

Gross revenue retention (GRR) strips out expansion entirely. It measures only what was kept — the same cohort, minus churn and contraction, with no credit for upsell. GRR is capped at 100% by definition. It is the floor.

The two numbers answer different questions, and a finance leader needs both. NRR of 115% looks healthy until you see it sits on a GRR of 78% — meaning nearly a quarter of the base is churning and a handful of large expansions are papering over it. That is a fragile business wearing a good number. SaaS Capital's benchmark data puts healthy GRR for private SaaS in the high 80s to low 90s; anything below the mid-80s is a churn problem masquerading as a growth story.

The relationship between the floor and the engine — why you report them as a pair and never one without the other — is the subject of gross vs net revenue retention: the floor and the engine.

What it decides: whether the retention story is durable or dependent on a few whales. GRR tells you what the business is worth if expansion stops.

Where it breaks: contraction is the hardest event to capture cleanly. A customer that downgrades from 50 seats to 30 is a partial loss that a logo-count churn metric misses entirely. If seat-level and dollar-level changes are not reconciled against actual billed amounts in the ledger, GRR overstates retention systematically — and always in the flattering direction.

Efficiency: four numbers that gate spending

Growth and retention describe the shape of the business. Efficiency describes whether it can afford itself. These four are where finance earns its seat, because they are the numbers that say stop or keep going.

CAC payback

Customer acquisition cost payback is the number of months of gross-margin-adjusted revenue it takes to earn back the cost of acquiring a customer. It is more actionable than the raw LTV:CAC ratio because it is measured in months, not a multiple — and cash comes back in months, not in lifetimes.

The durable benchmark: Bessemer's Atlas frames LTV:CAC in a healthy band of roughly 3:1 to 5:1, with CAC payback under 12 months for efficient early-stage companies and under 18 months for enterprise motions with longer sales cycles. Above 24 months, the company is financing its own growth on a credit card.

What it decides: whether to add sales capacity. If payback creeps from 14 to 22 months, hiring three more AEs makes the burn worse, not better.

Where it breaks: CAC is a fully-loaded number — sales and marketing salaries, commissions, tooling, allocated overhead. When it is calculated off a marketing spend figure that omits loaded headcount, payback looks artificially short. The only reliable version pulls actual S&M expense from the ledger, not a budget line from a plan.

Rule of 40

The Rule of 40 says a healthy SaaS company's revenue growth rate plus its profit margin should sum to at least 40%. A company growing 60% can afford to burn 20% of revenue; a company growing 15% needs to run at 25% margin to clear the bar. It is a single number that forces the growth-versus-profitability trade-off into the open.

The 40% threshold is the widely-cited standard, popularized by Brad Feld and now standard in McKinsey's and Bessemer's benchmark reporting. In the current environment, public-market investors weight the profitability half more heavily than they did in 2021.

Rule of 40 and CAC payback are best read together — one is the top-down health check, the other the bottom-up unit economics that explain it. When they disagree, that gap is diagnostic. The full method is in reading the Rule of 40 and CAC payback together.

What it decides: the fundamental posture — press growth or fix margin. It is the number a board uses to decide whether the next dollar goes into pipeline or into the bottom line.

Where it breaks: the margin half depends on which costs you count. Non-GAAP adjustments — stock comp, one-time items, capitalized R&D — swing the number by ten points. If the margin figure is not the same one the accounting team reports, Rule of 40 becomes a slide-deck artifact.

Gross margin

SaaS gross margin should sit in the 70–80% range; below 70% suggests the delivery model is closer to services than software, and the r/Accounting consensus is that the most common error is what gets classified as cost of revenue. Hosting and infrastructure belong in COGS. Customer success sometimes does and sometimes does not, depending on whether it is a cost center or an expansion engine. Where the line sits changes gross margin by several points, and it feeds directly into CAC payback and Rule of 40.

What it decides: every downstream efficiency ratio, and how much of each new dollar of revenue is actually available to fund growth.

Where it breaks: COGS classification is a ledger decision, not a spreadsheet one. When gross margin is computed in an FP&A model with its own cost mapping, and the accounting team maps the same costs differently, the two gross margins diverge and neither reconciles to the P&L.

Burn multiple

The burn multiple — coined by David Sacks — is net burn divided by net new ARR. It answers one question: how many dollars did you burn to add a dollar of recurring revenue. Under 1x is excellent, 1x–1.5x is good, 1.5x–2x is acceptable in a growth phase, and above 2x is a warning. It cuts through the growth-rate story because it prices the growth.

What it decides: runway and the timing of the next raise. A burn multiple sliding from 1.3x to 2.1x means the company is buying growth at twice the price it was — and the runway math the board is using is already wrong.

Where it breaks: it needs live cash burn and live net new ARR in the same period. When burn comes from the accounting close (three weeks late) and net new ARR comes from the CRM (real-time but unreconciled), the ratio is built from two numbers measured on different clocks. The Tools & Tech desk has noted the same failure across metric stacks: the inputs are individually fine and jointly meaningless.

Ownership is a data problem before it is a metric problem

The pattern across all seven is the same. Each metric has a defensible definition and a public benchmark. None of them breaks because the finance leader picked the wrong formula. They break because the number that reaches the board was assembled in a spreadsheet that sits downstream of the ledger, reconciled — if at all — long after the decision it informed was already made.

That is the real content of ownership. Not that finance chose the metric, but that finance can tie it to the books on demand, from live data, without a four-day reconciliation exercise. The board question that used to trigger a fire drill — why is ARR up but revenue flat — becomes a one-sentence answer because the two numbers were never allowed to drift in the first place. Practitioner threads on r/FPandA return to this repeatedly: the teams that lose credibility are not the ones with the wrong metrics, but the ones who cannot explain the gap between their metric and their financials when asked live.

A static dashboard refreshed monthly cannot deliver that, because the gap between the metric and the ledger is baked in the moment the export runs. The alternative is not a prettier dashboard — it is putting the metrics on the same live data as the books, so the number the board sees and the number in the general ledger are the same number, measured on the same clock. For teams working through what that looks like in practice, a growing number are wiring their SaaS metrics directly to the ledger rather than to a monthly export → — and the Operations desk has tracked the workflow shifts that follow.

Seven metrics. Each one changes a decision. Each one is only worth reporting if it ties to the books. Everything else on the dashboard is context — useful, occasionally, but not something a finance leader should be answering for at the board table.

■