OBLYTECH Logo
OBLYTECH Logo
ServiceNow License Optimization Best Practices

ServiceNow License Optimization Best Practices

Software license optimization techniques for ServiceNow come down to five moves: measure what you actually use, track installations against each license, categorize products by business impact, renegotiate renewals on real usage, and consolidate overlapping products. The sections below take them in that order, with the checks that stop a bad count from driving a bad decision.

Audit Your Current License Consumption

The first step in license optimization is measuring what you actually use. Many organizations discover they are paying for licenses that nobody has activated, supporting software versions that ran out of support years ago, or maintaining license agreements with volume commitments they often fall short of. The problem starts with incomplete data: if your CMDB does not track software CI relationships to servers, or your asset management system does not link licenses to installed software, you cannot see the full picture.

Start by querying your asset management data to count installed instances of each application by version, operating system, and department. Cross-reference this against your license agreements. You may find that you are licensed for 500 users of an application but only 50 are active, or that you have 10 maintenance licenses for an operating system you deprecated three years ago. For each discovery mismatch, contact the vendor to understand your true compliance position. In many cases, vendors allow you to adjust license terms at renewal, or to track down licenses you thought you had but could not locate.

Implement Automated License Tracking

Manual license tracking via spreadsheets breaks down quickly when you have dozens of vendors and hundreds of products. Automated tracking through your CMDB and asset management system helps make each software installation visible, linked to a license agreement, and flagged if it exceeds your entitlements. ServiceNow’s Software Asset Management application takes software installation data from ServiceNow Discovery and software usage data from Microsoft SCCM once an SCCM usage plugin is installed (those plugins are slated for deprecation, and first-time SCCM integrations are directed to the Service Graph connector for Microsoft SCCM), and checks it against your license entitlements, so that you can see license status at a glance.

Configure your software discovery tool to scan all servers monthly and import results into the CMDB. Link each scanned installation to the matching license record in your asset management database. Set up a rule that flags any installation without a matching license as a compliance risk. Create a dashboard that shows license utilization by vendor: if you have 100 licensed seats and 40 are used, that excess capacity is a candidate for renegotiation or reallocation. Update license records when you purchase or retire software so that your CMDB stays the working record of what is installed.

Categorize Licenses by Business Impact

Not all software licenses have equal value to your business. Critical applications that support revenue-generating functions deserve careful management and maintenance, while desktop utilities used by one team may be candidates for removal if they are expensive or create compliance liability. Treating all licenses the same leads to poor decisions: you might reduce spending on critical systems while maintaining expensive tools that deliver minimal value.

Classify software into three categories: critical (requires vendor support, full security patching, compliance tracking), standard (monitored but not mission-critical, can operate with delayed patches), and optional (nice-to-have, minimal support requirements, candidates for removal if budget is tight). Document the business driver for critical software: which services depend on it? Which teams use it? How would an outage impact revenue or operations? Use this categorization to guide your budget allocation and negotiations with vendors.

Negotiate Renewal Terms Based on Actual Usage

License agreements typically include automatic renewal at the previous year’s committed level unless you actively negotiate changes. If you have not audited usage, you renew for what you bought last year, not what you use this year. Vendors count on this inertia; many organizations renew without a detailed usage review.

Three months before each renewal, run a full usage audit against that vendor’s licenses. If you have 200 licenses but only use 60, request a reduction in your renewal commitment. If you use more licenses than your current agreement allows, you have negotiating power to request volume discounts or true-up provisions. Many vendors offer usage-based pricing models as an alternative to seat licensing; if your usage is variable, a usage-based model might be more economical than a fixed seat commitment. Involve your procurement team and vendor management so that the technical usage data informs your business negotiation.

Plan Software Standardization and Consolidation

Many organizations run multiple products that solve the same problem, often due to departmental autonomy or historical acquisitions. One team uses Product A for data analysis, another uses Product B; both products solve the same need but you pay for both. Over time, these overlaps create duplicate licensing costs and team confusion.

Annually review your application portfolio and identify duplicate functionality. For each overlap, assess the cost of standardizing on one product versus the cost of maintaining both. Consider training costs, data migration costs, and team preferences alongside license costs. Make a business decision: consolidate if the savings justify the migration cost, or maintain both if the standardization cost exceeds the license savings over the next three years. Document your standardization decisions in your IT strategy so that new projects use approved products and do not introduce new overlaps.

