OBLYTECH Logo
OBLYTECH Logo
Common ServiceNow License Optimization Mistakes and How to Avoid Them
Home / Solutions, Guides and Services / IT Asset Management: Guides and Services / License Optimization: Guides and Services / Common ServiceNow License Optimization Mistakes and How to Avoid Them

Common ServiceNow License Optimization Mistakes and How to Avoid Them

ServiceNow license optimization mistakes typically come from how licenses are counted, bought and retired, rather than from the software itself. This page walks through seven common errors, the symptom each one produces, the root cause behind it and the fix that stops it recurring.

Mistake 1: Licensing Based on Worst-Case Peak Usage

Symptom: You buy enough licenses for the peak number of concurrent users, but actual average usage is much lower. Often, you are paying for licenses you do not use. Root cause: peak usage happened once during a crunch period, and licensing was based on that peak rather than on typical usage. Fix: analyze usage patterns over months, not days. Calculate 95th percentile usage (meaning during occasional peak periods usage exceeds this level). License to that level instead of peak. Understand that occasional peaks do not justify full license purchases. Prevention: collect and analyze usage data before making licensing decisions. Track usage over time, not just snapshots.

Mistake 2: Not Tracking Installed Licenses Versus Deployed Licenses

Symptom: Procurement records show more licenses bought than the deployment records count. You are either overpaying for licenses you do not use, or the deployment process is broken. Root cause: installation and deployment are different. A license can be installed but never used. Or a license can be used without being properly installed (bootlegged or pirated). Fix: reconcile installed and deployed licenses. Identify licenses that are installed but not used and see if they can be repurposed or returned. Identify deployed licenses that are not installed and see if they are compliant. Prevention: make deployment tracking part of software provisioning. When software is installed, record it in the software asset records.

Mistake 3: Ignoring Unused Software Titles

Symptom: You maintain licenses for software nobody uses anymore. Money is wasted on maintenance and licensing for deprecated software. Root cause: software was necessary once but has been replaced. The old licenses were not decommissioned. Fix: audit deployed software. Identify titles with zero usage over a period you set. Confirm they are truly not needed, then cancel the licenses. Prevention: tie software retirement to license management. When IT retires software, the software asset records should be updated so licenses can be cancelled.

Mistake 4: Over-Buying When Negotiating Discounts

Symptom: Vendor offers a discount if you buy more licenses. You buy the bulk quantity to get the discount, then later discover you do not need all of them. Root cause: discount incentives can override good judgment about actual need. Fix: analyze total cost of ownership over the contract term. A discount that requires buying significantly more licenses might not be a good deal. Pass on discounts that require buying more than you need. Prevention: set spending authority rules: bulk license purchases require approval from someone who understands actual usage and future plans. Do not let procurement departments buy extra licenses just to hit discount thresholds.

Mistake 5: Not Automating ServiceNow License Compliance Checking

Symptom: Audits discover compliance violations (running more copies than licensed) only after vendors notice and send bills for true-ups. Root cause: license compliance was never monitored continuously. Violations accumulated without detection. Fix: set up automated compliance checks that compare deployed licenses to purchased licenses. The legacy Software License Compliance Checker colors a counter orange when it is within 5% of being out of compliance. Prevention: run the reconciliation on a fixed schedule, which Basic Software Asset Management defaults to weekly. Check license compliance at least monthly. When alerts trigger, investigate immediately rather than waiting for an audit.

Mistake 6: Consolidating Vendors Without Consolidating Licenses

Symptom: You consolidate on a single enterprise platform (like ServiceNow) but keep licensing from multiple vendors because switching would be disruptive. Over time, costs increase because you are paying overlapping vendor fees. Root cause: fear of disruption prevented migration even when it would be cost-effective long-term. Fix: calculate total cost of ownership including licensing cost. If consolidation saves more in licensing than the migration effort costs, do it. Break the project into phases to spread out disruption. Prevention: when evaluating platform consolidation, include licensing costs in the evaluation. Calculate savings over multi-year contracts, not just implementation costs.

Mistake 7: Not Using Open Source or Free Alternatives

Symptom: You pay for software for use cases where open-source or free alternatives would work. Root cause: nobody investigated alternatives because the original vendor was already chosen. Fix: audit your software portfolio. For each title, investigate whether free or open-source alternatives exist. Evaluate whether the alternative meets your needs. For cases where alternatives are viable, migrate if cost savings justify the effort. Prevention: include alternative evaluation in software procurement decisions. Do not automatically re-purchase the same vendor when contracts expire.

Prevention Summary

Optimize software licensing continuously, not just at renewal time. Track usage to drive licensing decisions. Retire software and licenses promptly when no longer needed. Consolidate vendors where it is cost-effective. Evaluate alternatives to expensive tools. Use continuous compliance monitoring to catch violations early.

Counting the unit the contract actually uses

