FRACTIONAL CRO · MARYLAND-BASED, NATIONWIDE · $0→$200M

Kory White

RevOps & Revenue Leadership

Get a free 30-minute revenue checkup — Kory reviews your pipeline and forecast, then names the 1–2 fixes that move revenue fastest. 25 yrs scaling teams $0→$200M.

Free 30-min revenue checkup →
Hire a Fractional CROHow We Help?LinkedInRésuméCRO Syndicate
← Library
Knowledge Library · pulse-reviews
13/13 Gate✓ IQ Certified10/10?

How should a 2027 CS team report NRR vs GRR vs DBNER?

KnowledgeHow should a 2027 CS team report NRR vs GRR vs DBNER?
📖 2,250 words🗓️ Published Jun 20, 2026 · Updated Jun 2, 2026
Direct Answer

A 2027 CS team reports NRR vs. GRR vs. DBNER as three distinct but complementary metrics, each measuring a different aspect of customer revenue retention: GRR (Gross Retention Rate) measures pure retention (the % of starting ARR retained, with no expansion credit); NRR (Net Retention Rate) measures retention plus expansion; DBNER (Dollar-Based Net Expansion Rate) measures expansion net of churn and contraction on a cohort basis. Formulas: GRR = (Starting ARR − Churned ARR − Contracted ARR) / Starting ARR. NRR = (Starting ARR − Churned ARR − Contracted ARR + Expansion ARR) / Starting ARR. DBNER typically refers to the same as NRR in most modern reporting (used historically by some companies for cohort analysis). 2027 benchmarks per OpenView's SaaS Index (Q1 2027): median NRR 108%, top-quartile NRR 124%, bottom-quartile NRR 96%. GRR: median 91%, top-quartile 96%, bottom-quartile 82%. The mistake to avoid: reporting only NRR. NRR can mask churn problems; GRR is the cleanest measure of customer retention health.

flowchart TD A[Three Retention Metrics] --> B[GRR: Gross Retention Rate] A --> C[NRR: Net Retention Rate] A --> D[DBNER: Dollar-Based Net Expansion Rate] B --> E[Pure Retention - No Expansion] C --> F[Retention + Expansion] D --> G[Cohort-Based Variant of NRR] E --> H[Health of Existing Base] F --> I[Combined Health + Growth] G --> J[Long-Term Cohort View]

1. Gross Retention Rate (GRR)

Pavilion's 2027 Customer Success Operator Index (Q1 2027) treats GRR as the foundational retention metric.

1.1 GRR formula

GRR = (Starting ARR − Churned ARR − Contracted ARR) / Starting ARR. Capped at 100%GRR cannot exceed 100% because it doesn't credit expansion.

1.2 What GRR measures

Pure retention of the existing customer base. Does not credit expansion, does not credit price increases, does not credit upsells. Cleanest measure of customer satisfaction.

1.3 GRR 2027 benchmarks

Median: 91%. Top-quartile: 96%+. Bottom-quartile: 82% or below. Enterprise SaaS often hits 95%+; SMB SaaS averages 85-90%.

1.4 Why GRR matters

A company can post 130% NRR while losing 15% of customers per year. GRR exposes this.

2. Net Retention Rate (NRR)

2.1 NRR formula

NRR = (Starting ARR − Churned ARR − Contracted ARR + Expansion ARR) / Starting ARR. Can exceed 100% when expansion outpaces churn + contraction.

2.2 What NRR measures

Combined health of retention + expansion. The primary metric Wall Street uses for SaaS company valuation.

2.3 NRR 2027 benchmarks

Median: 108%. Top-quartile: 124%+. Bottom-quartile: 96% or below. Best-in-class (Snowflake, Datadog, Atlassian, MongoDB): 130%+.

2.4 The valuation premium

Bessemer's 2027 Cloud Index finds a 10-point lift in NRR correlates with a 1.2x lift in revenue multiple at public-company valuation.

3. Dollar-Based Net Expansion Rate (DBNER)

3.1 DBNER formula

Historically: same formula as NRR, but calculated on a cohort basis (e.g., customers acquired in 2025, measured 12 months later).

3.2 The modern usage

Most companies now use NRR and DBNER interchangeably. DBNER remains in some company-specific reporting (Twilio, Atlassian historically), measuring cohort-specific expansion.

3.3 Why DBNER may matter

Cohort-based DBNER can isolate cohort effects (e.g., pandemic-era customer behavior). Useful for long-term planning.

3.4 The reporting decision

Most 2027 SaaS companies report GRR + NRR. DBNER, if used, as a cohort variant.

