Co-managed IT is an arrangement in which an internal IT team and an outside provider, usually a managed service provider (MSP), share the work of running a company’s technology. The internal team stays in place and keeps the decisions and the knowledge of the business; the provider adds coverage, tools or skills the team doesn’t have, under a written split of responsibilities. It sits between doing everything in-house and outsourcing IT entirely.
At a glance
- You keep your IT staff; the provider fills specific gaps such as after-hours support, monitoring, security or specialist projects.
- Responsibilities are divided by agreement, often by support tier, technology area or time of day.
- Clear handoffs, shared tools or integrations, and a written escalation path matter more here than in fully outsourced IT.
- Pricing is commonly per user or per device per month, with project work billed separately, depending on the provider.
- It works best when the internal team has an owner who manages the provider relationship.
What problem it solves
Mid-sized companies often have an IT team of a few people. They know the business well, but they can’t cover nights, weekends and vacations, keep up with each specialist area, and still deliver projects. Hiring more staff for coverage or rare skills is expensive and slow. Handing everything to an outside provider, on the other hand, can mean losing internal knowledge and control that the business values.
Co-managed IT addresses the gap without forcing that choice. The internal team offloads the work that is repetitive, round-the-clock or specialized, and keeps the work that depends on knowing the company. Done well, the IT manager spends less time on password resets and more on projects and planning, and users get help outside office hours.
How it works
Scoping the split. The arrangement starts with deciding who does what. Common divisions are:
- By tier: the provider handles first-line requests and escalates to internal staff for business-specific systems, a model described in tiered IT support.
- By hours: internal staff cover the business day; the provider covers nights, weekends and holidays.
- By domain: the provider runs monitoring, patching, backups or security; internal staff run applications and user support.
- By project: the provider supplies engineers for migrations, upgrades or rollouts.
Tools and access. Both sides need to see the same tickets and alerts. Some providers bring their own help desk, remote monitoring and management (RMM) and documentation tools; others work in the client’s systems. Shared access is agreed and logged.
Escalation and handoffs. A written escalation matrix states who is called for what, in what order and how fast. Without it, issues can sit between the two teams.
Governance. Regular reviews cover ticket volumes, response times against the service level agreement (SLA), open projects and changes to the split. Some providers add strategic advice, sometimes as a virtual CIO (vCIO) service.
When it matters for buyers
- When the team is small and stretched. One or two IT staff can’t provide around-the-clock coverage on their own.
- When you are scaling fast. Adding sites, users or acquisitions faster than you can hire is a common trigger.
- When you are downsizing. Keeping a smaller internal team and buying back coverage can protect service levels.
- When a specialist skill is needed occasionally. Network engineering, security or cloud work may not justify a full-time hire.
- When an IT leader leaves. A co-managed provider can keep operations steady during a search, though you’ll still need someone internal to own decisions.
Our help desk overview covers outsourced support options that commonly form part of a co-managed arrangement.
Questions to ask vendors
- Which tasks will you own, which will we own, and how is that written into the contract?
- Will you work in our ticketing and monitoring tools, or do you require your own?
- How do tickets and alerts move between your team and ours, and how fast?
- What are your response and resolution targets for each priority, and how are they reported?
- What access will your staff have, and how is it controlled and logged?
- How do you handle work that falls outside the agreed scope?
- If we end the contract, what documentation, data and tool configurations do we keep?
How it differs from fully managed IT
In a fully managed arrangement, an MSP runs most or all of your IT and is the main point of contact for users, often for companies with no IT staff of their own. In co-managed IT, the provider is a partner to an internal team: the company keeps ownership of decisions, priorities and business-specific knowledge, and the provider covers defined parts of the work. Both are forms of IT outsourcing (ITO); the difference is how much stays in-house and who users go to first. Many providers offer both, and some companies move between them as their team grows or shrinks.