Many compliance scares start with a counting mismatch rather than with any software being misused. A license sold per user is counted against each person, and the legacy calculation type Number of installs per user counts each installation on the hardware that person uses, up to a specified amount. A license sold per device is counted once for each installation on a machine, however many people share it. If the optimization model counts devices for a per-user product, every user with a laptop and a desktop appears to be two users, and the apparent over-deployment is an artifact of the method. The fix is to write the counting unit into the product record before any number is compared with it.

Splitting one product across two records

When an editing change, a version upgrade or a second purchase creates a new product record while the old one stays open, usage gets divided between them. Each record then looks under-used, and a reduction is proposed on a license that is in fact fully consumed. The signal is a pair of records with similar names, one of them carrying almost no use and the other carrying more than its entitlement. Merge the records only after confirming that both are covered by the same agreement, because merging across agreements hides the real position.

Trusting a vendor report without a second source

Vendor usage reports are useful and often authoritative for the vendor’s own metric. They are not automatically a fair picture of the estate. A report can omit users who sign in through a reseller account, count a service account as a person, or lag the internal record by a full billing cycle. Where the internal and vendor figures differ, the difference is the investigation. Neither figure should be adopted as correct until the reason for the gap is written down.

Reading a true-up as a failure

When an audit or a vendor count finds more use than was licensed, the instinct is to treat the result as a failure to be hidden or resolved fast. That instinct often produces the worst outcome. Under time pressure, teams buy the shortfall at list price, accept a long-term commitment they did not need, or dispute a count they had not checked. A true-up is a commercial settlement of a measured difference. Check the count first, then the contract’s terms for settling it, and only then decide whether a purchase, a re-platform or a documented exception is the cheapest honest answer.

Reducing seats in the middle of a move

A team that is migrating a product to a new platform may still see idle seats on the old one and decide to cut them. The cut is often reasonable on its own and damaging in combination with the move. The destination must hold its entitlements before cutover, and any user who has not yet moved still needs a seat. Hold reductions on products in an active migration until the cutover has passed its acceptance point.

A recovery sequence when a mistake has already been made

  1. Stop further changes to the affected products until the cause is known. A second reduction made on top of a miscount compounds the error.
  2. Record the current entitlements, counts and any changes already made, with dates. This is the baseline the rest of the work is measured against.
  3. Identify which of the patterns above explains the difference, using the table below.
  4. Correct the record, not just the figure. A corrected report with an unchanged metric will produce the same error next cycle.
  5. Brief the decision owner with the revised position and the revised saving. A saving that was never real should be withdrawn openly, since finance will otherwise plan around it.
Signal in the data Likely mistake First check
Installed count is far above or below the entitlement for one user population only Counting unit mismatch Confirm the metric on the agreement against the unit used in the count
Two similar records, one nearly idle, one over its entitlement One product split across records Compare the agreement numbers behind both records
Vendor report and internal record disagree at a steady gap Unreconciled second source List the accounts present in one source and absent from the other
A purchase was made under deadline pressure after a count True-up treated as failure Read the settlement terms before accepting the purchase figure
A seat reduction is pending on a product in migration Reduction ahead of cutover Check the cutover date against the reduction date

Can a mistake be fixed at the next renewal?

Sometimes, but a renewal is a poor moment to discover a counting error, because the commitment is already on the table. Find the metric problem before the renewal conversation starts, so the negotiation is based on a corrected count.

What is the earliest sign that the team trusts one source too much?

When a figure is quoted without its source attached. If the number cannot be traced to a named report, a dated export and a metric, it has not been checked.

Who should review counts before they reach finance?

Someone who did not build the count. A reviewer who has seen the agreement is often the strongest check, because many errors sit between the contract and the data, not inside either one.

Is a true-up always avoidable?

No. Some true-ups follow from real growth in use that nobody planned for. The aim is to make the settlement a decision rather than a surprise, and to know the cost before the count is confirmed.

A count that has already gone wrong is easier to correct when its evidence sits in one place.

Related guides: ServiceNow Software License Optimization Best Practices and ServiceNow CMDB Ownership: Assign Accountability by Data.

Optimization and Compliance Answer Different Questions in a Set Order

License optimization asks whether you pay for the software you use. License compliance asks whether you use the software you are entitled to. Both questions need the same two inputs, the entitlement and the usage, but they lead to different actions. In practice, settle compliance first so that each optimization decision rests on a count you can defend.

A compliance finding can force a purchase, while an optimization finding usually leads to a reduction. That asymmetry is why the inputs for compliance need settling before any reduction is proposed.

Question Entitlement Usage Typical action Risk if skipped
Are we compliant? Contracted counts and their counting unit Deployed and accessed use per record Buy the shortfall or document an exception A true-up at list price
Are we overpaying? Entitlement after any compliance correction Use across a full billing cycle Reduce at renewal or reassign seats Cutting seats a later audit still needs

