I sold ITSM platforms for years, so I know how the tier conversation goes. A single capability gets demoed, someone says they need it, and the whole organisation is quoted at the edition that includes it. The seat count then multiplies that decision across everyone. The buyer who separates the two axes, what tier do we actually need and how many seats of which kind, pays for the truth instead of the demo. The full pricing context is in the Vivantio pricing guide for 2026; this piece is about the tier and seat mechanics.
How does Vivantio license its platform?
Two things combine. The edition tier sets what the platform can do, from a core service desk through broader service management and enterprise capability. The per-seat license sets how many staff can work inside it. End users who only self-serve are not licensed seats. The important point for cost is that the tier is an organisation-level decision applied to every seat, so a higher edition is rarely about a few power users; it is a premium you pay across the whole team. Exact tier names, inclusions and rates vary by deal size, so confirm them against your own order form rather than a published table.
What is the difference between fixed and concurrent seats?
This is the seat decision that quietly sets your cost. A fixed or named seat belongs to one person. A concurrent seat is drawn from a shared pool and counts only users logged in at the same moment, which fits shift-based or follow-the-sun teams where headcount is large but simultaneous use is not. Concurrent can cut cost when usage is staggered, but the per-seat rate is usually higher, so the saving depends entirely on your peak-to-headcount ratio.
| Seat type | Best for | Watch out for |
|---|---|---|
| Fixed / named | Full-time analysts who are always logged in | Paying for leavers and occasional users left on named seats |
| Concurrent | Shift-based teams where peak use is well below headcount | Higher per-seat rate; the saving disappears if peak approaches headcount |
Which tier do you actually need?
Isolate the single capability that pushes you to a higher edition, confirm it is genuinely required, and weigh the cost of carrying every seat at that tier against the alternatives. Sometimes the feature is worth it across the base. Often it serves five people and is paying a premium on every seat you own. This is the same discipline we apply to tiered pricing on every platform, and it is where the largest single saving usually hides. The renewal-stage version of this work is in how to negotiate a Vivantio renewal.
Our gated ITSM License Optimization Field Guide includes the tier-justification test and the seat-reconciliation worksheet that drive this analysis.
Right-size the tier and the seats.
We isolate the feature forcing your edition, model fixed versus concurrent, and benchmark the rate before the renewal baseline locks. Fixed fee or gainshare.
Book a contract negotiation review →How do you right-size the seat count?
Pull the seat list and test each named seat against real activity. Leavers who were never removed, role changes that moved people off the service desk, and occasional users who could share a concurrent pool all keep drawing a license. Separate genuine full-time analysts from everyone else, then decide the fixed-versus-concurrent split on the concurrency data, not on habit. A reconciled seat list is both a lower bill and the evidence you bring to the table.
What should you negotiate, not just count?
Once the tier and seats are clean, benchmark them. The per-seat rate, the tier premium and any multi-year discount should be tested against deals of similar shape using how to benchmark a Vivantio contract, so your target rests on market data. Then lock the terms: cap the annual uplift so a clean count is not eroded next cycle, and keep a reduction right so you can drop seats if the team shrinks. Vivantio competes hard against the likes of Freshservice on cost and capability, which is leverage you can use, as set out in Vivantio vs Freshservice on cost and capability.
The firm has run this sequence across more than 500 engagements and $420M+ in ITSM contract value, averaging a 30% reduction by rebuilding the count from need. The discipline behind it is in our guide to ITSM renewal negotiation.
How do you test whether a tier is worth it?
Put a number on it. Take the per-seat premium between your current edition and the one below it, multiply by your total seat count, and you have the annual cost of the tier decision. Then list the specific capabilities the higher edition unlocks and how many people actually use each. If a single feature justifies the whole premium and five people touch it, you are paying a per-seat tax across the entire team to serve a handful of users, and there is usually a cheaper way to give those five what they need.
Sometimes the higher tier is genuinely worth it because the capability is used across the base or is load-bearing for the service. The point is not to assume either way; it is to make the call on the math rather than on the demo that sold the edition in the first place. That single test is where the largest saving on a Vivantio contract usually hides.
What does the cost of doing nothing look like?
It accumulates on both axes. On the tier, you keep paying a premium across every seat for a feature whose justification nobody re-checks. On the seats, leavers and role changes pile up on named licenses while a shift-based team that could share a concurrent pool stays on full-price fixed seats. And under an uncapped uplift, both of those inflated numbers grow every year. The contract drifts upward without a decision ever being made to spend more.
The buyer-side fix is to treat each renewal as a reset: re-run the tier math, reconcile the seats, re-test the fixed-versus-concurrent split, and cap the uplift so this year's clean numbers hold. The firm has run this sequence across more than 500 engagements and $420M+ in ITSM contract value, averaging a 30% reduction, and on tiered platforms like Vivantio the tier correction is frequently the single biggest line of it.
What to do next
Isolate the feature forcing your tier, model fixed versus concurrent on real concurrency, and benchmark the rate before the quote arrives. When you are ready to run it, the engagement goes through our contract negotiation service on fixed fee or gainshare, and the wider picture is in the Vivantio pricing guide.
Frequently asked questions
- How does Vivantio license its platform?
- An edition tier sets the capability ceiling and a per-seat license sets the volume; the tier applies to every seat. End users who self-serve are not licensed. Tiers and rates vary by deal size, so confirm against your order form.
- What is the difference between fixed and concurrent seats?
- Fixed seats are tied to one person; concurrent seats are shared from a pool and count only simultaneous logins. Concurrent suits shift teams but carries a higher rate, so the saving depends on your peak-to-headcount ratio.
- What inflates a Vivantio bill most often?
- Being carried at a higher tier for a feature few people use, and a seat list padded with leavers or occasional users. Reconcile the seats and isolate the tier driver before the baseline is set; we average a 30% reduction.
Book a Vivantio review.
Isolate the tier driver, right-size the seats, benchmark the rate, close capped terms. Fixed fee or gainshare.
Book a contract negotiation review →