Co-Managed IT Services: The Complete Guide for MSPs (2026)

Five years ago, "co-managed IT" meant "the client's internal IT person handles the easy stuff and calls us for everything else" — and most MSPs treated it as a stepping stone to a full managed services contract. You'd take the co-managed deal, prove your value over 12 months, and convert them to a full-stack agreement.

That playbook is obsolete. In 2026, co-managed IT is the destination — not the on-ramp. Companies with internal IT teams are keeping them and hiring MSPs to fill specific gaps: cybersecurity, 24/7 monitoring, compliance, backup management, or helpdesk overflow. They want the MSP's tool stack and expertise without surrendering control of their IT operations. The MSPs who treat co-managed as second-class revenue are losing deals to the ones who've built a real co-managed offering.

What Co-Managed IT Actually Means in 2026

Co-managed IT is a partnership where the client retains an internal IT team (or a single IT manager) and the MSP provides specific services that supplement — not replace — that internal capability. Unlike full managed services (where the MSP owns the entire IT function), co-managed agreements divide responsibility along clearly defined lines.

The most common co-managed models:

The key insight: successful co-managed agreements are scoped by function, not by percentage. "We'll handle 40% of your IT" is a recipe for confusion, finger-pointing, and unhappy clients. "We'll handle cybersecurity and backup management — your team keeps helpdesk and infrastructure" is clear, measurable, and defensible when something goes wrong.

How to Price Co-Managed IT Services

Pricing co-managed IT is trickier than pricing full-stack managed services because you're not spreading costs across every function. You're pricing individual service modules — and you need to make a profit on each one independently.

The Module Pricing Model

Instead of a single per-user rate, price each co-managed module separately:

The pricing principle: Each module must be profitable on its own. Don't price cybersecurity at cost hoping to make it up on helpdesk — the client may only buy cybersecurity. A good rule: target 40-50% gross margin on each individual module. If you can't hit that at a market-competitive rate, the module isn't viable as a standalone offering.

For a 100-user client buying cybersecurity + 24/7 monitoring + backup management at mid-range rates, that's roughly $85 + $35 + $20 = $140/user/month, or $14,000/month — solid revenue without touching helpdesk. Add helpdesk overflow and you're at $200/user/month or $20,000/month from a single co-managed client. Compare that to a full-stack agreement at $150/user/month where you own everything: the co-managed deal often generates higher margin on less scope because you're only delivering the services you're efficient at.

Scoping Co-Managed Agreements: The RACI Model

The number one reason co-managed relationships fail: unclear boundaries. When a server goes down at 2 AM, whose phone rings? If the answer isn't written down in a signed agreement, you have a problem.

Use a RACI matrix (Responsible, Accountable, Consulted, Informed) for every function you're co-managing:

This matrix is part of the contract — not an appendix, not a verbal understanding. Every ticket that arrives at your helpdesk should have a clear answer to the question: "Is this ours, or do we escalate to the client's IT team?" Without that clarity, your technicians waste time on scope disputes that should have been resolved before the agreement was signed.

How to Sell Co-Managed IT Without Cannibalizing Full-Stack Deals

The fear every MSP owner has: "If I offer co-managed, won't my full-stack prospects just buy the cheaper option?"

The answer is no — if you position co-managed correctly. Co-managed isn't "full stack but cheaper." It's a different product for a different buyer. The full-stack buyer is a company without internal IT — they need you to own everything. The co-managed buyer is a company with internal IT that's looking to supplement, not replace — they wouldn't buy full-stack at any price because they're keeping their IT director.

When you present a proposal to a co-managed prospect, the comparison isn't "co-managed vs. full-stack" — it's "co-managed vs. hiring two more IT staff at $160,000/year each." A $168,000/year co-managed agreement looks very different when the alternative is $320,000 in salary plus benefits.

Your proposal should lead with the modules they actually need, not a menu of everything you offer. A 200-person manufacturing company with a 3-person IT team probably needs cybersecurity and backup management, not helpdesk overflow. A 75-person law firm with one IT manager probably needs helpdesk overflow and monitoring, not vCIO services. Scope the proposal to their actual gap — the modules they don't buy today are future expansion opportunities, not missed revenue.

Common Co-Managed IT Mistakes

Under-scoping the agreement to win the deal. "We'll start with just monitoring and expand later" sounds reasonable — but monitoring without remediation means your team sees alerts they can't act on, which frustrates both your technicians and the client. If you're monitoring servers, you need the authority (and the paid scope) to patch them.

Not charging for tool access. Your RMM, PSA, and documentation platform aren't free to you — they cost $15–$35/endpoint/month. If the client's internal IT team is using your tools, you're paying for their efficiency. Charge for it.

Treating co-managed clients as second-tier. Co-managed clients who feel like afterthoughts churn. They should get the same onboarding experience, the same quarterly business reviews, and the same response times as full-stack clients. The only difference is scope — not quality.

No escalation path defined. When the client's IT director is stuck on a problem your team could solve in 20 minutes, but "project work" isn't in scope, everyone loses. Build an hourly project rate ($150–$200/hour is standard) into every co-managed agreement so there's always a path to yes.

For more on building MSP proposals that close, read our MSP pricing guide and RFP automation guide.