OBLYTECH Logo
OBLYTECH Logo
What Is ServiceNow License Optimization? A Plain-Language Guide

What Is ServiceNow License Optimization? A Plain-Language Guide

What ServiceNow license optimization is

Software License Optimization is the process of aligning software spending with actual usage. You pay for what you use and eliminate waste. In ServiceNow, license optimization sits inside the Software Asset Management application, which tracks, evaluates and manages software licenses, compliance and optimization. Reclamation rules for SaaS and SSO subscriptions set how long a subscription can go without activity before it is flagged as a reclamation candidate, and an SSO integration with Microsoft Entra ID or Okta supplies the login data for SSO applications. SaaS License Management is requested separately from the ServiceNow Store and needs Software Asset Management Professional, which is licensed for software uninstall (reclamation) only.

The goal: reduce software spending while maintaining compliance and service quality. This is often called “optimization” but really means “right-sizing.” Over-licensing often starts when organisations buy pessimistically (budgeting for peak usage that often never arrives) and then forget to clean up unused licenses as needs change.

What Problem It Solves

Organisations often spend heavily on software they barely use. A site licence for 500 users when only 200 are active. A SaaS subscription nobody remembers signing up for. Enterprise edition features when standard edition would suffice. Without visibility and discipline, software spending grows unchecked.

License Optimization gives you visibility: which software is used heavily (keep it), which is used lightly (downgrade or eliminate), and which is unused (eliminate). With this data, you can make trade-off decisions: do you use this tool enough to justify the cost?

How It Works at a High Level

Step 1: Inventory. Discover all software installed or licensed across the organisation. Hardware Asset Management and Software Asset Management provide the baseline.

Step 2: Usage tracking. Measure actual usage: how many users log in daily, how often is the software launched, how much data is processed. This requires integration with monitoring tools or the applications themselves.

Step 3: Analysis. Compare usage to licensed capacity. Which licenses have excess capacity? Which are over-subscribed? Which are abandoned?

Step 4: Recommendations. The platform surfaces reclamation and removal candidates and, for SaaS and SSO applications, an overlapping usage view; consolidating overlapping tools is a decision people make from that evidence. Some recommendations are tactical (immediate quick wins), others are strategic (long-term savings).

Step 5: Action. Negotiate new licensing terms based on recommendations, or eliminate software. Track savings.

Who Uses It and When

Scenario 1: Compliance Audit. You are being audited for license compliance. License Optimization shows where you are unlicensed (over-using) and where you are over-licensed (paying for unused capacity). This helps you true-up before the audit.

Scenario 2: Cost Control Initiative. Finance wants to cut IT spending. License Optimization identifies quick wins: redundant tools, unused seats, duplicate subscriptions. Consolidate and eliminate to reduce costs.

Scenario 3: Vendor Renegotiation. A vendor contract is up for renewal. License Optimization shows what you actually use. Use this data to negotiate better rates or terms based on real consumption instead of inflated usage.

Scenario 4: Consolidation Project. Your organisation has multiple divisions using different tools for the same purpose (three different CRM systems, two project management tools). License Optimization can show the true cost of this duplication and justify consolidation.

Typical Use Pattern

Consider a hypothetical large manufacturing company that wants to reduce software spending significantly. Finance has set an aggressive cost reduction target. A review of this kind would typically find:

  • Unused software subscriptions that are candidates for cancellation once their users have been checked.
  • Over-licensed seats for tools where actual usage is far below purchased capacity. Whether a lighter tier works depends on what those users need.
  • Multiple project management tools used by different divisions doing the same work. Consolidation to a single platform reduces redundancy and support overhead.

The size of any saving depends on the contract terms and usage data for each product, so the example does not give a figure.

How It Relates to Neighbouring Modules

License Optimization works closely with Software Asset Management (tracking what is licensed) and Hardware Asset Management (tracking what is installed).

Software Asset Management covers both: reconciliation shows whether use is within entitlement, and the optimisation features show which rights are paid for and not used. They work together: SAM ensures you are compliant with what you licensed, License Optimization ensures you licensed what you actually use.

When It Is a Good Fit and When It Is Not

