Ask three IT providers what managed services cost and you will get three answers structured three different ways, which makes comparison almost impossible. That is not always deliberate, but it does not help you.

Here is how the pricing actually works, what moves the number, and what to check before signing.

The three pricing models

Per user

You pay a monthly fee per employee, covering their devices and accounts. This is the most common model for office-based businesses and the easiest to budget, because it scales with headcount rather than with equipment count.

It works well when most staff have one laptop and a phone. It works badly when you have a lot of shared machines, kiosks, or production equipment, because those either get counted oddly or excluded.

Per device

You pay per endpoint. This suits businesses with unusual device-to-user ratios: a warehouse with shared terminals, a shop floor with dedicated machines. It penalizes businesses where everyone carries three devices.

Tiered or flat fee

A fixed monthly number for a defined scope. Simple to budget, but the scope definition is everything. A flat fee with a vague scope becomes a negotiation every time something unusual happens.

What moves the number

Two businesses with the same headcount can differ substantially in price. The drivers:

• Current state. An environment that has been maintained costs less to support than one that has not. Providers price for the stabilization work they can see coming.
• Compliance requirements. HIPAA, CMMC, PCI, or contractual security obligations mean documentation, auditing, and controls that take real time.
• Servers and infrastructure. On-premise servers, line-of-business applications, and production equipment cost more to support than a cloud-only office.
• Coverage hours. Business hours versus extended versus genuine 24/7 is a large multiplier. Be honest with yourself about what you need.
• On-site expectations. Remote-first with occasional visits costs less than a scheduled on-site presence.

What should be included, and what usually is not

A reasonable agreement includes helpdesk support, patch management, monitoring and alerting, endpoint security, vendor coordination, documentation, and periodic reporting.

Commonly excluded, and worth asking about explicitly:

• Hardware and software costs, which are normally passed through
• Projects such as migrations, office moves, and new deployments
• Third-party application support beyond basic coordination
• After-hours work outside agreed coverage
• Incident response for a major security event

None of these exclusions are unreasonable. The problem is only discovering them during an invoice dispute.

Contract terms worth reading

Term length and exit. Multi-year agreements with automatic renewal and short cancellation windows are common. Know the notice period before you need it.

Who owns the documentation. This is the one most people skip and the one that matters most. If you leave, do you get your network diagrams, configurations, and credentials? The answer should be an unambiguous yes, in writing. A provider that will not commit to that is relying on switching costs rather than service quality.

Response time definitions. A one-hour response should specify what response means. An automated ticket acknowledgment is not a response.

What happens when scope changes. You will add staff, open a location, or take on a compliance obligation. How does the agreement adapt?

How to compare quotes fairly

Normalize everything to a monthly cost per employee, including anything quoted as a one-off onboarding or stabilization fee spread across the first year. Then list what each provider excludes. The cheapest headline number frequently has the longest exclusion list.

Also ask each provider what they would fix first in your environment and why. The answers tell you more than the pricing does. A provider who has actually looked will name something specific. One who has not will talk in generalities.

If you want an independent read on a proposal in front of you, that is part of what our IT consulting work covers, and you do not need to become a managed services client to get it. You can also see what our own managed IT services include, exclusions stated plainly.