An operating rhythm that survives busy quarters

License practice often fails in the quarters when everyone is busiest. A good practice on paper gets dropped the moment a launch or a budget round arrives. The way round this is to split the work across cadences, so that each cadence asks a different question and none of them needs a full review every time. The table below sets out a rhythm that a small team can keep.

Cadence Question it answers Owner Output kept
Monthly Has any count moved outside its expected band? License register owner A short exception list with a named action per line
Quarterly Which products are under-used or over-run, and what changed in contracts? License owner with a finance partner A decision log entry for each product reviewed
Before each renewal Does the entitlement still match what the business expects to use? Procurement with the product owner A usage summary and a negotiating position
Annually Is the portfolio still the right shape? IT leadership and finance A revised list of products to keep, merge or retire

The point of the rhythm is not the meetings. It is that each cadence produces a written output that the next cadence can read without rebuilding the context from memory.

A minimum standard for every license record

Records that are reviewed on this rhythm need to be complete enough to review. A record without an owner cannot be challenged. A record without a counting metric cannot be compared with installations. A record without a source date cannot show whether it is current. Set a short minimum standard, and treat a record that fails it as an open item rather than as a valid entry.

  • A named owner who answers for the figures, not only for the product.
  • The counting metric from the agreement, written in the words the vendor uses.
  • The source and date of the quantity, so that a reviewer knows whether it reflects a contract or an estimate.
  • The end of the commitment and the notice period for changing it.
  • A link to the decision log entry that last changed the record.

The CMDB data quality rules article describes the same discipline applied to configuration records, and it is a useful model for building checks that run without a person having to remember them.

Practices that look right and underperform

Some common practices are sound in principle and weak in use. Recognizing them early saves a review cycle.

  • A quarterly usage report that nobody has the authority to act on. The report is accurate and changes nothing, because the decision owner is not on the distribution.
  • A renewal calendar kept in one person’s diary. It works until that person is away during the notice window.
  • Utilization targets set as a single figure for every product. A product used in short bursts can look idle on an average, while a steady tool may be correctly sized at a high level.
  • A large clean-up done once a year. The register drifts back between clean-ups, and the next review starts from a worse position than the last one ended.

Each of these is fixed by attaching the practice to a named owner and an output, rather than by adding more reporting.

A monthly review run in a fixed order

  1. Check that the usage and installation feeds ran, and note any that did not, before reading any figure.
  2. Pull the exception list for counts that moved outside their expected band.
  3. For each exception, confirm the metric and the source before deciding what the movement means.
  4. Assign one action and one owner to every exception that survives the check, and close the rest with a reason.
  5. Record any change to a contract, quantity or owner in the decision log on the same day it is agreed.

Running the checks in this order matters. Reading a figure before confirming its feed is how a missing extract becomes an apparent saving that nobody can later explain.

How many products should a monthly review cover?

Cover the products that carry the most cost or the most compliance exposure first, and rotate the remainder across the quarter. A monthly review that tries to cover everything in full often covers nothing well.

Does the rhythm need a dedicated tool?

No. A register, a log and a calendar are enough for a modest estate. A tool helps once the manual checks start to take longer than the decisions they support.

Who should be on the quarterly review?

The license owner, a finance partner and the people who manage the largest products. Add a product owner only when a decision about that product is due, so that the meeting stays focused.

What shows that a practice is working?

Its outputs are read by someone who acts on them. If the decision log grows but no entries lead to a changed contract or a closed exception, the practice is generating paperwork rather than control.

When a rhythm is in place but its outputs go unread, the gap is often ownership rather than effort.

Related guides: ServiceNow IT Asset Lifecycle Management Best Practices.

Choose the action for each license gap before the renewal date arrives

A license gap has one of three fixes: reduce the commitment, reallocate the entitlement to where it is used, or buy more. Which one applies depends on whether the gap is a surplus or a shortfall, how long it has lasted, and how much notice the agreement requires before the commitment can change. Make that decision for each product on its own, and make it while there is still time to act.

Confirm the gap is real before deciding anything. A surplus caused by an installation feed that missed a server, or a shortfall caused by a duplicate record, sends the negotiation in the wrong direction. Check the counting metric against the wording of the agreement, check the date the quantity was taken, and only then compare the confirmed count with the entitlement.

