How do I sell co-managed IT to companies with internal IT teams?
Internal IT staff often see an MSP as a threat. Co-managed IT works when you make their job easier, not replace them.
- Internal IT blocks our proposals.
- Who does what in co-managed?
- How do we price it?
Sell to the IT manager as backup: help with after-hours coverage, projects, security tools and the tasks they never get to. Define responsibilities in writing with a RACI chart, agree on shared tools and access, and set escalation rules. Price by scope, such as tools, hours or service desk overflow, not as a full managed contract.
What co-managed clients buy
- After-hours and vacation coverage.
- Security tools and monitoring.
- Project help: migrations, upgrades.
- Overflow service desk.
Responsibilities
| Area | Internal IT | MSP |
|---|---|---|
| Daily user support | Lead | Overflow |
| Security monitoring | Review | Run |
| Projects | Own | Deliver |
| After hours | Escalation only | First response |
How we look at it at ShoutEx
We write co-managed messaging aimed at IT managers and build the pages and outreach.
- Positioning as a replacement.
- No written split.
- Shared admin accounts.
- Pricing as full managed.
- Positioned as backup.
- RACI chart.
- Separate accounts and logs.
- Scope-based pricing.
What MSP owners and guidance say
Here is what MSPs and IT staff say.
Internal IT staff describe good and bad co-managed experiences.
Browse the threads →Community summaries describe recurring themes in public threads, not individual posts. Vendor pages describe vendor claims, so test them on your own calls.
Read next
Go deeper in the ShoutEx guides, or check the sources behind this answer.
We'll build co-managed messaging and outreach.
Book a call →Follow-up questions
Is co-managed profitable?
It can be, with clear scope.
Who owns the PSA tickets?
Agree it. Many use shared or integrated ticketing.
Can co-managed lead to full managed?
Sometimes, when internal staff leave.