Two SaaS companies can report the same annual recurring revenue and give a buyer very different reasons for confidence.
One may retain customers consistently, spread revenue across a stable account base, and grow through repeatable product adoption. The other may replace departing customers with new sales, rely on discounts to secure renewals, or depend on a few relationships managed by the founder.
ARR alone does not reveal those differences. To understand SaaS revenue quality, founders need to explain what supports the number and where it could change.
Start With a Clear Definition of Recurring Revenue
Subscriptions, maintenance agreements, and usage-based arrangements create different expectations about future revenue. An annual contract may offer more visibility than monthly billing, but its cancellation rights and purchase commitments still matter.
Document how your business calculates ARR. Explain how you treat variable usage, discounts, one-time implementation fees, and services. Keep the definition consistent across reporting periods so changes reflect business performance rather than changes in calculation.
A buyer should be able to trace the reported number to customer agreements and billing records, with any differences explained.
Read Retention Alongside Growth
New sales can keep ARR growing while existing customers leave or reduce their spending. Looking only at total growth makes that deterioration harder to see.
Gross revenue retention measures how much recurring revenue remains from an existing customer base after churn and contraction, excluding expansion. Net revenue retention includes expansion from those same customers. Neither should include revenue from newly acquired customers in that period.
Read both measures together. Strong expansion from a few large accounts can offset losses elsewhere and make net retention look healthier than the broader customer base.
Break the results down by customer cohort, segment, and product where the data allows.
Compare equivalent periods and use consistent definitions. Then investigate the reasons behind the movement: customer closures, poor fit, implementation problems, reduced usage, or a change in pricing.
The useful question is whether the pattern can be explained and whether the business is responding to it.
Check What the Contracts Actually Support
A contract’s duration is only part of the picture. Review:
- Renewal dates and notice periods
- Early termination rights
- Minimum purchase or usage commitments
- Pricing changes and customer-specific discounts
- Service obligations
- Assignment and change-of-control provisions
Have legal advisers review provisions that could affect a transaction. Avoid treating all contracted revenue as equally secure simply because the agreements share the same term.
Summarize material exceptions in one place. This helps the team understand which renewals need attention and gives a buyer a clearer view of the obligations they would inherit.
Understand Concentration Beyond the Percentage
Serving a specialized market can produce a concentrated customer base. Concentration deserves attention, but the percentage alone does not explain the relationship.
For each major account, review its share of recurring revenue, renewal timing, product usage, and the people involved on both sides. Ask what would happen if the customer’s main contact left or the founder stopped managing the relationship.
A customer may be deeply integrated into the product and supported by several established contacts. Another may use only a narrow feature and rely on a personal relationship with the founder. Those situations require different transition plans.
Document the risks without presenting a long contract or a strong relationship as a guarantee of renewal.
Separate Repeatable Expansion From One-Off Gains
Customers may expand by adding users, modules, locations, or usage. Identify which of these changes drives growth and how often it occurs across accounts.
Distinguish broader product adoption from price increases or occasional large upgrades. Each can contribute revenue, but they tell different stories about demand and future growth.
Track what typically precedes expansion, who manages the process, and whether it depends on founder intervention. This gives the business a more useful basis for forecasting than assuming last year’s largest upsell will happen again.
Make the Revenue Story Easy to Verify
Before buyer conversations, prepare a consistent set of records: customer-level recurring revenue, renewal dates, retention calculations, contract exceptions, and an explanation of expansion.
Reconcile these with billing data and explain timing differences. A practical revenue bridge should show how opening recurring revenue changes through new customers, expansion, contraction, and churn.
At Continuum, these are useful starting points for discussing how a software business can perform under long-term ownership. For founders, the same work can support better renewal planning and reduce surprises well before a sale.
If you are considering an acquisition, start a conversation with Continuum about your business and the customer relationships behind its revenue.