How MSPs are paid: understanding managed IT pricing models

Short answer: MSPs charge in five main ways – per user, per device, flat tiered, all-inclusive, or monitoring-only. Per-user is by far the most common in modern SMB managed IT because most employees now use cloud-first tooling and cost scales with people, not endpoints. Per-device makes sense in device-heavy environments (retail, manufacturing, healthcare with many kiosks). Flat tiered works for small predictable shops. Monitoring-only is a different product entirely – alerts without the operational layer. This article explains how each model actually works, what each is best and worst at, and how to pick the one that fits how your business actually operates.

The mechanics matter because two MSPs quoting “$10,000/month” for the same business can be using completely different pricing models underneath, and the one that is cheaper on paper today may be the more expensive one a year from now. Understanding the model is how you avoid that surprise.

The five pricing models at a glance

Model	How billing scales	Common in	Best at	Worst at
Per user	With headcount	Most modern SMB managed IT	Simple budgeting, cloud-first businesses	Device-heavy environments
Per device	With endpoint count	Retail, manufacturing, device-heavy healthcare	Predictable per-asset cost	Multi-device users (contractors, creatives)
Flat tiered	Banded (1-25 users, 26-50, etc.)	Very small / stable businesses	Simplicity	Growth friction at band edges
All-inclusive	One number covers everything	Mature 50-200 employee SMBs	Predictability at full scope	Pricing opacity, harder to switch
Monitoring-only	Per device, narrow scope	Businesses with internal IT	Cheap visibility	Not actual managed IT

Below, each model in depth.

Per-user pricing

How it works: The MSP charges a flat fee per employee covered by the agreement, regardless of how many devices the employee uses. A user with a laptop, phone, and desktop counts as one user. A user with no device counts as one user if they still consume support (typical for executives or salespeople).

Why it dominates modern MSP pricing: Most business IT cost today is driven by humans, not hardware. Account provisioning, password resets, M365 admin, security training, helpdesk tickets – the cost is the employee, not the device. Per-user pricing reflects that.

What typically scales with users

• Help desk tickets
• Microsoft 365 and identity management
• Security (MFA, conditional access, user training)
• Onboarding and offboarding
• Documentation overhead

What does NOT scale with users

• Server infrastructure (one server, 50 users, the server still costs the same to manage)
• Network equipment (firewalls, switches)
• Site-wide tooling (M365 tenant-level configuration)

Most MSPs using per-user pricing bundle infrastructure management into the per-user fee (amortized across the client base) and call out the exceptions where infrastructure is unusually complex.

What to verify about a per-user quote

• What counts as a user? Contractors? Shared workstations with multiple users? Service accounts? Ambiguity here turns into billing disputes.
• How often is the user count reconciled? Monthly true-up is ideal. Quarterly is common. Longer than quarterly lets the MSP over-bill during shrinkage and under-bill during growth.
• Is there a minimum user count? Some MSPs have a floor (e.g., “minimum 15 users”) that makes per-user pricing expensive for small businesses.
• Are servers and network gear included, or priced separately? Both models exist. Make sure the proposal is clear.

Best fit

Cloud-first businesses where most employees are knowledge workers with 1-2 standard devices. Professional services, software, finance, consulting, marketing agencies, legal, small healthcare practices. This is roughly 80% of SMB managed IT engagements in 2026.

Worst fit

Businesses where the device-to-user ratio is high – retail with many point-of-sale terminals, manufacturing with many shop-floor PCs, construction with shared site devices. In those cases, per-device pricing usually costs less.

Per-device pricing

How it works: The MSP charges a flat fee per managed endpoint. Workstation, server, firewall, switch, sometimes printers. A user with one laptop counts as one device; a user with three devices counts as three.

Common rate bands:

• Workstations: $50-$100 per device per month
• Servers: $150-$400 per device per month (complex production servers higher)
• Network gear: $25-$75 per device per month
• Mobile devices: $10-$25 per device per month

What typically scales with devices

• Patching work (each endpoint needs its own patch cycle)
• Agent licensing (RMM, EDR)
• Monitoring alerts
• Hardware-level incidents

