ServiceNow Software License Optimization Requirements Workshop Questions

A software license optimization requirements workshop is a structured session that turns a set of questions into decisions a program can act on. The questions cover installed base visibility, licensing metrics, renewal dates, usage evidence and product ownership. The page helps a program lead decide who must attend, what to collect beforehand and the agenda order.

Current Software Landscape and Asset Visibility

Start by establishing what software is currently deployed and how it is tracked. Questions to explore: What software applications does your organization use? Where is this software deployed (which departments, locations, or business units)? Do you have a current inventory of installed software, or do you rely on discovery to build it? What is your level of confidence in your current software inventory? Are there applications you know are running but are not captured in your asset database?

Answers to these questions define the scope of license optimization. Organizations with poor visibility into their software deployment often pay for licenses that are not being used. Discovery tools can help build an accurate baseline, but discovery requires network access and may discover licensed and unlicensed software alike.

Licensing Model and Cost Structure

Understanding how you currently pay for software is essential to optimization. Questions include: What licensing models does your organization use (per-seat, per-concurrent-user, subscription, perpetual, cloud-based)? How is each application licensed, and what are the usage metrics that drive cost (CPU cores, users, transactions, storage)? What is your current annual software spending, and how is it distributed across applications? Do you have visibility into license terms, renewal dates, and cost escalation clauses?

The answers reveal opportunities to reduce cost. Some applications can be right-sized from concurrent-user licensing to named-user licensing if usage patterns support it. Subscription models may be more cost-effective than perpetual licenses if you do not use the software long-term. Volume discounts or enterprise agreements may apply if spending is high enough.

Usage Patterns and Utilization

Many organizations pay for software that is installed but underused. Questions to ask: How many licensed seats or instances are actually in active use? Which applications have high adoption and which are rarely used? Are there applications being paid for that could be consolidated or replaced? What is the adoption trend for each application—growing, stable, or declining?

Answers to utilization questions identify redundancy and waste. If two applications serve overlapping purposes, consolidating to one reduces cost. If adoption is declining, renegotiating terms or switching to a pay-as-you-go model may save money.

Compliance and License Audit Risk

Software audits can result in significant unexpected costs if you are not in compliance. Questions to explore: Are you confident that your software deployments comply with license terms? Have you experienced a software audit, and if so, what was the outcome? Do you have processes to track compliance with usage-based licensing terms? What would be the financial impact of a licensing audit that found non-compliance?

Understanding audit risk helps prioritize optimization efforts. High-risk applications should be addressed first. Compliance tools and processes reduce audit exposure and can uncover legitimate savings.

Procurement and Contract Management

How software is purchased affects long-term costs. Questions include: Who makes decisions about software purchases? Is there a process to evaluate alternatives before selecting software? Are volume discounts or enterprise agreements negotiated, or are standard prices paid? How often are license agreements reviewed and renegotiated? Are there opportunities to consolidate purchases across departments to improve terms?

Answers reveal whether procurement is coordinated or fragmented. Centralized procurement with enterprise agreements typically yields better pricing than independent department purchases.

Cloud and SaaS Optimization

As organizations move to cloud and SaaS models, optimization takes different forms. Questions to explore: What portion of software spend is for cloud or SaaS applications, and what portion is perpetual licenses or subscription software running on-premises? Are there opportunities to move on-premises software to the cloud to reduce maintenance and licensing costs? Are cloud subscriptions being optimized for actual usage, or are you paying for unused capacity?

Cloud offers flexibility but can be wasteful if not managed. Overprovisioned instances, unused accounts, or stalled projects generate unnecessary spend. Regular reviews of cloud usage ensure you pay only for what you use.

Governance and Approval Process

Without governance, software spending grows unchecked. Questions to ask: Is there a process to approve new software purchases before they are acquired? Who has authority to purchase software? Are there standards or preferred alternatives? How are software assets tracked and decommissioned when no longer needed? Is there a process to regularly review active licenses and remove unused ones?

Governance creates accountability. A software approval board can review new requests, identify opportunities to use existing software, and enforce standards. Regular license reviews catch unused software and free up budget.

Integration and Platform Consolidation

Optimization often includes consolidation around core platforms. Questions to explore: Could some of your software be replaced by capabilities in ServiceNow or another core platform? Are there opportunities to integrate software instead of replacing it? What would it cost to consolidate, and what would you save? Which applications are strategic and which are tactical?

Platform consolidation can be a long-term strategy, but it often yields significant savings and operational simplicity.

Key Warning Signs to Address

Look for these patterns in your current state: unused or rarely-used software that is still being paid for; multiple applications serving the same purpose with overlapping functionality; high-cost licensing models that do not match your usage patterns; fragmented procurement across departments with no centralized oversight; audit findings indicating non-compliance with license terms; or rapid growth in software spending with unclear ROI.

