# Building the metrics layer: one source of truth for ARRARRAnnual Recurring Revenue (ARR) is the normalized, predictable revenue a subscription business expects to earn from active contracts over a single year.View full definition →, NRRNRRNet Revenue Retention measures the percentage of recurring revenue retained and grown from existing customers over a period, including upsell and expansion, net of downgrades and churn.View full definition →, and activation
The quarterly business review starts, and the CFO's slide says MRR is $2.1M. The Head of Product's dashboard says $1.95M. The RevOps deck says $2.3M. Nobody is lying. Everyone is using a different definition.
This is the single most common data failure in SaaS companies, and it costs you more than embarrassment in meetings. It erodes trust in every number, slows decisions, and lets each team quietly pick whichever definition flatters their narrative.
The fix is not another dashboard. It is a metrics layer: a governed place where core business definitions live once, are agreed upon, and feed every tool downstream.
Let's autopsy the $2.1M vs $1.95M vs $2.3M problem. MRRMRRMonthly Recurring Revenue: the predictable, normalized monthly revenue from active subscriptions, the baseline metric for SaaS and subscription businesses.View full definition → (Monthly Recurring RevenueMonthly Recurring RevenueMonthly Recurring Revenue: the predictable, normalized monthly revenue from active subscriptions, the baseline metric for SaaS and subscription businesses.View full definition →) sounds simple: sum up recurring subscription revenue per month. The disagreements come from unglamorous edge cases.
Finance often builds from the billing system (Stripe, Chargebee, Zuora). Product builds from the app database. GTMGTMThe strategy defining how you'll launch a product: target segments, channels, value proposition and coordinated action plan.View full definition → builds from the CRMCRMCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.View full definition → (Salesforce, HubSpot). Three source systems, three sets of assumptions, three answers.
None of this gets solved by picking the "right" system. It gets solved by writing the definitions down and enforcing them.
A metrics layer (also called a semantic layer) is a centralized definition of your business metrics, decoupled from any single dashboard or report.
Instead of the MRRMRRMonthly Recurring Revenue: the predictable, normalized monthly revenue from active subscriptions, the baseline metric for SaaS and subscription businesses.View full definition → logic living inside a Tableau workbook, a Looker file, and three analysts' SQLSQLSales Qualified Lead: a prospect the sales team has validated as ready for direct outreach and a proposal, having passed clear qualification criteria.View full definition → queries, it lives in one governed place. Every tool queries that definition. Change it once, and it changes everywhere.
Think of it as the contract layer between raw data and the people asking questions. Raw tables sit below it. BIBITechnologies and processes that turn raw data into actionable insights via reporting, dashboards and analysis, so teams can decide based on facts rather than intuition.View full definition → tools, spreadsheets, and AI assistants sit above it. The semantic layer in the middle guarantees that "MRRMRRMonthly Recurring Revenue: the predictable, normalized monthly revenue from active subscriptions, the baseline metric for SaaS and subscription businesses.View full definition →" means the same thing no matter who asks.
Popular implementations in 2026 include dbt's semantic layer, Cube, and the metric definitions built into tools like Looker (LookML). The specific tool matters less than the discipline.
Three metrics generate the most cross-functional arguments. Here is how to pin them down.
ARR (Annual Recurring Revenue) is the annualized value of your recurring subscriptions. Usually ARRARRAnnual Recurring Revenue (ARR) is the normalized, predictable revenue a subscription business expects to earn from active contracts over a single year.View full definition → = MRRMRRMonthly Recurring Revenue: the predictable, normalized monthly revenue from active subscriptions, the baseline metric for SaaS and subscription businesses.View full definition → x 12, but only if MRRMRRMonthly Recurring Revenue: the predictable, normalized monthly revenue from active subscriptions, the baseline metric for SaaS and subscription businesses.View full definition → is defined cleanly first.
Decisions you must write down:
NRR (Net Revenue Retention) measures how much recurring revenue you keep and grow from existing customers, ignoring new logos. It is one of the most watched SaaS metrics because it reflects whether your product gets more valuable over time.
The standard formula:
NRR = (Starting ARR + Expansion - Contraction - Churn) / Starting ARRWhere, for a fixed cohort measured over a period:
NRRNRRNet Revenue Retention measures the percentage of recurring revenue retained and grown from existing customers over a period, including upsell and expansion, net of downgrades and churn.View full definition → above 100% means your existing base grows even before you add new customers. That is the SaaS growth engine.
The fights here are about the cohort. Which customers? Measured over what window? Does a customer who churned then came back count? Investor benchmarks for NRRNRRNet Revenue Retention measures the percentage of recurring revenue retained and grown from existing customers over a period, including upsell and expansion, net of downgrades and churn.View full definition → are widely discussed; SaaS Capital publishes regularly updated retention research if you want an external reference point rather than a number pulled from thin air.
Activation is the moment a new user or account reaches first real value, sometimes called the "aha moment." Unlike ARRARRAnnual Recurring Revenue (ARR) is the normalized, predictable revenue a subscription business expects to earn from active contracts over a single year.View full definition → and NRRNRRNet Revenue Retention measures the percentage of recurring revenue retained and grown from existing customers over a period, including upsell and expansion, net of downgrades and churn.View full definition →, there is no universal formula. You have to define it for your product.
Examples of concrete activation definitions:
The rule: activation must be a specific, measurable event or set of events with a time window. "User seems engaged" is not a definition. "Completed onboarding step 4 within 14 days of signup" is.
Activation matters because it predicts retention. Users who activate stick around; users who never reachreachThe number of unique people exposed to your message in a given period. Unlike impressions, reach counts each person once, no matter how often they see it.View full definition → value churn. Getting product, growth, and data to agree on one activation definition is often harder than agreeing on MRRMRRMonthly Recurring Revenue: the predictable, normalized monthly revenue from active subscriptions, the baseline metric for SaaS and subscription businesses.View full definition →, because it feels subjective. Write it down anyway.
A metrics layer is only as good as the process that keeps it honest.
One owner per metric. Every core metric needs a named accountable owner, usually someone in finance or analytics for revenue metrics, product for activation. They approve changes.
Version the definitions. Metric logic should live in code, in version control (Git), so every change is reviewed and dated. When someone asks "why did NRRNRRNet Revenue Retention measures the percentage of recurring revenue retained and grown from existing customers over a period, including upsell and expansion, net of downgrades and churn.View full definition → jump in Q2," you can point to a specific definition change, not a mystery.
Certify the outputs. Mark governed metrics as "certified" in your BIBITechnologies and processes that turn raw data into actionable insights via reporting, dashboards and analysis, so teams can decide based on facts rather than intuition.View full definition → tool so users know which numbers are blessed and which are someone's experiment.
Document the edge cases in plain language. A non-technical VPVPA clear statement of the benefits your product delivers, the problems it solves and why customers should choose you over alternatives.View full definition → should be able to read "MRRMRRMonthly Recurring Revenue: the predictable, normalized monthly revenue from active subscriptions, the baseline metric for SaaS and subscription businesses.View full definition → excludes professional services and uses net contracted value" without opening SQLSQLSales Qualified Lead: a prospect the sales team has validated as ready for direct outreach and a proposal, having passed clear qualification criteria.View full definition →.
🎬 [VIDEO: "The Semantic Layer Explained" — youtube.com — a clear walkthrough of how semantic layers centralize metric definitions across BIBITechnologies and processes that turn raw data into actionable insights via reporting, dashboards and analysis, so teams can decide based on facts rather than intuition.View full definition → tools]
Knowledge check
1. According to the lesson, what is the root cause of three teams reporting different MRR figures for the same period?
2. Why does the lesson argue that adding another dashboard will NOT fix the conflicting-metrics problem?
3. What is the core purpose of a metrics (semantic) layer as described in the lesson?
4. Select ALL correct answers. Which of the following are edge cases the lesson identifies as sources of MRR disagreement?
Select all the correct answers.
5. Select ALL correct answers. What consequences does the lesson attribute to inconsistent metric definitions across teams?
Select all the correct answers.
Here is what a governed metric definition looks like in practice, using a dbt-style semantic layer. The point is not the syntax; it is that the logic exists once, readably, in one place.
metrics:
- name: mrr
label: "Monthly Recurring Revenue"
description: >
Net recurring subscription revenue, normalized to monthly.
Excludes one-time fees, professional services, and usage overage.
type: sum
sql: net_monthly_recurring_amount
filters:
- "revenue_type = 'recurring'"
- "subscription_status = 'active'"Now every dashboard, every export, and every AI query that asks for MRRMRRMonthly Recurring Revenue: the predictable, normalized monthly revenue from active subscriptions, the baseline metric for SaaS and subscription businesses.View full definition → resolves to this. The CFO, the Head of Product, and RevOps get the same $2.1M, because they are all pulling from the same definition.
You do not need to boil the ocean. A practical sequence:
1. Pick the five metrics that cause the most arguments. Usually MRRMRRMonthly Recurring Revenue: the predictable, normalized monthly revenue from active subscriptions, the baseline metric for SaaS and subscription businesses.View full definition →, ARRARRAnnual Recurring Revenue (ARR) is the normalized, predictable revenue a subscription business expects to earn from active contracts over a single year.View full definition →, NRRNRRNet Revenue Retention measures the percentage of recurring revenue retained and grown from existing customers over a period, including upsell and expansion, net of downgrades and churn.View full definition →, gross churn, and activation.
2. Convene the owners. Get finance, product, and GTMGTMThe strategy defining how you'll launch a product: target segments, channels, value proposition and coordinated action plan.View full definition → in one room. Agree on each definition, including edge cases. This meeting is the real work.
3. Encode them once in your semantic layer or, if you have no tooling yet, in a single governed SQLSQLSales Qualified Lead: a prospect the sales team has validated as ready for direct outreach and a proposal, having passed clear qualification criteria.View full definition → model.
4. Point one dashboard at it as the certified source. Deprecate the conflicting ones.
5. Publish a plain-language data dictionary so anyone can look up what "active" means.
The hardest step is #2, and it is not technical. It is organizational. The metrics layer just makes the agreement permanent instead of relitigated every quarter.