MSP Pricing Models

Selecting the right MSP pricing models is one of the most significant commercial decisions you will make for your business. It isn't just about how you bill; it’s about how you define your value, manage your margins, and align your interests with those of your clients. Get it right, and you build a scalable, profitable engine. Get it wrong, and you’ll find yourself trapped in a cycle of "heroics" where you work harder just to maintain a shrinking bottom line.

In the world of Managed Service Providers, pricing is often treated as a math problem—cost plus margin. But experienced operators know it’s actually a communication and strategy problem. It’s about ensuring that when you recommend a critical security upgrade or a project, the client doesn’t see an "upsell," but rather a natural progression of their business needs. At MSP Agenda, we believe that pricing should reflect the outcome you deliver, not just the hours you spend at a keyboard.

Luis Navarro, the founder of MSP Agenda, spent 15 years building Totality Services into a highly profitable MSP with over 150 clients. He learned that the most successful MSPs aren't just the most technical; they are the ones that can translate complex services into clear, commercially viable packages. This guide covers everything from per-user models to value-based pricing, providing the practical insights needed to scale your operations toward a successful exit.

What are MSP Pricing Models?

MSP pricing models are the structured frameworks that Managed Service Providers use to charge clients for IT support, cybersecurity, cloud management, and strategic consulting. These models define the scope of work, the billing frequency (typically monthly recurring revenue), and the unit of measure—such as per user, per device, or a flat monthly fee—to ensure the service is both profitable for the provider and valuable for the client.

• Per-User: A flat fee for every employee supported, regardless of how many devices they use.
• Per-Device: A fee for every workstation, server, or mobile device managed.
• Tiered Pricing: Offering "Bronze, Silver, Gold" packages with increasing levels of service and security.
• Flat Fee / All-You-Can-Eat: A single monthly price covering all defined support and maintenance.
• Value-Based: Pricing based on the specific business impact and risk mitigation provided to the client.

Core MSP Pricing Models Compared

There is no "perfect" model, but there are models that are perfect for specific stages of growth. Most MSPs start with something simple and evolve toward more sophisticated structures as they understand their costs better. The goal is to move away from trading time for money—which is the hallmark of a break-fix shop—and toward a recurring revenue model that rewards efficiency.

1. The Per-User Pricing Model

The per-user model has become the industry standard for a reason: it is incredibly easy for a business owner to understand. If they hire a new employee, their IT costs go up by exactly $X. If they let someone go, the cost goes down. This predictability is a massive selling point during the discovery phase of a sales cycle.

From an MSP's operational perspective, per-user pricing accounts for the fact that users generate tickets, not computers. A single user with a laptop, a tablet, and a smartphone still only has one set of credentials and one set of problems. By charging per user, you capture the true cost of support while remaining flexible as the client’s technology stack evolves.

Why it Scales

• Simplicity in Quoting: You don't need a three-hour audit to give a ballpark figure. "How many staff do you have?" is often enough to start the conversation.
• Future-Proofing: As clients move more services to the cloud (SaaS), the number of physical devices may drop, but the complexity of identity management increases. Per-user billing covers this transition perfectly.
• Higher Perceived Value: It positions the MSP as a partner supporting people, not a vendor fixing boxes.

When Luis Navarro co-founded Totality Services, the focus was on building a model that was transparent and commercially meaningful. In a per-user model, the MSP is incentivised to make the user as productive as possible. If the user is working efficiently without issues, the MSP's margin increases. This creates a "win-win" scenario that is easy to defend during a QBR (Quarterly Business Review).

2. The Per-Device Pricing Model

This was the original "gold standard" for the early managed services era. It is very granular. You charge $X for a server, $Y for a workstation, and $Z for a firewall. It feels very logical and is easy to track through your RMM (Remote Monitoring and Management) tool.

However, it has become less popular because it can lead to "nickel and diming" conversations. If a client buys a new printer or a tablet, should you charge them an extra $15 a month? If you do, it feels petty. If you don't, you're doing work for free. It also fails to capture the support time spent on cloud-based applications like Microsoft 365 or Salesforce, which aren't tied to a specific device.

When to use Per-Device:

• If you are supporting a highly specialised environment with few users but massive amounts of hardware (e.g., a lab or a manufacturing floor).
• If you are in a "co-managed" situation where you are only responsible for the infrastructure, not the end-user support.

3. Tiered Pricing (Good, Better, Best)

Tiered pricing is a classic retail strategy applied to B2B services. Usually, it looks like a "Bronze" package (remote support only), a "Silver" package (remote + on-site), and a "Gold" package (everything included plus advanced security and vCISO services).

The danger here is that clients will almost always look for the cheapest option. In the context of modern cybersecurity, offering a "Bronze" package that excludes basic security features like MFA enforcement or EDR (Endpoint Detection and Response) is a massive liability. If a client picks the cheap plan and gets breached, they won't remember they chose the low-tier package; they will only remember that their IT company let them get hacked.

Pro Tip: If you use a tiered model, ensure your "base" tier is still secure enough that you are willing to put your brand name on it. Never compromise on the essentials of risk management just to hit a lower price point.

4. Value-Based Pricing: The Holy Grail

Value-based pricing is the most advanced of the MSP pricing models. Here, you don't look at your costs or the number of users. Instead, you look at the business impact. For a law firm where an hour of downtime costs $10,000 in billable fees, the "value" of a high-availability solution is much higher than for a small retail shop.

To pull this off, you need to be an expert at the "Discovery" phase of sales. You aren't selling "managed services"; you are selling "business continuity," "compliance assurance," or "operational efficiency." This requires a deep understanding of the client's industry and their specific pain points.

Calculating the "Value"

