94. SaaS Metrics

SaaS metrics are useful only when they describe real recurring value.

It is easy to make a SaaS company look healthier than it is. Count services as ARR. Ignore churn. Mix pilots with subscriptions. Celebrate booked revenue before collections. Use LTV before you have enough retention history. Average all customers together and hide the bad segment.

The purpose of SaaS metrics is not to impress investors. It is to understand whether customers repeatedly receive value, repeatedly pay, and can be acquired efficiently.

The SaaS metric system

A useful SaaS dashboard should answer five questions:

1. Are we adding recurring revenue?
2. Are existing customers staying?
3. Are existing customers expanding?
4. Are we acquiring customers efficiently?
5. Are margins and cash healthy enough to keep going?

If your dashboard does not answer these questions clearly, it is not yet a management system.

Revenue metrics

MRR

Monthly recurring revenue is the recurring revenue normalized to a monthly amount.

Example:

• Customer pays Rs 12,00,000 per year for a subscription
• Monthly recurring revenue = Rs 1,00,000

MRR should include recurring subscription revenue. Be careful with:

• One-time setup fees
• Custom development
• Hardware
• Taxes
• Refundable deposits
• Usage spikes that may not repeat
• Unpaid invoices

If you include non-recurring revenue in MRR, you will fool yourself first.

ARR

Annual recurring revenue is usually MRR x 12.

ARR is useful when contracts are annual or when the company wants a yearly view of recurring revenue. But ARR should not become a place to hide weak collection, services revenue, or one-time deals.

For Indian founders selling to enterprises, separate:

• Contracted ARR
• Invoiced ARR
• Collected ARR
• Live ARR

These are not the same. A signed contract that has not gone live and has not paid is a different risk from a customer actively using and paying.

New MRR

New MRR is recurring revenue from new customers added in the period.

Track it by:

• Segment
• Channel
• Geography
• Plan
• Sales motion
• Founder-led versus sales-led

This helps you see whether growth is coming from the customers you actually want.

Expansion MRR

Expansion MRR is additional recurring revenue from existing customers.

Expansion is often the strongest proof of value. Customers expand when the product becomes more important, reaches more users, handles more workflows, or enters more departments.

Track why expansion happened:

• More seats
• More usage
• Add-on module
• More locations
• Higher tier
• Cross-sell
• Annual upgrade

Expansion from a few large customers can hide weak growth elsewhere, so review by cohort and segment.

Contraction MRR

Contraction MRR is recurring revenue lost from existing customers who downgrade but do not fully churn.

Contraction is an early warning sign. Customers may reduce seats, usage, modules, or plan level before leaving completely.

Common reasons:

• Product not used deeply
• Budget cuts
• Champion left
• Feature gaps
• Poor onboarding
• Too much implementation effort
• Cheaper alternative

Treat contraction as a customer success signal, not only a finance line.

Churned MRR

Churned MRR is recurring revenue lost when customers cancel.

Do not only record that churn happened. Record why:

• No longer needs product
• Never activated
• Price too high
• Internal team changed
• Product unreliable
• Poor support
• Missing integration
• Competitor won
• Company shut down
• Payment failure

The reason matters because each reason has a different fix.

Net new MRR

Net new MRR combines the movement:

Net new MRR = New MRR + Expansion MRR - Contraction MRR - Churned MRR

This is one of the clearest monthly SaaS numbers. It shows whether the recurring revenue base is actually growing after losses.

Customer metrics

Logo churn

Logo churn measures the percentage of customers lost.

If you start the month with 100 customers and lose 5, logo churn is 5 percent for the month.

Logo churn is useful, but it treats all customers equally. Losing a tiny customer and losing your largest customer count the same. That is why you also need revenue churn.

Revenue churn

Revenue churn measures the revenue lost from existing customers.

Revenue churn is more important than logo churn when customer sizes vary widely.

If a company has many small customers and a few large enterprise customers, logo churn may look fine while revenue churn is dangerous.

Gross revenue retention

Gross revenue retention measures how much existing revenue remains before expansion.

It answers: if we ignore upsells, how much revenue did we keep?

GRR is a clean measure of customer retention quality. High expansion can mask poor GRR, so founders should watch both.

Net revenue retention

