Hornbill Subscriber-Based Pricing Explained

The direct answer first. Hornbill uses a subscriber-based model: you license a pool of subscribers, each a named user, and the full application set is included rather than sold as separate modules. Because there is no per-app upsell, the cost driver is the subscriber count alone, which makes Hornbill simpler to model than tier-and-add-on platforms but puts all the negotiating weight on one number. The full platform picture sits in our Hornbill pricing guide for 2026.

What is subscriber-based pricing?

A subscriber is a named individual with access to the Hornbill platform. You buy a quantity of subscribers, and every included application is available to them within that subscription. This differs from the dominant ITSM model, where a base tier is sold per agent and capabilities are unlocked through paid modules or higher tiers. With Hornbill there is one rate and one count, and the applications do not change the price.

How does it compare with per-agent and tiered models?

The comparison matters because it changes where you look for savings. In a per-agent tiered model, cost leaks through tier inflation and module attach; in a subscriber model, those leaks do not exist, so the entire focus moves to the count and the uplift.

What drives the cost of a Hornbill subscription?

Two things. First, the subscriber count: every named subscriber who no longer needs access, or never used it, is recoverable. Pools drift upward as teams change and leavers are not deprovisioned, so the licensed count tends to sit above active use. Second, the annual uplift: with a single rate applied to the whole pool, an uncapped increase compounds across every subscriber, so capping it protects the entire contract at once. Hornbill does not publish enterprise rates, so the per-subscriber figure varies by deal size and should be confirmed against your order form.

How do you right-size the subscriber pool?

1. Pull the subscriber list and match it against active logins over the last 90 days.
2. Identify leavers and dormant accounts that are still consuming a subscription.
3. Separate genuine subscribers from occasional users who may not need standing access.
4. Set the renewal count from active need, not from the historical high-water mark.
5. Cap the annual uplift so the right-sized pool is not re-inflated by the increase.

What to do next

Because the model is clean, the discipline is too: reconcile the subscriber pool to active use, set the renewal count from need, and cap the uplift so the saving holds. There is no module maze to navigate, which means the prep is faster, but it also means the count is the only place value lives, so it has to be right. A sibling read on timing and tactics is in how to negotiate a Hornbill renewal.

When you want it run for you, our contract negotiation service reconciles the pool, benchmarks the rate and closes the terms on fixed fee or gainshare. We have negotiated more than $420M of ITSM contract value across 500-plus engagements since 2019, at a 30% average reduction.

Frequently asked questions

What is Hornbill subscriber-based pricing?

You license a pool of named subscribers and all Hornbill applications are included, rather than buying a base tier plus paid modules. The subscriber count is the only number that moves the bill.

What drives the cost?

The subscriber count and the annual uplift. Because one rate applies to the whole pool, an oversized count and an uncapped increase are the two places overspend accumulates.

How is it different from per-agent pricing?

Per-agent tiered pricing leaks cost through tier inflation and module attach. The subscriber model has neither, so the negotiation focuses entirely on right-sizing the pool and capping the uplift.