How to make it actually work — most people skip this part.
A good Co-Managed IT arrangement is easy to set up in theory and easy to get wrong in practice. This final article covers the three habits that separate partnerships that drift from ones that actually deliver.
You've made it to the final article. Maybe you've started sorting your IT functions into buckets. Maybe you've had a conversation about where your team's time actually goes. Maybe you've just been thinking: "This makes sense. Why hasn't anyone told us about this before?" Now here's the part that separates the businesses who think about Co-Managed IT from the ones who actually benefit from it.
A good idea, poorly executed, produces worse results than a mediocre idea executed well.
The way you set it up at the start determines whether it actually works — because clear expectations save everyone from confusion later.
A word to IT managers first
The concern: "What does this mean for me? Am I being replaced?" It's worth addressing directly — if your IT team feels threatened by the MSP relationship, it will undermine everything. The honest answer: a well-structured co-managed IT arrangement makes your team's working life better, not worse. They stop being on the hook for things they were never equipped to handle alone. They gain access to tools and expertise they didn't have before. They have a partner to escalate to when something is beyond their bandwidth.
The most effective IT leaders aren't the ones who try to do everything themselves. They're the ones who build the right team around them — inside the organisation and out.
The one document that makes everything easier
The most common reason co-managed IT fails isn't technical — it's ambiguity. Someone assumes the MSP handles backups. The MSP assumes your team does. Nobody checks. Something fails. The fix: one simple document. For every major IT function, answer:
-Who is the primary owner? -Who needs to be kept in the loop? -What does 'done' look like?
Write it down, share it with everyone involved, and revisit it every six months. That's it — no complicated frameworks, just a shared understanding of who does what.
Click here to download the ownership document template.
How to talk to your MSP so they actually understand your business
They're only as useful as the context you give them. Tell them when your busiest periods are. Walk them through how the business actually operates. Introduce them to the people whose IT lives they're going to be supporting. Share the history — the decisions, the workarounds, the things that are fragile. The best partnerships feel like a quiet extension of your own team — people who understand the business well enough to flag a risk before it becomes a problem, not just fix things after they break.
Where do you go from here?
You don't need to overhaul everything overnight. Most businesses start with one or two areas — security monitoring, data backups or after-hours coverage — and expand as they build trust and see results. Here's a simple starting point:
(1) Talk to your IT team about where their time actually goes. The answer is usually illuminating.
(2) Sort your IT functions into the three buckets from Article 2. It doesn't need to be perfect — just roughly right.
(3) Identify one or two areas where a specialist in the background would make the biggest difference. Start small, build trust, expand.
Stop running an IT model designed for a simpler time, and start building one that fits where your business is actually going.
--- If your organisation is exploring how a co-managed IT model could work for your team, or has questions about structuring an MSP partnership, the SMSSB team is here to help. Contact us.