Net revenue retention includes expansion, contraction, and churn.

It answers: did the existing customer base grow or shrink after all movements?

NRR above 100 percent means existing customers expanded enough to offset contraction and churn. That is powerful because growth can come from the installed base, not only new acquisition.

ARPA

Average revenue per account shows average revenue per customer account.

Track ARPA by segment. Blended ARPA can mislead if you serve very different customers:

• Indian SMB
• Indian mid-market
• Indian enterprise
• US SMB
• Global enterprise
• Agency or reseller customers

Each segment may have different support costs, churn, expansion, and sales cycle.

CAC

Customer acquisition cost measures the cost of acquiring a customer.

Include:

• Paid ads
• Sales salaries and commissions
• Marketing salaries
• Tools
• Events
• Content and agency costs
• Founder sales time, at least as a separate view

Early CAC is often undercounted because founders do unpaid selling. Create two views:

• Cash CAC: actual cash spent
• Fully loaded CAC: includes team and founder effort

Both are useful. Cash CAC shows short-term survival. Fully loaded CAC shows whether the model can scale beyond founder heroics.

LTV

Lifetime value estimates the gross profit a customer produces over their lifetime.

Use LTV carefully. It is unreliable when:

• You have limited retention history
• Customer cohorts are small
• Pricing is changing
• Product is changing
• Churn is not stable
• Expansion is unpredictable

Instead of worshipping LTV, founders should inspect the ingredients:

• Retention
• Gross margin
• Expansion
• Support cost
• Implementation cost
• Payback

Payback

CAC payback measures how long it takes to recover acquisition cost from gross profit.

For cash-constrained startups, payback is often more actionable than LTV.

Example:

• CAC = Rs 60,000
• Monthly revenue = Rs 20,000
• Gross margin = 80 percent
• Monthly gross profit = Rs 16,000
• Payback = 3.75 months

But if the customer pays late, cash payback may be longer. Track both economic payback and cash payback when collections are slow.

Revenue movement waterfall

Every SaaS founder should be able to explain monthly revenue movement without hiding inside one top-line number.

Use a revenue waterfall:

Movement	Meaning
Starting MRR	Recurring revenue at the start of the period
New MRR	New customers added
Expansion MRR	Existing customers paying more
Contraction MRR	Existing customers paying less
Churned MRR	Existing customers cancelling
Ending MRR	Starting MRR plus all movements

This view forces clarity. A company can add new customers and still have weak net growth if churn and contraction are high. A company can have modest new sales and still grow well if expansion is strong. A founder who looks only at ending MRR misses the quality of the movement.

Add notes beside the waterfall:

• Which segment produced new MRR?
• Which customers expanded and why?
• Which customers contracted and why?
• Which churn was avoidable?
• Which revenue required custom work?
• Which revenue was booked but not collected?

The notes are as important as the number. They teach the company what kind of revenue to pursue.

Cohort retention board

SaaS health is hard to see in blended numbers. Cohorts make it visible.

Create a monthly cohort table:

Cohort	Customers started	Activated	Month 1 retained	Month 3 retained	Month 6 retained	Expansion	Churn reason
Jan	12	9	8	6	5	2 accounts	Slow setup, weak champion
Feb	15	13	11	9	-	3 accounts	Better onboarding

Review by segment and channel. If customers from founder referrals retain well but paid leads churn, the acquisition channel may be wrong. If enterprise customers retain but require heavy services, the model may be viable only at higher ACV. If SMB customers activate quickly but churn after the first month, value may be shallow.

Cohorts are uncomfortable because they reveal decay. That is exactly why founders need them.

When services revenue is useful

Many SaaS founders are told that services revenue is bad. That is too simplistic.

Services can be useful when they:

• Help you learn the customer’s workflow
• Fund product development without dilution
• Reveal repeatable implementation steps
• Increase trust for complex B2B buyers
• Create a bridge to recurring product revenue

Services become dangerous when they:

• Hide the fact that the product does not work on its own
• Consume all engineering capacity
• Produce custom features for one customer
• Make gross margin look worse as revenue grows
• Confuse investors, team members, and founders about what the company is

Label services clearly. Track services revenue, services cost, and productized learnings separately. The goal is not to pretend services do not exist. The goal is to know whether services are a learning tool, a cash engine, or a trap.

