The MSP revenue model is the commercial framework through which a Managed Service Provider generates income by delivering IT services, cybersecurity, and consulting to business clients. Unlike traditional "break-fix" models that rely on hourly billing for reactive repairs, the modern MSP model prioritises proactive, recurring revenue (MRR) by charging a predictable monthly fee for ongoing management, monitoring, and security.
- Recurring Revenue: The foundation of the model, typically delivered through per-user or per-device pricing.
- Project Revenue: One-time professional services such as cloud migrations or hardware refreshes.
- Transactional Revenue: The resale of hardware, software licenses, and cloud subscriptions.
- Security-as-a-Service: Specialised high-margin layers that address modern compliance and risk management.
Building a successful MSP isn't just about being good at technology. It’s about building a predictable, scalable commercial engine. Luis Navarro, the founder of MSP Agenda, learned this over 15 years growing Totality Services from a small startup into a highly profitable MSP with an eight-figure exit.
Luis wasn't the technical lead; his focus was on the commercial reality of the business—sales, marketing, and the MSP revenue model. He learned that clients don't buy "managed services"; they buy uptime, security, and peace of mind. To deliver that while remaining profitable, an MSP must master its pricing and service delivery structure.
The Evolution of Managed Services Pricing
In the early days of IT support, the "break-fix" model was king. If something broke, you fixed it and sent a bill. While simple, it was a terrible business model for both parties. The client suffered downtime, and the MSP only made money when the client was in pain. It created a conflict of interest that hindered growth.
The modern MSP revenue model flips this dynamic. By charging a fixed monthly fee to keep things running, the MSP’s goals align with the client’s. If everything works perfectly, the MSP is more profitable because labour costs are low, and the client is happy because they have no downtime.
Common Revenue Streams for MSPs
| Revenue Type | Description | Typical Margin |
|---|---|---|
| Managed Services (MRR) | Ongoing support, monitoring, and maintenance. | 50% – 70% |
| Security Services | SOC, MDR, EDR, and compliance management. | 40% – 60% |
| Professional Services | One-off projects like server migrations or office moves. | 30% – 50% |
| Product Resale | Selling hardware (laptops, firewalls) and software. | 10% – 20% |
| Cloud Subscriptions | Microsoft 365, Google Workspace, AWS/Azure. | 5% – 15% |
Core Models: Per-User vs. Per-Device
One of the most frequent debates in the industry is whether to price based on the number of users or the number of devices. While both have their place, the trend in the United States and global markets has shifted significantly toward the per-user model.
The Per-User Pricing Model
This is generally considered the most "modern" approach. You charge a flat fee for every employee the client has. This user typically gets support for their laptop, their mobile device, their cloud identity (M365/Google), and their home office setup.
Pros:
Easy for the client to understand and forecast. Covers the modern "work from anywhere" reality. Simplifies billing as the client’s HR headcount changes.
Cons:
Can be risky if a user has an unusually high number of devices. Requires clear "fair use" policies in the contract.
The Per-Device Pricing Model
This model charges for every endpoint managed—servers, workstations, and mobile devices. It was the standard when everyone worked in a physical office with a single desktop computer.
Pros:
Very precise; you know exactly what you are managing. Good for environments with shared workstations (like manufacturing or retail).
Cons:
Becomes complex as users add tablets, smartphones, and home PCs. Billing can become a mess of small additions and subtractions every month.