Per User vs. Per Device Pricing: The Hard Math for Growing MSPs
You know how thin margins can be the silent killer as the owner or service delivery manager of a 10-technician MSP. You are not just handling running servers; you're handling a balance. When your pricing is not aligned with your client's work, your staff will be clocking in 60-hour work weeks while you're only in net single-digit positive numbers.
The dichotomy of "Per-User Pricing vs. Per-Device Pricing" is where the discussion of structuring your managed services agreements often ends up.
Vendor marketing makes it seem like there's one right answer, but there's really a lot of complication. There are things that every model has that can make a successful account sink fast.
Let's explore the realities of both models, the numbers, and the best approach to selecting the structure for your own MSP.
The Core Dilemma: What are you ACTUALLY Selling?
Before you examine the spreadsheets, make sure you understand what your client is paying for.
When you sell on a per-device basis, you're selling infrastructure stability. You are saying your core value is to maintain, fix, and keep physical assets online.
Selling employee productivity is equivalent to pricing per user. Your value is that you are keeping humans connected, secure, and functional, in whatever way they use their tools.
This is no academic matter for the 10-tech MSP. It influences your technicians' time, the auditing of your agreements, and the ease with which you can audit your client's agreements.
Also Read: LLM-Friendly Content Architecture: Structuring B2B Tech Blogs for Perplexity AI Retrieval
The Per-Device Pricing Model: Predictable but Fragile
Per-device model: You bill a flat monthly rate for all managed devices, which are usually segmented by several categories such as workstations, mobile devices, physical servers, and virtual servers.
The Pros: Simplicity and Direct Alignment
Easy Auditing: There is an RMM agent installed on a machine, or there isn't. In such a case, if your RMM is reporting 142 active agents, then you're billing for 142 agents. No grey area or manual reconciliation between user count and there.
Direct Cost Alignment: You're paying for most of your modern tool stack (RMM, antivirus, EDR, and backup software) on a per-endpoint basis. With per-device pricing, it makes obvious sense to match your main software expenses to your income.
The Cons: The Multi-Screen Trap and Client Friction
The average knowledge worker uses not just one computer in 2026. In the workplace, they have a desktop computer, a laptop at home, a tablet, and a smartphone that is used for business.
At $100 per device, that one employee will cost the client $300 per month. This often causes conflicts. To save money, clients will request that your agent take your agent off of their home laptop or their personal phone, and your MSP will end up with a security blind spot and uncompensated support calls when those unmanaged devices inevitably fail.
Related: Entity Optimization for ITES: How to Teach AI What Your Service Does
The Per-User Pricing Model: Modern but Complex!
A per-user model means that you bill a fixed fee per user employee. They pay this fee for support of all their associated devices, which is usually limited to a reasonable number (say, one laptop, one desktop, one mobile phone).
The Pros: Clean Scaling and High Margin Potential
Value-Oriented Pitch: CFOs understand headcounts. If a client is to hire a new account manager, they are aware exactly how much they will have to increase their IT budget. To them, it is reasonable and predictable.
Higher Margins on Multi-Device Users: The typical user in an average client portfolio uses 1.2-1.5 devices; a user with three devices can be a margin drain. If you charge your per-user fee at the right rate, then you'll be able to collect premium revenue from single-device users that will compensate for the multi-device ones.
The Cons: Shadow Support Burden and the Audit Overhead
Directory Chaos: Your client's Active Directory or Microsoft 365 tenant is not always clean like your RMM agents. The directory is often filled with terminated employees, shared mailboxes, and service accounts. Otherwise, you'll end up with active users who gladly pay for the privilege of using your site, or ghost users who are billed to you for services provided and then complain about the invoice.
The "Bring Your Own Device" (BYOD) Nightmare: When under a per-user model, clients can expect your helpdesk to be an "all things supported" helpdesk buffet for any device your employees bring in. This includes personal home PCs, family iPads, and smart TVs.
Under-the-Hood Math: Side-by-Side Scenarios
Let's take a look at two common client scenarios and how these models work.
Scenario A: The Multi-Device Knowledge Worker
Imagine a professional services company that has 30 staff members and a hybrid work environment.
Total Devices: 30 Office Desktops, 30 Work Laptops, and 15 company-provided Smartphones. (Total: 75 devices).
The Takeaway: Per-device pricing can provide better margins, as it directly accounts for the additional attack surface and maintenance burden of the additional physical device.
Scenario B: The Shared-Device Shift Worker
Imagine a manufacturing plant or medical center that has 60 workers working shifts.
Total Devices: 15 shared terminal PCs on the floor and 2 servers. (Total: 17 devices).
The Takeaway: Per-user pricing helps protect your margins for blue-collar, retail, or healthcare clients with many users and few devices. If you charged this client on a per-device basis, you're supporting 60 different people using your helpdesk across 15 devices, killing your profitability!
What Makes for an Operational Trap: What Breaks When You Choose Wrong?
Trap 1: The Active Directory Cleanup Nightmare
When you're on per-user pricing, your billing team needs to do a lot of reconciliations each month. When you import user lists directly from Microsoft 365, you may encounter shared mailboxes (info@client.com) or service accounts.
Your technician will overbill the client if he doesn't specifically note them as non-billable. You may end up leaving a real user unbilled if they delete them without verifying. If your PSA is not well integrated with your directory tool, this reconciliation can take up to 5-10 hours of administrative time per month.
Trap 2: The "Ghost Device" Margin Bleed
With per-device pricing, when the client retires a laptop and stores it in the closet, and your tech is not instructed to unload the RMM agent from the computer, you will continue to pay for that laptop's software license to your software vendors. Even worse, if you don't review your RMM to compare against your current billing contracts, you could be paying for a license that you aren't billing the client for.
How to Pick (and Switch) Without Leaving Your Clients Behind
It is not necessary to fit all of your clients into one standard mold. A Hybrid Pricing Model is one that many successful MSPs employ to ensure their margins are not compromised and that their clients are not let down.
The base fee for the servers, firewalls, and network is all covered, and the per-user fee is for end-user helpdesk and licensing, which protects your business from margin bleed by shift workers and from pushback from multiple devices.
Step 1: Analyze Your Existing Stack Costs
Before adjusting pricing, determine your true managed endpoint cost. Factor in:
Your RMM agent
The allocation of your PSA license
Using EDR / Antivirus / DNS filtering is the way to go
Backup licensing
Ensuring email security and backup
For high hard cost (more than $35/device), a per-device or hybrid setup is safer so you don't have to run a client into the red.
Step 2: Transition Slowly
If you must migrate your clients from per-device to per-user:
Don't do it during the contract. Wait until they renew annually.
Show them the data. Provide a 90-day ticket report that indicates that 80% of their support requests are categorized as user-initiated (such as password resets, application issues, printer mapping), and not hardware issues.
See it as a good thing. Tell them that per-user pricing allows their employees to work securely from their own computers or phones, and that the business isn't caught off-guard with expensive setup charges or security vulnerabilities.
Streamline Your Billing with the Right Tool
Regardless of pricing model – per-user, per-device, or hybrid, if you don't have a unified PSA and RMM, the cost leakage will take a serious toll on your margins, fast.
Your billing contracts automatically update with your real-time RMM agent count and AD users with the right tool. No more manual spreadsheets, no end-of-month recon problems, and no "ghost" devices. Simple, precise, and accurate invoices that reflect your actual business situation.
You know how thin margins can be the silent killer as the owner or service delivery manager of a 10-technician MSP. You are not just handling running servers; you're handling a balance. When your pricing is not aligned with your client's work, your staff will be clocking in 60-hour work weeks while you're only in net single-digit positive numbers.
The dichotomy of "Per-User Pricing vs. Per-Device Pricing" is where the discussion of structuring your managed services agreements often ends up.
Vendor marketing makes it seem like there's one right answer, but there's really a lot of complication. There are things that every model has that can make a successful account sink fast.
Let's explore the realities of both models, the numbers, and the best approach to selecting the structure for your own MSP.
The Core Dilemma: What are you ACTUALLY Selling?
Before you examine the spreadsheets, make sure you understand what your client is paying for.
When you sell on a per-device basis, you're selling infrastructure stability. You are saying your core value is to maintain, fix, and keep physical assets online.
Selling employee productivity is equivalent to pricing per user. Your value is that you are keeping humans connected, secure, and functional, in whatever way they use their tools.
This is no academic matter for the 10-tech MSP. It influences your technicians' time, the auditing of your agreements, and the ease with which you can audit your client's agreements.
Also Read: LLM-Friendly Content Architecture: Structuring B2B Tech Blogs for Perplexity AI Retrieval
The Per-Device Pricing Model: Predictable but Fragile
Per-device model: You bill a flat monthly rate for all managed devices, which are usually segmented by several categories such as workstations, mobile devices, physical servers, and virtual servers.
The Pros: Simplicity and Direct Alignment
Easy Auditing: There is an RMM agent installed on a machine, or there isn't. In such a case, if your RMM is reporting 142 active agents, then you're billing for 142 agents. No grey area or manual reconciliation between user count and there.
Direct Cost Alignment: You're paying for most of your modern tool stack (RMM, antivirus, EDR, and backup software) on a per-endpoint basis. With per-device pricing, it makes obvious sense to match your main software expenses to your income.
The Cons: The Multi-Screen Trap and Client Friction
The average knowledge worker uses not just one computer in 2026. In the workplace, they have a desktop computer, a laptop at home, a tablet, and a smartphone that is used for business.
At $100 per device, that one employee will cost the client $300 per month. This often causes conflicts. To save money, clients will request that your agent take your agent off of their home laptop or their personal phone, and your MSP will end up with a security blind spot and uncompensated support calls when those unmanaged devices inevitably fail.
Related: Entity Optimization for ITES: How to Teach AI What Your Service Does
The Per-User Pricing Model: Modern but Complex!
A per-user model means that you bill a fixed fee per user employee. They pay this fee for support of all their associated devices, which is usually limited to a reasonable number (say, one laptop, one desktop, one mobile phone).
The Pros: Clean Scaling and High Margin Potential
Value-Oriented Pitch: CFOs understand headcounts. If a client is to hire a new account manager, they are aware exactly how much they will have to increase their IT budget. To them, it is reasonable and predictable.
Higher Margins on Multi-Device Users: The typical user in an average client portfolio uses 1.2-1.5 devices; a user with three devices can be a margin drain. If you charge your per-user fee at the right rate, then you'll be able to collect premium revenue from single-device users that will compensate for the multi-device ones.
The Cons: Shadow Support Burden and the Audit Overhead
Directory Chaos: Your client's Active Directory or Microsoft 365 tenant is not always clean like your RMM agents. The directory is often filled with terminated employees, shared mailboxes, and service accounts. Otherwise, you'll end up with active users who gladly pay for the privilege of using your site, or ghost users who are billed to you for services provided and then complain about the invoice.
The "Bring Your Own Device" (BYOD) Nightmare: When under a per-user model, clients can expect your helpdesk to be an "all things supported" helpdesk buffet for any device your employees bring in. This includes personal home PCs, family iPads, and smart TVs.
Under-the-Hood Math: Side-by-Side Scenarios
Let's take a look at two common client scenarios and how these models work.
Scenario A: The Multi-Device Knowledge Worker
Imagine a professional services company that has 30 staff members and a hybrid work environment.
Total Devices: 30 Office Desktops, 30 Work Laptops, and 15 company-provided Smartphones. (Total: 75 devices).
The Takeaway: Per-device pricing can provide better margins, as it directly accounts for the additional attack surface and maintenance burden of the additional physical device.
Scenario B: The Shared-Device Shift Worker
Imagine a manufacturing plant or medical center that has 60 workers working shifts.
Total Devices: 15 shared terminal PCs on the floor and 2 servers. (Total: 17 devices).
The Takeaway: Per-user pricing helps protect your margins for blue-collar, retail, or healthcare clients with many users and few devices. If you charged this client on a per-device basis, you're supporting 60 different people using your helpdesk across 15 devices, killing your profitability!
What Makes for an Operational Trap: What Breaks When You Choose Wrong?
Trap 1: The Active Directory Cleanup Nightmare
When you're on per-user pricing, your billing team needs to do a lot of reconciliations each month. When you import user lists directly from Microsoft 365, you may encounter shared mailboxes (info@client.com) or service accounts.
Your technician will overbill the client if he doesn't specifically note them as non-billable. You may end up leaving a real user unbilled if they delete them without verifying. If your PSA is not well integrated with your directory tool, this reconciliation can take up to 5-10 hours of administrative time per month.
Trap 2: The "Ghost Device" Margin Bleed
With per-device pricing, when the client retires a laptop and stores it in the closet, and your tech is not instructed to unload the RMM agent from the computer, you will continue to pay for that laptop's software license to your software vendors. Even worse, if you don't review your RMM to compare against your current billing contracts, you could be paying for a license that you aren't billing the client for.
How to Pick (and Switch) Without Leaving Your Clients Behind
It is not necessary to fit all of your clients into one standard mold. A Hybrid Pricing Model is one that many successful MSPs employ to ensure their margins are not compromised and that their clients are not let down.
The base fee for the servers, firewalls, and network is all covered, and the per-user fee is for end-user helpdesk and licensing, which protects your business from margin bleed by shift workers and from pushback from multiple devices.
Step 1: Analyze Your Existing Stack Costs
Before adjusting pricing, determine your true managed endpoint cost. Factor in:
Your RMM agent
The allocation of your PSA license
Using EDR / Antivirus / DNS filtering is the way to go
Backup licensing
Ensuring email security and backup
For high hard cost (more than $35/device), a per-device or hybrid setup is safer so you don't have to run a client into the red.
Step 2: Transition Slowly
If you must migrate your clients from per-device to per-user:
Don't do it during the contract. Wait until they renew annually.
Show them the data. Provide a 90-day ticket report that indicates that 80% of their support requests are categorized as user-initiated (such as password resets, application issues, printer mapping), and not hardware issues.
See it as a good thing. Tell them that per-user pricing allows their employees to work securely from their own computers or phones, and that the business isn't caught off-guard with expensive setup charges or security vulnerabilities.
Streamline Your Billing with the Right Tool
Regardless of pricing model – per-user, per-device, or hybrid, if you don't have a unified PSA and RMM, the cost leakage will take a serious toll on your margins, fast.
Your billing contracts automatically update with your real-time RMM agent count and AD users with the right tool. No more manual spreadsheets, no end-of-month recon problems, and no "ghost" devices. Simple, precise, and accurate invoices that reflect your actual business situation.
Comments
Post a Comment