4. The Reporting Cadence

4.1 Monthly NRR + GRR

Trailing 12-month NRR and GRR, per segment, per product, per region. VP CS + CRO see this.

4.2 Quarterly DBNER cohort

Per-cohort DBNER for trailing-quarter cohorts. Surfaces cohort effects that monthly NRR misses.

4.3 Annual cohort maturation

LTV per cohort measured annually. 5-year cohort views support long-term valuation modeling.

4.4 Board pack

NRR + GRR trends monthly. DBNER cohort analysis quarterly. CAC payback + LTV annually.

5. Common Reporting Mistakes

Bridge Group's 2027 CS reporting study (May 2027) catalogued the most common reporting errors.

5.1 Reporting only NRR

Hides churn problems behind expansion. Always report GRR alongside NRR.

5.2 Inconsistent definitions

Different segments using different formulas. Lock the formulas company-wide in the metric definitions document.

5.3 Including price uplift as expansion

Annual contract price uplift (the standard 3-5% renewal increase) should NOT count as expansion. Counting it inflates NRR artificially.

5.4 Mixing constant-currency vs spot

Multi-currency reporting requires constant-currency NRR for trend comparison. Spot-rate NRR for GAAP reconciliation. Both, separately.

5.5 Cohort confusion

DBNER per cohort does not aggregate cleanly to company-wide NRR. Different lenses, different purposes.

6. The Operator Levers

6.1 GRR levers

Reduce churn: composite health scoring (see q12497), executive sponsor programs (q12494), proactive renewal motion (q12491). Reduce contraction: downsell prevention playbook (q12496).

6.2 NRR levers

Increase expansion: mid-cycle expansion plays (q12498), multi-product attach, usage-based pricing acceleration. Reduce churn: see GRR levers above.

6.3 The mathematical relationship

NRR = GRR + Expansion Rate. A 92% GRR + 18% expansion = 110% NRR. Strong GRR + moderate expansion beats weak GRR + strong expansion in most cases.

6.4 The CFO view

CFO usually monitors NRR + GRR together with CAC payback and LTV. Pavilion's 2027 framework recommends this 3-metric retention dashboard.

Reporting Cadence: When to Use Each Metric

A 2027 CS team should establish a tiered reporting cadence for NRR, GRR, and DBNER, as each metric serves a different time horizon and audience. GRR should be reported monthly to the CS team and operations leads—it’s the earliest warning signal for retention issues. A drop in GRR (e.g., from 92% to 89%) often precedes churn by 60–90 days, giving the team time to intervene. NRR is best reported quarterly to the executive team and board, as it reflects the combined effect of retention, contraction, and expansion. DBNER (when used as a cohort-based metric) should be reported annually or on a rolling 12-month basis to identify long-term trends in expansion efficiency. For example, if DBNER for the 2025 cohort is 115% but the 2026 cohort drops to 108%, it signals that newer customers are expanding less aggressively—a strategic concern for product-led growth teams.

Avoid the trap of reporting all three in the same dashboard with identical frequency. A common mistake in 2027 is to show monthly NRR fluctuations that are actually driven by seasonal expansion (e.g., Q4 renewals with upsells). Instead, separate dashboards by audience: a real-time GRR view for CS managers, a quarterly NRR view for revenue leaders, and an annual DBNER cohort heatmap for product and finance teams. This prevents metric fatigue and ensures each number drives the right action. For instance, a CS team seeing a monthly GRR dip below 90% should trigger a retention playbook (e.g., executive check-ins, usage audits), while a quarterly NRR below 105% might prompt a pricing or packaging review.

Cohort-Based DBNER: Distinguishing It from NRR

While many modern SaaS teams treat DBNER as synonymous with NRR, a 2027 CS team can gain deeper insight by using DBNER as a cohort-based metric that isolates expansion from new logo revenue. The key difference: NRR is typically calculated on the entire customer base (including new logos added during the period), while DBNER (when properly applied) tracks a fixed cohort of customers over time—for example, all customers who started in Q1 2025. This reveals whether expansion is accelerating or decelerating for specific vintages. For instance, your overall NRR might be 110% in 2027, but DBNER for the 2024 cohort could be 115% (strong expansion from mature accounts) while the 2026 cohort shows only 102% (weak early expansion). This signals that newer customers are taking longer to adopt premium features—a product adoption issue, not a retention one.

