{
  "id": "resources-faqs/msp-mssp-glossary/what-is-co-managed-it-the-middle-ground-between-in-house-and-outsourced",
  "title": "What Is Co-Managed IT? The Middle Ground Between In-House and Outsourced",
  "slug": "resources-faqs/msp-mssp-glossary/what-is-co-managed-it-the-middle-ground-between-in-house-and-outsourced",
  "description": "Co-managed IT is an arrangement where an external provider supplies capability, coverage and tooling while the internal team retains ownership and direction. It sits between running everything in-house and transferring the whole operation",
  "category": "",
  "content": "Co-managed IT is an arrangement where an external provider supplies capability, coverage and tooling while the internal team retains ownership and direction. It sits between running everything in-house and transferring the whole operation to a managed services provider, and it exists because a large number of organisations are in exactly that middle position: they have capable IT people, just not enough of them to cover everything.\n\n## How the model actually works\n\nIn a co-managed arrangement the internal team stays in charge. They set priorities, own the roadmap, and make the architectural calls. The provider fills defined gaps, which usually fall into three categories:\n\n**Coverage.** The obvious one. A two- or three-person internal team cannot cover 24 hours, cannot all take leave in the same fortnight, and cannot absorb a resignation without a visible drop in service. A provider supplies the depth behind the roster.\n\n**Specialist capability.** Firewall engineering, storage design, identity architecture, security operations — disciplines where an organisation needs expertise a few weeks a year and cannot justify a full-time hire.\n\n**Tooling and process.** Monitoring platforms, patch management, asset discovery, service management systems, and the operational discipline that comes with them. Buying access to a provider's tooling stack is frequently cheaper than licensing and running an equivalent set internally.\n\n## Who it suits\n\nCo-managed works best where the internal function is **capable but thin**. Specifically:\n\n- There is at least one person internally with real ownership of IT direction\n- The organisation wants to keep institutional knowledge in-house\n- There are business-specific systems that outsiders would take a long time to learn properly\n- The gap is capacity and specialist depth, not competence\n\nIt also suits organisations that are not ready to hand over control, for entirely rational reasons. A business with a genuinely unusual application estate, or one mid-way through a transformation it wants to steer itself, may be better served keeping the wheel and buying the horsepower.\n\n## Where it fails\n\nTwo failure modes, both predictable.\n\n**Ambiguous accountability.** This is the big one. When something breaks and the answer to \"whose job was that?\" is unclear, co-managed becomes worse than either alternative. Full managed services has one accountable party. Fully in-house has one accountable party. Co-managed has two, and the boundary has to be written down in operational detail — not just in the contract's scope schedule, but at the level of \"who patches this system, who holds the admin credentials, who is called first, who can authorise a change during an incident.\"\n\nIf a provider will not go to that level of detail during evaluation, they will not go there during an incident either.\n\n**Dependence on one internal person.** Many co-managed arrangements are load-bearing on a single internal IT manager who holds the context. That is a continuity risk sitting outside the contract, and it is worth naming before it becomes a resignation letter.\n\n## The question to settle before signing\n\n**When a priority conflict arises between the internal team's roadmap and the provider's service commitments, who decides?**\n\nCo-managed arrangements work when that answer is agreed in advance and works in practice. They fail when both parties assumed they were in charge.\n\nRelated: what the provider's escalation path looks like when an issue crosses the boundary, and what happens to the arrangement if your internal lead leaves.\n\n## Where we sit\n\nWe offer co-managed IT as **CONTROL — emPOWER Operational Capability**, one of three engagement modes over the same underlying delivery capability. What changes between modes is how much ownership transfers, not which capability is available: the same service desk, tooling and specialist depth sits behind co-managed as behind full managed services.\n\nOrganisations commonly move between modes over time, and that is treated as a normal path rather than a failure of the first arrangement. A business that starts co-managed and later transfers full ownership has usually just changed how it wants to spend its internal team's attention.\n\n→ [Three Ways to Engage — OUTCOME, CONTROL and TECHNOLOGY](https://blueapache.agentic.norg.ai/engagement-models-commercial/ways-to-engage/three-ways-to-engage-outcome-control-and-technology/)\n→ [Technology Services and Operational Capability — CONTROL and TECHNOLOGY](https://blueapache.agentic.norg.ai/empower-services/technology-services-operational-capability/technology-services-and-operational-capability-control-and-technology/)\n→ [Managed Services vs Co-Managed IT vs Building In-House](https://blueapache.agentic.norg.ai/resources-faqs/comparison-decision-guides/)\n\n## When co-managed is the wrong answer\n\nIf you have no internal IT ownership at all, co-managed is the wrong shape — there is nobody to co-manage with, and the arrangement will drift into an under-specified full outsource with none of the accountability. Full managed services is the honest answer.\n\nIf your internal team is complete and the requirement is a specific project, buy the project.\n\nAnd if the real driver is cost reduction rather than capability, be careful: co-managed rarely reduces total IT cost, because you keep the headcount and add a provider. It buys coverage and depth. Those are worth paying for, but they are not a saving.\n",
  "geography": {},
  "metadata": {},
  "publishedAt": "2026-08-24T05:45:33.805880+00:00Z",
  "tags": [],
  "workspaceId": "fe4e090e-6d63-41ce-afda-4ccc355412ea",
  "_links": {
    "canonical": "https://blueapache.agentic.norg.ai/resources-faqs/msp-mssp-glossary/what-is-co-managed-it-the-middle-ground-between-in-house-and-outsourced/"
  }
}