Investor-grade SaaS metrics room

Even before fundraising, prepare your SaaS metrics as if an intelligent outsider will inspect them.

Keep clean exports for:

• Customer list with start date, segment, plan, source, ACV, MRR, status, and owner
• MRR movement by month
• Churn and contraction reasons
• Expansion history
• Cohort retention
• Pipeline by stage
• CAC and payback by channel
• Gross margin assumptions
• Collections and receivables
• Services versus recurring revenue

This is not just for investors. It is for founder discipline. If you cannot explain your own revenue base, you cannot manage it well.

SaaS metrics for different motions

Self-serve SaaS

Important metrics:

• Visitor to signup
• Signup to activation
• Trial to paid
• Time to value
• Free-to-paid conversion
• Payment failure
• Product-qualified leads
• Cohort retention

The main risk is celebrating signups while activation and retention are weak.

Sales-led SaaS

Important metrics:

• Qualified pipeline
• Demo conversion
• Proposal conversion
• Sales cycle
• ACV
• Implementation completion
• Renewal risk
• Expansion pipeline

The main risk is closing deals that need heavy custom work and do not become repeatable product revenue.

Usage-based SaaS

Important metrics:

• Active accounts
• Usage growth by cohort
• Revenue per active account
• Gross margin by usage level
• Expansion from usage
• Usage concentration
• Cost per unit served

The main risk is revenue volatility and margin surprise.

AI SaaS

Important metrics:

• Cost per workflow
• Model/API cost as percentage of revenue
• Gross margin by customer
• Usage abuse or unprofitable usage
• Accuracy or quality score
• Human review cost
• Time saved for customer

AI products can look like software but behave like variable-cost services if inference and review costs are not controlled.

SaaS mistakes

Counting one-time revenue as ARR

Implementation fees, services, migration, and custom development may be valuable revenue, but they are not recurring subscription revenue. Separate them clearly.

Ignoring churn

New revenue feels exciting. Churn feels embarrassing. That is exactly why churn must be reviewed.

If customers leave, ask:

• Did we sell to the wrong customer?
• Did onboarding fail?
• Did the product fail to deliver?
• Did usage decline before churn?
• Did the buyer and user differ?
• Did price exceed perceived value?

Poor cohort tracking

Cohorts show whether newer customers are healthier than older customers.

Track customers by start month or quarter. For each cohort, measure activation, retention, expansion, support load, and churn.

Bad CAC math

Founders often calculate CAC from ad spend only. That is not enough for sales-led SaaS. Include people, tools, events, agencies, commissions, and founder effort.

No expansion tracking

If customers expand, you need to understand why. Expansion often reveals your best segment, strongest use case, and most scalable pricing model.

Weak revenue recognition

Do not confuse cash collected with revenue recognized, or bookings with revenue. Work with a qualified CA for accounting treatment. For operating dashboards, at least label numbers honestly:

• Booked
• Invoiced
• Collected
• Recognized
• Recurring
• Non-recurring

The India angle

Indian SaaS founders often operate across different worlds at once: Indian SMB, Indian enterprise, global SMB, global mid-market, and global enterprise. Do not mix these into one blended dashboard too early.

Key India-specific watchouts:

• GST and taxes should not be counted as revenue.
• Collection delays can distort cash health.
• Enterprise procurement can make sales cycles look worse than demand.
• Founder relationships can hide weak repeatability.
• Services revenue can hide product gaps.
• Global customers may have higher ARPA but higher expectations for support, compliance, and reliability.
• Indian SMB customers may need assisted onboarding even for a product that looks self-serve.

Build segment-level dashboards before making big strategy decisions.

A practical SaaS dashboard

Start with this monthly view:

Category	Metric
Revenue movement	New MRR, expansion MRR, contraction MRR, churned MRR, net new MRR
Retention	Logo churn, GRR, NRR
Acquisition	Qualified pipeline, CAC, payback
Customer value	Activation, usage, expansion, support load
Finance	Gross margin, burn, runway, collections

Then add cohort views:

• New customer cohort by month
• Activation by cohort
• Revenue retention by cohort
• Expansion by cohort
• Churn reason by cohort

ARR Quality Audit

