There is a persistent assumption that bringing in an IT provider means replacing whoever currently looks after your systems. For plenty of businesses that is not remotely what they want. They have a capable IT person, or a small internal team, and what they actually need is more hands, deeper specialism, and cover when someone is on holiday.
That is co-managed IT: an external provider working alongside your own people rather than instead of them.
What it looks like in practice
The arrangement is defined by an agreed split of responsibilities. There is no single correct division — the point is that it is explicit rather than assumed.
Common patterns:
The provider takes the day-to-day. Password resets, new starters, printer problems, the constant interruptions. Your internal person gets their week back for projects that actually move the business forward.
The provider brings specialism on demand. Your IT person is excellent generally but nobody is an expert in security, networking, cloud migration and telephony simultaneously. The provider supplies depth for specific pieces of work.
The provider covers the gaps. Holidays, illness, out of hours, and the resignation that would otherwise leave you with nobody who knows how anything works.
The provider handles the systems, the internal team handles the business. Your own person knows your processes and your people, which is genuinely hard to outsource. The provider runs the infrastructure underneath.
When it makes sense
Your IT person is permanently firefighting. If they never reach the strategic work, you are paying for capability you are not getting.
You are exposed to one person. If one individual leaving would be a serious problem, that is a risk worth reducing.
You need specialism occasionally. Hiring a security specialist for a business of forty people rarely makes sense. Access to one does.
You are growing. The setup that worked at fifteen people starts creaking at fifty, usually before anyone has budgeted for it.
The obvious worry
Most internal IT people initially hear “we are bringing in a provider” as “we are replacing you”. That reaction is entirely reasonable and needs addressing directly rather than managed around.
In practice, the arrangement usually improves their job considerably. Handing over the interruption work is a relief, not a demotion. What they lose is the part of the role nobody enjoys.
Two things make the difference. Bring them into the decision rather than announcing it — they know better than anyone which parts are eating their week. And write the split down clearly, because ambiguity is what actually causes friction. When both sides assume the other is handling something, it does not get handled.
Making it work
Agree who owns what, in writing. Agree how work reaches the right party, so users are not guessing who to contact. Give the provider the access they need to be useful — half-access produces half-service. And review the split after a few months, because the right division at the start is rarely the right one a year in.
The bottom line
Co-managed IT suits businesses that have someone internal and need more capacity, more specialism or more resilience rather than a replacement. Define the split explicitly, involve your internal person in the decision, and revisit the arrangement as the business changes.
FAQ
Is co-managed more expensive than fully outsourcing? Not necessarily. You are buying a defined portion of the work rather than all of it, so the cost reflects the split you agree.
What if our IT person leaves anyway? This is one of the stronger arguments for the model. A provider already familiar with your systems means a resignation is an inconvenience rather than a crisis.
Who is accountable when something breaks? Whoever owns that area under the agreed split — which is exactly why writing it down at the outset matters more than any other part of the arrangement.
