Growth Consulting for MSPs and IT Service Providers
Managed service providers are unusual: recurring revenue, contracted clients, predictable billing — and, and frequently no ability to say which clients are actually making money. That combination produces a specific failure mode. The business looks stable on the top line while margin erodes underneath it, and because the erosion is spread across dozens of contracts nobody can point to the month it started.
The unusual position MSPs are in
Most B2B businesses would trade a great deal for what an MSP already has: contracted recurring revenue, a predictable billing cycle, and a client relationship that renews by default rather than by pitch. That structure is genuinely valuable, and it is why the category attracts investment.
It also conceals problems better than almost any other model. When revenue arrives automatically, the signals that tell other businesses something is wrong — a bad quarter, a lost deal, a stalled pipeline — simply do not fire. An MSP can be steadily losing money on a third of its book and see none of it in the monthly numbers, because the monthly numbers are fine.
What is usually actually constraining growth
We diagnose against six lenses — market, revenue, operations, technology, intelligence, and leadership. In MSPs, two come up far more than the others, and neither is the one owners tend to name.
Intelligence: you cannot see profit per client
Ask an MSP owner which clients are most profitable. Many can produce revenue per client instantly and cost to serve not at all. Tickets are logged in the PSA, time is recorded inconsistently, after-hours work is often not recorded at all, and nothing joins that effort back to the contract that generated it.
The absence is the finding. Without it, every consequential decision in the business is being made blind: which clients to invest in, which to re-price, which to let go, where to add an engineer, and whether the next contract signed will help or hurt. The intelligence lens is the one that conceals the other five, and this is one of the clearest examples the lens produces.
Operations: cost to serve drifts and nothing catches it
An MSP contract is priced against an assumed level of effort. Then the client hires fifteen people, adopts three new applications, has a security incident, and develops a habit of calling the technician directly. None of that triggers a conversation, because each increment was small and the relationship is good.
This is scope creep, but the term undersells it — scope creep in a project ends when the project ends. In a recurring contract it compounds indefinitely and is inherited by whoever renews it. A contract priced correctly several years ago can be materially underwater today, and the business usually cannot identify which ones.
Why the usual growth advice makes this worse
The standard prescription for an MSP that wants to grow is more demand: marketing, outbound, a channel partnership, a vCIO offering to open larger conversations. Sometimes that is right. Applied to a business that cannot price accurately, it is actively harmful, because every new client is priced with the same model that produced the current problem.
That is the Law of Constraints doing its damage: improving anything except the binding constraint creates activity. Here the activity is real — new logos, growing revenue, a busier team — and the business gets less profitable while achieving it.
A read you can run this month
None of this needs a consultant. Pull twelve months from the PSA and answer five questions:
- What are total logged hours per client, and what is the spread between your highest and lowest client at similar contract value?
- What is revenue per hour delivered, by client? Rank it. Where does the bottom quartile sit against your blended cost per engineer hour?
- How much after-hours and emergency work is happening, for whom, and is any of it billed?
- Which contracts have not been re-priced since signing, and how long ago was that?
- What percentage of total ticket volume comes from your top three clients by ticket count — and are they your top three by revenue?
That last comparison is usually the one that lands. When the ticket ranking and the revenue ranking disagree sharply, you have found the shape of the problem and roughly what it is worth.
What we would recommend first
Not a re-price. Build the view before acting on it.
A margin-per-client view assembled from data the PSA already holds, reviewed monthly. Then one decision made with it — most usefully, which contracts enter a re-pricing conversation at their next renewal, in what order. Re-pricing before the data is trusted produces conversations you cannot defend and occasionally loses clients who were profitable all along.
Then, and only then, the structural fix: a pricing model with a defined effort assumption and a stated trigger for revisiting it. The trigger matters more than the model. Any sensible pricing drifts; what separates MSPs that hold margin is that something makes the drift visible before it compounds.
How to tell a diagnosis from a pitch
Four questions worth asking anyone selling growth help to an MSP:
- What would you look at before recommending anything? If the answer does not include cost to serve, they are going to sell you demand.
- What would you do if the constraint turned out to be something you don't sell? The only good answer is that they would tell you.
- What will a recommendation actually contain? Ask to see one. Observation, why it matters, evidence, action, expected impact, priority, and honest confidence should all be present. Ours is published in full.
- Who is accountable for the advice? A named person, not a framework.
Where Elevare fits
We are an Indianapolis-based growth partner for established B2B companies across Indiana and the Midwest, and MSPs sit squarely in that profile — recurring revenue, real operational complexity, and usually more data than visibility.
We do not resell tooling and we are not a PSA consultancy. We diagnose across all six lenses and recommend what the diagnosis calls for, which in this category is frequently a reporting view and a pricing decision rather than anything to buy. The starting point is a First Read: 30 minutes, free, no service menu.
Common questions
What does a growth consultant do for an MSP?
The useful version starts by establishing what the business cannot currently see — usually profitability per client and the real cost to serve each contract — before recommending anything. For most MSPs the constraint is not lead generation. It is that pricing, staffing, and renewal decisions are being made without the cost data that should drive them. A consultant who opens with marketing has skipped the diagnosis.
Why is my MSP growing revenue but not profit?
Almost always because ticket load per client has drifted upward since the contract was priced, and nothing triggers a re-price. Scope creeps one small favor at a time, each individually reasonable. Since most MSPs measure revenue per client but not hours per client, the divergence is invisible until it shows up in the aggregate — by which point several years of contracts are underwater.
Should an MSP hire a salesperson or fix operations first?
Ask what happens to margin if you add ten clients priced the way the last ten were priced. If the honest answer is that margin gets worse, hiring a salesperson accelerates the problem. Fix the pricing model and the cost-to-serve visibility first; selling more of an unprofitable service is the most expensive mistake available to an MSP.
How do MSPs usually price wrong?
All-inclusive pricing — per user, per device, or tiered — set once at onboarding and never revisited, against a cost base that varies enormously by client behavior. Two clients at the same seat count can differ several-fold in tickets, after-hours work, and hand-holding. Flat pricing across that variance means the low-touch clients subsidize the high-touch ones, and the high-touch ones are usually the ones asking for more.