Not all ARR is equal. Audit quality before using ARR in fundraising, hiring, or planning.

Question	Why it matters
Is it contracted, invoiced, collected, or only verbally committed?	Different confidence levels.
Is setup/services revenue excluded?	Prevents inflated recurring revenue.
Is usage-based revenue normalized correctly?	Avoids treating spikes as recurring.
Are discounts and credits reflected?	Shows real economics.
Are churned or at-risk customers removed?	Prevents false momentum.
Is customer concentration visible?	Shows dependence risk.
Are collections delays tracked?	Revenue is not cash.

ARR should be a truth metric, not a fundraising costume.

Churn Interview Loop

Every churned or downsold customer should create learning.

Ask:

• What did you expect when buying?
• Where did value fail?
• Was onboarding the issue?
• Did a competitor replace us?
• Was budget, priority, or internal ownership the issue?
• What would have made you stay?
• Should this customer have been sold in the first place?

Then tag churn:

Churn type	Meaning
Product gap	Product did not solve the workflow.
Segment mismatch	Wrong customer was sold.
Adoption failure	Value existed but users did not change behavior.
Budget/priority	Problem was not urgent enough.
Service failure	Support or implementation broke trust.

Churn is expensive, but unexplained churn is worse.

Reader action

Audit your current SaaS numbers. Create separate rows for:

• Recurring subscription revenue
• One-time setup revenue
• Services revenue
• Usage revenue
• Discounts
• Taxes
• Booked but unpaid revenue
• Collected cash

Then calculate net new MRR for the last three months. If you cannot calculate it cleanly, fixing the data system is the next operating priority.

Revenue Movement Reconciliation

Every month, reconcile revenue movement. This is one of the most useful habits in a SaaS company.

Use this table:

Movement	Amount	Customer count	Notes
Starting MRR
New MRR			New customers only
Expansion MRR			Existing customers increasing
Contraction MRR			Existing customers decreasing
Churned MRR			Customers leaving
Ending MRR			Starting + new + expansion - contraction - churn
One-time revenue			Separate from MRR
Services/setup revenue			Separate from MRR
Cash collected			Finance reality

Then ask:

• Did revenue improve because the engine improved or because one customer expanded?
• Did new MRR come from the target ICP?
• Did expansion hide churn?
• Did discounts or unpaid invoices make the month look better than reality?
• Did support or infrastructure cost rise with revenue?

Net new MRR without the movement story is incomplete.

SaaS Quality Scorecard

Score the business monthly.

Area	Healthy signal	Risk signal
New revenue	Comes from target ICP and repeatable channel	Random custom customers
Activation	Customers reach first value quickly	Founder-heavy onboarding
Retention	Churn reasons are understood and reducing	Churn appears suddenly
Expansion	Expansion follows usage/value	Expansion depends on founder relationships
Gross margin	Costs scale predictably	AI, support, or services cost rises quietly
Collections	Cash follows invoices	Revenue booked but unpaid
CAC/payback	Acquisition cost tied to retained customers	CAC calculated from ad spend only
Data trust	MRR, churn, and customer counts reconcile	Multiple dashboards disagree

This scorecard is not for investor theatre. It is for deciding what to fix next.

Cohort Review Template

Review one cohort at a time:

Question	Answer
How many customers joined in this cohort?
Which segment/source did they come from?
How many activated?
What was time to value?
How many expanded?
How many contracted or churned?
What support load did they create?
What did this cohort teach us?

The goal is to know whether newer customers are better than older customers. If newer cohorts are not healthier, growth may be scaling old mistakes.

MRR Source Of Truth

SaaS companies need one trusted source of truth for MRR. Without it, every investor update, board deck, and founder review becomes an argument.

Define:

Item	Rule
Customer	What counts as one customer: legal entity, workspace, account, billing relationship, or logo?
Active subscription	What status counts as active?
Start date	Contract signature, invoice date, payment date, or service start date?
Churn date	Cancellation date, access end date, invoice non-payment date, or renewal failure date?
Expansion	When is expansion counted: contract, invoice, payment, or usage confirmation?
Discounts	Are temporary discounts normalized or reflected in current MRR?
Taxes	Are taxes excluded from revenue metrics?
Services	Are setup, implementation, support, or success fees excluded from MRR?
Usage revenue	Is usage recurring enough to include, or reported separately?
Bad debt	When does unpaid revenue get removed or flagged?

