So who actually does what? Here's a simple way to figure it out.
The most common concern about Co-Managed IT isn't technical — it's clarity. Who owns what? This article gives you a practical framework to answer that, based on where your team's time actually goes.
"It sounds good lah, but I can already see it — things will fall through the cracks, nobody will know who's responsible for what, and we'll end up with people pointing fingers at each other."
That's a fair concern. And it's exactly what happens when people set up a co-managed IT arrangement without thinking it through properly. So let's think it through.
Start by asking a different question. Not what needs to get done — but who is the best person to do each thing? To answer that, you first need to know where your team's time is actually going.
A quick exercise that takes two weeks and is surprisingly revealing
Ask your IT team to track time in broad categories for two weeks. Most teams find:
-50–60% reactive work — fixing, troubleshooting, answering requests, cyber security monitoring
-20–30% keeping things running — software upgrades, renewals, backups
-10–20% strategic or proactive — planning, improving, preventing
Most of that reactive and routine work is exactly what an MSP is designed to handle — at scale, with the right tools, often at lower cost than doing it internally. That frees your team to spend more time on the 10–20% bucket — where the highest-value IT work lives in your business.
The goal isn't to hand your IT team's job to someone else. It's to take the parts grinding them down and give those parts to people who specialise in them — so your team can do the work they're actually there to do.
Three buckets to sort your IT into
Bucket 1 — Keep In-House -Managing your team -Supporting business apps -IT decisions & company direction/strategy
Bucket 2 — Partner Out -24/7 security monitoring -Cyber threat detection -Backup and disaster recovery -Cloud mgmt & after-hours
Bucket 3 — Share -New office IT setup -Cloud migrations -System upgrades -Backup and DR drills
When you sort your IT functions into these buckets, the conversation stops being "should we bring in an MSP" and becomes "here's specifically what we'd want them to handle." That specificity is what makes the arrangement actually work.
What about losing control? In a well-run co-managed IT arrangement, you have more visibility, not less. Your MSP runs dashboards you can see at any time. Every ticket, alert, and action is logged. Compare that to the alternative: one IT person who holds all knowledge in their head, and if they leave tomorrow, you're starting from scratch.
A good MSP partner should make you feel more in control, not less. If you ever feel like things are happening you don't understand, that's a sign the arrangement isn't set up correctly — not that Co-Managed IT is the wrong model.
A starting point that works for most SMEs
Your team handles: daily support, app management, onboarding, vendor conversations, IT planning.
MSP handles: 24/7 monitoring, patching, backups, cybersecurity, after-hours.
Shared: major projects, planning conversations, migrations.
This isn't permanent — it evolves as your business grows. The important thing is that it's intentional, written down, and reviewed regularly. Which brings us to the final article.
--- 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.