We don’t know your business. We’ve been in dozens of conversations with MSP operators in the last six months, and the one thing we’ve learned is that no two MSPs are actually the same. Different stacks. Different verticals. Different staffing models. Different stories about how the business got here. The pattern we keep seeing isn’t in the technical operation. It’s in everything around it.
You can probably diagnose a network issue at 2am, walk a client through a compliance framework they’ve never heard of, and hold someone’s hand through a bad day on the internet without losing your composure. That’s the part of the work the world rewards you for. It’s the part you got into this for.
But if we asked you, today, how many hours your team spent writing proposals last month — or which of your clients is most likely to leave in the next ninety days — would the answer come quickly? For most of the operators we’ve talked to, it doesn’t. Not because the answer doesn’t matter. Because there’s no system that tells you.
That’s the gap we keep looking at. It’s the gap Catalyst OS exists to close.
This letter is what we’d like you to know about us before we ever ask for a meeting.
A technical operating system. No equivalent for the business.
Every MSP we’ve talked to runs on a technical operating system. RMM, PSA, ticketing, documentation. ConnectWise or Kaseya or NinjaOne sits at the center of it. It monitors environments, tracks tickets, keeps the team from stepping on each other. It runs while your attention goes to the work that actually needs you.
What strikes us is how much of the rest of the business doesn't.
What would it look like if your pipeline reported its own health, the way your endpoints do? If a client showing the early signs of disengagement triggered a workflow the way a failed backup does? If the proposal that took your senior tech four hours on a Saturday took ninety minutes on a Tuesday? If the QBR you’ve been postponing was already drafted by the time you sat down with your coffee, waiting for you to add color?
That’s not a wishlist. It’s how the technical layer of your business already works. It’s just that the business layer has been left to you, your team, and a lot of willpower.
The owners we talk to describe a recurring pattern: client churn that erodes a year of growth before the year ends, QBRs done at the last minute, proposals out the door late. Industry research has surfaced the same shape across multiple reports — we’ve deliberately stepped back from citing specific percentages we can’t fully verify. What we hear consistently is that clients leave because of communication, not service. The QBR is the system that’s supposed to communicate the service. It’s also the one most often skipped, postponed, or done at the last minute when everything else is on fire.
We don’t think this pattern describes every MSP. But it keeps showing up. The technical problem is largely solved. The business problem is not. That gap is where we operate.
An infrastructure problem the major vendors have no incentive to solve.
We believe the MSP business layer is not a technology problem in search of a solution. It’s a business operations problem the major vendors have no incentive to solve.
ConnectWise and Kaseya are building technical operating systems — and building them well. They may add business-layer features at the edges. They may even ship a QBR generator. But their economic model rewards stack consolidation — selling more PSA seats to existing customers — not building the business infrastructure that makes their PSA easier to walk away from. That’s the right fight for them. It’s not our fight.
Our fight is what sits above the technical stack and below the ceiling of what an MSP can reach without it: client retention, business development, revenue visibility, proposal execution, and market authority. These aren’t technology problems. They’re infrastructure problems. And infrastructure problems get solved by installing the right infrastructure — not by adding another SaaS subscription, and not by hiring a person to manage a spreadsheet.
We also think the MSP owner’s time is one of the most misallocated resources in services. You’re a senior operator spending your day on tasks that could be automated, a business developer who can’t develop business because delivery never stops, and a marketer who has no time to market. The business layer exists to give that time back — not by replacing your judgment, but by removing the work that doesn’t require it.
A small set of operating systems. One layer.
Catalyst OS is a small set of operating systems for the business layer of an MSP. Five at the moment, with a shared spine. We’re going to be honest about what they do for the operator and deliberately quiet about how we build them. The first part is what matters to you. The second is our work.
Here’s what your week starts to look like when these systems are running.
The QBR you've been dreading is already drafted on Tuesday morning. You add color. You don't write from a blank page. It goes out on time. The clients who needed it most read it.
The client who's about to leave shows up in your inbox before the email from their CFO does. You make a call. They're surprised you noticed. That call alone changes the relationship.
A discovery on Monday turns into a proposal on Monday evening — not Friday, not next week. Your senior tech goes back to delivery. Your close rate moves because speed is the most underrated variable in the MSP sales cycle.
You can see, without opening a spreadsheet, where every deal is, what's coming next, and what's gone cold long enough to need a conversation.
In the background, content in your voice goes out to the audience you actually want — before they have a problem they need to solve. So when they do, they think of you.
That’s what we’re building toward. We’re shipping it in a small handful of modules, with the early adopters who join us through the Early Adopter Program — operators willing to pressure-test every assumption while we build. The product is in active build. It’s not pretending to be finished. It’s not pretending the design is settled. We’d rather be honest about that than overstate what’s running on day one.
Five systems. One operating layer.So your time goes to the work that actually needs you.
A few things we want to be careful not to claim.
We’re not saying your MSP is broken. Most MSPs we talk to are technically excellent — better at delivery than the clients they serve could ever appreciate. The business layer problem isn’t a competence problem. It’s a time and infrastructure problem. You didn’t build these systems because you were too busy building the technical ones. That was the right call at the time.
We’re not saying AI solves this. AI is how we build these systems efficiently and keep them running. It’s the engine under the hood — not the product, not the pitch, not the thing your clients hear about. Your clients hear about QBRs that happen on time, proposals that arrive the same day, and a pipeline you can actually see. How we produce those outcomes is our problem to solve. It’s not yours to understand.
We’re not saying every MSP needs all five systems on day one. The right place to start is wherever the bleeding is. For some operators, that’s churn — the revenue leaving quietly. For others, it’s proposals — the revenue never arriving. Start there. Add the next system when the first one is running and you can see what it gave back to you.
We’re not saying this was easy to figure out. It took us longer to understand the MSP business model deeply enough to design infrastructure that actually fits it than it will take to ship the infrastructure itself. We didn’t build a generic AI platform and point it at the MSP space. We’re building this in partnership with operators, because generic platforms produce generic outcomes — and generic outcomes don’t save anyone’s business.
The honest version of what we have, today.
We don’t have a logo wall. We don’t have thirty case studies. We have a thesis grounded in the documented operational reality of the MSP industry, a team whose lived experience overlaps with the problem from three different angles, and a platform purpose-built for the business layer that the major MSP vendors have left unaddressed — in active build with our first early adopters.
Deliverables in writing. Signed before a dollar changes hands.What we build, what you see, when.
We’re not the right fit for every MSP. If the problems above don’t feel familiar — if your pipeline is visible, your QBRs run on time, your clients never leave without warning, and your proposals go out the same day they’re requested — you don’t need us. We’d rather you tell a peer who does.
If those problems do feel familiar, we’d like to have the conversation. Not because we’re going to tell you something you don’t already know — you know your business better than we do. Because we’re building the infrastructure that closes the gap, and we can walk you through it on a working demo and explain what it would look like inside a business shaped like yours. We’d rather show you than describe it.
A category that doesn't exist yet.
The MSP business layer isn’t a product category yet. There’s no logo wall of vendors who own it. No analyst report that defines it. No conference track dedicated to it.
That's the point.
The MSPs who install this infrastructure first — while it’s still a competitive advantage rather than a baseline expectation — will see the compounding effects first. Not because the technology disappears. Because the business outcomes compound. Clients retained this year become referral sources next year. Proposals closed faster this quarter build the pipeline that funds next quarter’s growth. Content published consistently this month becomes the authority that generates inbound two years from now.
The business layer can run the same way the technical layer does — quietly, in the background, freeing your attention for the work that actually needs you. The question is whether you’ve installed it.
If any of this sounds like your week — even some of it — we’d like to hear from you. Not for a pitch. For a conversation. We’re trying to build something useful for operators like you, and the only way we know how is to keep listening.
Yours,
The Catalyst Shift Co-Founders