There are two kinds of revenue inside your MSP right now, and the market values them completely differently.
One is project work: scoped, delivered, invoiced, gone. The other is recurring managed services: scoped once, delivered continuously, billed every month. They feel similar on the way in the door. They are not similar on the way out — not in margin, not in stickiness, and not in what a buyer will pay for them.
This post is about the gap between those two. The numbers are sharper than most owners want to admit, and the AI cycle is widening them by the quarter.
The margin gap is no longer a rounding error
Start with the uncomfortable baseline. MSP project margins fell to roughly 13% in Q4 2024, down from 23% a year earlier (ConnectWise Service Leadership Index). That is not a soft patch. That is a margin getting cut nearly in half in twelve months.
Recurring managed-services margins, by contrast, run around 46% (Service Leadership Index) — a 25 to 35 point gap over project work.
Sit with that spread. Two engineers, similar skills, similar effort. One is booked against a project at 13 points. The other is booked against a recurring service at 46. Same cost base, radically different economics. You are not running one business with a mix of work — you are running two businesses stapled together, and only one of them is healthy.
The same hour of skilled labor is worth roughly three times as much when it sits inside a recurring service instead of a one-off project.
The macro picture says this is not your problem to wait out. 18% of MSPs ran at a loss in Q4 2024, up from 14% the prior quarter. Worldwide managed-services revenue growth slowed to about 1%. The commodity tier is getting more crowded and less profitable at the same time. AI is accelerating it — the routine build-and-deliver work that filled project pipelines is exactly the work getting automated and compressed first.
Two futures for the book you already have
Forget greenfield growth for a second. Take the revenue you already own and run it forward three years. Two paths.
Future A — the commodity path. You keep selling project work. Margins hold at best around 13% and more likely drift lower as AI compresses the value of execution. Every engagement ends, so every engagement has to be re-won. And your customers leak: annual MSP churn runs 5 to 12%. A book that has to be constantly re-sold, at thinning margins, against more competitors, is a book that quietly shrinks while you sprint to stand still.
Future B — the practice path. You take those same client relationships and the same problems you were solving as projects, and you convert them into recurring managed services at ~46% margin. The work doesn’t end at go-live — it compounds. The client stops being a series of transactions and becomes an annuity.
The difference between A and B is not incremental. It is the difference between a business that decays and a business that compounds.
Stickiness is the multiplier you’re ignoring
Margin is only half the story. The other half is retention, and recurring services change it structurally.
A project client has no reason to stay. The job is done; the relationship resets to zero with the next RFP. A managed-services client is embedded — the service runs their workflows, sits inside their operations, and carries switching costs that go up every month it runs. Churn drops because leaving is now genuinely painful, not just inconvenient.
That matters because churn compounds against you. At 12% annual churn, you lose roughly a third of a cohort over three years. Drag that down toward the low single digits and the same sales effort builds a book that grows instead of one that refills a leaking bucket. Higher margin on revenue that also stays longer — the two effects multiply, they don’t add.
The punchline: it re-rates the whole company
Here’s the part owners and CFOs underweight. Converting project revenue to recurring revenue doesn’t just lift this year’s P&L. It changes what the entire business is worth.
Recurring revenue is typically valued at roughly 1.5 to 2 times the multiple of one-off project revenue. Buyers pay up for predictability, and they discount lumpy, re-won-every-year project income hard. In private MSP M&A, the median deal runs around 8.9x EBITDA, rising past 11x for the largest firms (Aventis Advisors). The difference between those two numbers is, in large part, revenue quality.
A useful conservative frame: a book that crosses 60%+ recurring revenue commands roughly one to two additional EBITDA turns. On a business doing real EBITDA, one or two turns is not a rounding error — it is often the single largest value-creation lever available to the owner, and it comes from re-mixing revenue you already have rather than chasing new logos.
This is the move that does double duty: it raises the profit you earn each year and the multiple applied to it. Margin times multiple is how enterprise value compounds.
For a PE-backed MSP, that re-rating is the entire thesis. For a founder eyeing an exit, it is the difference between selling a services shop and selling a platform business.
Why this didn’t work before — and what changed
The obvious objection: “We tried productizing services. The build cost ate the margin.” Fair. The reason converting project work to recurring services was historically hard is that every conversion meant custom software — long builds, heavy maintenance, and a delivery cost that erased the margin advantage you were chasing.
That math changes when you stop building from scratch.
This is where the execution layer matters. AI advises. Humans decide. Workflows execute. You can use AI to design and accelerate the solution, but you need a place for it to actually run — reliably, governed, repeatable across clients. That place is Kinetic.
Kinetic is the orchestration and experience layer that turns a solution into a repeatable, multi-tenant managed service:
- Configuration-driven delivery — stand up solutions in days, not weeks. Industry studies put config-driven delivery at roughly 2 to 3x faster than traditional development, which is what makes per-client conversion economically sane.
- Multi-tenant by design — build a solution once, deliver it to many clients, capture recurring revenue on each. The build cost amortizes instead of repeating.
- 100+ connectors — orchestrate across the tools your clients already run. No rip-and-replace, which is what kills adoption and lengthens sales cycles.
- Federal-grade governance — IL5-certified controls, so the same service sells into regulated and enterprise buyers without a second build.
This is the model behind MSPs like Dataprise and Advanced: build with AI, execute with Kinetic, and turn delivery from a cost center into a recurring-revenue engine. You don’t rip out what you have — you put an execution layer on top of it.
Run your own numbers
The thesis is general; your book is specific. So model it.
Our MSP Practice Transformation calculator walks you through the two futures with your inputs. The default profile — a $50M MSP with 200 clients — is illustrative and fully adjustable, and it lands on numbers worth staring at:
- ~$22M three-year profit gap — the cost of standing still in Future A.
- +$4.5M new annual recurring revenue from converting project work.
- +$14M enterprise value from the margin lift and the multiple re-rating combined.
- 60% less build effort via configuration-driven, multi-tenant delivery.
Change the client count, the conversion rate, the margins — make them yours. The shape of the answer won’t change much, and that’s the point.
The market has already decided that project revenue is worth less every quarter and recurring revenue is worth a premium. The only open question is which side of that line your business is on in three years.
For the strategic case behind this math, read The MSP Race to the Bottom Is Over. Then run your numbers in the calculator and see how the conversion works on our MSP solutions page. Build with AI. Execute with Kinetic.
Share this article