---
title: "Right-sizing SaaS plans"
description: "When a cheaper SaaS tier is enough, how to set a usage threshold per tier, when to ask the seat holder, and how to compute the saving of a downgrade."
url: https://www.cureman.de/en/articles/right-size-saas-plans
language: en
updated: 2026-11-16
alternate_de: https://www.cureman.de/de/artikel/passenden-saas-tarif-finden.md
---

# Right-sizing SaaS plans

> A cheaper tier is enough for a seat holder who does not use what the higher tier adds. To find these seats, write down in one sentence what each tier adds, pick one usage figure that shows whether a holder uses it, set a threshold per 30 days, and ask every holder whose usage was not measured. The saving is the number of seats to move, times the price difference between the two tiers, times twelve. A plan change for the whole subscription needs a list of required features first.

A cheaper tier is enough when the holder of a seat does not use what the higher tier adds. That sentence contains the whole method: know what each tier adds, find out per holder whether it is used, and move the seats for which it is not. Right-sizing comes after reclaiming: a seat nobody uses at all should be removed, as described in [how to find unused software licences](https://www.cureman.de/en/articles/find-unused-software-licences), and is not a candidate for a cheaper tier.

## Two kinds of right-sizing

| Kind | What changes | What decides it |
| --- | --- | --- |
| Tier per seat | Some holders move from a higher to a lower licence type, the rest stay | Each holder's usage, or their answer |
| Plan for the subscription | Every seat moves to a lower plan, or the billing cycle changes | The features the organisation as a whole relies on |

The first works where the vendor sells mixed licence types in one account, for example a full and a basic licence, or editor and viewer roles. The second is all or nothing and needs more care.

## Step 1: write down what each tier adds

For each pair of tiers, write one sentence: what does the higher one add? Usually it is one of three things: a higher limit (meeting length, storage, requests), a capability (recording, automation, advanced reporting) or administration (single sign-on, audit log). The sentence has two uses. It tells you which figure to measure, and it is what you tell holders when you ask them.

## Step 2: choose a usage figure and a threshold

Pick one figure per tier pair that shows whether a holder uses what the tier adds, counted per 30 days: meetings hosted, premium requests made, documents edited. Then set a threshold below which the lower tier would have been enough.

Three rules keep the threshold honest:

- It is a default with a stated reason, and the application's owner can change it.
- It is measured over a recent period. Figures older than about two months describe a different team.
- A sign-in is not a usage figure. Someone can sign in daily and never host a meeting.

Where the vendor's API does not report the figure per user, its admin console often does, as a table that can be exported.

## Step 3: sort every active seat

Go through the active seats on the higher tier and put each one into exactly one row. The holder's own answer outranks the measurement.

| What is known about the holder | Decision |
| --- | --- |
| Said a lighter licence is enough | Move |
| Said they need the tier | Leave |
| Usage measured, below the threshold | Move |
| Usage measured, at or above the threshold | Leave |
| Usage not measured | Ask; do not count |

The last row matters most. Missing data is never zero. A holder without a measured figure is a question, not a saving.

## Step 4: ask the holders you cannot measure

Ask one question that names the tier, says in a few words what it adds over the lighter one, and offers three answers: "I need the full licence", "a lighter licence is enough" and "I don't need it at all". The third answer turns some downgrade candidates into released seats. The wording and the follow-up are covered in [asking employees about their licences](https://www.cureman.de/en/articles/ask-employees-about-licences).

## Step 5: compute the saving

Saving per year = seats to move × (price of the current tier − price of the target tier) × 12.

A worked example with invented figures: 30 seats on a full licence at 45.00 a month, a basic licence at 20.00. Of the 30 holders, 9 are below the threshold and 3 said the basic licence is enough. 12 × (45.00 − 20.00) × 12 = 3,600.00 a year. Eight more holders were not measured. They are listed as "to ask" and are not in the figure.

Use the price the organisation actually pays for each tier. Where it has no seats on the target tier yet, the list price is the only source, and the result should say so.

## Changing the plan for the whole subscription

A lower plan for everyone is only a candidate when it keeps every feature the organisation relies on. Usage data cannot tell you that, because features such as single sign-on, audit logs or guest access are used by the organisation and not by a holder. So the order is:

1. List the features of the current plan that the lower plan drops.
2. Have the application's owner mark which of them are required.
3. Compare only plans that keep all required features, priced for today's seat count.
4. Check the billing cycle separately: the same plan billed yearly often costs less than billed monthly, and commits the seat count for twelve months.

Until the required features are recorded, a cheaper plan is a question to the owner and not a saving.

## What goes wrong

- **Counting a seat twice.** A seat that is unused belongs to the reclaim list. Listing it again as a downgrade inflates the total.
- **Treating the threshold as a verdict.** A holder just below it in a quiet month may need the tier next month. Ask when in doubt.
- **Forgetting what the downgrade removes.** Recordings, automations or history can become unavailable on the lower tier. Check what happens to existing data.
- **Missing the date.** A tier change on a committed term takes effect at renewal. Bring the list to the renewal, as described in [preparing a SaaS renewal](https://www.cureman.de/en/articles/prepare-saas-renewal).

## How Cureman does it

In Cureman, what is known about a service lives in a playbook: its tiers, what each adds, which usage figures exist per seat, and the checks that apply, each with a threshold per 30 days and its reasoning. The thresholds are defaults the organisation can change. Usage comes from the vendor's connector or from a file exported from the admin console, and figures older than 60 days are not used. For each active seat the check follows the table above: the holder's answer first, then the measured figure, and a seat without a figure is listed as "to ask" and not counted. The saving is computed as seats to move times the price difference times twelve, with the calculation shown, and a seat is claimed by one check only. A lower plan for the whole subscription is quantified once the required features are recorded; before that, one finding asks for them and counts nothing. Questions to holders are drafted and go out after a person approved them. See the page about [licence optimisation](https://www.cureman.de/en/modules/licence-optimisation).

## Questions and answers

### What does right-sizing a SaaS plan mean?

It means matching the tier each person holds, or the plan the whole organisation is on, to what is actually used. A holder who needs the product but none of what the higher tier adds is moved to the lower tier. It is a different question from unused seats, where the holder does not need the product at all.

### How do you know whether a cheaper tier is enough?

From a usage figure that reflects what the higher tier adds, compared with a threshold, or from the holder's own answer. A holder whose measured use over 30 days is below the threshold is a candidate. A holder whose use was not measured is asked, because missing data does not mean no use.

### How is the saving from a downgrade calculated?

Seats to move, times the monthly price of the current tier minus the monthly price of the target tier, times twelve. The price of a tier is what the organisation pays for it where it already has seats on that tier, and the list price otherwise. A saving that rests on a list price nobody has verified should be marked as such.

### Can a tier be changed during the contract term?

A move to a lower tier usually takes effect at the next renewal for a committed term, and from the next invoice with monthly billing, unless the vendor agrees to an earlier change. Some vendors let tiers be mixed within one subscription and some do not, which decides whether single seats can move at all.

### What should be checked before moving the whole organisation to a lower plan?

Which features the organisation relies on, as a written list agreed with the application's owner. Features such as single sign-on, audit logs or retention settings are often tied to a plan and are used by nobody in particular, so no usage figure shows them. Only a plan that keeps every required feature is a candidate.

## The module that does this

[Licence optimisation: seats, plans and renewals](https://www.cureman.de/en/modules/licence-optimisation): The licence optimisation module reads seats, plans and activity from vendor APIs, finds unused seats and oversized plans, and asks seat holders after approval.

## Read next

- [How to find unused software licences](https://www.cureman.de/en/articles/find-unused-software-licences): A step-by-step method to find unused software licences from the vendor's own data, ask the seat holders, and remove seats before the renewal date.
- [Asking employees about their licences](https://www.cureman.de/en/articles/ask-employees-about-licences): How to ask seat holders whether they still need a licence, with the wording, the answers, one reminder, the manager step and the people who are never asked.
- [Preparing a SaaS renewal](https://www.cureman.de/en/articles/prepare-saas-renewal): How to prepare a SaaS renewal. Work out the notice date, the seats you need and the plan mix, and decide what to ask the vendor for before the deadline.