Good fit: organisations with diverse software portfolios, multiple vendors, and usage that does not match licensing. If you suspect you are over-licensed or have shadow IT, License Optimization helps. Also good if you are consolidating or recovering from a merger where duplicate systems exist.

Not a good fit: organisations with a small software footprint or strategic tools where usage is not negotiable (e.g., required safety software must run everywhere, regardless of usage). Also not essential if your software spending is already highly optimised.

Prerequisites: you need visibility into actual software usage. This requires monitoring, user surveys, or API calls to applications. Without usage data, optimisation recommendations rest on assumptions.

The words you will hear in the first conversation, and what they mean here

People new to license optimization usually meet the same handful of terms in their first meeting, and they are often used loosely. Finance says “seats”, the vendor says “entitlements”, and the operations team says “installations”. Those three words describe different things, and a reduction proposed in one vocabulary can be rejected in another. The table below translates the common terms into what they mean for a decision, so that a non-specialist can ask a sharp question without sounding unsure.

Term you will hear What it means for a decision Question to ask in response
Seat or named user A person-level right that is paid for whether or not the person logs in How many of these people have used the product in the last full cycle?
Entitlement The right the organization holds under a contract, which may differ from what was bought on the invoice Which order form or amendment created this right, and does it still apply?
Installation One copy of a product found on a device, server or cloud resource Was this copy discovered once or several times, and is it still running?
True-up Paying for usage that exceeded what was licensed, usually at a set price Is the true-up price lower than the cost of reducing the usage first?
Metric The unit the vendor counts, such as user, device, core or transaction Which unit does the contract actually use, and who can confirm it in writing?

The first look: what to examine before anyone proposes a change

The first look at an estate should answer whether the organization is paying for software it does not use and whether it is exposed to a shortfall. Those are different risks, and the same review can surface both. Work through the sequence below before forming any view on savings.

  1. List the products with the largest annual renewal values and the earliest notice dates.
  2. For each, confirm the metric and the number of entitlements that the contract grants.
  3. Compare the entitlement count with the number of installations and the number of active users.
  4. Mark each product as over-deployed, under-deployed or unclear, and state the evidence behind the mark.
  5. Pick the two or three products where the evidence is strongest and the notice window is nearest, and examine only those in depth first.

The discipline is to resist examining everything at once. A broad first look produces a long list of possible savings and no decisions, because each item needs its own evidence.

What a sensible first outcome looks like

A good first outcome is modest. It is a short list of products with a stated reason for each, a named owner for every renewal in the next cycle, and a note of the data that is missing. It is not a total savings figure. Early totals depend on assumptions about usage that have not yet been tested, and when those assumptions fail, the credibility of the whole effort fails with them. Present early figures as ranges with their basis written beside them, and expect the ranges to narrow as the evidence improves.

The mistake of treating optimization as a cost cut

Many programs begin as a request to cut spend and quietly become a program about fit. A product that appears unused may be used heavily for a few days a year, by a team that matters a great deal at that time. A product that appears duplicated may serve two populations with different workflows. Starting from the question of fit, which asks whether each product matches how the business actually works, produces better decisions than starting from a reduction target. The common mistakes guide describes the other errors that follow from a cost-first framing.

What the team needs in place before the first decision

Three things should exist before a decision is made: a reasonably complete list of installations and users, a register of contracts with their notice dates, and a named decision-maker for each product. Without the first, usage claims are guesses. Without the second, the team can miss a notice window and be locked into another cycle. Without the third, a reduction is approved by no one in particular and defended by no one when users complain. If any of these is missing, the first task is to close that gap, not to start optimizing.

The relationship with the asset lifecycle is worth understanding early. The asset lifecycle management article covers how records move from purchase to retirement, and much of the data that license optimization relies on is produced at those same stages.

Signs the program is off track

A program is drifting when its reports are admired but no renewal has changed, when the most active discussions are about the methodology rather than a product, or when users learn about a reduction from a removed login rather than a message. Each of these means the program has become an analysis exercise. Bring it back to decisions by choosing one product, one owner and one date.

Frequently asked questions for a first-time reader

