Two ways to divide the work
Fully managed IT means a provider owns the technology function end to end. They run the help desk, the monitoring, the patching and the projects, and your organisation holds a relationship rather than a rota. Co-managed IT means you keep an internal team and bring a provider in to cover specific gaps, whether that is after hours support, a specialist skill or simply more hands during busy periods.
Neither is more advanced than the other. They answer different questions. Fully managed asks how to get reliable IT without building an internal team. Co-managed asks how to make an existing internal team more effective without hiring more of them.
Who does what
The split of responsibility is the whole point, so it helps to see it laid out.
- Fully managed: provider owns day to day operations, escalations, patching, backups and often strategy, while the client sets priorities and budget
- Co-managed: internal team keeps ownership and context, provider fills defined gaps such as overnight coverage, tooling, project surge or a niche skill
- Shared in both: someone must still own security decisions and vendor relationships, so name that person explicitly
The trade offs
Fully managed reduces the load on your organisation the most and removes the risk of a single internal person being a bottleneck, but you give up some direct control and day to day context passes to the provider. Co-managed keeps control and institutional knowledge in house and can be more cost effective when you already have capable staff, but it only works when the boundary between the two teams is written down clearly. The most common failure in co-managed arrangements is not cost or skill, it is two teams each assuming the other was handling something.
Which one fits
If you have no internal IT and want reliability without hiring, fully managed is usually the simpler path. If you have a small capable team that is stretched thin or missing a specific skill, co-managed lets you extend that team without carrying more headcount. Growing organisations often start fully managed and shift toward co-managed as they hire, which is a healthy progression rather than a reversal.
Whichever you choose, the deciding document is the responsibility matrix. Write down every recurring task and mark who owns it, then confirm the provider agrees in writing before onboarding rather than discovering the gaps during an incident.
Key takeaways
- Fully managed hands the whole IT function to a provider.
- Co-managed keeps an internal team in charge and adds outside capacity where it helps.
- The biggest co-managed risk is an unclear boundary, so write the responsibility split down.
- Many organisations move from fully managed to co-managed as they hire.
Common questions
Is co-managed IT cheaper than fully managed?
It can be when you already employ capable staff, because you are buying specific coverage rather than the whole function. If you have no internal team, fully managed is often more cost effective than building one from scratch.
Does co-managed IT mean the provider reports to my IT manager?
Usually the internal team keeps ownership and the provider fills defined gaps, but the exact reporting line should be written into the agreement so both sides know who decides what.
Can I switch from fully managed to co-managed later?
Yes, and many organisations do as they hire internal staff. Plan the handover of knowledge and access deliberately so context is not lost during the transition.