The MSP Billing Decision Most Owners Made Without Making It
TL;DR: Most MSPs didn't choose their billing model so much as inherit it. Per-seat and per-device pricing both produce recurring revenue, but they behave very differently as your client base, your tooling costs, and your environments evolve. This post breaks down where each model wins, where each one quietly eats your margin, and how to make the decision deliberately instead of by default.
Choosing a billing model for your MSP is a bit like picking a cell phone plan in 2009. Everyone just picked whatever Verizon handed them, assumed it was fine, and didn't think about it again until the bill got weird. The decision got made, just not on purpose.
That's exactly how most MSP owners end up with their billing model. Not from a spreadsheet, not from a strategy session: from whatever their first few clients expected or whatever the peer in their Facebook group was using. It works until it doesn't, and by the time it doesn't, you've got 30 clients on a structure that's quietly working against you.
The stakes are higher than they look. Your billing model isn't just an invoicing preference; it determines how your revenue scales, how your vendor costs align with what you charge, and how much margin you're actually keeping on every client in your book. In a market where tooling costs keep climbing and clients keep adding devices, the wrong model can erode profitability without ever showing up as an obvious problem.
Per-seat and per-device pricing are the two models that dominate MSP contracts. Both produce recurring revenue. Both can work. But they behave very differently depending on your client mix, your security stack, and how modern your clients' environments actually are.
This post breaks down the differences so you can make the decision deliberately instead of by default.
Table of Contents
- How Per-Seat Pricing Works
- How Per-Device Pricing Works
- Where Per-Seat Wins
- Where Per-Device Wins
- The Modern Environment Problem
- How to Choose (and How to Switch)
- The Model You Picked Is the Business You're Building
- Key Takeaways
- Frequently Asked Questions
How Per-Seat Pricing Works
Per-seat pricing bills clients based on the number of employees you're supporting, regardless of how many devices those employees use. A 20-person company pays for 20 seats. Whether each of those people uses a laptop, a phone, and a tablet, or just a desktop, the invoice stays the same.
Per-user pricing is the dominant model in 2026, with roughly 22% of MSPs using it as their default, a number that has risen every year since 2021, according to Kaseya's MSP Benchmark Survey. The appeal is straightforward: it's simple to quote, it maps to headcount (which clients already track), and it scales naturally as clients hire.
One MSP owner who scaled through the growth stage put it directly: business owners always know their headcount, but rarely know their device or server count. Asking "how many servers do you have?" risks making the prospect feel uninformed and erodes trust before a quote even lands. A human-friendly number, "$150 per user, 20 employees, $3,000 a month," closes faster and causes fewer awkward pauses.
How Per-Device Pricing Works
Per-device pricing bills based on the number of managed endpoints: workstations, servers, mobile phones, printers, or whatever you've agreed to cover. Each device type typically carries its own rate.
A common example: an MSP might charge $100 per workstation and $250 per server each month. That fee stays consistent regardless of how much support each device actually requires, because billing is tied to inventory rather than usage.
The appeal here is precision. If you're supporting an environment with a lot of infrastructure relative to headcount, per-device pricing can accurately capture the complexity you're managing. A 10-person manufacturing shop with 30 workstations, 3 servers, and a pile of networked equipment is a materially different support load than a 10-person law firm with 10 laptops and a cloud-based everything.
Where Per-Seat Wins
Per-seat pricing is purpose-built for the modern knowledge-work environment. It handles BYOD naturally. It doesn't penalize clients for using multiple devices. It aligns with how security tools are licensed (most EDR, MFA, and identity management platforms price per user, not per device), which keeps your cost model and your billing model pointed in the same direction.
It also makes the sales conversation easier. Prospects understand headcount. They don't always understand device inventories, and anything that requires them to go count their endpoints before you can give them a number is friction you don't need. When clients feel the pricing process is simple and transparent, they're more likely to sign and less likely to dispute invoices later.
Per-seat pricing also scales cleanly. When a client hires five people, your revenue goes up by five seats. No audit required, no renegotiation, just a bigger invoice that reflects a bigger relationship.
Where Per-Device Wins
Per-device pricing earns its keep in environments where device counts tell the real story. A client with heavy infrastructure, lots of servers, specialized hardware, or a high device-to-user ratio represents a legitimate support burden that per-seat pricing might underestimate.
It's also easier to audit. You can run a network discovery, count the devices, and arrive at a number that's defensible and hard to dispute. For MSPs who serve clients in manufacturing, healthcare (on-prem equipment, medical devices), or any industry with complex physical infrastructure, per-device pricing can protect margins that per-seat would quietly erode.
For MSPs who are earlier in their growth and working with smaller, more traditional client environments, per-device also offers a familiar structure that doesn't require re-educating clients who are used to thinking about IT costs in terms of machines.
The Modern Environment Problem
Here's where per-device starts to crack. Hybrid work, multi-device use, and BYOD policies are pushing providers to reevaluate traditional billing models. What once felt straightforward can break down fast in complex environments.
The average knowledge worker in 2026 uses multiple devices across multiple locations. If you're billing per device and your client allows BYOD, you either charge for personally owned hardware (which clients hate) or you don't (which leaves you supporting devices you're not getting paid to support). Neither is a good answer.
Per-device also creates tension around security licensing. Most modern security tools (EDR, identity protection, email security) are priced per user. If you're billing clients per device but your vendor costs are per user, your cost model and your billing model are running in opposite directions. That gap quietly eats margin.
How to Choose (and How to Switch)
A practical decision framework: if your average client has more than two devices per user and a heavy security stack, default to tiered per-user pricing; everywhere else, plain per-user tends to be the cleaner choice.
If you're considering switching models on existing clients, tie the change to a contract renewal or a service upgrade. Never change the billing model mid-contract without a value story attached. Frame it around simplicity and alignment with how your tooling actually works, and most reasonable clients will follow.
As we covered in the previous post, Your MSP Pricing Is Either Building Your Business or Bleeding It, the right pricing model has to connect to your true cost per user. Whichever model you choose, make sure it's doing math that works in your favor, not just math that feels familiar.
The Model You Picked Is the Business You're Building
Per-seat and per-device pricing both work. But the one you're on shapes everything downstream: how your revenue scales, how your vendor costs align, and how much margin you actually keep as your client base grows. The difference between a deliberate choice and an inherited default is the difference between a pricing structure that compounds and one that quietly caps you.
The problem is that most MSPs don't discover the gap until they're already deep in it: margins tighter than they should be, vendor costs running in one direction and billing in another, and no clean moment to course correct without disrupting existing client relationships. By the time it's obvious, it's already been expensive.
Tactics works exclusively with MSPs, which means billing model decisions, positioning gaps, and pipeline problems aren't abstract concepts here. They're the actual conversations we have every week with owners who are delivering excellent service and wondering why the revenue doesn't reflect it. If your pricing model is working against your growth, that's a fixable problem, and it usually starts with getting the right clients in front of the right message.
Get in touch with Tactics Marketing, and let's make sure your pricing is building the business you're actually trying to build.
Key Takeaways
- Per-seat pricing bills by headcount; per-device bills by endpoint count. Both produce recurring revenue, but they scale differently and behave differently under pressure.
- Per-seat is the dominant model in 2026 and aligns naturally with modern security tooling, BYOD environments, and knowledge-work clients.
- Per-device pricing holds up in environments with high device-to-user ratios, heavy infrastructure, or specialized hardware.
- Your billing model and your vendor cost model should point in the same direction. If they don't, margin disappears quietly.
- Per-device pricing creates a structural tension with modern security licensing. Most security tools price per user; if your billing doesn't match, the gap eats margin silently.
- Switching models is cleanest at contract renewal, with a clear value story attached.
Frequently Asked Questions
1. Can I use both per-seat and per-device pricing in the same MSP?
Yes, and many MSPs do. A common approach is to default to per-user pricing for standard managed clients and use per-device pricing for specific environments (like manufacturing or healthcare) where infrastructure complexity makes per-device the more accurate fit. The key is consistency within each client contract and a clear rationale for why the model fits that environment.
2. What happens to per-device pricing when a client goes remote or hybrid?
It gets complicated quickly. Remote and hybrid environments often involve BYOD, personal devices, and hardware spread across multiple locations. Billing per device either forces awkward conversations about what's "covered" or leaves you supporting endpoints you're not charging for. Per-user pricing sidesteps this entirely because it's based on people, not physical inventory.
3. Which model is better for sales conversations?
Per-user pricing wins on the sales call almost every time. Prospects know their headcount and can do the math instantly. Per-device pricing requires them to know their inventory, which they often don't, creating friction before you've even gotten to the value conversation. Simpler math closes faster.