What does NOT scale with devices

• User-level work (helpdesk calls, M365 admin)
• Site-wide security configuration
• Compliance documentation

Per-device pricing treats these as overhead distributed across the per-device fees.

What to verify about a per-device quote

• What qualifies as a “managed device”? Only covered devices get support. A user with a BYOD laptop that is not in the count gets no help when it breaks.
• What is the billing for multi-device users? A creative agency where every designer has a laptop + desktop + iPad + phone pays 4x the per-device rate for one person.
• What about periphery devices? Printers, conference room systems, signage – are they in the count? Expensive if yes; excluded from support if no.
• How is device removal handled? If a device dies, when does billing stop? Some contracts bill for 30 days after decommissioning.

Best fit

High device-to-user ratio environments. Retail (many POS terminals per employee), manufacturing (shop-floor PCs, industrial controls, kiosks), warehouse/logistics, healthcare with many patient-facing kiosks, schools with device-heavy classrooms. Also businesses with substantial server infrastructure beyond the typical SMB one-or-two-server setup.

Worst fit

Businesses where employees use many devices each – creative agencies, high-end consulting, firms with traveling salespeople who carry three devices. Per-device pricing penalizes the multi-device user pattern.

Flat tiered pricing

How it works: The MSP defines employee or device bands – “1-25 users,” “26-50 users,” “51-100 users” – and charges a fixed monthly fee for each band. Inside the band, you pay the same regardless of exact count.

Why MSPs offer flat tiered pricing

Simplicity. Both sides know exactly what the monthly bill is. No true-ups, no reconciliation disputes, no worry about crossing a threshold mid-month. For small businesses where headcount is stable, this is easier to budget around than per-user. (The MSP line is one of six in a full IT budget – see what the total small business IT budget should cover.)

The math problem

Flat tiered pricing is fair on average and unfair in the moment. A 28-person business pays the same as a 50-person business if both fall in the 26-50 band. The 28-person business is over-paying relative to pure per-user pricing, and knows it.

The problem compounds at band edges. A 50-person business thinking about hiring its 51st employee faces a discrete cost increase (moving to the 51-100 band) that has nothing to do with the actual marginal cost of supporting one more person. Some clients artificially delay hiring to stay in a band, which is a bad incentive for an IT pricing model to create.

What to verify about flat tiered pricing

• Where are the band boundaries, and what happens when you cross them? Is it prorated (you pay the new tier from the day you cross), or does it kick in at the next renewal?
• Can you go down a band? Some contracts only ratchet upward – once you cross 51 users, you stay in the 51-100 band even if you shrink back to 40.
• What happens to per-user services (M365 licensing, security tooling) that scale linearly? Usually still billed per user; only the MSP’s own fee is flat.

Best fit

Stable small businesses (under 25 employees typically) that want simplicity. Seasonal or predictable headcount. Businesses where per-user reconciliation is not worth the bookkeeping.

Worst fit

Growing businesses. Businesses with variable headcount. Businesses near a band boundary, which is most businesses at some point.

All-inclusive pricing

How it works: The MSP quotes one flat monthly fee that covers everything – per-user operational layer, infrastructure, tooling, M365 licensing, backup licensing, sometimes hardware leases. One invoice, one line item.

Why buyers like it

Pure predictability. No line-item surprises. No “was that in scope?” arguments. You know exactly what you are paying every month, and it covers what you need.

The pricing opacity problem

The trade-off is that you cannot see what you are paying for each component. That makes it hard to evaluate whether the pricing is reasonable (“is this fair?”) and hard to compare against other MSPs that do line-item pricing (“is that other quote really cheaper, or just unbundled?”).

All-inclusive pricing also makes switching harder. If you want to move to a provider that prices per-user with separate licensing pass-through, you are rebuilding the cost breakdown from scratch. (If you are actively planning a switch, the full playbook covers pre-notice audit, parallel running, and normalizing cost across different pricing models.)

What to verify about all-inclusive pricing

