Why per-seat IT pricing rewards your provider for doing less

We were working with an organization a while back. Their previous provider had them on a per-seat agreement, and by the numbers that provider reported, the account looked healthy. Ticket volume had been falling steadily for two years.

Falling ticket volume is usually good news. Fewer problems, fewer interruptions, a stable environment.

That is not what had happened. The staff had stopped asking for help, because asking had become more painful than working around the problem. People were doing their own workarounds, sharing passwords to avoid a reset request, and living with a printer that had not worked properly in months.

The environment was not getting better. The reporting was.

Here is the part worth sitting with: under that agreement, nobody had a reason to notice. Fewer tickets meant less cost against the same monthly payment. The provider was not committing fraud. The structure was working exactly as designed.

How the math actually works

Most managed IT agreements in our market are priced per user or per device. You count your staff, multiply by a monthly rate, and that is your IT bill. It is simple to quote, simple to budget, and simple to compare across providers.

It also means your provider collects the same amount whether they do a great deal of work or almost none.

If your environment is quiet in a given month, most of that payment is profit. If you have a hard month, every ticket, every site visit, and every after-hours call comes out of the same fixed number.

Nothing about that is dishonest. It is arithmetic. But follow it forward and you can see what it encourages.

The provider's best month is the month you need them least. Their worst month is the month you need them most.

That is the opposite of what you want from a partner.

What it looks like from your side of the table

You will rarely see this as a line item. It shows up as texture.

Tickets that get closed rather than solved. A recommendation that starts from the provider's standard stack instead of your actual problem. Reluctance to send someone on-site when a remote session would technically do. A slow drift toward "that is out of scope."

And the quiet one from the story above: your people stop asking. That never shows up in a report, because the report only counts what was reported.

None of those are lies. They are the rational response to how the agreement is built.

In fairness, per-seat is not always the wrong answer. If your environment is genuinely uniform, your headcount is stable, and you want one predictable number in the budget, it can work well. Plenty of organizations are served properly by it, and we have told prospects exactly that when it was true.

The problem is not the model. The problem is choosing it without knowing what it rewards.

How we price instead, and what that costs you

We work from pooled hours and reoccurring agreements built around what an organization actually needs. On-site visits on a set schedule, remote shifts, on-demand help desk, extended hours when the work calls for it. You can see how we structure flexible support if you want the detail.

The practical difference is that we are paid for work performed. You tell us what you need, you can see where the hours went, and you are never paying for something you did not get work for.

That flips the incentive. We do better when we do more for you, and you stay in control because you decide what "more" means.

Now the honest part. This model has a real tradeoff and we would rather say it than have you find it later.

Your bill varies. A quiet quarter costs less than a heavy one. If your finance lead wants a single unchanging number on the budget line for the next three years, our model takes more planning than a flat per-seat fee. We handle that with regular reviews and a forward-looking roadmap rather than surprises, but it is still more moving parts than one flat rate.

We also do not use long-term locking agreements. That is by design. If we are not doing right by you, the ability to leave is what keeps us honest. It also means we have to re-earn the relationship continuously, which is uncomfortable in a way that is probably good for us.

We have client partnerships measured in decades, not years. We would rather that come from the work than from a signature.

Four questions worth asking any provider

Whoever you are talking to, including us, these will tell you more than a capabilities deck. We put a longer version of this on our page about whether your IT provider is a partner or just a vendor.

1. If we have a heavy month, does your revenue go up, down, or stay flat? There is no wrong answer here. There is only an answer they should be able to give you plainly.

2. When you recommend something, is it from your standard stack or from our environment? Ask for a specific example of something they recommended that they do not sell.

3. What triggers an on-site visit, and who decides? For any organization with physical infrastructure, this is where fixed-fee models tend to quietly pinch.

4. If our ticket volume drops, how would you tell the difference between a healthy environment and people giving up? A provider who has thought about this will have an answer involving conversations with your staff, not a chart.

If a provider gets uncomfortable with any of those, the discomfort is information.

The point

We are not arguing that every per-seat provider is doing badly by their clients. Many are good at the work and genuinely care about the organizations they support.

We are arguing that you should know what your agreement rewards before you sign it, because that structure will shape a hundred small decisions you will never see.

If you want a plain-English read on your current setup, we are happy to have that conversation even if it ends with us telling you to stay where you are. We have done that before.