ServiceNow

ServiceNow Licensing Changes: AI at the Core of the Platform

ServiceNow licensing has evolved with Foundation, Advanced, and Prime — three tiers with increasing AI, automation, and agent capabilities. Learn how to choose the right model.

June 9, 2026 4MATT Insights

ServiceNow licensing has undergone a structural change: Foundation, Advanced, and Prime are the three new tiers of the platform, each with increasing AI, automation, and agent capabilities. Understanding which model fits the organization's operational maturity is the first step to renewing intelligently and avoiding unnecessary costs.

What has changed with Foundation, Advanced, and Prime?

ServiceNow has begun structuring its products and packages into three main levels: Foundation, Advanced and Prime. First, each tier incorporates AI capabilities. Furthermore, these models progressively evolve in terms of automation, agents, analytics, and governance.

The Foundation tier delivers foundational AI capabilities for insights, routine automation, and preconfigured AI skills and agents. The Advanced tier adds more sophisticated agentic workflows, productivity features, and advanced analytics. Finally, the Prime tier enables advanced capabilities, including the creation of new AI skills and custom agents, inbound MCP Server support, and AI Specialists.

In practice, this represents a significant change in how companies should evaluate ServiceNow licensing. Previously, the focus was primarily on how many users needed to access the platform. Now, the analysis includes new questions: how much AI will be used, which processes will be automated, which agents will be activated, what the expected consumption will be per business area, and which tier best aligns with the organization's operational maturity.

The official ServiceNow documentation presents a comparison between the three levels, or tiers. In addition to AI capabilities, the tiers differ in their ITIL process coverage: Change Management is reserved for the Advanced and Prime tiers, while Foundation covers basic Incident Management, Request Management, Asset Management Core, and CMDB. 4MATT prepared the table below for easier executive review:

Capability Foundation tier Advanced tier Prime tier
AI skills and routine AI agents Supported Supported Supported
Preconfigured AI skills and agents Supported Supported Supported
Agentic workflows with contextual AI synthesis Supported Supported Supported
Incident Management (basic), Request, Asset Management Core and CMDB Supported Supported Supported
Change Management Not supported Supported Supported
Problem and Major Incident Management Not supported Supported Supported
On-Call and Walk-up Experience Not supported Supported Supported
DevOps Change Velocity Not supported Not supported Supported
Platform Analytics Advanced Not supported Supported Supported
Creation of new AI skills and custom agents Not supported Not supported Supported
MCP Server inbound Not supported Not supported Supported
Autonomous workforce with AI Specialists Not supported Not supported Supported

Note on DevOps Change Velocity: previously part of ITSM Professional, it is now exclusive to the Prime tier under the new model.

How do we interpret each model in practice?

Model Main focus Interpretation for IT managers
Foundation tier AI skills, insights, and routine agents. Recommended for organizations that want to start using assistive AI, summarization, categorization, pattern recognition, and less complex operational automation.
Advanced tier Agentic workflows and advanced analytics Recommended for companies with more structured ITIL processes, greater maturity in ITSM, ITOM and analytics, and an interest in automating complete workflow steps.
Prime tier Custom agents, inbound MCP, and AI Specialists Best suited for organizations with a clear roadmap of custom agents, AI Specialists, multiple agentic workflows, and advanced AI governance.

ServiceNow states that the Foundation and Advanced tiers allow the configuration of off-the-shelf skills and agents, while the creation of new AI skills and custom agents is restricted to the Prime tier.

Why does ServiceNow licensing change the purchase and renewal strategy?

For IT, procurement, and finance leaders, the main change is that renewals and ServiceNow licensing decisions now require a more technical analysis. Therefore, comparing the previous contract with the new annual price is not enough. First, the organization must determine whether it is selecting the right tier for its operational maturity.

Furthermore, the critical point is that embedded AI does not mean unlimited AI. New models may include limits, consumption pools, specific metrics, or additional capabilities contracted separately, depending on the product, contract, and customer entitlement.

Consequently, a new management discipline emerges: AI consumption modeling. Companies that activate agents, summarizations, automated analyses, and agentic flows without planning may have difficulty predicting costs, measuring adoption, or demonstrating a return on investment.

Fulfiller Model: Who Actually Consumes a ServiceNow License?

One point that often leads to sizing errors is understanding who consumes a license on the platform. ServiceNow has traditionally licensed fulfillers, meaning users who actively work in the platform, such as agents who resolve tickets, administrators who configure workflows, and managers who run reports. By contrast, requesters, who only submit requests through the self-service portal, are generally not counted under the same model.