Do we need to buy anything new to start?

Not necessarily. The first look can be done with the contract register, the discovery data already held and the finance records. What matters is whether those sources agree with each other, and a short reconciliation will show that quickly.

Who should lead it, finance or IT?

Neither alone. Finance owns the money and the renewal calendar, IT owns the installations, and the program needs someone who holds both views. Many organizations place the lead in procurement or in the asset management team, because those roles already sit between the two.

How is this different from a compliance review?

A compliance review asks whether the organization is using software it is not entitled to use. Optimization also asks whether it is paying for rights it does not need. The same data supports both, but the decisions they produce are different.

What is the most useful early question to ask a vendor?

Ask which metric the contract uses and how the vendor counts it in practice. Many surprises come from a difference between the metric written in the contract and the way the vendor’s tools count usage.

Should we tell users that we are looking at their tools?

Yes, before any change affects them. Users who learn about a review after a reduction often treat it as a betrayal. A short notice explaining the purpose and the decision date often prevents much of that reaction.

Next step

A first conversation is often enough to decide which products deserve a deeper look.

Software license optimization techniques that reduce spend without cutting access

The techniques that lower software license spend work by matching what you pay for with what people actually use. Five approaches are set out below, and they differ in how much evidence they need and how quickly they pay back.

Start with the approaches that need the least evidence. Each one below names the data it depends on, so the team can see when it is ready to act.

  • Reclaim inactive named seats. Take back seats held by people who have not used the product in the last full cycle. Agree the reclamation rule with the business in advance, so that removing access does not come as a surprise.
  • Right-size the edition. Check which premium features are switched on and which ones are used. When a higher edition charges for features nobody uses, a lower tier may cover the real work.
  • Remove duplicate tools. Where two products serve the same team, compare their actual use and keep one. Consolidation can return more than trimming seats in each product separately, because it can also remove the support and admin cost alongside the license.
  • Match the license metric to how the business counts. When the contract counts devices, cores or transactions and the business thinks in people or sites, a metric change can remove a cost driver that no seat count will fix. Ask for the change in writing at renewal.
  • Negotiate renewals with measured use. Bring consumption data into the renewal conversation so the quantity reflects use rather than the peak year. Start before the notice date, because a late start leaves the vendor with the stronger position.

The first two techniques target spend on access or features that nobody uses. The last three change contract terms or the tool estate, so they need agreement from procurement and the product owners before anyone acts on them. Test the simpler changes first, and let the evidence decide how far the rest go.

For the wider picture, read the software license optimization guide. Teams that want help running the inventory and renewal work can look at the software licensing and optimization service. On the platform side, the Software Asset Management Professional guide covers the reclamation features, and the integration patterns page shows how usage data reaches the analysis.

Software license optimization needs a fixed usage window and a written cut-off before any seat is reclaimed

A license is idle when nobody has used it across a full billing cycle, and the cut-off that defines idle should be agreed before anyone pulls usage data. Choosing the window and the threshold after the numbers arrive is a common way for reviews to end in argument rather than savings.

Start with the window. It has to cover the product’s busiest normal period. A finance tool that only sees heavy use at month-end will look idle if the review runs mid-month. Measure across one full cycle at minimum, and extend the window when the product has a known peak. Record the dates it covers so the same logic can be rerun at the next renewal.

Next, define what counts as use. A sign-in is rarely real evidence of use for an expensive product. Many teams settle on a rule such as at least one action inside the product, and apply it to every product in the same way. A mixed rule makes the comparison meaningless.

Then agree the cut-off with the business owner in writing. For example: a named seat with no recorded activity in the window is a reclaim candidate, unless the owner gives a reason to keep it. The software asset compliance workflow approach shows how that approval can be routed, so removal decisions do not depend on whoever holds the spreadsheet.

Some mistakes come up repeatedly. Reviews that count installations instead of active people keep paying for machines nobody uses. Reviews that skip the entitlement records miss the case where the contract allows more than the team has installed. Check where your release keeps the entitlement counts, then compare them against the software model records.

  • Set the window to cover one full cycle plus any known peak.
  • Use one activity rule for every product.
  • Agree the cut-off and exception reasons before data is pulled.
  • Record each decision and its approver against the seat.