For early startups, a well-maintained spreadsheet can be enough. The issue is not tool sophistication. The issue is whether the founder, finance owner, sales owner, and investor update all use the same truth.

Revenue Quality Layers

Not every rupee or dollar of SaaS revenue has the same quality.

Layer revenue like this:

Layer	Quality question
Contracted recurring revenue	Is the contract recurring and enforceable?
Invoiced recurring revenue	Has the customer been billed correctly?
Collected recurring revenue	Has cash arrived?
Activated recurring revenue	Is the customer using the product?
Retained recurring revenue	Has the customer renewed or continued after initial excitement?
Expanded recurring revenue	Is the customer increasing usage, seats, modules, or spend?

A startup with high contracted revenue but weak activation is fragile. A startup with high invoiced revenue but delayed collections has a finance problem. A startup with high new revenue but weak retained revenue has a product or ICP problem.

Use revenue quality to decide what to fix:

• Sales issue: not enough qualified new recurring revenue.
• Product issue: customers pay but do not activate or retain.
• Success issue: value exists but adoption does not spread.
• Finance issue: invoices do not become cash.
• Strategy issue: revenue comes from customers the company cannot repeat or serve profitably.

SaaS Board Metrics Without Theatre

Investor and board updates should show the business clearly, not decorate the story.

Include:

• Starting ARR/MRR.
• New, expansion, contraction, churned, and ending ARR/MRR.
• Logo churn and revenue churn.
• GRR and NRR.
• Activation and time to value for new customers.
• CAC/payback by channel where data is reliable.
• Gross margin including hosting, AI, support, implementation, and customer success costs.
• Receivables and collection risk.
• Customer concentration.
• Top churn reasons and actions.
• Runway and burn multiple.

Add a short commentary:

• What improved?
• What worsened?
• What is noisy or uncertain?
• What decision does the founder need from the board?

Do not hide uncomfortable metrics. A strong founder can explain weak metrics with diagnosis and action. A weak update makes every number look positive and leaves the real problem vague.

Expansion Revenue Diagnosis

Expansion is not one thing. Diagnose what type of expansion is happening.

Expansion type	Meaning	Risk
Seat expansion	More users in same account.	Adoption may be shallow if forced by buyer.
Usage expansion	Customer uses more of the core product.	Usage spikes may not repeat.
Module expansion	Customer buys additional product areas.	Product breadth can increase support load.
Price expansion	Customer pays more for same use.	Needs value proof, not only renewal pressure.
Services-to-product expansion	Manual work becomes software revenue.	Services may hide weak product adoption.

Healthy expansion follows visible value. If expansion depends only on founder relationships or custom work, treat it as a signal to inspect, not proof of a scalable engine.

SaaS Metrics Reconciliation Meeting

Run one monthly reconciliation meeting before sending investor updates, board updates, or internal dashboards. SaaS numbers are easy to make messy: sales may count bookings, finance may count invoices, product may count active accounts, and the founder may talk about ARR from memory.

Reconcile these views:

View	Source	Question
Bookings	Signed contracts or accepted orders	What was committed?
Billing	Invoices or payment system	What was billed?
Collections	Bank/payment records	What cash arrived?
Revenue	Finance/accounting view	What should be recognized for reporting?
Product usage	Product analytics	Who is actually active?
Customer status	CRM/CS view	Who is healthy, risky, paused, or churned?

For each customer, check:

• Is the account active in product?
• Is the contract/payment status clear?
• Is the MRR/ARR amount correct?
• Are taxes, one-time services, implementation fees, and pass-through costs excluded or separated?
• Is expansion, contraction, or churn recorded in the correct month?
• Is the account still a customer or only a legacy invoice?

Create a monthly revenue movement table:

Movement	Amount	Notes
Starting MRR
New MRR		New paid customers only
Expansion MRR		Existing customers paying more
Contraction MRR		Existing customers paying less
Churned MRR		Lost paying customers
Ending MRR		Must reconcile

The founder should understand this table personally, even if finance prepares it. A startup can survive weak metrics for a while, but it cannot safely fundraise, hire, or scale when revenue numbers are not trusted.

