The Break-Fix Shift Is Over. The Catalog Problem Isn't
Randy Hall, CEO

Most MSPs already quit pricing like a repair shop. The harder part of the shift from break-fix to fully-managed is not the contract, it's whether your service catalog can actually carry a client's entire IT footprint, and for a lot of owners it still can't.
The billing switch already happened
By any measure, the money has already moved to recurring revenue. In ScalePad's 2026 MSP Trends Report, 78% of MSPs say their recurring revenue grew over the past year, and 34% of respondents now generate between 41% and 60% of total revenue from recurring contracts. Fifty-eight percent of MSPs told ScalePad they actively track monthly recurring revenue as a core financial metric, more than any other number on the list.
Growth expectations line up with that shift. The same report found 55% of MSPs are still projecting double-digit growth in 2026. Growth is increasingly coming from existing accounts rather than new logos, too: 60% of MSPs point to acquiring new clients as a top growth driver, while the share pointing to growing existing accounts rose to 49%, up from 35% in 2025. That is not a small shift. The argument over hourly billing versus flat-rate contracts, the one that dominated MSP conferences for a decade, is mostly settled. What isn't settled is what "fully managed" is supposed to include once the invoice stops itemizing hours.
What's actually stopping MSPs from going fully managed?
A flat monthly rate does not automatically mean a complete catalog. Plenty of MSPs bill like a managed provider but still deliver something closer to break-fix wrapped in a subscription, covering helpdesk and patching while treating security, compliance, cloud governance, and collaboration-platform management as add-ons they quote separately or skip entirely. The billing model changed before the service list did, and that gap is where clients start shopping competitors for the pieces you don't offer.
Vendor-side research backs up the mismatch. ScalePad reports that 60% of MSPs now operate a formal Customer Success program, which sounds like the industry has matured past break-fix thinking entirely. The same page notes that most of those programs still lack the maturity to function as a real differentiator, which tracks with what a lot of owners already suspect: the structure for a managed relationship exists, but the service depth behind it often doesn't yet.
Cybersecurity got the budget. Compliance didn't.
Cybersecurity is the clearest example of a category MSPs have folded into the core offering rather than sold as an extra. ScalePad's report found cybersecurity took the top spot in 2026 as the most common service MSPs offer, and it is also the top service MSPs plan to expand this year. That is years of channel pressure finally showing up in the data: clients expect security to be baked in, not billed as a side project.
Compliance work hasn't caught up at the same pace. ScalePad found compliance still makes up less than 25% of most MSPs' revenue today. The same report calls it a "potential goldmine" that most MSPs haven't figured out how to productize. The pattern repeats anywhere a service requires specialized knowledge an MSP doesn't already have on staff. Cloud governance, Microsoft 365 adoption, and structured compliance work all sit in roughly the same spot: clients want it included, and most providers still quote it separately because they don't have anyone in-house who can deliver it at scale.
Can you hire your way into a broader catalog?
For most MSPs, no, not at the pace the market is moving. O*NET OnLine, the U.S. Department of Labor's occupational database, projects slower than average growth of 1 to 2 percent for computer network support specialists through 2035, with about 9,000 total job openings projected across the entire decade, even as demand for the services those technicians support keeps growing.
That's not a labor pool an MSP owner can count on to staff a new compliance practice, a cloud migration team, and a Microsoft 365 governance line in the same budget year. Specialist hires for each new service line are expensive, slow to recruit, and hard to keep billable at full margin until the client base catches up. Most owners who try end up with one overextended generalist covering three disciplines badly instead of one discipline well. It's part of why ScalePad found 43% of MSPs now say AI already has or will fully replace roles in their business. Automation and productized tools are filling headcount gaps the labor market simply isn't going to fill.
Consider a hypothetical 18-technician MSP that wants to add a Microsoft 365 intranet and SharePoint governance line to its catalog. Hiring and ramping a dedicated specialist realistically costs a full year of salary and onboarding before the practice turns a profit, and that's before the MSP has proven client demand exists at all. Licensing a white-labeled tool that lets existing technicians deliver the same engagement removes the hiring step entirely and lets the MSP test the service against real client demand inside a single quarter instead of a fiscal year.
Where white-labeling actually closes the gap
This is the part of the shift that strategy conversations tend to skip. Billing models can change overnight with new contract language. Service catalogs can't, because each new line usually requires either a specialist hire you can't make fast enough or a new certification path for existing staff. Forge University exists for the second option, building the bench strength a growing catalog needs without waiting on a hiring market the labor-market numbers say isn't going to loosen up.
Productized, white-labeled tools solve the same problem from the delivery side. An MSP doesn't need a dedicated SEO analyst on staff to sell a recurring website-health service to clients, and it doesn't need an intranet architect to run Microsoft 365 adoption projects for every account. It needs a tool built for a technician who already knows the client relationship and just needs the specialized workflow handed to them. That's the difference between a catalog that grew because the owner decided to grow it, and one that stalled because growth depended on a hire that never came through.
How wide should your catalog be before you call it fully managed?
There's no fixed number of service lines that makes a provider "fully managed" instead of break-fix with a subscription attached to it. The practical test is simpler: can a client call you for security, compliance, cloud, and collaboration-platform needs and get a real answer, or do they still need a second vendor for anything outside helpdesk and patching? Owners who can answer yes to the first question are the ones capturing the recurring-revenue growth ScalePad's data shows across the industry this year.
Owners still answering yes to the second question are the ones break-fix competitors and specialist shops are quietly picking off, one service line at a time. Every gap in the catalog is an opening for someone else to get introduced to your client, and once a second vendor is in the account, the "fully managed" relationship you're billing for stops being true.
Growing the catalog doesn't have to mean growing headcount at the same rate the market is shrinking it. The MSPs pulling ahead right now are the ones treating white-labeled, productized tools as the fastest path to a genuinely complete service list, not a replacement for recurring revenue but the thing that finally makes the recurring-revenue number mean what it's supposed to mean. Our stack builder walks through which service lines are missing from your current catalog and what adding each one would actually cost against hiring for the same role. The full product catalog covers the tools built to fill those gaps without a new hire.
If your billing already looks like a fully-managed provider but your service list still has holes that send clients looking for a second vendor, that's the gap worth closing next. See the full stack to see which white-labeled lines close it fastest.
