They are not.
They are buying management of an N-factorial interdependency surface.
Those are not the same thing. They are not even close to the same thing.
The managed services industry priced itself as a utility.
Utilities are simple. You consume power, you pay for kilowatts. You consume water, you pay for gallons. The meter measures what you use, the invoice reflects the number, everyone understands the exchange.
So the MSP industry looked for its meter. It found devices first — when the dominant asset was physical hardware sitting on desks and in racks, counting endpoints made intuitive sense. Then the cloud arrived, identity became the organizing principle of the environment, and the industry followed the asset class. Seats replaced devices. Users replaced machines as the thing worth counting.
Neither transition was a principled decision about how to price the actual work. Both were the industry pointing at whatever it could see and count. Devices when iron was the thing. Users when identity became the thing.
Some have experimented with network bandwidth — which is at least measuring something that moves. Bandwidth feels more sophisticated than seats. It is still the wrong measurement. A quiet environment with deeply tangled interdependencies may consume less bandwidth than a simple one full of video calls. The meter would call the tangled environment cheaper to manage. The engineer living inside it would disagree.
All of these are attempts to find a consumption proxy for work that does not scale with consumption. They measure the surface of the environment. None of them measure what is underneath.
When you add one employee to a managed environment, you are not adding one unit of complexity. You are adding one new node to a network where every existing node now has a new potential connection. The math is not additive. It is combinatorial.
A 300-person organization is not twice as complex as a 150-person one. The per-seat invoice says it is. The actual environment says otherwise.
Consider what one employee actually touches in a properly managed environment. An identity account. MFA enrollment. A PC, a phone, possibly a tablet. Email. Team chat. Six SharePoint sites with distinct permission sets. Four cloud applications. A VPN certificate. A phone extension. Membership in three security groups that gate access to two on-premises applications.
That is not one unit of complexity. That is twelve to eighteen connections to other managed systems — each with its own update cycles, its own failure modes, its own governance requirements.
The odometer clicked once. The engine did something considerably more interesting.
Per-seat pricing feels transparent. The client can see the number. They can compare it. They can negotiate it. It feels like a clear and honest exchange.
What it does not show is the architectural labor underneath — the interdependency management, the change impact assessment, the governance overhead, the eighteen-step onboarding workflow that touches six domains every time someone joins or leaves.
The invoice is legible. The work it represents is not.
Measuring the wrong thing with precision is not transparency. It is a well-formatted misunderstanding.
Nobody in this structure is incentivized to reduce complexity.
The vendor profits from adding it — every new SaaS tool landed in the client's environment increases the interdependency surface. The vendor does not manage that surface. The MSP does. At the same rate.
The client has no visibility into whether their environment is getting more or less complex over time. They add the fifth SaaS tool because the vendor pitched it well. They do not see the interdependency it creates. The MSP absorbs it.
The MSP absorbs it silently because the invoice has no line for architectural debt. There is no mechanism that makes complexity visible to the client as a cost. There is no reward for reducing it.
Show a client their environment mapped as a network — not a conceptual diagram, but their actual systems, their actual connections, their actual interdependencies labelled and counted — and something shifts in the conversation.
They stop asking why this costs so much. They start asking why it is this complex.
Those are entirely different questions. The first is a negotiation. The second is a strategy conversation.
When you can show a client that their 300-person environment contains 42 direct connections between 20 managed components — and that 62% of those connections cross domain boundaries — you are no longer explaining a bill. You are explaining a system.
That is not a managed services provider. That is a fractional CIO with receipts.
Most MSPs will read this and think about pricing.
The right response is to think about positioning.
The MSP that can make complexity visible is not selling managed services. It is selling organizational intelligence.
The per-seat conversation is over before it starts. The complexity conversation has no competition.
The MSP Contrarian: Unstacking the Business Model An independent publication. Not affiliated with, sponsored by, or particularly popular with any vendor in the managed services ecosystem. Subscriptions are free. Opinions are not.