Once the window and cut-off are fixed, the first pass produces a list people can act on. Usage counts are only as reliable as the asset records they match against, so the CMDB and ITAM data work should come first where those records are weak.

Four account types to exclude before a reclaim list is final

A reclaim list built from last-login data is a list of candidates, not a list of seats to remove. Before any seat leaves it, take out the accounts that look idle but belong to work that is still going on. Each group needs its own rule, because a sign-in count measures the wrong thing for every one of them.

  • Integration and service accounts. They act through the API, so interactive sign-ins can stay near zero even when they run every day. Classify them by the job they do and review them as a separate class, outside the seat rule.
  • Shared logins. One account used by a team looks busy or idle depending on who signed in last. Confirm whether the login serves several people. If it does, the question of named accounts is a licensing decision for the owner, not a cleanup step.
  • Leavers. A seat held by someone who has left is an offboarding gap, not a saving. Route it through the offboarding process so the account and its records close in one step.
  • People on fixed-term absence. A secondment, long leave or a seasonal role can look idle for a full cycle and return within the year. Ask the line manager for a return date and keep the seat until that date has passed.

The four groups share one pattern: the decision depends on a fact the usage data does not hold. Ask for that fact before the rule runs. Record the reason for every exclusion against the seat, with the name of the person who gave it and the date. The next review then starts from accounts that have already been checked.

Test the rule on a small group before it reaches the whole estate. Choose one product and one business unit, reclaim a small batch, and wait a week for complaints. A complaint in that week usually means a group was missed from the exclusions, and that is far cheaper to find on a small batch.

The matching step matters as much as the rule. A reclaim is only as accurate as the link between the user record and the asset record, so clean those records before the first batch. The offboarding controls set how leaver accounts are closed, the CMDB data quality work keeps the records that usage is matched against accurate, and the asset lifecycle service covers how those records stay current.

Maximise ServiceNow license investment: check usage and applications before renewal

You save money on a ServiceNow licence by matching what you pay for with the people and applications that actually use the platform, and you do that before the renewal date rather than after it. The drift often sits in the user count and in applications that are switched on but unused.

Start with the user records. Check how your agreement defines a counted user before comparing seat numbers. Pull active users for one full cycle, then set those counts against the order form. A gap in either direction is a finding. Idle work access costs money, and active users without the matching entitlement are a compliance exposure.

Next, list every licensed application against a named business owner and a last-used date. Where no owner can describe a use, it becomes a candidate for removal, provided the decommission steps are written down first.

A first pass usually follows four steps:

  • Pull active users for one full cycle, using one activity rule throughout.
  • Match those counts to the order form and every amendment, because amendments can change the count without changing the summary.
  • List each licensed application with its owner and last-used date.
  • Note the renewal and notice dates, and agree target quantities with the business before the vendor conversation begins.

The common error is treating the order form as the full record. Amendments and added applications change what you hold, so the register has to be rebuilt from the contract history. A review that skips that step can cut the wrong thing at renewal. For the licensing and cost factors that apply to one add-on, read the Integration Hub licensing and cost factors article. The ServiceNow health check and assessment page describes a wider platform review, and the link between platform spend and results is set out in how to turn ServiceNow investment into realised value.

Frequently asked questions

How much time does license optimisation take?

An initial audit takes longer for larger portfolios. Ongoing optimisation (quarterly or annual review) is lighter. Factor in time for vendor negotiations and implementation of changes.

What if a department refuses to give up a tool they like?

Involve them in the analysis. Show the cost and usage. Sometimes the tool provides value that justifies the cost. Sometimes a cheaper alternative exists. The goal is informed decision-making, not cost-cutting at any cost.

Can License Optimization work with SaaS and cloud tools?

Yes, often better than on-premise software. SaaS usage is easier to track (login counts, API metrics). Cloud platforms (AWS, Azure) provide detailed usage data. Use this data to right-size cloud subscriptions.

Talk to Oblytech

Planning, running or fixing a ServiceNow programme? Tell us where you are and we will suggest a sensible next step.

Contact us