Finding Out Which Managed IT Clients Actually Make You Money

Published by
Throne of Profit Editorial

Reviewed by
William Hassell
Founder & Chief Editor, Throne of Profit

Most MSP owners can name their biggest clients by revenue in about two seconds. Ask which ones are actually profitable and the room goes quiet. The monthly recurring number is easy to see — it's on the invoice. What's invisible is the other side of the ledger: the tickets, the after-hours calls, the one user who emails your team six times a day, the site visit nobody billed for. A flat-fee contract hides all of it until you go looking.

That's the trap of the managed-services model. You get paid the same amount whether a client barely touches you or drowns your team in support. Revenue tells you who's big; only revenue measured against the hours and tickets they consume tells you who's making you money — and the two lists are almost never the same.

   CLIENT PROFITABILITY = revenue  vs.  load consumed

   Client A  $$$$  ▇▇                 → high margin (quiet)
   Client B  $$$   ▇▇▇                → healthy
   Client C  $$    ▇▇▇▇▇▇▇▇           → underwater (bleeding)
             ↑ contract   ↑ tickets · hours · after-hours

Owner symptoms

  • A few "important" clients seem to generate a wildly disproportionate share of your tickets and escalations.

  • Your team is always busy and revenue looks fine, but margin is thin and you can't say exactly where it goes.

  • You dread certain client names showing up in the queue, but they've never shown up as a problem on any report.

Why this happens

The managed-services model is designed to smooth revenue into a predictable monthly number — which is its great strength and its blind spot. Because the fee is flat, the cost of serving each client floats free of what they pay. Nothing in your invoicing forces the two numbers together. A client priced three years ago on a headcount that's since doubled, an account with one high-maintenance user, a contract that quietly absorbed a second location — each one drifts underwater without a single alarm going off. The load lives in your ticketing system and your techs' hours; the revenue lives on the invoice; and unless someone deliberately puts them side by side, they never meet.

Common mistakes

  • Ranking clients by revenue alone, so the biggest invoice is assumed to be the best account.

  • Never tying tickets and labor hours back to the client who generated them.

  • Ignoring after-hours and escalation load, which is where unprofitable clients do their real damage.

  • Treating the flat fee as fixed forever, even as a client's size and support needs grow.

  • Averaging everything together, so a couple of bleeding accounts hide inside a healthy-looking blended margin.

Business consequences

An unprofitable client isn't just a break-even account — it's an active drain, because every hour your team spends bailing it out is an hour stolen from clients who actually pay for that attention and from the new business you can't take on. Left unmeasured, one or two heavy accounts can quietly consume the margin of five good ones, which is why an MSP can grow its revenue and shrink its take-home at the same time. The owner who measures profitability client by client sees exactly which accounts to reprice, restructure, or let go — and usually finds that fixing two or three of them does more for the bottom line than landing the next new logo.

How experienced operators think about it

They treat every client as its own small profit-and-loss statement, not a line on the revenue report. The mental model is simple: what does this account pay us per month, and what does it cost us to serve — in tickets, in labor hours, in after-hours interruption — to earn it? They know the flat fee is a bet on how much support a client will need, and that bets go stale, so they re-check the load against the revenue on a regular rhythm. Most importantly, they separate big from good. A large account that eats twice its fee in labor is a bigger problem than a small one, not a bigger asset — and they'd rather have ten quiet, right-priced clients than three loud ones that keep the team underwater.

Practical actions

  1. Pull tickets by client for the last few months, not just totals — count them per account and per user so the heavy consumers surface.

  2. Attach labor hours to each client, including after-hours and escalations, so you're measuring true support load and not just ticket count.

  3. Set the monthly revenue beside that load for every account, and calculate a rough margin — even a back-of-envelope hourly cost of your team makes the underwater accounts obvious.

  4. Flag the outliers first. You're not repricing everyone; you're finding the two or three accounts consuming far more than they pay.

  5. Decide account by account whether each outlier gets repriced, restructured, or let go — and re-run the comparison every quarter so a good client that drifts underwater gets caught early.

Questions every owner should ask

  • If I put each client's monthly fee next to the hours and tickets they consumed, which accounts would flip from "big" to "bleeding"?

  • Do I know which single users or sites drive a disproportionate share of my support load?

  • When was each contract last priced against the client's actual size and support needs — or has it just carried forward?

Frequently asked questions

How do I estimate a client's true cost if I don't track labor hours cleanly?
Start rough — precision comes later. Even a simple count of tickets per client over three months, multiplied by a rough average handle time and a loaded hourly cost for your techs, gets you a usable cost figure. Add a manual note for the big after-hours or project interruptions your ticket count misses. The goal isn't an accounting-grade number; it's separating the clearly-underwater accounts from the healthy ones, and a rough comparison does that just fine. You can tighten the tracking once you see how much it changes the picture.

A client is unprofitable but they're my biggest name — do I really drop them?
Identifying an unprofitable client isn't the same as deciding to fire them; it just tells you the account can't continue as-is. Usually the first move is repricing or restructuring the contract to match the real support load, not termination. A prestigious logo can be worth carrying at thin margin for references or referrals — but that's a decision you make on purpose, with the true cost in front of you, not one you back into blindly. Letting go is the last option, covered in the sibling article below.

Related articles

Every business has more decisions than time

Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.

Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.

Explore Throne of Profit

Previous
Previous

Balancing Ticket Load So One Tech Isn't Drowning While Another Coasts

Next
Next

Getting Your Software Subscription Costs Under Control