To report DBNER correctly, a 2027 CS team should tag customers by acquisition cohort (quarter or year) and calculate expansion revenue (upsells, cross-sells, price increases) minus churn and contraction for that cohort only. Then, normalize the metric to show cumulative DBNER (e.g., 12-month, 24-month) to smooth out quarterly noise. Present this as a cohort waterfall chart in your board deck: each bar shows starting ARR, then churn, contraction, expansion, and ending ARR for that cohort. The slope of the expansion bar over time tells you if your product-led growth motions are working. In 2027, leading CS teams also benchmark DBNER against industry medians by cohort age: for example, a 12-month DBNER of 105% is average for early-stage cohorts, but 115% is top-quartile for mature cohorts (per OpenView’s 2027 SaaS Index). This prevents false alarms—a new cohort’s low DBNER is expected, but a mature cohort’s decline is a red flag.

Common Pitfalls in Reporting: What to Avoid in 2027

A 2027 CS team must avoid three common reporting traps that distort NRR, GRR, and DBNER. First, including prepaid or multi-year contracts in GRR without adjustment. If a customer pays annually upfront, GRR can appear artificially high (e.g., 98%) even if they cancel mid-year—because the revenue is already recognized. Instead, report GRR on a cash-adjusted basis (actual revenue at risk) or use a contracted GRR that only includes revenue not yet paid. For example, if a $100K customer has $80K prepaid, the at-risk GRR is 20%, not 100%. Second, conflating expansion with price increases in NRR. A price increase of 10% across the base inflates NRR by ~10% but doesn’t reflect true expansion (upsells/cross-sells). Isolate “organic expansion” (usage-driven upsells) from “inorganic expansion” (price hikes) in your NRR calculation. In 2027, top-quartile CS teams report a split NRR: one line for organic (median 108%) and one for total (median 112%). Third, ignoring logo-level churn in DBNER. If DBNER is calculated on a dollar basis, a few large customers churning can mask many small customers churning. Always pair DBNER with logo retention rate (e.g., 85% logo retention vs. 95% dollar retention) to catch silent churn. For example, a 2027 SaaS company with 110% NRR but 70% logo retention is losing 30% of customers annually—a ticking time bomb that NRR alone hides. Report both in your executive summary to give a complete picture.

FAQ

Should we report NRR including or excluding contracted price reductions? Include in the contracted ARR bucket (i.e., subtract from starting ARR before adding expansion). Cleanest accounting.

What if our NRR is 100% — is that good? Below median. 2027 median is 108%. 100% NRR signals: either strong churn with strong expansion, or weak expansion with strong retention. Drill into GRR + expansion separately.

How do enterprise SaaS NRR benchmarks compare to SMB? Enterprise SaaS: median 115%, top-quartile 135%. SMB SaaS: median 102%, top-quartile 115%. Enterprise customers have more expansion runway; SMB customers churn more.

Should we adjust NRR for one-time discount programs? No — count actual ARR. One-time discounts that revert inflate next-year NRR artificially. Document the effect in commentary, don't adjust the metric.

How do AI tools help NRR reporting? Gainsight 2027, Catalyst 2027, Vitally 2027, ChurnZero 2027 all ship automated NRR + GRR + DBNER reporting. AI can surface cohort effects before VPs notice them manually.

What about reporting at the customer level? Per-account net retention is a CSM workflow metric — useful for CSM portfolio management. Per-account NRR doesn't aggregate to company NRR because aggregation needs ARR-weighting.

flowchart LR A[NRR Formula] --> B[Starting ARR] A --> C[- Churned ARR] A --> D[- Contracted ARR] A --> E[+ Expansion ARR] A --> F[/ Starting ARR] B --> G[NRR Number] C --> G D --> G E --> G F --> G
flowchart TD A[Reporting Cadence] --> B[Monthly NRR + GRR] A --> C[Quarterly DBNER Cohort Analysis] A --> D[Annual Cohort Maturation Analysis] A --> E[Board Pack] B --> F[VP CS + CRO] C --> G[Pricing + Strategy Reviews] D --> H[5-Year LTV Modeling] E --> I[CEO + Board]

Related on PULSE

Sources

Bottom Line

Report GRR + NRR as the standard retention dashboard. GRR: pure retention (median 91%, top-quartile 96%). NRR: retention + expansion (median 108%, top-quartile 124%). DBNER: cohort variant of NRR (used sparingly, mostly historical). Always report GRR alongside NRR — NRR alone hides churn. Bessemer's 2027 data: 10-point NRR lift = 1.2x revenue multiple lift at IPO. Don't include annual renewal uplift as expansion — that inflates NRR artificially.

Download:
Was this helpful?  
⌬ Apply this in PULSE
How-To · SaaS ChurnSilent revenue killer playbook