MSP Profitability: Where Your Margins Are Really Going

Revenue growth and profitability are not the same thing. That sounds obvious, but it is an easy distinction to lose sight of when a managed service provider (MSP) is growing. New clients come in, monthly recurring revenue climbs, technicians stay busy, and the ticket queue never seems to get any shorter. On paper, the business looks healthy.

Then you look at the margin.

For many MSPs, this is where the numbers become harder to explain. Revenue may be heading in the right direction while the cost of delivering that revenue is rising underneath it.

The problem is rarely one enormous expense. More often, MSP profitability takes a hit because of small leaks across service delivery, technician time, contracts, tooling and client environments.

The first step to fixing that is understanding where those leaks actually happen.

Why MSP revenue can grow while profit margins shrink,

Most MSPs have a good handle on what they charge a client.

The harder number to pin down is what it really costs to serve that client.

Take a typical managed services agreement. You might charge per user, but the services included in that agreement are not necessarily delivered per user.

Microsoft 365 licenses might be priced per user. Endpoint security is typically tied to devices. Network services may be delivered at a site level. Technician time cuts across all of them.

That creates an important gap between how a service is billed and how it is actually delivered.

Take, for instance, a client with 100 users. Over the course of the year, the headcount barely changes, but the business adds laptops, tablets, network equipment, and new locations. Your recurring invoice may not change much,  but the cost to serve the client can.

In such cases,  MSP margin erosion can be difficult to spot. Nothing looks obviously wrong from a revenue perspective, but the economics of delivery change.

Where MSP profitability tends to leak

1. Your pricing model doesn't reflect the real cost of delivery

Per-user, per-device, and flat-rate managed services make billing easier for clients. But they can also hide complexity.

An MSP might bill a customer per user while delivering services across users, assets, sites and networks. In theory, the fix sounds simple: bill for whatever's driving the cost. In practice, contracts are rarely that tidy. Most are a blend of flat fees and bundled services, decided at the point of sale, with no separate line item for something like endpoint volume in the first place.

Consider a simple example.

An MSP charges $150 per user for 100 users, generating $15,000 in monthly revenue. Initially, the cost of delivering the underlying services is $10,000. Gross margin is roughly 33%.

The customer adds more assets over the next few months. Endpoint costs climb accordingly, but the change happens gradually, service by service, with no line item to flag and no clear moment that says "renegotiate this contract." Service costs rise to $11,600, revenue stays at $15,000, and gross margin falls to around 22.6%.

By the time anyone adds it up, months of margin are already gone.

The client didn't become less valuable overnight. The cost of serving them changed. If you cannot see that change, you cannot do much about it.

2. Technician utilization doesn't always mean profitable utilization

Technician time is one of the most important resources an MSP has. Every hour spent troubleshooting, maintaining, documenting, patching, escalating, or communicating carries a cost.

But that time isn't always captured in a way that connects it back to the client, service, and contract generating the work.

That makes a crucial distinction difficult to see:

Is the team busy, or is the team doing profitable work?

A highly skilled technician repeatedly handling low-value issues for one client can quietly erode margin even when that client looks valuable from a revenue perspective.

3. Disconnected MSP tools create profitability blind spots

Many MSPs have built their technology stack over time, adding different tools for different needs. One product handles endpoints, another manages network devices, while the helpdesk, contracts, time tracking, billing, and accounting may all live across separate systems. Reporting often pulls data from several of them.

Individually, each tool may do its job well. The problem shows up when you try to answer a business question across all of them.

For example:

Which clients are consuming more technician time than their contract supports? Which services have become more expensive to deliver? Which contracts have high revenue but poor margins? Which clients have added assets without a corresponding change in commercial value?

Answering those questions often means pulling together data from multiple places and trying to reconstruct what happened.

And the further profitability reporting is removed from the actual delivery of work, the more assumptions find their way into the numbers.

4. Reactive service is expensive service

There is also a cost to the way work enters your business.

An MSP that spends most of their time reacting to recurring alerts, noisy environments, preventable incidents, and the same support issues over and over again is using technician capacity inefficiently.

That does not always show up as a line item on a P&L.

It shows up as more hours required to produce the same amount of recurring revenue.

This is one of the biggest differences between revenue growth and profitable growth.

If your MRR grows by 20%, but the effort required to deliver it grows by 30%, the business is scaling in the wrong direction.

Standardization, policies, automation, and proactive management matter because they reduce the amount of human effort required to maintain service quality.

That is not just an operational benefit, but a margin benefit.

MSP profitability starts with knowing your real COGS

When MSPs talk about profitability, the conversation often starts with reports and dashboards.

But the report is only as useful as the information feeding it.

To understand whether a client, contract, or service is profitable, you need to know the true cost of goods sold behind it.

That includes both the products and services delivered to the client and the technician labor required to support the client

Those costs then need to be connected to the revenue being generated by that client or contract. Only then can you get a reliable picture of margin.

This is also why profitability cannot live exclusively in an accounting system. The data required to understand profitability is created much earlier, inside service delivery itself.

It starts when an endpoint is onboarded, a service is assigned,  a ticket is created, a technician starts working, when a contract applies, or when the environment changes.

From fragmented service data to a profitability picture

This is the problem SuperOps is designed to solve.

SuperOps brings the operational side of an MSP - endpoint management, monitoring, MDM, network monitoring, policies, patching, and software management - together with the business side of service delivery, including PSA, helpdesk, client management, contracts, SLAs, billing, and invoicing - all powered by AI. 

The point isn't simply to have several MSP tools under one roof.

The value comes from connecting the data between them.

The clearer the connection between what you manage, what you deliver, how much work it requires, and what you earn from it, the clearer your profitability picture becomes.

You cannot manage margin well if the true cost of service delivery is hidden across multiple systems.

The question MSPs should ask isn't “How busy are we?”

A packed service desk can feel like a sign of success, but the more useful questions are:

• Are we spending technician time on the right work?

• Are our contracts keeping pace with what we actually deliver?

• Are certain clients consuming more resources than their revenue justifies?

• Are we automating enough of the repetitive work?

• Do we know our real cost of serving each client?

Those are profitability questions, and they cannot be answered from revenue alone.

MSPs do not necessarily become more profitable by doing more work. What’s important is understanding the work they already do and turning more of that work into predictable, measurable revenue.

Once you know where profitability is leaking, the next question is:

How do you connect the work you deliver to the revenue it generates?

That’s where we’ll go in the next article: how service delivery connects operations, technician effort, contracts, and revenue.