How to Share SaaS Metrics With Investors

SaaS metrics look objective, but two companies can report identical ARR figures using definitions that produce completely different results when stress-tested. Investors know this, and they will check. This guide explains how to share SaaS metrics in a way that survives scrutiny.

TL;DR

• Write a metrics definitions document before anything else — ambiguous terms cost more time to explain than they save to skip.
• Reconcile each metric back to the underlying billing system or CRM, not just to a summary spreadsheet.
• Keep cohort tables, gross and net retention, and churn data in the same folder as the definitions.
• Assign one person to own the metrics release and to answer follow-up questions consistently.
• Update the definitions document when the reporting methodology changes, and note the date of the change.

Investors in SaaS companies will probe MRR, ARR, churn, expansion revenue and retention figures more carefully than almost any other data set. The metrics are highly comparable across portfolio companies, so anomalies stand out quickly. The most common problem is not fraud — it is inconsistency. A number that looks strong in one slide appears weak in another when the definitions differ.

Why SaaS metrics reviews fail

The failure mode is almost always definitional. Consider a company reporting 115% net revenue retention. That figure can mean different things depending on whether annual upsell revenue is counted in the same period as churn, how the denominator cohort is defined, and whether customers who churned and returned are re-included.

No investor will accept "that's just how we calculate it" as an answer. Nor should they. If your metrics are genuinely strong, a clear definitions document makes them stronger. If they are nuanced, clear definitions explain the nuance before the investor asks the harder question.

1. Write a metrics definitions document first

Before sharing any data, create a short definitions document. It should cover:

• How MRR is calculated and what is excluded (trials, pilots, unpaid accounts)
• How ARR is derived (MRR × 12, or annualised contract value)
• How churn is defined — by logo or by revenue, and over what period
• How gross retention and net retention are calculated and which cohorts they include
• How expansion revenue (upsell, cross-sell, seat growth) is recognised
• The "as of" date for each figure
• The source system (Stripe, Chargebee, Salesforce, internal billing system)

This document should be two to four pages maximum. Longer than that and investors will not read it before the first call.

2. Reconcile to the source system

Investors will ask to trace at least one headline metric to the underlying billing data. Prepare for this.

For each metric, link to the source extract. This can be a CSV export from the billing system, a Salesforce report or a manually prepared reconciliation. Label it with the date of the export and the system it came from. Do not rely on a dashboard screenshot — screenshots cannot be traced to their underlying data.

3. Prepare the cohort table

A cohort table is one of the most trusted documents in a SaaS diligence process because it shows retention over time rather than at a single point. Investors use it to identify whether churn is improving, consistent or deteriorating.

Prepare a monthly or quarterly cohort table that shows:

• The starting MRR for each cohort at month zero
• The remaining MRR from the same accounts at each subsequent period
• Expansion revenue separated from base retention
• The final net retention percentage for each cohort

If your cohort table shows an anomaly — a cohort that churned heavily, a period with unusually high expansion — address it proactively. A brief explanatory note in the data room is far better than waiting for the investor to raise it on a call.

4. Separate what is contracted from what is forecast

One of the most damaging things a SaaS founder can do is present a contracted ARR figure alongside a growth projection without making the distinction obvious. When both appear in the same document without labels, investors assume the higher number is contracted and the lower is already a concern.

Label each figure explicitly:

• Contracted ARR — signed, active agreements as of the reporting date
• Committed pipeline — signed or verbally agreed but not yet invoiced
• Forecast ARR — projected based on pipeline conversion assumptions

Keep these three categories in separate rows or separate documents. Never combine them in a headline figure without a footnote.

5. Build a controlled metrics release process

The metrics release should follow a defined sequence:

1. Define — agree the definitions document internally before any external sharing.
2. Extract — pull the source data from the billing system and CRM.
3. Reconcile — confirm that the summary metrics match the underlying extracts.
4. Review — have a second person check the figures, particularly retention and churn.
5. Release — share via named access, not an open link.
6. Log — record who received the metrics, which version and when.

When a metric is updated because a new period has closed, note what changed in the release log. If the revision affects a figure that was shared previously, tell the investor the figure has been updated and explain why.

A platform like SendNow can help you track which investors have opened and reviewed your metrics documents, which is useful before a diligence call when you need to know how prepared the other side is.

Editorial disclosure: SendNow has a commercial relationship with this publication.

6. A realistic example

A B2B SaaS company at Series B is preparing metrics for a lead investor. Their headline numbers: $2.8m ARR, 118% net revenue retention, 4% monthly churn.

The metrics definitions document explains that ARR is calculated as MRR × 12, using the last day of the preceding month. Churn is defined as logo churn — not revenue churn — for accounts active for more than 90 days. Net revenue retention uses a 12-month cohort window.

The reconciliation shows the ARR figure ties to the Stripe billing total for the period. The cohort table shows that retention has been above 110% for three consecutive cohorts, with one outlier cohort at 97% explained by a single enterprise customer that reduced headcount.

The investor receives the metrics definitions document, the cohort table and the reconciliation alongside the financial model. Because the definitions are clear and the cohort anomaly is explained, the diligence call focuses on growth strategy rather than metric clarifications.

7. Common mistakes

• No definitions document. Every investor will ask how you calculate churn. Having the answer pre-written saves hours.
• Mixing ARR and ACV. Annual Contract Value and ARR are not the same thing in multi-year deals. Define which you use.
• Reporting net retention without gross retention. Net retention can look strong even when gross retention is declining if expansion is high. Show both.
• Using different reporting periods in different documents. If the deck uses January figures and the data room uses December, explain the difference.
• Counting trials or freemium users in active customer metrics. Define what counts as an active customer and apply it consistently.

8. Pre-release checklist

• Metrics definitions document covers MRR, ARR, churn, gross and net retention
• Each metric is reconciled to the source system extract
• The "as of" date is visible on every summary table
• Cohort table is prepared and any anomalies are annotated
• Contracted, pipeline and forecast figures are labelled separately
• A second person has reviewed the reconciliation
• Access is set to named recipients with a release log
• A process exists for updating the metrics when a new period closes

Frequently asked questions### What is the most common metric mistake that raises investor concern?

Inconsistent churn definitions. If monthly churn in one document implies an ARR that does not match the ARR figure in another, investors notice. Write the definition once and use it everywhere.

How granular should the cohort table be?+

Monthly cohorts are preferred for businesses with monthly billing. Quarterly cohorts are acceptable for annual contract businesses. Annual cohorts are too coarse for most early-stage investors to trust.

Should I show every metric investors might ask for, or only the most important?+

Lead with the metrics that directly support your fundraising narrative. Include supporting metrics in a second-tier folder in your data room. Do not bury strong metrics, and do not hide weak ones — add context instead.

What if my billing system does not produce the exact output investors want?+

Be transparent about the limitation. Prepare a manual reconciliation that bridges the billing system output to the investor-facing metric. Label it clearly as a manual calculation and note the assumptions used.

How do I handle a metric that changed definition during the period?+

Note the change date and present both series: one using the old definition and one using the new. Explain why the definition changed. Investors respect methodological evolution when it is explained; they distrust silent restatements.

Final takeaway

Sharing SaaS metrics with investors is not about presenting the most flattering version of your business. It is about giving reviewers enough context to understand what the numbers actually mean. A clear definitions document, a source-reconciled data set and an honest cohort table will get you through diligence faster than a polished dashboard with undefined terms.

Related articles

• How to Share a Financial Model With Investors Securely
• How to Prove Revenue During Fundraising Due Diligence
• Build a Fundraising Investor Q&A Workflow