Profile
Software licences grow on their own and never shrink. A tool gets added, someone leaves, a department switches, and the invoices keep coming.
The Licence Monitor compares usage with contracts and invoices, and shows where you are paying for something nobody uses.
It cancels nothing. It makes visible what the conversation should be about.
What it does, step by step
- Take stock of licencesWhat you have bought, in what quantities and at what price.
- Measure usageWho actually logs in, and how often.
- Show the gapsPaid seats without a user, users without a licence, duplicate tools for the same job.
- Flag renewalsWhich contracts are ending and when a decision is needed.
- Make a proposalWhat can go down, what needs to go up, and what is worth a conversation with the vendor.
Works with these systems
- Microsoft 365
- APIs
Azure DevOps
SharePoint
OneDrive- Databases
Is your system not listed? We can connect any system, even if there is no standard integration. View all integrations.
What runs automatically and what does not
You stay in control.
Not every decision should be made automatically. For each workflow, we set out:
- What can happen automatically.
- What is put forward for approval first.
- When a person is brought in.
- What information is stored.
- How actions are logged.
Is this a fit for your organisation?
A good fit if
- Organisations with many SaaS subscriptions.
- Businesses where departments buy their own tools.
- Situations where nobody has a complete overview.
Less of a fit if
- Organisations with a handful of licences from one vendor.
- Negotiating with vendors: that stays human work.
What it can deliver
- Visibility of what you pay for without using.
- Renewals that do not slip through unnoticed.
- Evidence for a conversation with a vendor.
Directions, not promises. As soon as there is evidence from a client project, it will appear here as a substantiated result.
Frequently asked questions
How does it measure whether a licence is being used?
From login data and activity in the systems themselves, where available. For tools without a usable API it can only look at the contract side, and then we say so instead of pretending the picture is complete.
Is measuring usage per employee not a privacy concern?
It can be, which is why setting it up means a conversation with your data protection officer and your works council. The goal is licence management, not performance monitoring. In practice, aggregated figures per department are often enough.
Does it cancel subscriptions itself?
No. It flags and provides the evidence. Cancelling touches contracts and sometimes colleagues' work, so that is a decision for a person.
What does this give you at renewal time?
Figures on actual usage at the moment you talk to the vendor. That is different from negotiating on gut feeling about numbers nobody knows exactly.
How to put this to work
- 1A short callTogether we look at your process and your systems, and whether this task is the best place to start.
- 2Set up on your rulesIntegrations with your own systems, and agreeing what may run automatically and what a person approves.
- 3Measure and adjustFirst alongside your team, only then on its own. We look at what it delivers and adjust.