Turning a workshop into decisions the program can act on

Workshops on license optimization often fail in one of two ways. Either it produces a long list of observations that nobody owns, or it produces a tidy document that agrees with whatever the most senior attendee already believed. The aim of the session is narrower. By the end of it, the team should know which decisions are unblocked, which are waiting on data, and who is accountable for getting that data. Written for the program lead or analyst who runs the session and then has to turn the notes into a backlog. For the broader program context, the software license optimization overview explains how the pieces fit together.

Before the room: who must attend and what to collect

Much of the value is lost when the right people are missing. Finance must be present for any question about cost base and renewal timing, because nobody else can say which invoices are real. Procurement owns the contract wording, including the clauses on change of use and true-up. The people who run discovery and the owners of the installed base need to sit in on the visibility section, since they know which blind spots are structural and which are simply untidy. Ask each attendee to bring two artefacts: the renewal notice for their largest software agreements, and the list of tools their team pays for through personal cards or expense claims. The second list is often the first sign of spend that never went through procurement.

Send the question list out in advance but keep the scoring sheet back. Attendees who prepare their answers tend to answer honestly. Attendees who see how the answers will be scored tend to answer for the score.

A decision table for each question area

The table below keeps the session pointed at decisions. Each question area only earns its place in the agenda if the decision in the second column is written down before the meeting ends, and the evidence in the last column is requested before anyone signs off.

An ordered agenda for running the session

The order matters. Questions about cost mean little until the team agrees what is installed and what is contracted, so the agenda should follow this sequence.

1. Confirm each data source and its known gaps before anyone discusses savings.
2. Agree the licensing metric for the largest agreements, one contract at a time.
3. Place every notice date on one calendar and name the owner of each date.
4. Walk through usage evidence for each product and mark it as sufficient, partial or missing.
5. Record every open question with an owner and the date its answer is needed.
6. Read the decisions back aloud and ask whether anyone would dispute them in front of finance.

Questions that reveal the real scope of the program

Some questions sound routine but change the size of the whole effort. Ask whether any software is bought through a cloud marketplace subscription that never passes through the procurement workflow. Ask whether any agreement charges for usage above a level that nobody is monitoring. Ask which products came in with an acquisition and whether those contracts transferred cleanly or still sit with the former owner. Ask whether developers or data teams run licensed tools on personal or team accounts. Each answer tends to widen the inventory, and it is far cheaper to learn that in a workshop than during a vendor audit. Teams that have acquired a business often find the same problem in a different form, which the asset lifecycle discussion covers from the hardware side.

How to tell whether the workshop worked

A good workshop leaves behind a short decision log, a named list of data gaps and a date for the next review. It does not produce one agreed figure for total software spend. That figure is often unavailable at this stage, and a team that insists on it often invents one. A poor workshop ends with enthusiasm and no owners. If the notes contain phrases such as “we should look into” with no name beside them, the session has not finished its job. The gaps it leaves should later be checked against the testing and acceptance checklist, so that the answers recorded in the room are the ones the system is later tested against.

When a session for the whole estate is the wrong format

Do not run a program-wide workshop when the question is narrow. If the only issue is one vendor renewal with a short notice window, a focused meeting with procurement, finance and the product owner will do more good than a session for the whole estate. Also avoid holding the workshop before discovery has produced any data. Without a baseline, attendees argue from memory, and the most confident memory wins. In that case, run a short data review first and schedule the workshop for when there is something concrete to test against.

Frequently asked questions about running the workshop

How many people should sit in the decision group?

Keep the decision group small enough to reach a position in one sitting. Bring specialists in for the sections that need them and let them leave once their section is closed. A room where every attendee holds a veto often decides nothing.

Should the business sponsor stay for the whole session?

The sponsor should open the session and return for the final read-back. Sitting through the detailed metric discussion adds little, and sponsors who stay often reopen points the team has already closed.

What happens to questions that nobody can answer on the day?

Log each one with an owner, the system that should hold the answer and the decision it blocks. A question that blocks nothing can wait. One that blocks a renewal needs a date attached to it.

Can one question set be reused for every software product?

Reuse the structure but rewrite the wording for each product. The metric question for a per-core database is different from the one for a named-user collaboration suite, and generic wording produces generic answers.

How soon after the workshop should changes begin?

Start with decisions that need no new data, such as correcting a known duplicate record or confirming who owns a renewal. Anything that affects users or contract terms should wait until the evidence checks are complete.

Next step

If the estate spans several business units with different contracts, scoping the session before invitations go out keeps it to the decisions that matter. The asset management consulting service page describes how an engagement typically begins, with a review of the current state.