Running a Profitable Managed IT Services Business

Published by
Throne of Profit Editorial

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

An MSP looks like a clean business from the outside: recurring revenue, sticky clients, a monthly invoice that lands whether the phone rings or not. But recurring revenue only stays profitable if the cost of serving each client stays below what you charge them — and that gap is where most MSPs quietly lose money. Most owners came up as strong technicians and were never taught the handful of operating problems that decide whether the contract that looked good in year one still makes money in year three. The trouble is rarely the technology. It's the shape of the agreement, the tiers, the onboarding, and the ticket load around it — the parts that determine how much labor each flat monthly fee actually costs you.

None of it shows up as one bad month. It leaks. A pricing model that punishes you when a client hires, a bottom tier priced below what it costs to serve, a sloppy onboarding that generates tickets for a year, a queue where everything is "urgent." Each feels small, and together they turn a healthy-looking book of recurring revenue into a business that runs flat-out on thin margin. Here's the map of where MSP profit leaks:

   WHERE MSP PROFIT LEAKS

   PRICING MODEL    per-device vs per-user misaligned with cost
   SERVICE TIERS    bottom tier priced below cost to serve
   ONBOARDING       messy start = a year of avoidable tickets
   TICKET LOAD      no triage, so everything is "urgent"
   SCOPE CREEP      "quick favors" that never made the contract
   ────────────────────────────────────────────
   Flat fee, variable cost. The gap is the whole business.

Owner symptoms

  • Revenue is up and the team is busier, but margin per client keeps shrinking.

  • Your cheapest clients somehow generate the most tickets and take the most time.

  • New clients are chaos for months before they settle down.

  • The queue is always full and everything in it is marked high priority.

  • You keep saying yes to "quick" requests that were never in the agreement.

Why this happens

MSP problems come from the structure of a flat-fee, variable-cost business, not from anyone slacking:

  • The pricing model doesn't track the cost driver, so growth on the client's side quietly erodes your margin.

  • Tiers get set by what feels sellable, not by what each tier actually costs to deliver — especially the bottom one.

  • Onboarding is treated as setup, not a system, so undiscovered problems become tickets for a year.

  • Every request enters the same queue at the same priority, so real emergencies and password resets compete for the same attention.

  • Scope lives in people's heads, so favors accumulate until the contract and the actual work no longer match.

Common mistakes

  • Picking a pricing model by habit instead of matching it to what actually drives your labor cost.

  • Underpricing the bottom tier to win deals, then serving it at a loss forever.

  • Rushing onboarding to start billing sooner, and paying for it in tickets all year.

  • Treating every ticket as urgent, so nothing is actually prioritized and the team burns out.

  • Absorbing out-of-scope work quietly because saying no feels like bad service.

Business consequences

An MSP that never gets on top of these grows revenue while margin thins underneath it. More seats and more devices mean more labor, but a mismatched pricing model means the extra work isn't fully paid for. An underpriced bottom tier subsidizes your smallest clients with the profit from your best ones. Messy onboarding burns technician hours you'll never bill, and an untriaged queue means senior people spend their day on trivial tickets while the important work waits. Scope creep is the quietest of all — a favor here, a favor there, until you're delivering a premium service on an economy contract. The owner who tightens each of these — aligns the pricing model, prices the tiers honestly, onboards cleanly, triages the queue, and holds the scope line — usually finds the profit was there all along, buried in the cost of serving each account.

How experienced operators think about it

They stop thinking like the best engineer in the building and start thinking like the person who owns the margin on every contract. They pick a pricing model by asking what actually drives their cost to serve, and they price each tier so even the cheapest one covers the work it creates. They treat onboarding as the highest-leverage week in the whole relationship, because a clean start prevents a year of noise. They sort the queue before they work it, so effort goes where it matters instead of where it shouts loudest. And they treat the contract's scope as a line worth defending — not out of stinginess, but because an MSP that gives away unlimited work on a fixed fee eventually can't afford to serve anyone well.

Practical actions

  1. Match your pricing model to your cost driver. Decide whether devices or users better track the labor each client generates, and price on that — so growth on their side is growth on yours, not a margin leak.

  2. Price every tier to cover its cost to serve. Especially the bottom one. A tier you serve at a loss isn't a growth engine; it's a subsidy your best clients pay for.

  3. Make onboarding a repeatable system. Discover, document, and stabilize each new client's environment up front so it doesn't generate avoidable tickets for a year.

  4. Triage the ticket queue. Sort by real impact and urgency before you work it, so senior time goes to what matters and "everything is urgent" stops being true.

  5. Define and defend scope. Write down what's in the agreement, and have a calm, standard way to handle requests that fall outside it.

Questions every owner should ask

  • Does my pricing model get more profitable or less as a client grows?

  • What does my cheapest tier actually cost to serve — and is it above what I charge?

  • How many tickets in a new client's first year trace back to a rushed onboarding?

  • How much senior time goes to low-impact tickets because nothing is triaged?

  • How much out-of-scope work am I giving away each month without noticing?

Frequently asked questions

What's the single biggest profit leak for most MSPs?
It varies by shop, but a mismatched pricing model and an underpriced bottom tier are the two that most often hide in plain sight. The pricing model leaks because the cost to serve a client grows faster than the fee; the bottom tier leaks because it was priced to win the deal, not to cover the work. Both are very fixable once you look at your actual cost to serve each account.

Per-device or per-user pricing — which one is right?
Neither is universally right; the correct answer is whichever better tracks what drives your labor for a given client base. A client where every person has one laptop looks very different from one where each user has a phone, a laptop, and two monitors. The point is to price on the thing that actually moves your cost, so that when the client grows, your revenue grows with the work — not behind it.

How do I stop scope creep without looking like I nickel-and-dime clients?
Define scope clearly up front and handle exceptions with a calm, consistent process rather than a case-by-case flinch. Most clients don't mind boundaries; they mind inconsistency and surprises. When the agreement is explicit and out-of-scope requests have a standard path, saying "that's outside your plan, here's how we can handle it" reads as professional, not petty — and protects the margin that lets you serve everyone well.

Related articles

Try a free Weekly Focus assessment

If your MSP keeps adding clients but margin keeps thinning, the leaks are usually in the shape of the agreements, not the technical work. Throne of Profit's free Weekly Focus assessment is a no-cost way to see where your business stands and what to fix first.

Previous
Previous

Turning More IT Proposals Into Signed Agreements