MSP Flat Rate Pricing

Building a Profitable Flat Rate Stack

You cannot offer MSP flat rate pricing successfully if your service delivery is chaotic. If you allow every client to choose their own firewall, their own antivirus, and their own backup solution, your labour costs will fluctuate wildly. To protect your margins, you must mandate a standard technology stack.

Standardisation is the foundation of profitability. When your team knows exactly how every client's network is configured, they solve problems faster. Faster resolution means less labour cost per ticket, which makes the flat rate more profitable. If a prospect refuses to move to your standard stack, they are likely not a good fit for a flat rate agreement.

What Should Be Included?

• Remote Monitoring & Management (RMM): The "eyes" on the network that allow for proactive patching and alerts.
• Endpoint Detection & Response (EDR): The baseline security requirement for modern businesses.
• Help Desk Support: Unlimited remote support during business hours is the core of the value proposition.
• Strategic Consulting: Regular QBRs or Security Reviews to ensure the technology aligns with business goals.
• Cloud Backup: Protecting data at the source, usually billed as a pass-through or bundled into the user fee.

Luis Navarro’s experience building Totality Services showed that clients don't want to buy a list of tools; they want to buy a result. They want to know that their data is safe and their people are productive. By bundling these tools into a single flat rate, you take the complexity off their plate and position yourself as the expert who manages the risk.

The Commercial Reality: Managing Scope Creep

The biggest threat to MSP flat rate pricing is "scope creep"—the slow expansion of services beyond what was originally agreed upon. If you aren't careful, a flat rate agreement can turn into a charity project for the MSP. You must be incredibly clear about what is not included in the monthly fee.

Generally, flat rate pricing covers maintenance and support (keeping things running). It should not cover projects (changing things). If a client wants to migrate from on-premise servers to Azure, that is a project with a separate Statement of Work (SOW). If you include projects in your flat rate, you are essentially gambling that the client won't decide to overhaul their entire office next month.

Common "Out of Scope" Items

• Office moves or physical cabling.
• Major software migrations (e.g., moving from G-Suite to Office 365).
• New hardware procurement and setup.
• After-hours or weekend emergency support (unless explicitly tiered).
• Recovery from a breach where the client ignored previous security recommendations.

Using a tool like MSP Agenda helps manage these boundaries. By conducting regular Security Reviews, you can identify where the client is falling behind and present those needs as separate projects. This keeps your flat rate recurring revenue clean while creating additional high-margin project revenue.

Calculating Your Flat Rate: A Practical Formula

Don't just look at what your competitors are charging. You need to understand your own numbers. Pricing should be a reflection of your costs, your desired margin, and the value you provide. Most successful MSPs aim for a gross margin of 50% to 70% on their managed services.

To calculate your per-user rate, use this basic framework:

(Total Monthly Tool Cost Per User) + (Average Monthly Help Desk Labour Hours per User x Hourly Labour Rate) + (Administrative Overhead) = Total Cost of Service (CoS) (Total Cost of Service) / (1 - Desired Margin %) = Target Flat Rate Price

For example, if your tools cost $20, and the average user consumes 30 minutes of support a month (at a labour cost of $50/hr), your base cost is $45. To achieve a 65% margin, you would need to charge approximately $128 per user. If that seems high for your market, you must either lower your labour costs through better automation or increase your perceived value through better reporting and security outcomes.

The Sales Transition: Moving from Hours to Flat Rate

Selling MSP flat rate pricing requires a different conversation than selling break-fix. In break-fix, you are a "vendor" who gets called when things are broken. In flat rate, you are a "business partner" who ensures things never break in the first place. The sales hurdle is often the initial price jump.

Clients who are used to paying $500 one month and $0 the next might be scared of a consistent $2,000 monthly bill. Your job is to show them the hidden costs of downtime. A "cheap" break-fix model is actually very expensive when you account for lost employee productivity, missed sales opportunities, and the risk of a catastrophic data breach.

Focus on Risk, Not Features

Instead of talking about "patching," talk about "vulnerability management." Instead of "help desk," talk about "employee uptime." As Luis Navarro often says, the client doesn't need a 40-page technical report; they need to understand the risk and what you are doing to mitigate it. When they see the flat rate as "insurance" for their productivity, the price becomes secondary to the value.

Maximising Profitability in a Flat Rate Model

Once the contract is signed, the game changes. In MSP flat rate pricing, every minute of labour you don't spend on a client is profit in your pocket. This isn't about providing poor service; it’s about providing service so efficiently that the client rarely needs to call you.

• Automation is everything: Use your RMM to auto-remediate common issues (like disk space alerts or service restarts) before a human ever has to touch them.
• Standardise the stack: We cannot stress this enough. If every client uses the same firewall, your senior engineers spend less time "figuring things out" and more time on high-value projects.
• Document everything: A well-documented environment allows a Tier 1 tech to solve a problem that would otherwise require a Tier 3 engineer. This lowers your labour cost significantly.
• Conduct regular Security Reviews: Use these meetings to move clients toward your standards. A client who follows your security recommendations is less likely to have a complex, time-consuming emergency.

MSP Agenda was built to support this exact cycle. By standardising how you communicate risk and value, you build the trust necessary to keep clients on your standard stack, which in turn protects your flat rate margins.

Common Pitfalls of MSP Flat Rate Pricing

Even experienced MSP owners can get flat rate pricing wrong. Here are the most common mistakes to avoid as you scale your business.

1. Underestimating the "Noise"

Some clients are simply "noisier" than others. A law firm with 20 employees might generate three times as many support tickets as a construction company of the same size. If you don't audit your ticket data before quoting a flat rate, you might end up with a client that eats all your profit.

2. Failing to Increase Prices

Inflation, vendor price hikes, and the rising cost of technical talent mean your costs will go up every year. If your MSP flat rate pricing doesn't include an annual escalator (usually 3-5%), your margins will slowly erode over time. Your contract should allow for these adjustments without needing a full renegotiation.

3. Including Hardware in the Flat Rate (HaaS) Without Proper Financing

Some MSPs include new computers every three years in their flat rate. This is called "Hardware as a Service." While it's great for standardisation, it's terrible for cash flow if you are funding the hardware yourself. Only do this if you have a solid financing partner or a very healthy cash reserve.