MRR is not revenue — and why that matters for your margin
MRR and revenue answer different questions. Why mixing them inflates gross margin, and how to use each one correctly in a SaaS dashboard.
October 2, 2026 · 1 min read
“We're at $40k MRR and spend $8k a month on infrastructure, so our margin is 80%.” It sounds right. It usually isn't.
Two different numbers
- MRR is the monthly value of active subscriptions — a snapshot of run-rate.
- Revenue is money actually earned in a period, net of refunds, disputes and tax.
Annual plans, refunds, failed payments, trials and usage-based charges all make them differ. Read more in Stripe revenue vs MRR.
Why it matters for margin
Costs are real money spent in a period. Comparing them with a run-rate mixes timeframes: a refund-heavy month or an annual-plan cohort makes the margin look better or worse than it was.
The rule
Use revenue for gross margin, and MRR for growth, churn and NRR. Keep both — they answer different questions.
Related
- Your AI feature is a cost line, not a feature flagEvery AI request has a price. How AI features quietly change SaaS gross margin, why the monthly invoice is too late, and what to measure daily instead.
- Stripe fees are part of your cost of goods soldPayment fees are often a SaaS company's third-largest cost after hosting and AI. How to account for Stripe fees in gross margin and estimate them per plan.
- Cloud credits are hiding your real gross marginStartup cloud credits make infrastructure look free until they expire. Why to exclude credits from COGS and plan for the margin you'll have without them.
See your real margin in five minutes.
Connect Stripe and your cost providers with read-only access. Free for two connections — no card required.