SaaS Health Scorecard

Use a health scorecard to connect SaaS metrics to operating action. The goal is not to create a perfect score. The goal is to see which part of the business is fragile.

Area	Healthy signal	Warning signal	Founder action
Acquisition	Qualified pipeline comes from repeatable channels.	Leads depend only on founder network or one event.	Test channel repeatability before hiring aggressively.
Activation	New customers reach first value quickly.	Paid customers need repeated founder rescue.	Fix onboarding and implementation before adding more sales.
Retention	Cohorts stabilize and churn reasons are specific.	Early churn is high or unexplained.	Interview churned customers and inspect promise/product mismatch.
Expansion	Existing customers expand because value is visible.	Expansion depends on custom work or pressure.	Build success proof and package expansion logically.
Revenue quality	MRR/ARR is recurring, collectible, and reconciled.	Revenue includes unpaid, one-time, or unclear amounts.	Clean definitions and separate services, taxes, and pass-throughs.
Gross margin	Delivery cost is understood and improving.	Support, AI, implementation, or hosting costs are hidden.	Track cost-to-serve by segment and plan.
Cash	Invoices convert to cash predictably.	Receivables grow or payment terms stretch.	Improve collections, terms, finance contact, and buyer process.
Concentration	No single customer can distort the company story.	One account dominates revenue or roadmap.	Manage enterprise dependence and roadmap tradeoffs explicitly.

Review this monthly. If one area is red, the company may still be healthy if the founder has a plan. If several areas are red, do not hide behind top-line ARR. SaaS quality matters as much as SaaS quantity.

SaaS Revenue Quality Audit

ARR is not automatically high-quality revenue. Two companies with the same ARR can have very different health depending on collectability, retention, support load, concentration, discounts, implementation effort, and expansion potential.

Audit revenue quality monthly:

Area	Question	Risk if weak
Recurrence	Is this truly recurring, or partly one-time services?	ARR overstatement.
Collection	Has cash arrived, or only invoice/contract exists?	Runway illusion.
Usage	Is the customer active and reaching value?	Future churn hidden.
Discounting	Was the deal won through unsustainable price cuts?	Weak pricing power.
Service load	Does revenue require custom founder/team work?	Margin and scalability risk.
Concentration	Does one customer dominate revenue or roadmap?	Fragile company story.
Contract quality	Are terms, renewal, termination, and payment clear?	Forecast and legal risk.
Expansion path	Can the account grow naturally?	Flat account economics.

Score each account:

Green: recurring, collected, active, low support, clear renewal path.
Yellow: useful but has discount, usage, support, collection, or contract concern.
Red: revenue exists but is fragile, custom, unpaid, inactive, or likely to churn.

Founder revenue note

Before reporting ARR externally, write a note:

• What is included?
• What is excluded?
• What is contracted but not collected?
• What is one-time service revenue?
• What is at-risk revenue?
• What is concentrated in top customers?
• Which customers are active versus merely paying?

This protects the founder from accidentally believing the cleanest version of the number. Good investors, acquirers, and operators will eventually inspect quality. Inspect it first yourself.

SaaS Finance Handoff

As SaaS revenue grows, the founder should not keep revenue logic only in their head. Finance, sales, customer success, and product need a shared handoff model.

Create a monthly handoff:

Owner	Must Provide
Sales	New contracts, discounts, payment terms, start dates, renewal dates, special promises.
Customer success	Activation status, health, expansion risk, churn risk, support burden.
Product	Usage, first-value completion, feature adoption, product incidents.
Finance	Invoices, collections, taxes, recognized revenue, receivables, refunds.
Founder/CEO	Interpretation, risks, board/investor narrative, decisions.

Then reconcile:

Question	Why It Matters
Is every ARR/MRR customer active?	Prevents revenue hiding churn risk.
Is every active customer billed correctly?	Prevents leakage.
Is every invoice collectible?	Prevents cash illusion.
Are one-time services separated?	Prevents ARR inflation.
Are discounts and custom terms visible?	Prevents weak pricing power from hiding.
Are support-heavy accounts flagged?	Prevents margin surprises.

This handoff is not bureaucracy. It is what lets the founder trust the revenue story before hiring, fundraising, or scaling sales.

