# Per Device Pricing

Managing the financial health of a Managed Service Provider (MSP) often comes down to one fundamental decision: how you charge for your services. Per Device Pricing is one of the most established billing models in the IT services industry, offering a straightforward way to tie revenue to the physical infrastructure you manage.

Managing the financial health of a Managed Service Provider (MSP) often comes down to one fundamental decision: how you charge for your services. **Per Device Pricing** is one of the most established billing models in the IT services industry, offering a straightforward way to tie revenue to the physical infrastructure you manage. While it may seem simple on the surface, its success depends on how well you account for the hidden costs of modern security and multi-device users.

At MSP Agenda, we believe every pricing conversation should start with commercial clarity. Our founder, Luis Navarro, built Totality Services from a small team to a highly profitable MSP with over 150 clients across London and Johannesburg. That journey, which led to an eight-figure exit, wasn't built on technical jargon. It was built on understanding the relationship between the work performed, the value delivered to the client, and the resulting profitability of the business. **Per Device Pricing** is a tool to manage that relationship, provided you use it correctly.

## Key Takeaways

- **Predictability:** Per Device Pricing offers a tangible, easy-to-track metric for both the MSP and the client.
- **Scalability:** As a client adds hardware, your recurring revenue grows automatically, aligning your growth with their infrastructure.
- **Hybrid Reality:** Modern MSPs often combine device-based billing with user-based components to cover cloud services and security.
- **Inventory Management:** Success requires a disciplined approach to RMM (Remote Monitoring and Management) and asset tracking.
- **Profitability Risk:** Without clear boundaries on "what counts as a device," MSPs risk margin erosion from unbilled peripherals.
- **Client Communication:** This model is highly effective for clients who view IT as an infrastructure cost rather than a productivity cost.

### What is Per Device Pricing?

**Per Device Pricing** is a managed services billing model where the client is charged a flat monthly fee for every specific piece of hardware supported by the MSP. This typically includes servers, workstations, laptops, and sometimes mobile devices or network infrastructure like firewalls and switches. It is a "unit-based" approach that makes the monthly invoice directly reflect the physical scale of the client’s environment.

- **Workstations/Laptops:** Usually the core of the billing, covering OS updates, security software, and helpdesk support.
- **Servers:** Billed at a higher rate due to the complexity of maintenance, backups, and critical nature of the hardware.
- **Network Equipment:** Managed switches, firewalls, and BDR (Backup and Disaster Recovery) appliances are often included as separate line items.
- **Mobile Devices:** Increasingly common in MDM (Mobile Device Management) scenarios, though often at a lower price point than PCs.

### The Commercial Logic of Device-Based Billing

From a commercial perspective, billing by the device is rooted in the "cost of goods sold" (COGS). Every laptop you manage requires a seat of your RMM tool, an antivirus license, an EDR agent, and a slice of your technical team's time. By using **Per Device Pricing**, you are essentially creating a direct link between your overhead and your revenue.

Luis Navarro’s experience at Totality Services showed that clients often appreciate the transparency of this model. When a client hires five new employees and buys five new laptops, they expect their IT bill to go up. It’s a logical, easy-to-digest conversation that doesn't require a deep dive into technical architecture. If the device exists, it’s supported; if it’s supported, it’s billed.

## Comparing Pricing Models: Device vs. User

Choosing between **Per Device Pricing** and Per User Pricing is one of the most frequent debates in the industry. Neither is objectively "better," but they suit different types of client environments and business strategies. Understanding the nuances is critical for maintaining healthy margins.

| Feature | Per Device Pricing | Per User Pricing |
| --- | --- | --- |
| **Primary Metric** | Number of hardware endpoints (PCs, Servers) | Number of employees/identities |
| **Client Perception** | Easy to audit; feels like utility billing | Focuses on the person and productivity |
| **Multi-Device Handling** | Revenue increases if a user has two PCs | Revenue stays flat regardless of hardware count |
| **Admin Overhead** | Requires constant RMM inventory sync | Requires HR/Active Directory sync |
| **Security Alignment** | Best for endpoint-centric security (EDR/AV) | Best for identity-centric security (MFA/SaaS) |

