Markets and business models
Usage metering and NRR
What you count is the business. Bad meters leak revenue or enrage customers, and usage NRR hides dollar churn inside retained logos.
Usage businesses live or die on what you count. Bad meters create revenue leakage (you underbill) or customer rage (you overbill). Design the billable event with finance and product together.
Seat SaaS NRR rises when seats and upsells grow. Usage NRR rises when surviving customers consume more. That is powerful in expansion markets and terrifying in contractions: the same logo can cut 40% of spend without "churning" in the CRM.
Concept
NRR (net revenue retention) asks whether dollars from last year's cohort grew or shrank, including expansion, contraction and churn. Logo retention asks only whether the account stayed. In usage businesses you must track both.
Meter design
- Idempotent events — retries must not double-charge.
- Clear unit definitions — "token," "message," "credit," "GB-month" need docs a customer CFO can audit.
- Latency of billing — daily vs monthly aggregation; disputes need raw event access for N days.
- Caps and alerts — spend alerts are a retention feature; surprise $50k invoices are a churn feature.
Product counters that are not billed (rate limits, quotas, soft limits) still need the same rigor — they are how you stop free-tier abuse from becoming a COGS spiral.
Expose a usage dashboard early. Customers who can forecast their bill expand more calmly than customers who fear the invoice. Transparency is a sales asset.
Walking through usage NRR
Starting usage revenue $1.0M/month across 200 accounts. Over 12 months: 10 logos leave (−$80k), surviving accounts grow usage +18% on their base.
Churned revenue ≈ $80k
Expansion ≈ 0.18 × ($1.0M − $80k) ≈ $165.6k
Ending ≈ 1000 − 80 + 165.6 = $1,085.6k
Rough NRR ≈ 1086 / 1000 ≈ 109%Same logo churn with −10% usage intensity on survivors flips you under 100% NRR fast. Usage intensity is the hidden churn.
Track three things: logo retention, revenue retention / NRR, and usage intensity (median vs p95). A healthy book often shows a power law: a minority of accounts drive most usage.
Engineers own metering correctness and cost observability per tenant. A missing user_id on a span is a margin bug.
Common mistakes
- Retries that double-charge. Idempotency is a billing feature.
- Watching logo retention only. Dollars can leave inside retained accounts.
- No spend alerts. Surprise invoices churn better customers than high list prices do.
Check yourself
$1.0M starting, $80k churned, +18% usage on survivors. Rough NRR?
About 109%. Ending ≈ $1,085.6k / $1,000k.
A logo stays and cuts usage 40%. Did they churn?
Not as a logo. As revenue, they did. That is why usage NRR and intensity matter.
Key takeaways
- The meter is the product. Idempotent events, clear units, caps and a dashboard.
- Usage NRR is consumption of survivors, not seat upsells.
- Track logos, dollars and intensity separately. Power-law whales dominate.
- Transparency (alerts, dashboards) is retention.
Further learning
SaaS Metrics 2.0 (David Skok)“If you cannot measure it, you cannot improve it” – Lord Kelvin This article is a comprehensive and detailed look at the key metrics that are needed to understand and optimize a SaaS business. It is a completely updat…For Entrepreneurs