The order matters because a reduction built on a wrong count can leave the estate short once the vendor counts it. Optimization is only as good as the entitlement baseline underneath it. The practical order runs as follows:

  1. Agree the entitlement baseline for each product: the contracted counts, the counting unit and the agreement that covers it.
  2. Reconcile usage against that baseline across the full billing cycle, and write down every gap with its cause.
  3. Close the compliance gaps first, either by buying the shortfall or by recording a documented exception.
  4. Only then look for idle entitlement, and propose reductions at renewal where the contract allows that.
  5. Repeat the reconciliation before each renewal, because a count that was right last quarter can drift by the next one.

Usage data is where this sequence often stalls. Decide how the usage feed reaches the optimization model before the first reconciliation, because the collection method decides how far the result can be trusted. The options are set out in our license optimization integration patterns.

If this reconciliation has to run every cycle, the next step is the software asset management professional guides.

ServiceNow license optimization is the decision to keep, move or retire each entitlement

ServiceNow license optimization means comparing what your contracts entitle you to run with what people and systems actually use, then deciding what to do with the gap. For each product the answer is one of three: keep the entitlement because the use is real, move it to a user or team that needs it, or retire it at the next renewal.

A decision order that tends to hold up starts with the purpose of the review: a renewal date, a budget reset or an audit notice. Next, look at use across a full billing cycle rather than one busy week. Then find out who holds the idle entitlement. A seat held by someone who has left is a retirement candidate. A seat held by someone on a three-month leave is not, and a reduction made on the first reading often has to be reversed. The ServiceNow software license optimization guides collect the related pages.

Keeping a license is often the right answer, even when it looks idle on a chart. Where a product is in steady use and the next project will need it within the term, releasing a seat and buying it back later can cost more than carrying it. Reassignment sits between the two. A seat that one group has stopped using can often move to a group that needs it, which avoids a new purchase.

  • Keep: use is steady or rising, or a project will need the seat within the term.
  • Move: use has fallen in one group and risen in another for the same product.
  • Retire: no named user has signed in across a full cycle and no migration is planned.

Two situations need a pause before any of the three. The first is a product that a team is still migrating away from. The destination has to hold its entitlements before the old seats are released. The second is a product where the vendor count and the internal count disagree. Until the reason for that gap is written down, neither figure is safe to act on.

For the review itself, see the software licensing and optimization page. When a retirement is part of a larger change, the IT asset lifecycle guides help set the end date.

A Renewal Review Works Best in a Fixed Order That Starts Before the Notice Date

A renewal review goes wrong when it starts from the vendor’s quote. The quote sets the quantity, so the team ends up deciding how many licenses to buy rather than how many it uses. A sounder approach begins with the contract terms, follows a fixed order and ends with the purchase decision.

Start with the notice terms. Find the last date for changes, whether the agreement rolls over automatically, and whether a reduction is allowed at renewal or only at the anniversary. In many agreements a reduction is easier to secure before the notice date than after it, so the calendar is part of the analysis.

Step What to confirm Mistake it guards against
1. Read the notice terms Last change date and rollover Deciding under deadline pressure
2. Confirm the counting unit Per user, per device or per core, written into each product record A counting mismatch that looks like over-deployment
3. Reconcile vendor and internal counts A written reason for every difference Trusting a single source
4. Check for split records One product held under two names on the same agreement Reducing a license that is fully used
5. Hold changes on products in a move Destination entitlements in place before cutover Cutting seats mid-migration
6. Decide keep, move or retire Measured use across the review window Buying to reach a discount threshold

Measure use over a window long enough to cover a normal business cycle. A few weeks can catch a quarter-end surge or a quiet holiday stretch. If one team uses a product heavily and another hardly at all, the answer may be a move between teams rather than a purchase.

Step two and step four need a named owner for each product record, or the reconciliation stalls. The way CMDB and ITAM records get an accountable owner is the practical starting point.

Close with one page for the decision owner stating the current entitlement, the measured use, the proposed change, the cost or saving, and the source of each count. If compliance checks are still run by hand, the software asset compliance workflows show how alerts can reach that owner before the renewal arrives.

Frequently asked questions

How do we know if we are overpaying for software?

Track usage over time and compare to licenses purchased. If you are using approximately half of purchased licenses on average, you might be overpaying. Analyze the last quarter's usage to see whether contracts are sized appropriately.

What should we do about legacy software that nobody uses?

Do not let legacy licenses continue to auto-renew. Before renewal, audit usage. If usage is zero, recommend not renewing. If the software is completely replaced, cancel proactively rather than waiting for renewal.

How do we stay compliant during licensing transitions?

Maintain compliance throughout the transition. If you are switching from one tool to another, purchase the new tool before decommissioning the old one. Run both in parallel temporarily if needed to ensure you do not violate old license terms while transitioning.

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