• Cost of Downtime: Calculate exactly what happens to the client's revenue if their systems go dark.
• Risk Mitigation: What is the potential cost of a data breach or a regulatory fine?
• Strategic Growth: How does your technology roadmap help the client reach their three-year revenue goals?

This model offers the highest margins because it completely separates your compensation from your labour. It also makes your business much more attractive to buyers during an acquisition, as it demonstrates that you are a strategic partner rather than a commodity service provider.

The Commercial Reality of Managed Services

Pricing is not just a number on a contract; it is the foundation of your business’s valuation. When Luis Navarro helped grow Totality Services to an eight-figure exit, the profitability of the recurring revenue was a key driver. Potential buyers look for high gross margins and low churn. If your pricing is too low, you can't afford the quality of staff needed to keep clients happy, which leads to churn and a lower valuation.

A common mistake is forgetting to build in "cost of goods sold" (COGS). Your price must cover:

1. The Tech Stack: RMM, PSA, EDR, Backup, Email Security, etc.
2. Labour: The cost of the engineers and helpdesk staff supporting that client.
3. Overhead: Rent, utilities, and administrative staff.
4. Profit: The margin you need to reinvest in the business.

If you aren't tracking your Gross Margin per Client, you are flying blind. Some clients who seem profitable on the surface might actually be "margin killers" because they submit ten times the average number of tickets or refuse to upgrade legacy hardware that requires constant patching.

Standardisation and Pricing

One of the biggest hurdles to profitability is "client sprawl"—supporting ten different antivirus products and five different firewall brands across twenty clients. This destroys your margins because your team has to be experts in everything.

Standardisation is the secret weapon of high-growth MSPs. When you standardise your tech stack, your pricing becomes much easier to manage. You know exactly what your COGS are for every new user. This is why we built MSP Agenda. It’s designed to help MSPs standardise their Security Reviews and recommendations. When you have a standard way of assessing risk and presenting solutions, the sales process becomes predictable, and the pricing follows suit.

"A recommendation that a client doesn't understand is unlikely to become a project." This core belief at MSP Agenda applies to pricing too. If your pricing model is so complex that a Finance Director needs a spreadsheet to decode it, you’ve already lost the momentum.

The Role of Project Work in Pricing

While recurring revenue (MRR) is the lifeblood of an MSP, project work is the "accelerant." Many MSPs struggle with whether to include projects in their flat-fee pricing.

In our experience, the best approach is to include "business as usual" support in the monthly fee but treat major changes—like a cloud migration or a full hardware refresh—as separate projects. This prevents "scope creep" and ensures that the MSP is compensated for the intense labour spikes that come with major transitions.

What to include in MRR:

• Helpdesk support (Remote & On-site)
• Patch management and updates
• Ongoing security monitoring
• Strategic planning (QBRs)

What to charge as a Project:

• Office moves
• Server migrations
• Implementation of entirely new software suites
• Major cybersecurity remediation after a pre-onboarding audit

Common Pricing Mistakes to Avoid

After 15 years in the trenches, Luis Navarro has seen where MSPs typically stumble. Most of these mistakes stem from a fear of losing the deal, but a bad deal is often worse than no deal at all.

• Underpricing for "Foot in the Door": You think you'll raise prices later, but you never do. You end up stuck with a high-maintenance, low-profit client that drains your resources.
• Bundling Too Much: Including expensive software licenses (like Microsoft 365) in your base seat price without a "pass-through" mechanism. When Microsoft raises their prices, your margin disappears.
• Lack of an Annual Increase Clause: Inflation and rising labour costs are real. Your contracts should include an automatic annual price adjustment (e.g., 3-5% or CPI) to protect your margins.
• Ignoring the "Legacy Debt": Pricing a client with 10-year-old servers the same as a client with a modern cloud-native setup. The older environment will cost significantly more to support.

How to Transition Your Pricing Model

If you realise your current MSP pricing models are hurting your growth, don't panic. You don't have to change every client overnight. The transition should be handled strategically to avoid mass churn.

Step 1: The Audit

Calculate the effective hourly rate for every client. Total Revenue minus COGS, divided by the hours spent on them. You will likely find that 20% of your clients are subsidizing the other 80%. These "bottom 80%" are where you need to focus your price adjustments.

Step 2: The "New Client" Standard

Start immediately by quoting all new business at your new, higher rates. This proves to you and your team that the market will pay for your value. It builds confidence for the harder conversations with existing clients.

Step 3: The Renewal Conversation

As contracts come up for renewal, use the opportunity to introduce your new model. Frame it around the additional value they are getting—better security, faster response times, or more strategic guidance. If they are on an old per-device model, show them how moving to a per-user model simplifies their billing.

Step 4: Use Security as the Lever

It is very difficult to raise prices for "the same service." However, it is very easy to explain why a price increase is necessary to cover new, essential security layers like Managed SOC or Advanced Email Protection. Security is a non-negotiable business requirement, and most clients understand that the threat landscape has changed.

This is where a tool like MSP Agenda becomes invaluable. By running a standardised Security Review, you can show the client exactly where their risks are and why the new service level (at the new price) is necessary to protect their business. It turns a "price hike" into a "risk mitigation strategy."

Pricing for Profitability and Exit

If your ultimate goal is to sell your MSP, your pricing model needs to be "clean." Buyers love predictability. A per-user model with a clearly defined tech stack and a high gross margin is the most attractive asset in the M&A market.

When Luis Navarro sold Totality Services, it wasn't just because of the client list; it was because the business was built on a foundation of profitable, repeatable processes. The pricing models were designed to scale, and the commercial relationships were built on trust and transparency.

Remember, an MSP is more than just a collection of technical skills. It is a commercial entity. Your pricing model is the bridge between your technical expertise and your business success. It should be firm enough to protect your margins but flexible enough to grow with your clients.