---
title: "Reducing software costs: where to look first"
description: "Seven places to look when software costs have to come down, ordered by how strong the evidence is and how soon the money stops flowing."
url: https://www.cureman.de/en/articles/reduce-software-costs
language: en
updated: 2026-11-17
alternate_de: https://www.cureman.de/de/artikel/softwarekosten-senken.md
---

# Reducing software costs: where to look first

> To reduce software costs, start where the evidence is strongest and no one loses anything. First come seats held by people who have left, then paid seats that are unassigned or inactive, then seats on a higher plan than their holders use. After that come two tools that do the same job, software nobody manages, and what the invoices show, such as a raised price or a period billed twice. The calendar decides the order among contracts, because most reductions take effect only at renewal and need notice before it. Count a saving once the seat is gone or the new price is on an invoice.

To reduce software costs, look first where the evidence is strongest and nobody loses a tool they use: seats of people who have left, then unassigned and inactive seats, then plans that are higher than their holders need. Consolidation, unmanaged software and the invoices follow. No estimate is needed for any of it, because the vendor's own data and your invoices contain the answer.

## The order, and why

Three things decide where to look first: how strong the evidence is, who has to be asked, and when the money stops flowing.

| Where to look | Evidence | Who must agree | When it pays |
| --- | --- | --- | --- |
| Seats of people who left | Directory against seat list | Nobody | Next invoice or renewal |
| Unassigned and inactive seats | Seat list and last activity | The holder, for inactive seats | Next invoice or renewal |
| Plan higher than needed | Usage per seat against what the plan adds | The holder | Next invoice or renewal |
| Two tools for one job | Seat lists of both tools | The teams that use them | When the smaller contract ends |
| Software nobody manages | Invoices against the inventory | Whoever ordered it | When the subscription ends |
| Invoices | Price history, billing periods | The vendor | With the credit note or the corrected price |
| Chat seats with little use | Use per person | The holder | At renewal |

## 1. Seats of people who have left