In practice, a company with thousands of employees may need only a few dozen or a few hundred licensed fulfiller users, depending on the operating model. Understanding the ServiceNow fulfiller model is therefore the first step in preventing overlicensing and supporting negotiations based on actual usage rather than commercial estimates.

This is precisely where a mature ITAM program generates immediate savings: by reclassifying profiles, reclaiming idle licenses, validating active users, and sizing to the correct tier before renewal.

Now Assist Cost: Planning for AI Consumption

With AI embedded in the Foundation, Advanced, and Prime tiers, a new cost variable emerges: consumption of generative and agentic capabilities. Now Assist is no longer just a feature; it becomes part of an adoption strategy that must consider volume, frequency, use cases, participating teams, and contractual limits.

The critical point for purchasing, finance, and contract management is that embedded AI does not mean unlimited AI. High-volume teams that activate assisted resolutions, agents, and automated workflows without planning can quickly consume contracted capacity, requiring a review of the model or additional contracting, according to applicable commercial terms.

Evaluating the cost of Now Assist in ServiceNow requires projecting monthly consumption by business area, prioritizing the highest-impact use cases, and building a safety margin into the initial plan. This turns AI consumption modeling from a one-time analysis into an ongoing governance discipline.

Annual Uplift and the ServiceNow Renewal Negotiation Window

There is also a component that directly impacts the multi-year budget: the annual uplift built into the ServiceNow contract, typically formalized in the order form or in commercial terms applicable to renewal. This recurring uplift, coupled with the expansion of modules and the increasing consumption of AI, can raise the total cost of ownership over the contract cycle.

The recommendation for managers is to begin preparing for renewal well in advance, ideally 9 to 12 months before the term expires, in order to build a usage baseline, streamline licenses, identify underutilized modules, and assess potential AI consumption before commercial discussions.

Anticipating this work changes the dynamics of the negotiation. Instead of reacting to supplier closing pressure, the organization arrives with data, a defined scope, adoption criteria, and the ability to negotiate based on value, risk, and projected consumption.

AI Platform Enablers: Capabilities to Include in the Strategy

Beyond the tiers, ServiceNow positions a set of platform capabilities as enablers of the AI experience. These components should be included in assessments of architecture, data, governance, and ServiceNow licensing.

Enabler Role on the platform Impact on management
Now Assist Generative AI experience embedded in the ServiceNow AI Platform, with features such as summarization, sentiment analysis, response generation, and resolution support. Requires adoption controls, use-case governance, and productivity measurement.
Now Assist AI Agents Extends generative AI to agentic workflows and supports configuring prebuilt agents or, with Prime, creating custom agents. Requires agent governance, permissions, testing, and activation criteria.
AI Agent Fabric Communication layer between ServiceNow agents and third-party AI systems, including protocols such as A2A and MCP. Requires an integration architecture and cross-platform risk controls.
AI Control Tower Provides centralized governance, lifecycle management, and visibility into AI assets. Supports controls, compliance, inventory, and value tracking.
Workflow Data Fabric Connects applications, databases, and systems to the ServiceNow AI Platform without requiring data movement or replication. Depends on trusted data and integration with the enterprise architecture.
RaptorDB ServiceNow's next-generation database, designed for performance and scale in AI-native workloads. Relevant for analytics, scalability, and performance in high-volume data environments.

ServiceNow states that Now Assist is available across the tiers in the new AI experience, that AI Control Tower serves as the governance layer, and that capabilities such as Workflow Data Fabric and RaptorDB play an important role in supporting AI-native workloads.

A sound ServiceNow licensing strategy should combine contract analysis, operational maturity, AI consumption, data governance, and an automation roadmap. Without this integrated view, a company risks selecting a tier beyond its maturity level or underestimating AI’s financial impact.

Actionable checklist for managers before ServiceNow renewal

Before your next ServiceNow renewal or expansion, review:

  • Inventory of users, profiles, and modules in use.
  • Active, inactive, and underutilized fulfiller licenses.
  • Current and projected consumption of automation and AI.
  • CMDB quality and discovery coverage.
  • Dependencies between ITAM, ITOM, ITSM, and operational data.
  • Real-world use cases for Now Assist and AI agents.
  • ROI indicators, such as reduced MTTR, productivity, automation, and cost savings.
  • Access governance, skill activation, and area-specific control.
  • Organizational maturity to operate Foundation, Advanced, or Prime.
  • Dashboards to track AI adoption, performance, and consumption.

How to Choose the Right ServiceNow Licensing Model

The choice of tier should reflect maturity, roadmap, and governance. First and foremost, the Foundation tier tends to suit organizations seeking assistive AI, summarization, categorization, pattern recognition, and routine automation.

Next, the Advanced tier is better suited to companies with structured ITIL processes, more advanced analytics, and an interest in agentic workflows.

