What Is Co-managed IT?

What Co-Managed IT Means for an MSP

Co-managed IT is an arrangement where an MSP works alongside a client's own IT staff rather than replacing them. The client keeps its people, the MSP takes on a defined share of the work, and a written agreement says who owns what. For the MSP, it opens a market that fully managed service cannot reach: organizations large enough to employ IT staff and too stretched to cover everything with them.

It is also a different business from fully managed support. You control less of the environment, you coordinate more, and your work is reviewed by people who understand it. That combination can be a strong, sticky relationship or a slow loss, and the difference is almost entirely in how the agreement and the price are built.

Why Clients Ask for It

Clients come to co-managed IT for two reasons that sound similar and lead to different agreements. Some have an IT team that is overloaded and needs capacity. Others have one trusted IT person they want to keep, but they know one person cannot cover holidays, nights, sickness or specialist areas such as security. The first is a capacity conversation, the second is a risk conversation, and pricing one as the other is a common mistake.

Demand is growing. In Kaseya's 2025 benchmark survey, 61% of executive respondents said their co-managed IT revenue was up year over year. For an MSP owner, that makes co-managed a service worth designing deliberately rather than a set of exceptions to your standard agreement.

• Capacity: the internal team has more work than hours, often around projects or growth.
• Coverage: after-hours support, holidays and sickness for a small internal team.
• Tooling: access to RMM, backup, documentation and security tools the client could not justify alone.
• Specialist skills: security operations, cloud architecture, compliance work such as HIPAA or CMMC.
• Strategy: a vCIO to support an IT manager who reports to a non-technical executive.

How the Work Is Usually Split

There is no standard division, but one pattern survives contact with reality more often than others. The MSP takes the work that benefits from tooling, scale and coverage. The internal team keeps the work that benefits from knowing the business.

Write the split down as a responsibility matrix and attach it to the agreement. The matrix is what you both point at when a ticket lands in the wrong place, and it is the document a new internal hire will read first.

Pricing Co-Managed So It Does Not Lose Money

The most common mistake is pricing co-managed as a discounted version of fully managed support. It looks logical, because the client's staff do part of the work, but the cost structure is different. You carry the same tooling per device, you spend more time coordinating, and you often inherit an environment you are not allowed to fully standardize.

Build the price from what you deliver rather than from your fully managed rate minus a percentage. How MSPs price their services covers the models, and the client margin calculator shows whether a specific agreement covers its costs once coordination time is counted. Track each co-managed client's gross margin separately for the first year, because losses here stay hidden until someone measures the meetings, handoffs and duplicate work.

Tooling-only arrangements, where the internal team uses your stack and you provide little labor, are a legitimate product. Price them as tooling plus administration, and be explicit that the internal team's use of the tools is their responsibility.

Revisit the price at the first renewal with real data. By then you know how many tickets came from the internal team's changes, how much of your time went into meetings, and which parts of the responsibility matrix you ended up doing anyway. Those facts make a price adjustment a conversation about scope rather than a request, and the price increase letter gives you a starting draft.

Contract Terms That Prevent Disputes

Co-managed disputes almost always trace back to a question the agreement never answered. These are the terms worth settling before the first ticket:

• Who has administrative access to which systems, and whether the internal team may change settings your tools manage.
• Who is accountable when an internal change causes an outage your team has to fix, and whether that work is billable.
• Change control: how either side announces changes, and how long the other side has to object.
• Incident command during a security event: who leads, who talks to insurers and who talks to the client's executives.
• What happens to your tools, access and documentation if the internal IT person leaves or the client ends the agreement.
• Service targets written as an SLA that covers only the work you own.

The access terms matter most. Shared administrative accounts between two teams are a common co-managed habit and a real risk, for the reasons set out in removing shared admin accounts. Named accounts on both sides make every change traceable.

Running It Day to Day

A co-managed relationship works when both teams can see the same work. Give the internal team access to your ticket portal and the tickets that affect them, agree on one documentation system, and decide whose PSA is the source of truth for shared tickets. If both teams keep their own queue with no link between them, work is duplicated or dropped.

Meet more often than you would with a fully managed client, especially in the first months. A short standing call with the IT lead, plus a regular QBR with the executive who signs the contract, keeps both relationships healthy. Onboarding still matters too: the client onboarding checklist adapts well if you mark each item with an owner from the responsibility matrix.

Warning Signs and What They Mean

Some co-managed agreements drift into trouble slowly. These signals are worth acting on early:

• Your team spends more time in coordination calls than on the work itself.
• The internal team routinely reverts changes your standards require.
• Tickets per endpoint rise with no change in the environment, often a sign that problems are being handed over rather than solved.
• The executive sponsor only hears about the relationship from the internal IT lead.
• The internal IT person is leaving, which usually means the client will ask you to take on everything at the co-managed price.

The last one is also an opportunity. When the internal role changes, reopen the agreement rather than absorbing the work. Many co-managed clients become fully managed clients this way, and the renewal conversation is easier with the renewal cost worksheet in hand.