Resource
What is co-managed IT
Co-managed IT is not a smaller version of fully outsourced support. It is a different division of responsibility, where an internal person keeps the business relationships and institutional knowledge while a provider supplies coverage, tooling and escalation that one person cannot provide alone.
Who owns what
The matrix is agreed before anything starts and reviewed quarterly, because the failure mode is not conflict, it is a task both sides assumed the other one owned.
| Responsibility | Owner |
|---|---|
| User support and requestsThey know the people and the business context | Internal |
| After hours coverageOne person cannot cover 168 hours a week | Provider |
| Monitoring and alertingTooling a single seat cannot justify | Provider |
| Security stack and responseSpecialist depth and continuous review | Provider |
| Vendor relationshipsInstitutional knowledge stays in the building | Internal |
| DocumentationSurvives staff changes | Provider |
When it is the right choice
Five situations where co-managed beats both alternatives.
- You have one internal IT person who cannot take leave without their laptop
- Projects keep slipping because day to day support consumes the week
- Nobody covers evenings, weekends or the fortnight they are away
- Security tooling is thin because licences do not make sense for one seat
- Exactly one person understands the firewall
The failure mode to design against
Co-managed arrangements rarely fail through disagreement. They fail through gaps: a patch cycle, a backup check or an alert that both parties believed the other one owned.
The fix is unglamorous. Every recurring task has a single named owner, anything genuinely shared has a named lead, and the matrix is reviewed quarterly rather than filed after signature.
The other failure is human. If the arrangement is really a redundancy decision nobody has said out loud, the internal person will sense it and hand nothing over. Be honest internally before the provider arrives.
Common questions
Answered before you ask.
Is co-managed cheaper than fully outsourced?
The monthly fee is lower because the scope is narrower, but you are still carrying a salary. Total cost is usually higher than pure outsourcing and lower than building a full internal team. The reason to choose it is rarely cost. It is that you want institutional knowledge to stay in the building while removing the single point of failure.
Will our IT person feel replaced?
That depends on how it is introduced. In a well run arrangement their job improves: recurring low value work moves out, tooling gets better, and they finally do the projects that have been waiting. Involve them in designing it from the start rather than presenting it as a decision already made.
Can we change to fully managed later?
In both directions, and it happens regularly. Because documentation and tooling are already in place, the transition either way is far less disruptive than the original onboarding was.
Related
Read next.
Co-managed IT
Tooling, escalation and coverage that support an internal IT lead.
IT consulting and vCIO
Budgets, roadmaps, procurement and quarterly reviews.
In-house, outsourced or co-managed
The fully loaded cost of one internal hire against a contract.
What is a vCIO
The strategic layer, and what it should produce.
IT support and help desk
Tiered support with published response targets, remote and onsite.
Start with the assessment, not the contract.
We document what you have, test whether your backups restore, and give you the findings in writing. Yours to keep either way.