### When Per Device Pricing Wins

This model excels in environments where the device-to-user ratio is high or highly variable. For example, in a laboratory or a manufacturing facility, there may be multiple specialised workstations shared by a rotating shift of workers. In this scenario, billing per user would drastically underrepresent the amount of hardware maintenance and security monitoring required.

It also provides a natural "buffer" for MSPs. If a power user insists on having a desktop at the office and a high-end laptop for travel, **Per Device Pricing** ensures you are paid for the extra management, patching, and security licensing required for that second machine. Under a per-user model, that second device is effectively a "free" support burden that eats into your profit.

### The Downside: The "Invisible" User

The primary risk with **Per Device Pricing** is that it can ignore the amount of time spent supporting the *human* using the device. A user struggling with Microsoft Teams or a forgotten password takes the same amount of helpdesk time regardless of whether they are on a laptop or a tablet. As IT shifts more toward cloud services (SaaS) and identity management, the "device" becomes only a small part of the total support story.

## Operationalizing the Model

To run a profitable business using **Per Device Pricing**, you need absolute accuracy in your asset tracking. If your RMM shows 100 devices but you are only billing for 85, you are essentially giving away 15% of your service for free. This is where many MSPs struggle—the gap between technical reality and billing accuracy.

#### 1. Standardising Your Definitions

You must be crystal clear in your contracts about what constitutes a "billable device." If a client plugs in a personal NUC or brings in an old home laptop, does it automatically get added to the bill? 
 

We recommend defining billable units as:

 Any endpoint with your RMM agent installed.
 Any network device requiring firmware updates and monitoring.
 Any virtual or physical server requiring backup and patch management.

#### 2. Automating the Sync

Don't rely on manual audits. The most successful MSPs integrate their RMM tool directly with their PSA (Professional Services Automation) and billing software. This ensures that the moment a new device is onboarded, the next month's invoice reflects the change. This "proactive billing" is a hallmark of a commercially mature MSP.

#### 3. Tiered Device Pricing

Not all devices are created equal. You shouldn't charge the same for a basic office PC as you do for a high-performance CAD workstation or a critical database server. Most MSPs use a tiered structure:

 **Standard Workstation:** Base support, AV, and patching.
 **Premium Workstation:** Includes advanced EDR, SOC monitoring, and backup.
 **Server Tier:** Significantly higher fee to cover high-availability requirements.

## Security Reviews and Per Device Value

A major part of the MSP Agenda philosophy is that security should not be a "hidden" cost. Whether you use **Per Device Pricing** or another model, your clients need to understand the value of what you are protecting. This is why standardised Security Reviews are vital.

When you sit down for a QBR (Quarterly Business Review), the device count shouldn't just be a number on an invoice. It should be a gateway to discussing risk. Each device is an entry point for a threat. By framing the conversation around the security posture of those devices, you move from being a "hardware guy" to a strategic partner. If a device is out of warranty or running an old OS, it’s not just an old machine—it’s a commercial risk to the client's operations.

Luis Navarro always emphasised that a recommendation the client doesn't understand is unlikely to become a project. If you are billing per device, use your security reviews to explain *why* the security stack on that device matters. This builds the trust necessary to move clients toward more advanced (and profitable) security tiers.

## Commercial Pitfalls to Avoid

Even experienced MSP owners can get tripped up by the nuances of hardware-centric billing. Here are the most common mistakes we see in the field:

### 1. Ignoring "Ghost" Devices

"Ghost" devices are old machines that have been replaced but never decommissioned in your RMM. If you keep billing for them, you risk a frustrated client when they eventually audit their own hardware. If you stop billing but keep the agent active, you’re paying for licenses you aren't recouping. Discipline in the offboarding process is just as important as the onboarding process.

