Licence optimisation: seats, plans and renewals
The licence optimisation module of Cureman answers three questions for every connected application: who holds which seat, who uses it, and what the right plan would cost. It reads seats, plans and activity through read-only connectors, applies each service's playbook, shows every saving with its calculation, and where the data cannot answer it asks the seat holder, after a person has approved the message.
Most organisations know what they pay for software and do not know who uses it. This module closes that gap from the vendors' own data and turns the result into steps that someone can approve.
What it reads
For every connected application the module reads three things through the vendor's admin API: the subscription (plan, paid seats, price, renewal date), the seat list (who holds which licence type) and activity (last sign-in or last action, and usage figures where the vendor reports them). Connectors are read-only. Per-seat usage that a vendor does not expose through its API can be imported as a file.
What it finds
| Finding | How it is computed |
|---|---|
| Inactive seats | Seats without activity for longer than the period the organisation set, times the price per seat |
| Seats of people who left | Seat holders that are no longer in the directory |
| Paid but unassigned seats | Paid seats minus assigned seats |
| A higher plan than needed | The service playbook's usage threshold for a tier, compared with what each holder used |
| Overlapping tools | Two applications that do the same job |
| Renewals coming up | The contract's notice date, with what is open on that application |
Each finding shows its calculation and says how sure it is. A finding that rests on a list price nobody has verified is labelled and stays out of totals until a person verifies the price in the catalogue.
Service playbooks
What is known about one service lives in a playbook: which tiers exist, what can be measured per seat, which offers the vendor makes, and which checks apply. A playbook is data, not code. Its thresholds are defaults that an organisation can change, and every check states its reasoning. Vendor offers such as paying a year up front are listed with a ceiling and never counted as savings, because nobody has quoted them.
Asking the seat holder
Where the data cannot answer the question, the module asks. It drafts the message for each situation (an inactive seat, a tier that looks too high), in the organisation's wording, for email or Slack. A person reads and approves the campaign before it goes out. The holder answers with one click on a page of their own. Answers are interpreted and filed; people who do not answer get the reminder that was approved with the campaign, and after that the question goes to their manager, if the approved plan says so. The method is described in asking employees about their licences.
From finding to done
Every finding has an action plan: manual steps, outreach, drafted messages to the vendor, and, where the organisation has allowed it, a call to the vendor's API. Each step that leaves the organisation waits in the list of decisions with what it is worth. When the plan is finished the finding is marked done, and only then does its saving count.
What it measures
The module meters the annual savings of findings marked done, spread over the twelve months after completion. That figure is the basis of the module's monthly statement.
Related reading
Questions and answers
Does the module change anything at the vendor?
- Not by itself. Connectors only read. A change at a vendor, such as removing a seat, is a step of an action plan that is prepared, shown in full and approved by a person, and it is switched off unless the organisation allows vendor API actions.
Which applications can be connected?
- Connectors are defined as YAML manifests, one per vendor, for services such as Microsoft 365, Google Workspace, Slack, GitHub, Atlassian, Salesforce, Zoom, Notion and others. A manifest is marked beta until it has been run against a live account. A new vendor is added by writing a manifest, without code.
Are employees contacted automatically?
- No. The module drafts the question for each situation, and a person approves the draft before anything is sent by email or Slack. Reminders and the message to a manager are shown and approved together with the campaign. Nobody on the organisation's do-not-contact list is asked.
What does the module measure as a saving?
- The annual saving of findings that were marked done, spread over the twelve months after completion. Seats that are only "in question" are not counted, and a finding that rests on an unverified list price stays at low confidence.