What is a SaaS Downgrade?

SaaS downgrading is a method by which a customer transitions to a subscription package (with a lower cost), often involving a reduction in the number of licensed seats and/or available optional features. It should be noted that this change is not followed by a break in the customer relationship, unlike in a cancellation. Implementing a downgrade path can contribute to retaining users with cost concerns or require fewer features, and it can also provide finance teams with information regarding instances of revenue reduction.

All of the following concepts are frequently interchangeable in meaning. Their characteristics diverge with respect to billing and retention:

• A downgrade refers to the continuation of the product’s subscription, where adjustments to plans, seats, or usage levels correlate with a reduced cost.
• Recurring revenue changes can be quantified by churn, which represents reductions stemming from either account downgrades (revenue churn) or complete service cancellations (logo churn).
• A cancellation signifies that no subscription remains active; consequently, no additional charges are applied, with user access ceasing at the close of the paid duration.
• A pause in a subscription indicates a suspension of services, which results in the cessation of billing; reactivation of the account and its associated data is typically an available option.

Downgrading and pausing actions generally maintain the customer relationship, whereas cancellation concludes the existing agreement. Churn is a metric mirroring the overall revenue or customer effects linked to these identified occurrences.

Typically, the SaaS product is structured to present several downgrade possibilities for customer products, allowing a choice to be made before service discontinuation:

•       Changing the tier from one to another, for instance, from Enterprise to Pro or Starter.
•       Reducing the number of licenses by less, without upgrading the customer plan at the same time.
•       Adjustments involving features or add-ons considered supplementary to the main product.
•       If it is metering or usage-based pricing, then it would be changing the number of units consumed to fewer.
•       Billing period adjustment, which is the most noticeable one, since changing a plan to monthly might significantly lower your commitment compared with, e.g., the standard price that is still the same although you will pay per month rather than annually.

The availability of this flexibility allows customers to modify particular elements prior to the situation evolving negatively, potentially resulting in their complete withdrawal.

Practically, when it comes to the billing system, a proper implementation of a downgrade functionality is usually built with a couple of key components and mechanics.

1.   Obviously, proration calculation (the billing engine decides whether the customer should be credited/refunded or charged for the new plan price difference over the remaining period) is one of them.
2.   A relevant consideration is determining the precise moment a downgrade will become active, either immediately or following the subsequent renewal, given that system configurations can influence functionality access within the current cycle.
3.   Yet another is entitlement updates: as soon as the new plan starts functioning, it adjusts feature permissions, licensed seat limit, etc.
4.   Lastly, the change confirmation letter along with any applicable refund information should be sent to the customer, which is usually by the billing engines themselves.

Net​‍​‌‍​‍‌ Revenue Retention (NRR) is the growth (or loss) of the recurring revenue of the customer base over time that does not take into account the revenue growth from the new customers. Downgrades and cancellations are factors that relate to a reduction in NRR, and upgrades and expansions are also elements influencing NRR.

Since downsizers decrease the revenue and at the same time the customer doesn’t leave, they are typically considered a somewhat less destructive result than cancellation; the account continues, and there is a chance the lost revenue can be recovered through a future upsell.

In addition, an unproblematic and easily operable downgrade path may result in various implications:

Pros:

•       Providing an intermediary option to budget-constrained customers can influence the frequency of full cancellations
•       The status of customer relationships may correlate with subsequent SaaS upsell capacity
•       There will be a better understanding of why and how revenue is shrinking because you can extract that from clean data
•       Communicating product flexibility may influence customer trust and brand perception

Cons:

•       It is plausible that this relates to immediate recurring revenue with a limited effect
•       Ensuring the technical and complete accuracy for proration, entitlements, and tax could involve complexities
•       Regular modifications of service plans linked to usage peaks could lead to customers altering their subscription choices to manage cost

Ask yourself:

Is customer cancellation behavior influenced by the availability of straightforward downgrade options? Does the team make manual processing of plan changes, rather than automatically handling them? Do you have any insight into the financial impact stemming from upgrades and cancellations?

If any of these point to gaps, a structured downgrade process is worth prioritizing. Key factors to weigh:

•       Does your billing engine have features that allow for prorations and mid-cycle plan changes?
•       How critical is your retention data to your business reporting and planning?
•       What kind of service or features do your customers expect when managing their account on their own (self-service)?