### 2. The "BYOD" Dilemma

Bring Your Own Device (BYOD) can be a nightmare for **Per Device Pricing**. If an employee uses their personal iPad for work email, do you charge for it? If you don't, you're providing "free" support for the mail setup and security. If you do, the client might push back because they don't own the hardware. The best approach is to charge a flat "Mobile Support" fee or shift those users to a hybrid per-user/per-device hybrid model.

### 3. Margin Squeeze from Licensing

Many MSPs bundle software (M365, AV, Backup) into their per-device fee. However, software vendors often bill per *user*. If you have a client with one user who has three devices, you are collecting three device fees but only paying for one M365 license. That’s great for your margin. But if you have three users sharing one device, you are collecting one device fee while paying for three M365 licenses. This "licensing mismatch" can quietly kill your profitability if you don't monitor it.

## Strategic Growth and Exit Value

For those looking to eventually sell their MSP—much like Luis did with Totality Services—the consistency and predictability of your revenue model are paramount. Acquirers look for high "Recurring Revenue" (RR) and clear, scalable processes. **Per Device Pricing** is highly attractive to buyers because it is easily auditable.

When your pricing is standardised, it shows that your business is a "machine" rather than a collection of custom deals. A buyer can look at your RMM count, look at your billing, and see a direct correlation. This transparency reduces their perceived risk and increases your valuation.

### Transitioning to a Strategic Conversation

While the bill is based on devices, the *value* is based on outcomes. Don't let your client meetings devolve into a debate over whether a specific printer should be $10 a month. Use the device count as a baseline to talk about uptime, security, and employee productivity.

As we often say at MSP Agenda, your client doesn't need another technical report. They need to understand what is wrong, why it matters, and what they need to do next. Whether you are billing for 50 laptops or 5 servers, the goal of your reporting should be to create accountability and drive the next profitable project that keeps them secure.

## Frequently Asked Questions

### Is Per Device Pricing better than Per User Pricing?

It depends on the client’s environment. **Per Device Pricing** is superior when there are more devices than users (e.g., labs, factories, or power-user firms). Per User is often better for modern office environments where users work across multiple devices and SaaS platforms. Many successful MSPs use a hybrid approach.

### How do I handle price increases with this model?

Price increases should be tied to the increasing cost of the "stack" on the device. When you add a new security tool (like Managed EDR) to your service offering, you should increase the per-device rate accordingly. Communicate this change through a Security Review, explaining how the new tool reduces the client’s specific business risks.

### Should I charge for network equipment like switches?

Yes. Although they don't require helpdesk support in the same way a laptop does, they require monitoring, firmware updates, and periodic configuration changes. Most MSPs charge a smaller, flat fee for network infrastructure components to ensure the time spent managing the "backbone" is covered.

### What happens if a client refuses to pay for a device?

If a device is on the network and requires support or security, it must be billed. If a client refuses to pay for it, you must officially "exclude" it from support and, ideally, block it from the network. Supporting "unmanaged" devices is a significant security risk and a liability for your MSP.

### How does Per Device Pricing affect my company’s valuation?

It generally has a positive effect because it is easily verified during due diligence. A clear link between a technical asset (the device) and a financial asset (the monthly fee) makes your revenue stream feel "solid" to potential acquirers.

### Can I include Microsoft 365 in a per-device fee?

You can, but it is risky. Since Microsoft bills per user, your margins will fluctuate based on the user-to-device ratio. It is usually safer to bill for hardware support per device and for SaaS/Licensing per user as a separate line item on the same invoice.

At the end of the day, **Per Device Pricing** is about creating a fair exchange of value. You provide the expertise and tools to keep the hardware running and secure, and the client provides a predictable fee that allows you to scale your team and your business. By focusing on the commercial reality of this relationship—rather than just the technical details—you position your MSP for long-term growth and a successful future exit.

---

Source: https://mspagenda.com/glossary/per-device-pricing
Last updated: 2025-12-25