The table sets out the usual first move for each situation and the check to make first.

Situation Usual first move Check before acting
Surplus that has held for at least two monthly reviews Reduce the renewal commitment Notice period and any minimum volume the agreement sets
Surplus that follows a project or a seasonal peak Reallocate the licenses to another team or product Whether the peak falls inside the same contract term
Shortfall on a confirmed count Buy the difference, or true up at renewal What the agreement says about buying mid-term
Shortfall on a disputed count Hold and re-verify before any purchase The installation records behind the disputed figure

A surplus that has shown up in one quarter is weak evidence. Use consecutive monthly reviews from the rhythm described above before cutting a commitment, because a single quiet month often reflects a release cycle or a holiday rather than a changed need.

Write the decision into the decision log on the day it is agreed, with the product, the quantity, the date and the reason. The next quarterly review can then see why a product was reduced without anyone rebuilding the story from memory. The software license optimization guides and services cover how this fits into a wider program. Where license data needs to flow from discovery into the record, the integration patterns for license data set out the options. If you want someone to run the reviews and the renewal work, the software licensing and optimization support is the service for that.

Software License Optimization Depends on the Metric You Are Charged On

Software license optimization works best when the lever matches the way the vendor counts your use. Named-user seats, concurrent sessions, core counts and tiers each need a different fix, so read the counting metric in the agreement first. The table gives the usual first move for each one.

Counting metric What it counts Usual first move
Named user People entitled to log in, active or not Remove leavers and unused seats, then reduce the commitment
Concurrent user Sessions open at the same moment Size the pool to the measured peak
Core or processor Processing capacity on the hosts running the product Consolidate hosts, then reassess the core allocation
Consumption or tier Measured use or the plan level chosen Compare the tier with peak demand

Named-user seats are tied to a person, so much of the saving can sit in the people data. If the HR feed and the license register disagree about who still holds a role, the register will overstate the need. Clean up leavers and transfers first, then count what remains. For the wider process, see the software asset management guides.

Concurrent pools are measured by peak, not by head count. A large user list can share a small pool when the users never log in together. Measure peak simultaneous use across a full cycle that includes month end, because a short peak sets the number you need. The CMDB metrics that matter for installation counts show how to track the installation side.

Core-based products count hardware, so the saving usually comes from the hosts. Consolidating onto fewer servers reduces the core count only if the allocation is reassessed afterwards. Check which hosts run the product, how many cores are assigned, and which core factor the agreement applies to the processor type, against your own contract rather than a summary.

Consumption and tiered models charge for measured use or a plan level, so the lever is the tier. A tier larger than your peak is a candidate for downgrade at the next term. Keep the usage record current between renewals with software asset compliance workflows, so the decision rests on more than one quarter of data.

Reducing ServiceNow License Spend by Reclaiming Dormant User Licenses: Finding Accounts That Have Not Logged In

A dormant ServiceNow user is an active account that has not signed in for longer than the inactivity window agreed for its role. Reclaiming those seats takes three steps: find candidates from login data, check each one against the people who should still hold it, and only then remove or reassign the entitlement. Much of the effort sits in the first two steps, because a list built from one report flags legitimate but infrequent users as well.

Start with the last-login date. Build a report on the user records showing the account name, active status, roles and department, with the last login date where the instance records it, filtered to active accounts and sorted oldest first. Identity Center login history keeps records for 30 days, so use it to confirm recent sign-ins rather than to judge a longer dormancy window.

Set the inactivity window by role, not as one figure for the whole estate. A frontline agent who has been quiet for a few weeks is a strong candidate. A finance approver who signs off only at quarter end can look dormant for most of the year and still be needed. Frontline roles usually need a shorter window than periodic ones, and the role owner should agree the figure in writing.

Keep an exception list before removing any seat. Seasonal and contract staff should carry an expected return date. Break-glass and emergency administrator accounts should be excluded by name and reviewed on their own schedule, because they are meant to sit unused. Service and integration accounts are not people and may not count against named-user seats, so check the agreement’s wording.

Run the report monthly and feed its exceptions into the monthly review, so each candidate has one owner and one action. Alert on the count of dormant accounts in a role rather than on every idle user, because a rising count is a useful signal and a constant stream of alerts gets ignored.