SaaS Metrics By Board Question

Boards and investors do not need every SaaS metric every month. They need the metrics that answer the company’s current question.

Board Question	Metrics To Bring
Is demand real?	Qualified pipeline, win rate, sales cycle, customer segment, pricing objections.
Is product value real?	Activation, time to value, usage depth, retention cohorts, support burden.
Is revenue quality improving?	MRR/ARR movement, GRR, NRR, churn reasons, collections, discounting.
Can we scale acquisition?	CAC direction, payback estimate, channel quality, pipeline source, conversion.
Are margins safe?	Gross margin, implementation effort, support cost, cloud/AI cost, services mix.
Is cash under control?	Burn, runway, receivables, committed spend, hiring plan.

Use the board packet to force clarity:

The main SaaS question this month is ______.
The numbers say ______.
The weakness in the data is ______.
The decision we need is ______.

The goal is not to impress the board with metric volume. It is to make the company easier to help.

SaaS Metrics Cleanup Checklist

Before hiring sales, raising capital, reporting to a board, or planning growth spend, clean up the SaaS metric base. Many early SaaS dashboards look precise while mixing different kinds of revenue and customer states.

Use this checklist:

Check	Founder question
MRR definition	Does MRR exclude one-time services, setup, taxes, pass-through fees, and unpaid experiments?
ARR definition	Is ARR annualized recurring revenue, not total contract value or optimistic bookings?
Customer definition	Are trial, pilot, free, paid, churned, inactive, and internal accounts separated?
Churn definition	Do logo churn and revenue churn use clear start/end customer sets?
Expansion	Is expansion separated from new logo revenue?
Contraction	Are discounts, downgrades, reduced seats, and usage decreases visible?
Collections	Which invoices are raised, due, overdue, and collected?
Services	Which customers need custom work or heavy implementation?
Cohorts	Can retention be viewed by start month, segment, plan, and channel?
Source of truth	Which system wins if CRM, billing, finance, and spreadsheet numbers differ?

SaaS metric cleanup sprint

Run a three-day cleanup sprint:

Day	Work	Output
1	Reconcile customer list across CRM, billing, finance, and product.	One customer table with status.
2	Reconcile MRR/ARR movement and collections.	Revenue movement waterfall.
3	Add health fields: activation, usage, support load, churn risk, expansion risk.	Account health view.

The sprint should end with one founder note:

The revenue number we trust is ______.
The number we do not trust yet is ______.
The biggest quality risk is ______.
The operating decision is ______.

Clean SaaS metrics are not accounting decoration. They protect hiring, fundraising, pricing, runway, and founder credibility.

Bookings, Billing, Collections, And Revenue

Early SaaS founders often use revenue words loosely. This creates confusion in board updates, fundraising, sales planning, and cash management. Separate the stages of money clearly.

Term	Meaning	Founder Risk If Confused
Pipeline	Potential future deals that are not yet won.	Hiring or spending against hope.
Booking	Customer commitment or signed order.	Treating a signature as cash.
Invoice	Amount billed to the customer.	Assuming invoice raised means invoice collected.
Collection	Money received in the bank.	Ignoring payment delays and working capital.
Recognized revenue	Revenue accounted for over the service period.	Overstating monthly performance.
ARR/MRR	Recurring subscription run-rate under clear rules.	Inflating recurring business with one-time work.

For Indian B2B SaaS, this distinction matters a lot. Payment terms, GST invoices, procurement cycles, finance department delays, annual purchase orders, partner margins, and implementation milestones can create a gap between “deal won” and cash in bank.

Use this reconciliation view:

Customer	Booking	Invoice raised	Cash collected	Recurring amount	One-time amount	Payment terms	Risk

Ask every month:

What did we book?
What did we invoice?
What did we collect?
What is truly recurring?
What is at risk of delay, refund, downgrade, or non-renewal?

The founder should never be surprised by the difference between ARR on a slide and cash in the bank. SaaS metrics are useful only when they connect product value, contract quality, collections, and retention.

Related links

• 92. Startup Metrics Basics
• 93. Stage-Based Metrics
• 78. Investor Readiness
• 67. Retention and Churn
• 89. Startup Finance Basics