There is a point at which a SaaS customer is still paying, still included in ARR and still shown as active—yet the revenue has already begun to weaken.
The contract has not been cancelled. The renewal date may still be several months away.
Nothing has changed in the accounts. But the relationship underneath the revenue has changed.
Over the last few months, we have been looking more closely at the distance between reported recurring revenue and the commercial strength of the customers behind it.
This matters because churn rarely begins on the day a customer decides not to renew. It often begins much earlier.
Product usage declines. A senior sponsor leaves the customer’s business. Implementation remains incomplete. Support conversations become less frequent—not because the customer is satisfied, but because it has gradually stopped relying on the product.
An important feature is never adopted. A promised integration is delayed. The customer begins reviewing costs internally or comparing alternatives.
None of these events immediately reduces revenue.
If the customer is halfway through an annual contract, the company may continue recognising the same monthly amount. ARR remains unchanged. The board report still shows the account as live.
From a financial perspective, the customer appears stable.
From an economic perspective, the renewal may already be in danger.
This creates a particular problem for growing SaaS businesses.
Management decisions are often made using revenue figures that describe what has been contracted, while saying very little about what is likely to remain.
A company may look at its current ARR and conclude that it can afford another hire, increase acquisition spending or commit to a larger product budget. That decision may be reasonable if the existing customer base is genuinely secure.
It is less reasonable if a meaningful part of the revenue is approaching renewal with weak usage, unresolved delivery problems or no active executive relationship. The difficulty is that the financial consequence arrives later than the operational warning.
By the time churn appears in the accounts, the underlying deterioration may have been visible for months. The lost customer then appears to have created a sudden revenue problem. In reality, the revenue problem was gradual. Only its recognition was sudden.
This is why contracted recurring revenue and dependable recurring revenue are not necessarily the same figure.
Consider two SaaS companies with identical ARR.
The first has customers using the product regularly, successful implementations, several users within each account and renewal conversations beginning well before contracts expire.
The second has low adoption among several large customers, delayed onboarding, heavy dependence on individual champions and a significant portion of ARR renewing within the same quarter.
On a headline revenue report, the two companies may appear equally strong. They do not have the same financial position.
One has a revenue base capable of supporting further commitments. The other has a revenue base that may require protection before it can safely support expansion.
The distinction becomes more important when customer concentration is high. If a small number of accounts represent a large proportion of ARR, weakness in one relationship can materially change the company’s cash forecast, hiring capacity and runway.
Yet a conventional forecast may continue carrying the customer at full value until management receives a formal cancellation notice. That is often too late.
The purpose of a forecast is not merely to reproduce existing contracts. It is to help the business make decisions before the outcome becomes certain.
This does not mean reducing forecast revenue whenever a customer raises a support ticket or uses the product less for a few weeks.
Nor does it mean allowing subjective concerns to replace financial discipline. It means connecting commercial evidence to the financial view of the business.
For material accounts, management should be able to distinguish between revenue that is contracted and healthy, revenue that is contracted but showing signs of weakness, and revenue whose continuation depends on a renewal decision that has not yet been secured.
The categories do not need to be complicated. What matters is that they influence the forecast.
A customer approaching renewal with strong adoption and an active sponsor should not be treated in the same way as one with falling usage, unresolved implementation work and no meaningful engagement.
Both may currently be paying. Only one may be dependable. This changes the way the business evaluates future cash.
A base forecast can include revenue supported by realistic renewal evidence. An upside case can include renewals that remain achievable but are not yet secure. A downside case can show what happens if the accounts displaying genuine weakness are lost or reduced.
The result is not a prediction of exactly which customer will leave. It is an understanding of how exposed the company is if current warning signs become financial outcomes.
That understanding affects more than the revenue forecast. It affects hiring.
A permanent employee creates a monthly cost that continues whether or not a major customer renews. If the affordability calculation assumes that all current ARR will continue without examining renewal quality, the business may be converting uncertain revenue into a certain obligation.
It affects customer acquisition.
A company may increase marketing expenditure to replace revenue that has not yet officially disappeared. Without recognising the weakness in the existing base, management can mistake replacement activity for growth.
It also affects valuation.
Recurring revenue is valuable partly because it is expected to recur. When renewal quality weakens, the headline ARR figure may remain unchanged while the economic value underneath it declines.
This is one reason apparently healthy SaaS businesses can miss forecasts abruptly. The forecast did not necessarily fail because the cancellation was impossible to anticipate. It may have failed because information already present in customer success, product usage and account conversations never reached the financial model.
Finance saw the contract. Customer success saw the relationship. Product saw the usage. Sales saw the renewal conversation. But nobody combined them into one view of what the revenue was becoming.
A useful SaaS finance function should help close that gap.
The objective is not to turn every customer signal into another dashboard. It is to identify the signals capable of changing a financial decision and make sure they are reflected before cash is committed. This is particularly important during periods of rapid growth.
New bookings can conceal weakness in the existing customer base. ARR continues rising because new revenue is entering faster than old revenue is leaving.
The company appears to be expanding. But if an increasing proportion of sales effort is required merely to replace customers already drifting away, the quality of that growth is deteriorating.
The business is filling a container without first examining the leak.
At N.P. Ummer Financial, we have been considering how SaaS forecasts can reflect not only the revenue a company has contracted, but the evidence supporting its continuation.
That means placing renewal timing beside the cash forecast, examining material customers individually and translating commercial warning signs into realistic scenarios before another fixed commitment is made.
Recurring revenue should create confidence. But that confidence should come from more than the existence of a contract.
A contract tells the business what a customer has agreed to pay today. The relationship determines whether it will still be revenue tomorrow.