• What is actually included? A detailed appendix listing every service, tool, and license. The word “everything” is not a scope.
• How does pricing change over time? Annual escalator? Triggered by headcount thresholds? Microsoft licensing pass-through?
• What is NOT included? Project work almost always is not. On-site visits may not be. 24/7 tier may not be. Get the exclusions list.
• Can the bundle be unbundled if you leave? Some all-inclusive contracts make it hard to take partial components (e.g., your M365 licensing) to another provider.

Best fit

Mature SMBs (50-200 employees) that value predictability over price transparency, have stable requirements, and trust their MSP relationship. Often selected at multi-year renewals as the relationship matures.

Worst fit

Newer clients who have not yet built trust in the MSP. Cost-sensitive clients who want to see the math. Clients likely to change scope materially during the contract.

Monitoring-only pricing

How it works: The MSP deploys monitoring tooling (RMM, sometimes EDR) and charges a low per-device or per-user fee to run it. When an alert fires, the MSP notifies the client, but remediation is either the client’s responsibility or billed hourly as project work.

Typical pricing: $25-$75 per device per month for monitoring-only.

Why this exists

Two legitimate use cases:

1. Businesses with internal IT that want third-party monitoring coverage without outsourcing helpdesk. The internal team handles tickets and remediation; the MSP watches for issues the internal team might miss.
2. Very cost-sensitive businesses that want some visibility into their environment but cannot afford full managed IT.

Why it gets misrepresented

Some providers sell monitoring-only pricing as “managed IT” because the price point is attractive. It is not managed IT. When EDR fires an alert at 2am, monitoring-only service sends an email. Managed IT containment. Different products.

If a quote for “managed IT” looks dramatically cheaper than the standard SMB range, check whether it is actually monitoring-only dressed up in managed-IT language.

What to verify

• What does “detection” trigger? Alert only, or alert + response?
• What are the labor rates for out-of-scope work (i.e., fixing alerts)? Monitoring-only can get expensive fast when a real incident needs hours of remediation.
• What is covered and what is not? A monitoring-only contract that does not cover your M365 tenant, email security, or backup is only monitoring what EDR sees on endpoints.

Best fit

Businesses with capable internal IT that want second-set-of-eyes coverage. Businesses with very specific narrow needs (only EDR, or only server monitoring).

Worst fit

Businesses that want managed IT. Get full managed IT pricing or be honest about running IT yourself – do not pretend monitoring-only service is something it is not.

Hybrid models (and why they exist)

Most MSP contracts in practice are some combination of the above:

• Per-user for operational work + per-device for infrastructure. Common in businesses with both a knowledge-worker population and meaningful infrastructure.
• Per-user + per-server. Cleanest for cloud-first businesses that happen to have one or two servers.
• All-inclusive for managed IT + hourly for project work. Standard in most mature engagements. The recurring service is all-inclusive; specific projects (migrations, deployments, compliance prep) are scoped and quoted separately.
• Per-user with passthrough tooling licensing. Common when the MSP wants to pass Microsoft licensing changes through transparently rather than absorb them.

None of these hybrids are red flags. They reflect the reality that business IT cost is driven by multiple variables, and forcing everything into a single pricing unit is often a bad approximation.

What matters is that the contract is clear about which services are priced which way, so you can predict how your bill will change as your business changes.

How to pick the right model for your business

Work through these questions before an MSP conversation, then evaluate which pricing model each provider is offering against your answers.

1. How many devices does the average employee use?

• 1-2: per-user is probably the best fit
• 3+: per-user still works; per-device will likely cost more
• Devices per user is variable and high: per-device or a hybrid

2. What is your device-to-user ratio?

• 1.5:1 or less (typical office): per-user
• 2-5:1 (some shared workstations, some specialty devices): hybrid or per-device
• 5:1+ (retail, manufacturing, kiosks): per-device

3. How stable is your headcount?

• Very stable, low growth: flat tiered possibly
• Moderate growth / normal variability: per-user
• Aggressive growth: per-user with monthly reconciliation

4. How much infrastructure do you have?