Compare the seat list of each application with the directory. A billable seat whose holder has left is unused whatever the activity data says, and it is also an open door. Nobody needs to be asked. The method is in [licences at offboarding](https://www.cureman.de/en/articles/offboarding-licences).

## 2. Unassigned and inactive seats

A seat that is paid for and assigned to nobody can go. A seat without activity for a period you set, for example 60 or 90 days, is a question to its holder, because activity data misses some kinds of use. The steps are in [how to find unused software licences](https://www.cureman.de/en/articles/find-unused-software-licences).

## 3. The plan behind each seat

Many vendors sell the same product in several plans. A holder who uses only what the lower plan contains can move to it and keep working as before. This needs usage figures per seat and a threshold per feature. See [right-sizing SaaS plans](https://www.cureman.de/en/articles/right-size-saas-plans).

## 4. Renewals, by date

The first three points produce a list. The calendar decides which contract comes first, because a seat count under a committed term usually falls only at renewal and notice has to be given before that. Sort the contracts by notice date and work on the nearest ones first. What to bring to the talk with the vendor is covered in [preparing a SaaS renewal](https://www.cureman.de/en/articles/prepare-saas-renewal).

## 5. Two tools for one job

Two video tools, two project boards, two survey tools: where people hold a seat in both, one of them can usually go. The saving is uncertain until the holders have said which one they use, and moving a team takes time. See [finding overlapping SaaS tools](https://www.cureman.de/en/articles/overlapping-saas-tools).

## 6. Software nobody manages

Subscriptions booked by a team on a card or by invoice are in none of the lists above. They show up when the software suppliers on your invoices are compared with the application inventory. See [shadow IT](https://www.cureman.de/en/articles/shadow-it).

## 7. The invoices themselves

Invoices show what the seat lists cannot: a unit price that rose without notice, a period billed twice after a plan change, the same invoice sent twice. These are claims against the vendor and are settled with a credit note or a corrected price. See [finding price increases on invoices](https://www.cureman.de/en/articles/price-increases-on-invoices).

One newer item belongs here as well. Chat assistants are often bought as a seat for everyone, while use differs widely from person to person. For light users, paying by the token can cost less than a seat: see [seat licence or pay per token](https://www.cureman.de/en/articles/ai-chat-seat-licence-or-pay-per-token).

## A worked example

The figures are invented and round. A company has 100 seats of a tool at 20.00 a month on the higher plan. The lower plan costs 12.00.

| Finding | Calculation | A year |
| --- | --- | --- |
| 4 seats of people who left | 4 × 20.00 × 12 | 960.00 |
| 10 seats inactive for 90 days | 10 × 20.00 × 12 | 2,400.00 |
| 15 seats that fit the lower plan | 15 × (20.00 − 12.00) × 12 | 1,440.00 |

The total in question is 4,800.00 a year. The first row is certain. The second needs the holders' answers: if 7 of the 10 release their seat, it becomes 7 × 20.00 × 12 = 1,680.00. No seat is counted in two rows. And none of it is saved before the renewal at which the seat count and the plan change.

## What goes wrong

- **Starting with the largest contract.** The largest invoice is not where the most unused seats are. Start with the evidence.
- **Counting a seat twice.** A leaver's seat that is also inactive and also on too high a plan is one seat, not three findings.
- **Reporting findings as savings.** Finance will ask for the invoice that shows it. The article on [proving procurement savings](https://www.cureman.de/en/articles/prove-procurement-savings) explains what counts.
- **Missing the notice date.** A finding made a week after the date waits twelve months.
- **Using list prices as facts.** What you pay is on your invoice and in your contract. A price from a vendor's website is an assumption until someone has checked it.

## How Cureman does it

Cureman reads seats, plans and activity through read-only connectors to the vendors and the directory through the connector to the identity provider. It lists seats of people who have left, inactive seats, seats that fit a lower plan, overlapping tools and renewals that are close, each with its calculation, and a seat is counted in one finding only. A list price that nobody has verified is labelled as unverified and kept out of totals. Where the data cannot answer, it drafts the question to the seat holder, and a person approves the draft before anything is sent. With invoice audit booked as well, invoices are checked for price increases, double-billed periods and duplicates, and software suppliers without an application in the inventory are listed. A finding counts as a saving once it is marked done. The modules are described on the pages about [licence optimisation](https://www.cureman.de/en/modules/licence-optimisation) and [invoice audit and spend analysis](https://www.cureman.de/en/modules/invoice-audit-and-spend-analysis).

## Questions and answers

### Where do you start when software costs have to come down?

With seats that are paid for and used by no one. A seat whose holder has left the company and a seat assigned to nobody need no judgement, only a comparison of the vendor's seat list with your directory. Inactive seats come next, and they need a question to the holder before anything is removed.

### How quickly do software savings take effect?

That depends on the contract. With monthly billing a removed seat lowers the next invoice. With a committed annual term the seat count usually falls only at renewal, and the vendor must be told before the notice date. A list of findings should therefore always carry the date from which each one pays.

### Is cancelling tools the fastest way to save on software?

Rarely. Ending a tool means moving people and data and takes months, while the contract keeps running. Removing unused seats and moving seats to a fitting plan touch nobody's work and can be decided in days. Consolidation is worth doing, but it belongs later in the order.

### How do I know that a saving is real?

A saving is real when the next invoice shows it or when the vendor has confirmed the new seat count or price in writing. Until then it is a finding with a calculation. Keep both lists apart, and report only the second one as saved.

### How often should software costs be reviewed?

Seats change every month, because people join, leave and change roles, so the seat comparison is worth repeating monthly. Contracts need a look well before each notice date. A yearly review alone finds the same seats again each year, after they have been paid for twelve months.

## 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.
- [Right-sizing SaaS plans](https://www.cureman.de/en/articles/right-size-saas-plans): 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.
- [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.