On the other hand, the Prime tier should be considered when there is a clear roadmap for creating custom agents and skills. In this case, the company also needs a technical team capable of designing, operating, and governing these capabilities.

In every scenario, the choice of the right ServiceNow licensing model should be guided by actual usage data, the contractual baseline, operational maturity, and clarity about the AI use cases to be activated.

Impact on ITAM: Cost Control and Data-Driven Negotiation

The ITAM program plays a strategic role in governing ServiceNow licensing. While software asset management previously focused on licenses, users, modules, and compliance, it must now also account for the consumption of AI and automation capabilities.

A mature ITAM program should answer questions such as:

  1. Which users actually use the platform?
  2. Which modules are underutilized?
  3. What AI capabilities were activated?
  4. Is there overlap among subscribed capabilities?
  5. Does the projected consumption justify the chosen tier?
  6. Which areas generate the greatest demand for automation and AI?
  7. What indicators demonstrate increased productivity or reduced costs?

This assessment strengthens procurement during negotiations and prevents decisions based solely on commercial estimates. For 4MATT, one of the most important goals is to turn ServiceNow licensing into an ongoing governance practice rather than a one-time discussion at renewal.

Impact on ITOM and CMDB: Without Trusted Data, AI Loses Value

The changes also increase the importance of ITOM and CMDB. This is because agentic workflows, autonomous agents, and capabilities such as Now Assist depend on reliable operational context.

If CIs, relationships, critical services, dependencies, and technical owners are not correct, agents may operate with incomplete context. As a result, the company may experience less accurate recommendations, less reliable automations, and increased operational risk.

Furthermore, in ITOM environments, this problem directly affects event correlation, root cause analysis, incident response, and change automation. Therefore, before expanding the use of AI in ServiceNow, it is essential to review the quality of the CMDB, discovery coverage, and integration between ITSM, ITOM, ITAM, and corporate data.

How does 4MATT support this process?

With experience in ServiceNow, ITAM, ITOM and CMDB, 4MATT supports organizations in evaluating contracts, rationalizing usage, improving data quality, and designing a roadmap for the safe adoption of AI on the platform.

This support can include real-world usage diagnosis, maturity analysis, CMDB review, AI consumption governance, use case prioritization, and technical support to determine which model—Foundation, Advanced, or Prime—is most aligned with the company's objectives.

In practice, 4MATT helps turn ServiceNow licensing into an ongoing governance agenda that connects contracts, actual usage, operational maturity, platform data, and the AI automation roadmap.

Conclusion

In summary, the changes to ServiceNow licensing represent a shift toward a model driven by AI, consumption, and operational value. To capture that value without losing cost control, however, companies must integrate ITAM, ITOM, CMDB, and platform governance in a single strategy.

In addition, embedded AI expands ServiceNow’s potential while increasing responsibility for management, data, consumption, and ROI. The objective is clear: license more effectively, automate with control, and extract greater value from the platform.

For IT, procurement, and finance managers, the new ServiceNow licensing model should be treated as a strategic platform decision, not merely a contract renewal.

Frequently Asked Questions About the New ServiceNow Licensing Model

1. Has the Traditional Fulfiller-Based Licensing Model Disappeared?

No. The concept of paid users, such as fulfiller users who resolve tickets or operate the platform, remains an important foundation of ServiceNow licensing. The change is that the new models combine this concept with tiers of capabilities, embedded AI, automation, agents, and consumption.

2. What Happens If the Company Uses More AI Than Planned?

The outcome depends on the contract, the subscribed product, and the applicable commercial model. The company should therefore monitor AI consumption, understand limits, pools, and usage metrics, and plan additional capacity when necessary. High-volume use cases should not be activated without consumption governance.

3. Will I Be Required to Move to Foundation, Advanced, or Prime at the Next Renewal?

Not necessarily immediately. The transition depends on the existing contract, commercial terms, the contracted product, and ServiceNow's strategy for each client. Even so, it's advisable to evaluate the new models before renewal to understand the financial, technical, and operational impact.

4. What Is the Practical Difference Between Advanced and Prime?

The Advanced tier expands productivity, analytics, and agentic workflow capabilities. The Prime tier adds more advanced capabilities, including the creation of new AI skills and custom agents, inbound MCP Server support, and AI Specialists. In practice, Prime requires greater technical maturity and stronger governance.

5. How Do ITAM and SAM Help Reduce Costs in This New Scenario?

ITAM and SAM help identify actual users, unused licenses, underutilized modules, functional overlap, and rationalization opportunities. In the new model, they also support AI consumption governance so that automations and agents are activated deliberately, measured, and tied to expected returns.