Software licences

SaaS licence management: what to track and when

Updated 5 min readMarkdown
In short

SaaS licence management is keeping one current record of every subscription the organisation pays for (plan, paid seats, price, renewal and notice date, owner), of who holds each seat and of whether that person uses it, and acting on the differences before each contract renews. Four counts per application carry most of the work: seats paid, seats assigned, seats in active use and seats needed. The rhythm is monthly for joiners and leavers, quarterly for inactivity, and a fixed lead time before every notice date.

SaaS licence management answers four questions for every application the organisation pays for: what was bought, who holds it, who uses it, and when it can be changed. It is bookkeeping first and optimisation second. An organisation that can answer the four questions from one record will find its unused seats and oversized plans almost as a by-product.

What to track for every application

Five records are enough. Each has one source, and it is worth writing the source down next to the value.

RecordWhat it holdsWhere it comes from
ApplicationName, purpose, business owner, administratorYour own inventory
SubscriptionPlan, paid seats, price per seat, billing cycle, end of term, notice period, automatic renewalThe contract and the vendor's billing page
SeatsHolder, licence type or tier, date assignedThe vendor's user list
ActivityLast sign-in or last action per seat, usage figures where the vendor reports themThe vendor's activity or audit data
PeopleEmployment status, department, managerThe directory or the HR system

The subscription record is the one most often incomplete. The plan and the price are on the invoice; the notice period and the renewal clause are only in the contract or the order form. Record the notice date as a date, not as "60 days before renewal", because a date can be put in a calendar.

Four counts that explain the bill

For each application, put four numbers side by side.

CountMeaningThe gap to the next count
Seats paidWhat the subscription billsPaid minus assigned: seats nobody holds
Seats assignedBillable seats with a holderAssigned minus active: seats whose holder is inactive or has left
Seats in active useHolders with activity inside the period you setActive minus needed: holders who could do with a lighter tier or with another tool
Seats neededWhat the business owner confirms for the next termThis is the number to renew

Each gap has its own method. Unassigned seats are arithmetic. Inactive seats need a threshold and a question to the holder, described in how to find unused software licences. Seats of people who have left need a join with the directory, described in licences at offboarding. The step from active to needed is a question of tiers: see right-sizing SaaS plans.

Who does what

  • The business owner of an application decides which features and how many seats the team needs. Without this person, every question about a downgrade ends in "better leave it".
  • The administrator assigns and removes seats in the vendor's console and knows which accounts are service accounts.
  • Procurement or IT keeps the record, runs the calendar and talks to the vendor.
  • Finance confirms what is actually invoiced, which is not always what the contract says.

The yearly rhythm

Licence management fails less from missing data than from missing dates. A workable rhythm has four beats.

WhenWhat happens
Every monthReconcile seat lists with the directory: remove seats of leavers, check that joiners got what they need
Every quarterReview inactive seats and tiers for the largest applications, ask holders where the data cannot answer
A fixed lead time before each notice date, for example twelve weeksRenewal review: seats needed, plan mix, what to ask the vendor for
After each renewalUpdate the record: new term, new price, new notice date, what was agreed

The lead time before the notice date matters most. A reduction found one day after the notice date waits a full term. How to use the weeks before it is covered in preparing a SaaS renewal.

Where to start

  1. Build the inventory from what is paid. Take twelve months of invoices and card statements and list every software vendor. Add what the single sign-on provider knows. The two lists never match, and the differences are the first findings.
  2. Sort by yearly cost. Work downwards. The ten largest subscriptions usually justify the effort; the long tail can wait.
  3. Record the dates. For each of the largest subscriptions, find the end of term and the notice period in the contract and write the notice date into a shared calendar.
  4. Name an owner. One person per application who can say what is needed.
  5. Read seats and activity. Start with the applications whose notice date comes first, through the vendor's admin API where there is one.
  6. Run the first review on the application with the nearest notice date, then let the calendar drive the rest.

What goes wrong

  • The record lists contracts and stops there. Without seats and activity it shows what is paid and never why.
  • Renewal dates without notice dates. The renewal date is when the money moves. The notice date is when the decision is due.
  • Seats in question reported as savings. A seat counts when its holder released it and the vendor's seat count was reduced.
  • Two applications for one job. Nobody sees it while each is reviewed alone. See overlapping SaaS tools.
  • A project and no rhythm. A clean-up done once is undone by the joiners, leavers and role changes that follow.

How Cureman does it

Cureman keeps this record from the vendors' own data. Read-only connectors fetch the subscription, the seat list and the activity of each connected application, and the directory comes from the identity provider. Deterministic code then computes the gaps: inactive seats against the inactivity period the organisation set, seats of people the directory marks as having left, paid seats that are assigned to nobody beyond a buffer the organisation chose, tiers that are higher than a holder's measured use, two applications for the same job, and renewals with their notice date. Every finding shows its calculation. A list price nobody has verified is labelled as unverified and is not added to totals. What needs a person waits in one list ordered by deadline and worth, and a question to a seat holder goes out only after a person approved it. The module is described on the page about licence optimisation.

Questions and answers

What is SaaS licence management?

It is the recurring work of knowing which software subscriptions an organisation pays for, who holds each seat, whether the seat is used, and when each contract can be changed. The result is a record per application with plan, paid seats, price, renewal date, notice date and owner, and a set of decisions taken before each notice date.

How is SaaS licence management different from classic software asset management?

Classic software asset management counts installations against purchased licences to stay within the terms of a licence audit. With SaaS the vendor enforces the count itself, so the risk is the opposite one, paying for seats and tiers nobody uses. The data also sits elsewhere, in the vendor's admin console and API instead of on the organisation's own machines.

Who should own SaaS licence management?

One function keeps the record and the calendar, usually IT or procurement, and every application has a named owner in the business who decides what is needed. Finance supplies what is paid. Without a named owner per application nobody can answer whether a seat or a tier is still needed, and the renewal passes unchanged.

How often should licences be reviewed?

Leavers and joiners are reconciled monthly, because seats of people who left cost money and keep access open. Inactivity is reviewed quarterly, or continuously where the vendor's API can be read. Every contract with a term gets its own review that starts a fixed number of weeks before the notice date.

Is a spreadsheet enough for SaaS licence management?

For the subscription record, yes, as long as someone keeps it current. It stops being enough for seats and activity, which change every week and have to be read from each vendor again and again. An export is a photograph, and a record built from exports is out of date by the time it is complete.