The Case Against Per-Seat Pricing

We price Signal at a flat monthly rate per account, and that is a deliberate disagreement with the industry norm. Per-seat VoIP pricing bills you for headcount when what you consume is call capacity, phone numbers, and support hours. It taxes growth, penalizes shared and part-time phones, and quietly pushes administrators toward worse configurations.

What is per-seat pricing charging for?

Per-seat pricing assigns a monthly license to each named user or extension. Add a person, add a license. Add a lobby phone with its own extension, add a license. The unit of billing is an identity in the system.

The pitch is fairness — you pay for what you use. The problem is that a seat is not what you use.

The mismatch between those two columns is the whole argument. An office with fifteen extensions and four concurrent calls consumes less than an office with eight extensions and eight concurrent calls, and per-seat pricing gets that backwards.

Why the unit is wrong

Consider an eleven-person clinic. The staff count says eleven. The phone system says something else: eleven staff extensions, a lobby phone, a break-room phone, two hallway phones outside the exam rooms, and a conference room. Fifteen extensions.

Nobody is standing in the break room making sales calls. That phone exists so someone can reach the front desk without walking. Under per-seat pricing it costs the same as the practice manager, every month, for the life of the contract.

Now add the part-time reality. A front-desk person who works Tuesdays and Thursdays needs an extension, voicemail, and a queue login. A seasonal hire during a busy stretch needs the same. Both are billed as full seats, and the second one is billed for months after they leave unless someone remembers to remove the extension — which is the single most common silent cost on a phone bill.

The damage nobody talks about

Here is the part of the argument that goes unstated, and it is the reason we feel strongly about it: per-seat pricing changes how people configure their phone system, and always for the worse.

When each extension has a price, administrators start economizing on extensions. The predictable results:

• Shared logins. Two people on one extension, so call history and voicemail belong to nobody.
• No extension for the part-timer, so their calls land in a general voicemail box and get returned late or not at all.
• The lobby phone hangs off someone's desk extension, so a call parked there rings a person who is with a patient.
• No dedicated extension for the role, so dialing permissions cannot be set per person and the international dialing control everyone wanted is not practical.
• Departed employees left in place, because deleting an extension is a billing conversation rather than an administrative one.

Every one of those is a support ticket waiting to happen, and every one exists because someone was told extensions cost money. Extensions should be free the way folders are free. They are records in a database describing how you want calls handled.

What per-seat pricing gets right

It is not a scam, and we should say so.

Per-seat is legible. A finance department can forecast it. At several hundred employees it becomes a reasonable proxy for consumption, because at that scale headcount and call volume genuinely do track each other, and the shared-phone distortion averages out. It also gives vendors a clean way to package feature tiers, which large organizations often want.

Our objection is specific to the band we sell into: 5 to 25 people. At that size, the proportion of extensions that are rooms rather than people is high, part-time staff are a meaningful share of the roster, and headcount moves by 20% in a quarter without call volume moving at all. Per-seat pricing is mispriced at that scale, not immoral.

What flat per-account pricing means in practice

We look at extension count, phone numbers, locations, and expected usage, then quote one monthly figure. After that:

Adding a person does not change your bill. Neither does adding a lobby phone, a conference room phone, a second device on an existing extension, or a shared departmental voicemail box.

What does change it is what genuinely changes our cost: buying additional phone numbers, adding a location, or usage outside the plan such as international minutes. Those are line items we can point at and explain, which is the standard we would want as a customer. Billing basics shows how the invoice is laid out.

The practical effect is that you configure the system correctly. Every person gets an extension. Every room that needs a phone gets one. Every role gets a shared voicemail box instead of a person's inbox doubling as the department's. That configuration produces fewer missed calls, and it produces them because nobody was rationing extensions.

Why we can offer to match or beat your bill

Because we are pricing an account rather than counting heads, and because we know what an account actually costs to run.

When you send us a current invoice, we are not guessing at your consumption — the invoice tells us your numbers, your usage, and how many extensions you were persuaded to license. Frequently the gap between what you pay and what your system consumes is the seat count, and that gap is where a match-or-beat quote comes from. It is not a loss leader. It is the difference between billing the right unit and the wrong one.

If you want to see the arithmetic on your own office first, how much a business phone system costs lays out the six line items, and auditing a VoIP invoice covers reading the bill you already have.

Frequently asked questions

What is per-seat pricing for a phone system?

A model that charges a monthly license for each named user or extension in the system. Adding an employee, a lobby phone, or a conference-room extension each adds a license. The billing unit is an identity in the platform rather than call capacity, phone numbers, or usage — which is what the system actually consumes.

Is per-user VoIP pricing bad for small businesses?

At 5 to 25 people it usually prices the wrong thing. Small offices have a high ratio of rooms to people, meaningful part-time staff, and headcount that moves without call volume moving. At several hundred employees per-seat becomes a reasonable consumption proxy and the distortion averages out.

What is flat-rate phone system pricing?

One monthly figure for the account, set from extensions, numbers, locations, and expected usage, that does not change when headcount does. Additional phone numbers, additional locations, and usage outside the plan still carry charges, because those reflect real cost. Adding a person or a room phone does not.

Should a lobby phone count as a seat?

Under per-seat pricing it typically does, and that is the clearest illustration of the problem. A phone that exists so someone can reach the front desk without walking down a hall is billed at the same rate as a full-time employee. Under flat per-account pricing, it costs nothing extra to place phones where they are useful.

How can a provider match my existing phone bill?

By pricing the account rather than the seat count. Your current invoice reveals your numbers, usage, and licensed extensions. When a meaningful share of the bill is seat licenses for rooms, part-time staff, and departed employees, a flat quote for the same capability can land lower without cutting anything you use.

Send us the invoice you are paying now and we will show you, line by line, which part of it is seats. If a flat quote does not beat it, we will tell you that too.