MSP Pricing Models: Per-User vs Per-Device
This article is for educational purposes only and does not constitute professional compliance advice or legal counsel. Your specific situation may vary, and you should evaluate any service provider relationship based on your organization's unique requirements.
You're asking for an MSP quote and you've gotten back three numbers that don't make sense to compare. One vendor quoted $100 per user. Another quoted $40 per device. A third has something called tiered pricing with different levels at different price points. You're trying to figure out which one is actually cheaper and what you're actually getting, and the vendors aren't making it easy to translate between their models.
This is deliberate. Pricing models aren't neutral—they're financial structures that align the vendor's incentives with how they'll deliver service. Understanding the differences between per-user, per-device, and hybrid models is the first step toward comparing MSP quotes fairly and knowing whether you're looking at a good deal or a trap.
The Fundamental Logic Behind Per-User Pricing
Per-user pricing is the simplest model to understand in theory: you pay a monthly fee for each employee, and the MSP manages all the devices that person uses. One person with a laptop, desktop, and phone? Still one monthly fee. Another person with just a laptop? Same monthly fee. The MSP's responsibility is that person's entire technology footprint, regardless of how many devices make up that footprint.
The appeal is obvious. Your company probably has an accurate headcount. Headcount is relatively stable, which means your IT costs are predictable. If you hire someone, you know the cost increases by exactly one month's fee. If someone leaves, you know you save that fee. You can build a budget and stick to it. For finance teams, this predictability is genuinely valuable because it eliminates the complexity of calculating device counts and managing variable costs.
But here's where per-user pricing gets complicated: what does "managed" actually mean? The devil isn't just in the details—the devil is that the details are usually vague. Does per-user pricing include unlimited helpdesk support or is there a cap on the number of tickets? Does it include all security services like endpoint detection and response, or are some security features extra? Does it cover cloud services, or are cloud costs billed separately? Does it include all hardware support or just software? Some MSPs define per-user pricing very broadly and include almost everything. Others define it narrowly and use per-user as a base with dozens of add-ons.
Per-user pricing works best for organizations with a stable employee count where employees have similar device configurations. If most of your people have a laptop and a phone, and that's it, per-user makes sense. If half your organization has simple single-device setups and the other half has extensive hardware—developers with multiple machines, engineers with specialized equipment—then per-user pricing starts to misalign with the actual work the MSP is doing.
The incentive built into per-user pricing is worth understanding. The MSP gets paid the same whether a user has one device or five devices. This means the vendor's incentive is actually to minimize device count per user, not to accumulate devices. A good per-user vendor won't try to talk you into buying extra devices you don't need. They'll want to keep your device footprint efficient. A vendor on this model also won't be motivated to spend extensive time supporting complex device ecosystems because more complex deployments don't pay them more—they just cost more to support.
How Per-Device Pricing Changes the Economics
Per-device pricing reverses the incentive structure. You pay a fee for each managed device, whether it's a workstation, laptop, server, network switch, or printer. One person with one device is one unit of cost. One person with three devices is three units of cost. This creates a more granular cost model that theoretically aligns cost with the actual complexity the MSP is managing.
Per-device pricing is less predictable than per-user because device count can swing independently of headcount. If you hire two people but they're taking over from two people who left, headcount stays flat but device counts might change. If your organization standardizes on laptops instead of desktops, your device count decreases without headcount changing. New regulations or security frameworks might require additional monitoring devices, which increases cost. Per-device pricing makes your IT costs variable in ways that per-user pricing doesn't.
The advantage of per-device pricing becomes apparent if your organization has legitimate reasons for high device counts. If you're managing significant server infrastructure, per-device pricing might actually be cheaper than per-user pricing because you're paying only for the devices you actually manage. If you have a warehouse full of IoT equipment or point-of-sale systems that require management, per-device pricing aligns cost with what the vendor is actually doing.
The catch, and this is important, is that supporting one person with one device is fundamentally less work than supporting one person with three devices. An MSP on per-device pricing knows this. They set their per-device price accordingly, which typically means you're paying a premium compared to per-user pricing when you account for total cost. The vendor is compensating for the fact that device complexity is real work.
Hybrid pricing models split the difference. You pay a per-user base fee, and then you pay for additional devices beyond a baseline number. So maybe you pay $100 per user for the first device, and then $25 for each additional device beyond that. This acknowledges that most people have one primary device but some people need more, without forcing everyone into the overhead of per-device accounting. Hybrid models are increasingly popular because they're more flexible than pure per-user while being more predictable than pure per-device.
Understanding "Managed" in All-Inclusive Packages
This is where MSP pricing gets genuinely confusing. When an MSP says they provide "all-inclusive" pricing or "fully managed" services, those words mean different things to different vendors. All-inclusive might mean they cover helpdesk, monitoring, patching, and backup. Or it might mean something much narrower. You need to push past the marketing language and get specific definitions in writing.
Take "managed backup" as an example. To one MSP, managed backup means backups are configured, data is being backed up daily, and the backup system is monitored to make sure backups are happening. To another MSP, managed backup might include all of that plus disaster recovery testing—quarterly exercises where they actually restore your data to verify it works. To a third MSP, managed backup might mean they use their own backup infrastructure and you're essentially renting backup capacity from them, which means switching vendors is difficult because you're locked into their system.
The same vagueness applies to security services. One vendor's all-inclusive package might include basic firewall monitoring. Another might include endpoint detection and response on all devices. A third might include both, plus threat intelligence, plus incident response consulting. These are wildly different service levels at different price points, and if you're comparing vendors based on "per-user cost," you might miss the fact that one vendor is giving you significantly more service.
This is where getting everything in writing becomes non-negotiable. When an MSP says their per-user price includes security services, ask them to itemize exactly what security services are included. Ask for definitions. "Advanced monitoring" means nothing without specifics. Does it mean 24/7 monitoring by humans? Automated monitoring with human review during business hours? What exactly is being monitored? At what frequency? What happens when something is detected?
All-inclusive pricing creates an incentive for the MSP to define scope conservatively. Remember, they get paid the same monthly amount regardless of how much work they actually do, so their incentive is to keep work manageable. They'll define scope narrowly to protect their margin. Then, when you ask for something that's technically outside scope, it becomes extra. This is where most organizations encounter their first surprise bill—they think something is included, the MSP says it's extra, and now you're negotiating. The way to prevent this is to get scope definitions in writing before you sign.
The Hidden Complexity of Comparing Models
Here's where most organizations struggle: comparing pricing across vendors using different models is almost impossible without creating a detailed specification of what you actually need, then pricing that specification across each vendor's model.
Let's say you're a 50-person company with mostly laptops, a few desktops, a couple of servers, and network equipment. Vendor A quotes you $100 per user, which comes to $5,000 per month. Vendor B quotes you $40 per device. You count up 60 devices total, so that's $2,400 per month. Vendor A looks expensive. But wait—Vendor B's per-device price doesn't include security monitoring, which is another $15 per device, bringing it to $3,300. Vendor A's per-user price includes security. Vendor A also includes disaster recovery testing; Vendor B charges extra for that. Now you need to add another $500 per month to Vendor B's cost. You're actually closer than it looks.
The real way to compare is to create a spreadsheet. List every service you need. List everything that's essential versus nice-to-have. Go to each vendor and get a complete quote with every service itemized. Add it up. The vendor with the lowest advertised price isn't necessarily the cheapest overall, and the vendor with the simplest pricing model isn't necessarily the easiest to understand once you dig into details.
Watch for vendors who come in significantly cheaper than everyone else. Sometimes they're just more efficient. Sometimes they're defining "included" more narrowly. If one vendor is $80 per user and another is $120 per user and everyone else is clustered around $100-110, understand why. Ask the cheap vendor what they're not doing that the others are doing. Ask the expensive vendor why they cost more. The answer usually reveals what's actually different about their service.
The Role of Volume Discounts and Scaling
As your organization grows, volume discounts usually apply. Vendors understand that larger customers are more efficient to serve, so they offer better pricing at scale. A vendor might quote $100 per user at 50 users, $90 per user at 100 users, and $80 per user at 200 users. This is standard and reasonable.
What matters is understanding when those discounts kick in and whether they actually stick. Some MSPs will offer you a discount to win your business and then later argue that the discount doesn't apply to new services you add, or doesn't carry forward to the next contract year. Get discount tiers and terms in writing. Get clarity on whether discounts apply to the entire contract or just the initial term. Get clarity on whether adding new services resets discount calculations.
Contract terms affect pricing significantly. A three-year contract might have better pricing than a one-year contract because the vendor has longer revenue certainty. But longer contracts lock you in longer. The tradeoff is typically between 5-10% better pricing for a longer commitment. Understand what you're giving up in flexibility versus what you're gaining in price reduction, and make sure that tradeoff actually makes sense for your situation.
Cost Structure and What It Tells You
Understanding the MSP's cost incentives helps you understand their pricing strategy. On per-user pricing, the vendor's profit comes from managing many users as efficiently as possible. They win by minimizing the actual work they do per user. On per-device pricing, the vendor's profit increases with device count, so they have more incentive to identify every device in your environment and make sure it's under management.
On tiered pricing with lots of add-ons, the vendor's profit comes from selling higher tiers and additional services. This creates incentive to recommend upgrade paths and identify reasons to add services. This doesn't mean MSPs are being dishonest, but it does mean their incentives might not be perfectly aligned with your interests. You need to understand the pricing model well enough to know what you're actually paying for and why the vendor is recommending what they're recommending.
The best pricing model is the one where the vendor's incentives align with your actual needs. If you need comprehensive monitoring and security, a vendor on per-user pricing where security is included is probably better than a vendor on per-device pricing where security is an add-on, because the per-user vendor's profit doesn't increase by upselling you security—they already get paid for it.
The Closing Reality
The pricing model is less important than understanding what you're paying for and making sure it aligns with your actual needs and budget. A per-user model that includes everything you need is better than a per-device model that's cheaper upfront but has expensive add-ons. A tiered model that gives you flexibility is worse than an all-inclusive model if the tiered model gradually becomes expensive as services accumulate.
Get everything in writing. Get pricing that's itemized by service. Get clear definitions of what's included and what's extra. Once you understand what you're actually paying for, comparing vendors becomes possible. Until you do, you're comparing numbers that don't mean the same thing across vendors, and that's how you end up with surprises in your first bill.
Fully Compliance provides educational content about IT compliance and cybersecurity. This article reflects general guidance about MSP pricing models. Individual MSP relationships vary — evaluate any provider based on your organization's specific needs, size, complexity, and budget.