• Cloud-first, no servers: per-user covers it
• One or two servers: per-user with separate per-server pricing
• Meaningful on-prem infrastructure: hybrid or per-device

5. How important is pricing predictability vs pricing transparency?

• Predictability is paramount: all-inclusive or flat tiered
• Transparency is paramount: per-user with line-item breakdown
• Middle ground: per-user with passthrough licensing

6. Do you have internal IT?

• No: full managed IT (per-user or per-device)
• Yes, handling ops: monitoring-only might fit, or a scoped specialty engagement
• Yes, but overwhelmed: full managed IT or co-managed IT

7. Are you in a regulated industry?

• HIPAA, SOC 2, PCI, CMMC: expect premium pricing tiers and more all-inclusive bundling to cover compliance overhead

The model matters. The rate matters more. Use the MSP cost benchmarks to sanity-check whether the number you are being quoted is reasonable for the model and scope.

Why the cheapest model is rarely the cheapest outcome

MSP pricing optimization is a common buyer mistake. The goal is not to find the cheapest pricing model – it is to find the model that aligns with how your business actually consumes IT support, because that is the one that will have the fewest surprises.

Common mistakes:

Picking per-device pricing because the per-device rate looks lower. For most modern SMBs, this ends up costing more once you count every device per user.

Picking flat tiered pricing because it is simple. Simple breaks down when your headcount changes. The businesses that save money with flat tiered are the ones that sign a contract and never grow, which is rare.

Picking all-inclusive pricing to avoid thinking about it. All-inclusive works when you trust the MSP. When you do not yet have the relationship, you are paying for opacity. Start with per-user and graduate to all-inclusive when you have data.

Picking monitoring-only because the headline number is low. This is only “managed IT” for businesses that run IT themselves. For everyone else, the remediation labor costs blow the headline savings within the first incident.

Not understanding what drives the scaling variable. If your business grows primarily by adding users, per-user makes sense. If it grows by adding locations, per-device or hybrid makes sense. If it grows by adding server-based services, per-server plus per-user makes sense. The scaling axis should match your growth pattern.

How pricing models interact with SLA and scope

Pricing models are not isolated choices. They interact with other contract elements.

Tighter SLAs cost more in any model. A 1-hour response SLA is a premium over a 4-hour response SLA regardless of whether you are per-user or per-device. See the SLA primer for what realistic SLA tiers look like.

All-inclusive pricing implies broader scope. If an MSP is charging one number for everything, they have absorbed more scope variability than a line-item provider. That is worth paying for, within reason.

Monitoring-only implies narrow scope. Do not expect an all-inclusive service from a monitoring-only fee.

Per-device pricing in device-heavy environments may come with an onboarding fee per device. Large environments (100+ devices) often have five-figure onboarding fees because deploying agents and configuring compliance is substantial work. What the onboarding fee actually buys you in the first 90 days covers the phase-by-phase breakdown.

These interactions are captured in the MSA guide – the eight sections every contract should have, with pricing-model clarity being one of them.

How Sequentur prices managed IT

Sequentur is a security-first MSP / MSSP for small and mid-sized businesses across the 15-to-250-employee range, including both general SMBs and regulated industries like healthcare, legal, financial services, and defense contractors. Our default pricing model is per-user for operational managed IT, with separate per-server pricing for clients with meaningful on-prem infrastructure, and project-based pricing for deployments and migrations. We use all-inclusive bundling for mature clients who have been with us long enough to want simplicity, and we never sell monitoring-only dressed up as managed IT.

We do not publish a public fee schedule because the right number depends on your environment, your security posture, your compliance scope, and your coverage needs. What we will tell you in any pricing conversation: which pricing model we are proposing, why that model fits your business, what is included at each tier, what counts as project work, and what the onboarding looks like. If the pricing model does not match how your business operates, we will say so and propose a different one.

If you want to work through which pricing model actually makes sense for your business, schedule a call. We will walk through your device-to-user ratio, your growth pattern, and your IT consumption profile, and tell you what model we would propose. If another MSP’s model is the better fit for you, we will say that too.