The cleanest reduction comes from stopping accounts going stale. A leaver feed from HR should disable the account on the leaving date. The report then catches what the feed misses, such as contractors, transfers and managers who never raised the change. The controls for a clean leaver handover cover the handover side of that feed.

How to Read a ServiceNow Renewal Quote That Costs More Than Last Year

A renewal quote that comes in above last year’s total has one of three causes: the quantity moved, the unit price moved, or the counting metric changed. Split the quote into those parts before you reply to the vendor. Multiply the confirmed count from your register by the unit price on the quote, then compare that figure with last year’s total. If the quantity matches your records, the rise is a price or term change, and the next question is which clause in the order form sets it.

Ask the vendor to state the basis of any increase in writing. Ask whether it is a fixed uplift, a change to list price, or a term change, and whether it applies at renewal or part way through the term. File the written answer with the decision log entry for that product, so the next review can see why the figure moved.

What changed on the quote First question to answer Usual response
Quantity rose, unit price flat Is the confirmed count above the entitlement? Verify the count, then decide on the gap
Unit price rose, quantity flat Which clause sets the change, and when does it apply? Get the basis in writing and check it against the term
Counting metric or tier changed Does the new unit match how the product is used? Model both metrics against measured peak before accepting
Quantity and price both rose Which part is the business need and which part is price? Reduce the quantity first, then negotiate the unit price

Watch the metric closely. A move from named users to a tier, or to any other counting basis, can look like a price rise when the thing being bought is different. Compare like with like before you judge the number. When the quote adds Integration Hub or another add-on, check its entitlement on its own rather than against the bundle total.

Should you accept a higher renewal before the need is confirmed?

Not on one month’s figures. A quote is a prompt to check, not a reason to commit. Use consecutive monthly reviews to confirm the need, and where the notice period is short, ask the vendor for a written extension while the count is finished. Renewing on last year’s terms by default is the outcome to avoid. A value review shows whether the spend still earns its place.

Fulfiller roles held by requesters are worth checking against the seat count

A person who holds a fulfiller role but only raises and tracks their own requests may be occupying a seat the work does not need. Finding these grants can help trim a ServiceNow license count without changing how the people who do the work operate. Whether the count follows the roles a user holds or the tasks they complete depends on the agreement, so confirm on your own contract and release which roles count.

Role grants drift in a predictable way. Three common patterns lie behind grants that do not match the job:

Pattern What usually happened First check
Project role kept after the project closed Access outlived the work it was granted for Compare the grant date with the project end date
Manager given a working role for visibility A reporting need was met with task access Confirm whether reports or dashboards would cover it
Contractor copied from a permanent colleague Roles were often not scoped to the contract Compare the grant list with the contract scope

Someone in this position may sign in regularly, so a last-login report can miss them. Start with an export of users, their role grants and the grant dates. For each person holding a fulfiller-type role, ask whether they have worked a task in the last quarter, whether the job requires it, and whether the grant is tied to something that has ended. A no to the first two questions makes them a reduction candidate. Hold the change until the role owner agrees, since an approver who completes tasks in the queue is not a requester. Settle who may grant and remove roles under the platform operating model before the first change is made.

Reduce the grant rather than deleting the account. Removing the role changes what the person can access, so note the grant before removing it in case the need returns. Log each change in the decision log with the role, the person, the date and the reason. Where the access rules are unclear, the security and risk governance work sets the baseline. For an estate that has grown untidy, see the health check and audit page.

Frequently asked questions

How often should we audit software licenses?

Audit regularly, aligned with your renewal cycles. If you make significant infrastructure changes (migration, decommissioning, acquisition), audit promptly after the change to catch license impact. Track changes throughout the year so the annual audit is a confirmation, not a discovery process.

What should we do with unused license seats?

Investigate first: is the seat truly unused, or are users just not reporting their usage? If it is unused, contact the vendor at renewal to negotiate a reduction. Some vendors allow license sharing or concurrent use models that reduce seat requirements. Document your decision to reduce seats so you do not accidentally repurchase them later.

How do we handle software that changes functionality between versions?

Track version-specific license terms because older versions may have different entitlements or support terms than current versions. When planning a major upgrade, confirm that your current license agreement covers the new version at the same or better terms. Renegotiate before the upgrade if needed.

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