Co-managed IT vs fully outsourced IT support: which fits your business?
What is the difference between co-managed and fully outsourced IT support?
Fully outsourced means a provider owns the whole IT function. Co-managed means an internal person or team keeps ownership and a provider supplies the layers they cannot cover alone - out-of-hours, specialist skills, tooling, and cover for leave. Co-managed is usually the better fit once you have internal IT you want to keep.
Fully outsourced
The provider runs everything: service desk, infrastructure, devices, identity, security, procurement, projects. You retain a commercial relationship and a budget, not a team.
Works when you have no internal IT, or your internal capability is one person doing it alongside another job, or you are growing quickly and need capability now rather than after two hiring rounds.
Fails when the business has specialist internal systems the provider cannot reasonably learn, or when nobody internally has enough technical understanding to hold the provider to account. That second failure is common and quiet. Without an internal counterpart, the provider effectively marks its own work.
Co-managed
Responsibilities are split explicitly. A typical arrangement:
Function | Internal | Provider |
|---|---|---|
First-line support | ● | ○ overflow and out-of-hours |
Line-of-business applications | ● | |
Infrastructure and cloud | ○ | ● |
Security monitoring | ● | |
Device management and builds | ○ | ● |
Projects | ○ | ● |
Strategy and roadmap | ● | ● joint |
Vendor management | ● | ○ |
Works when you have an internal person or small team who understand the business, and you need to remove single-point-of-failure risk, add specialist skills, and get 24-hour or holiday cover without hiring.
Fails when the split is not written down. Ambiguity produces the worst outcome in IT: everyone assumes someone else is watching.
The case for co-managed in a growing business
The typical mid-market situation is one capable internal person who has become a dependency. They cannot take annual leave without exposure, they have no peer to review decisions, and everything they know lives in their head.
Replacing them with a provider throws away business knowledge that took years to build. Co-managed keeps that knowledge, and adds the depth around it. It also tends to be the model internal IT people prefer, because it removes the parts of the role that were never the interesting parts.
What to define before you start
A written responsibility matrix. Every function, one owner. No shared ownership without a named lead.
A single ticketing system. Two queues means work falls between them.
Escalation rules. What goes to the provider immediately, and what the internal team handles first.
Shared visibility. Both sides see the same monitoring, the same asset list and the same reporting.
Access boundaries. Who holds which administrative credentials, and how privileged access is logged.
Cost
Co-managed is not automatically cheaper. You are still paying an internal salary. What changes is what you get for the combined spend: broader coverage, out-of-hours cover, and specialist capability you could not hire at that level.
Compare the total of salary plus provider fee against the cost of hiring a second and third internal person to reach the same coverage. For most businesses between 50 and 500 staff, co-managed reaches it sooner and cheaper. See what UK businesses pay per user.
How to decide
No internal IT, and none planned - fully outsourced.
One internal person you want to keep - co-managed.
A small team stretched across too much - co-managed, with the provider taking infrastructure and security.
An internal team with specialist systems and a clear roadmap - co-managed, provider as overflow and specialist.
If you are unsure, start co-managed. Moving from co-managed to fully outsourced later is straightforward. Rebuilding internal capability you have already released is not.
NVOY works in both models. See IT Support or signs you have outgrown your current arrangement.
BLOGS
