Why per-seat pricing breaks on-call.

You don't have coverage. You have partial coverage.

Per-seat pricing charges you for every person who can be reached, so teams ration who gets an account. The volume responders get their seats, but when the cost line is drawn, low volume becomes hard to justify. The result is a coverage gap you don't feel until the night it matters.

Volume is usage, and usage is the natural place to start when you have to justify a cost. But this is incident response. The value on any given night is whoever is best suited to help, not whoever gets paged the most, and as severity climbs, the help you need shifts toward the people who are rarely called in on the routine volume work.

Architects. Principals. Specialists. Management. Tier four and five

These contributors often never get considered as a contact at all, because the cost is hard to defend. They do not turn up in routine incidents, so on a spreadsheet they are the obvious trim.

What makes them rare is the same thing that makes them matter. Nobody calls a principal engineer because a disk filled up. You call one when something is strange enough that nobody on shift has seen it before, and that is the same night a slow answer costs the most. Per-seat pricing charges the same for the person paged forty times a month and the person paged twice a year, so the cut lands on the second one. On the spreadsheet that trim is obvious. On the bridge it is a number nobody can find.

The delay in reaching someone is the visible cost. The one that does more damage is what your front line is doing while it happens.

They could have reached that person with a few clicks. Instead they are working a phone tree. Hunting a number in a directory that may be a year out of date. Leaving a voicemail, then writing down who it was left with so the next person on the bridge does not repeat it. Trying to remember whether the second architect was actually reached or only dialed.

None of it is incident work. The people who should be looking at the problem are doing administrative work, at the point in the night when attention is scarcest. And the clock on the incident does not stop for any of it.

At $25 per person per month, taking that risk is a numbers decision. A role paged twice a quarter is genuinely hard to justify at $300 a year, and for a long time there was no third option on the menu. Pay for everyone, or accept the holes and improvise on the night. Risk acceptance is how partial coverage became the norm, but the norm only holds for as long as the math does.

On-call exists to make sure the right person can be reached when something breaks. Its value grows with every person who can be paged, looped in, or shown what is happening. Per-seat pricing makes each of those people a line item, so the tool's value and the tool's cost pull in opposite directions.

Every other budget conversation in IT trims waste. This one trims reach. When a license renewal comes around, nobody asks whether the monitoring is too thorough. Someone always asks whether all those on-call accounts are really necessary.

Per-seat pricing comes from the expansion-revenue playbook, land with a small team, then grow the bill as adoption spreads. That is a fine model for a document editor, where each new user gets roughly the same value. It fits badly on a tool whose whole job is making sure nobody is unreachable.

A pricing model that makes you think twice before adding a responder is not neutral plumbing. It is a design decision, and it is working against you.

Below about ten people, per-seat is cheaper and you should take it, the crossover math is linked below. The problem starts when headcount grows and the ladder grows with it, because from that point the bill scales with your org chart instead of your incidents.

root9 has no seat fees. Plans are flat, users are unlimited, and the meter sits on delivery, the part that costs real money, with the numbers published up front. Whether ten people or the whole company can see the board and be reached by an escalation is your operational call, not a licensing negotiation.

How much does per-seat on-call pricing cost? Major on-call tools price their professional tiers per user per month, commonly in the $20 to $40 range. A 25-person deployment at $25 per user runs $7,500 a year, and that is before anyone outside the rotation gets visibility.

What is the alternative to per-seat pricing for on-call? Flat platform pricing with usage-based delivery. Everyone who needs access has it, and the meter sits on what actually costs money, such as SMS and voice delivery. Adding a responder, a service owner, or a stakeholder costs nothing, so coverage stops being a budget decision.

Does root9 charge per user? No. root9 plans are flat with unlimited users. Delivery such as SMS and voice paging is metered, with the numbers published up front, and adding people to escalation paths or the alert board never costs a seat.