ServiceNow Licensing: Fulfiller vs. Unrestricted User Models

[Bill Martin]

Introduction

In the world of ServiceNow platform governance, one decision stands above the rest in terms of financial impact: choosing between the Fulfiller (Named User) and the Unrestricted User model. As a ServiceNow Certified Technical Architect (CTA), I’ve seen this single choice result in a $780,000 variance in spend over a standard 3-year contract.

The Financial Magnitude of Licensing Waste

Public data suggests that 20-25% of ServiceNow licenses in large-scale enterprises are "ghost users"—dormant accounts or misassigned roles that generate zero value. When you factor in an annual uplift of 7-12%, the cost of choosing the wrong model compounds aggressively.

The Comparison: Fulfiller vs. Unrestricted

Type	Fulfiller (Named User)	Unrestricted Model
Pricing Model	Per Named User / Per Year	Flat Fee / Per Instance
Scalability	Linear (Pay as you grow)	Unlimited (Fixed Cost)
Compliance	High (Requires ITAM/SAM)	Low (Simplified Audit)
Ideal For	Stable IT Teams	Enterprise-Wide Digital Transformation

 

3 Strategic Scenarios for 2026

1. The Stable IT Org: If your headcount is under 300 and turnover is low, the Fulfiller model offers the tightest cost control.

2. The Aggressive Growth Strategy: If you are expanding to HR, Legal, and Finance, Unrestricted is the only way to avoid "Success Tax"—where the more you use the platform, the more you are penalized.

3. The Multi-Instance Architecture: A critical trap for global firms. Licensing is per instance. If you run separate instances for North America and EMEA, you are doubling your costs. I often recommend Domain Separation as a strategy to consolidate these costs.

 

The Break-Even Analysis Framework

To determine your crossover point, you must calculate:

• Current vs. Projected Fulfiller Count (3-year outlook).

• The cost of License Governance (Headcount for SAM/ITAM).

• Contract lock-in risks.

Watch the Full Technical Breakdown

I’ve recorded a deep-dive video covering the Breakeven Calculator and the specific Architecture

Patterns required for each model.

[Lenny Leppers]

Hey @Bill Martin  great piece—really useful breakdown on the licensing trade-offs.

One quick correction though: Unrestricted Users (UU) aren't actually flat fee. They're still user-based. The "unrestricted" part means unlimited roles within the module, but if the customer's sys_user table grows, they're buying more UU licenses. That's the key difference from Fulfiller—which scales with named IT folks, while UU scales with total active users.

This actually strengthens your point about the Aggressive Growth Strategy, by the way. If they're expanding to HR, Legal, Finance—and those teams mean hundreds of new users—the real cost driver with UU is headcount growth, not role complexity. Worth flagging that distinction so customers make the right call.

[Bill Martin]

@Lenny Leppers, thank you.

This is exactly the kind of correction that makes these breakdowns better, and you're right to raise it.

You caught a real oversimplification in how I framed it. I described Unrestricted User as a flat fee, unlimited users model, and that blends two separate ideas that deserve to stay apart.

The real distinction is this. Unrestricted refers to role and access breadth inside the product. A UU is not boxed into the narrow set of roles a named Fulfiller effectively lives within. But it is still a user based license that counts against active users, and it remains a restricted entitlement rather than an open flat fee. As the population using that product grows, the UU count grows with it, and so does the cost. It is not immune to headcount, and I should not have presented it that way.

What I appreciate most is that your point makes the growth argument stronger, not weaker.

The real story is about what drives the cost curve.

Fulfiller scales with your named IT and agent population. UU scales with the total active users touching the product. So when the enterprise rollout brings HR, Legal, and Finance online, the thing moving the number is headcount expansion, not role complexity.

That is a cleaner and more truthful way to tell it, and it helps buyers make the right call for the right reason.

For context, this video was built on the earlier licensing model, where the named Fulfiller versus Unrestricted User choice was the headline decision.

That is the world the narrative lives in, and it is worth calling out so viewers place it correctly on the timeline.

The good news is that Series 2 already picks up where this leaves off. I tackle the new April 2026 packaging directly there, walking through the AI infused Foundation, Advanced, and Prime tiers and the shift to a subscription commitment paired with usage based meters. Your correction lands even more cleanly in that newer world, because the meters make it explicit that value is captured across user types as adoption scales.

So here is what I've done. I've already updated this piece to drop the flat fee, unlimited users language, reframe UU as a restricted, user based meter, and reset the break even discussion around user count growth on both sides. I've also added a note at the top crediting your clarification and pointing viewers to Series 2 for the April 2026 tiers, so anyone reading the thread sees both the correction and where the model stands today.

One thing I would genuinely value your read on, since you are closer to the source. Across the current tiers, does the UU meter true up against total active users regardless of whether they are only consuming, or is there still a threshold where light and self service users do not pull a UU?

That threshold is where a lot of the real procurement math lives, and I want to get it right.

Thank you again for keeping this accurate.

It genuinely means a lot to have the ServiceNow team engaging directly and helping the community get the details right.