Why Everyone Is Talking About Consumption-Based Licensing (And You Should Too)

Why Everyone Is Talking About Consumption-Based Licensing (And You Should Too)

When software costs depend on what your platform does, not just who can access it, usage evidence becomes a financial control. For ITAM and SAM leads, CIOs and ServiceNow platform owners, that changes the work: you need to understand how activity is measured, what drives consumption and whether your data can support a renewal conversation.

The shift is already tangible in ServiceNow’s Now Assist model. ServiceNow describes an assist as a billable unit, with consumption calculated using the action taken and the relevant skill’s assist ratio. That puts a new question beside the familiar entitlement check: can you explain, with reliable evidence, how your estate is using what it has bought?

Consumption-based licensing is not one pricing model

Seat-based licensing gives organisations a relatively familiar starting point: count users, assign entitlements and compare access with the contract. Consumption-based pricing changes the unit being measured. Depending on the product and agreement, a metric might relate to subscription units, capacity, transactions, API calls, credits, tokens or AI actions.

In practice, many offers combine models. A base subscription may sit alongside a usage allowance, a capacity limit or charges for consumption above an included pool. This hybrid structure can provide flexibility, but it also makes it harder to understand total cost by looking at user counts alone.

The distinction matters in a ServiceNow estate. A workflow might be used by staff through the platform, triggered automatically by a system integration, or powered by an AI skill. Those activities do not necessarily map neatly to a seat. The precise billing unit and rules depend on the relevant product and contract, so do not assume that one metric or entitlement model applies across the platform.

Flexera’s overview of the shift towards hybrid SaaS pricing describes how usage measures such as tokens, credits and compute units are becoming part of software pricing. For platform owners, the implication is practical: licensing governance must keep pace with how work is actually executed.

Why ServiceNow usage evidence deserves attention now

ServiceNow’s guide to monitoring Now Assist usage in Subscription Management explains how organisations can view consumption across instances and examine usage by skill. It says that actions are converted into assists using a skill-specific assist ratio. It also notes that production and sub-production environments both count towards the total pool, while demo and evaluation instances are excluded.

That detail has direct operational consequences. Testing in development and test environments can draw on the same pool as production. Custom skills and workflows may also need to be correctly mapped for their consumption to appear as expected. If teams only review a top-level allowance, they may miss where usage is accumulating or whether the reported breakdown is complete.

The guide also notes that some detailed, skill-level visibility requires data sharing to be enabled, and that usage alerts are not currently available there. That makes active governance important: teams should decide who reviews consumption, how frequently it is checked and what action follows when usage trends away from the plan.

A key change: when usage becomes part of the pricing basis, monitoring is not just operational reporting. It is part of cost control, contract governance and audit readiness.

Five governance questions to answer

A consumption metric can make the link between activity and cost more visible. It can also expose gaps that a seat-based view does not reveal. Before expanding use or negotiating a renewal, answer these questions:

1. What exactly is the meter? Confirm the contractual unit, how it is counted, when it resets and what is included in the base entitlement. Get clarity on overage treatment and any exclusions.
2. Which activity counts? Establish whether production, sub-production, integrations, custom workflows and AI-enabled processes contribute to consumption.
3. Can you reproduce the figures? Identify the system of record, reporting period, data ownership and method for reconciling the vendor’s usage view with your own evidence.
4. Who owns the decision? Assign accountability across platform operations, ITAM or SAM, procurement and finance. Operational teams need practical visibility, while leaders need an explainable forecast.
5. What happens when demand changes? Agree how you will respond to a spike, a new workflow, a change in AI adoption or an unexpected variance between internal and supplier reporting.

These questions help organisations avoid two common assumptions: that a seat-based baseline will still describe their exposure, and that a vendor dashboard alone provides enough evidence for internal control.

The risks to manage before the bill arrives

Unpredictable spend. Consumption can vary with workflow volumes, business cycles, automation and AI adoption. A quiet month may not predict a peak period. Forecasting only from current usage can leave budgets exposed when demand changes.

Metering disputes. If your team and supplier use different definitions, periods or reporting views, reconciling a charge can become difficult. Contract language should clarify how consumption is measured and what evidence each party can access.

Data quality becoming a cost issue. Incomplete mapping, inconsistent reporting or unclear ownership can make it harder to explain the usage figure. For regulated organisations, that is not only a budget concern. It can affect auditability and confidence in approvals.

Dormant entitlements becoming less obvious. A consumption view does not automatically show which paid capabilities are unused. If teams focus only on total usage, low-activity entitlements or services that no longer support a business need can be overlooked. Keep entitlement reconciliation alongside consumption monitoring.

A practical preparation checklist for your ServiceNow estate

Start now, even if your current contract remains primarily seat-based. Building these controls before a pricing change or renewal gives ITAM, procurement and platform teams a stronger evidence base.

1. Record your current entitlement baseline

Capture the products and capabilities you have purchased, the relevant contract terms, renewal dates, included units and any usage allowances. Record who owns each subscription and where the entitlement evidence is stored. This gives managers a dependable reference point and helps platform teams understand what they can safely adopt.

2. Instrument usage evidence

Decide which ServiceNow reports, Subscription Management views and internal records will support your consumption review. Document the reporting period and metric definitions. Check that the activity you expect to see is visible, particularly for custom workflows, AI skills and non-production instances.

3. Map workflows to possible meters

Create a practical inventory of workflows that could drive measured activity. Include automated processes, integrations and AI-enabled use cases, not only transactions initiated directly by an employee. Work with platform owners to identify likely volume drivers and establish who will review changes before they are deployed at scale.

4. Pressure-test variable demand

Model more than one scenario. Consider normal demand, a seasonal or operational peak, and an adoption case where a workflow or AI capability becomes popular. Include the assumptions behind each forecast and identify what level of variation would prompt a budget review.

5. Negotiate for evidence rights

Before signing or renewing, clarify how you can access consumption data, how often it is updated, what detail is available and how discrepancies are resolved. Ask for contract language that makes the measurement method, audit evidence and overage handling clear. A price is only governable if you can understand how it is calculated.

6. Review the model as the platform changes

Consumption governance is not a one-off procurement exercise. New workflows, changed business volumes and expanding AI use can alter the usage profile. Schedule reviews with the platform team, ITAM or SAM, procurement and finance so that operational decisions and commercial exposure stay connected.

Turn licensing change into a governance advantage

Consumption-based licensing does not make seat-based controls irrelevant. It adds another layer: organisations need to reconcile what they own with how the platform is used, and understand how that use translates into cost. For staff, the aim is to enable useful workflows without avoidable friction. For managers, the aim is a predictable forecast, defensible evidence and clear accountability.

BGTS helps organisations strengthen ServiceNow platform governance and ITAM practices, connecting usage visibility with practical operational controls. Explore our ServiceNow services or review how we assess platform opportunities through our ServiceNow assessments. The outcome is a licensing approach that can support adoption while keeping cost and risk in view.

You already have ServiceNow. Are you getting everything you should from it?

Book a 15-minute ServiceNow operations review to identify immediate opportunities to improve usage visibility, governance and value.

BGTS
Cost Out. Hours Back. Risk Removed.
+44 20 4620 4488