Co-Managed IT Support

Co-managed IT is exactly what it sounds like: your internal IT team and an external MSP working together. Rather than fully outsourcing IT or trying to handle everything internally, you combine both models to get the best of each. This isn't a new concept, but it's becoming increasingly common as businesses recognise that neither pure in-house nor pure outsourcing is always the right answer. Maybe you have a talented IT person who handles the strategic work brilliantly but can't be everywhere at once. Maybe you need specialist skills occasionally but not enough to hire for. Maybe you just need someone to answer the phone when your IT manager is on holiday. Co-managed IT solves these problems without forcing you to choose between keeping or replacing your internal team.

**You have one or two IT staff who are stretched** This is the most common scenario. You have internal IT capability that works well for strategic projects, complex systems, and being the technical brain of the business. But they're also fielding password resets, printer problems, and "my computer is slow" calls. Co-managed support handles the reactive work so your internal team can focus on what adds real value. **You need specialist skills occasionally** Your IT manager is excellent at keeping systems running and managing projects. But they're not a cybersecurity specialist, a cloud architect, or a Microsoft 365 expert. Co-managed arrangements give you access to specialist expertise when you need it without maintaining that capability in-house. **You need coverage beyond business hours** Your IT person works 9-5, but your business runs outside those hours. Rather than expecting them to be on-call constantly (which leads to burnout and resignation), co-managed support provides out-of-hours coverage. **You want a safety net** What happens if your IT manager is ill? On holiday? Leaves? Co-managed arrangements provide continuity and backup that reduces your dependency on any single person. **You're growing faster than your IT team can scale** You're adding staff, offices, or systems faster than you can hire IT capability. Co-managed support provides the elasticity to handle growth without constant recruitment.

**Tier 1 / Helpdesk Only** Your internal team handles complex issues, projects, and strategy. The MSP handles frontline support - password resets, basic troubleshooting, routine requests. This frees your internal IT to focus on higher-value work. *Typical cost: £15-30 per user/month* **Specialist Augmentation** Your internal team handles day-to-day operations. The MSP provides specialist expertise - cybersecurity assessments, cloud migrations, complex projects - on demand. Think of it as having consultants available without the consultant price tag. *Typical cost: Retainer plus project work* **Extended Coverage** Your internal team handles business hours. The MSP handles out-of-hours, providing monitoring and response when your team isn't working. This is particularly valuable for businesses with extended operations or international clients. *Typical cost: £20-40 per user/month* **Full Partnership** A more comprehensive arrangement where the MSP and internal team work as a genuinely integrated unit. Shared tools, shared tickets, joint planning. The MSP might handle infrastructure while internal IT focuses on applications, or vice versa. *Typical cost: £30-50 per user/month*

The difference between successful and failed co-managed arrangements usually comes down to clarity and communication. **Clear Role Definition** Who handles what? Where are the boundaries? What triggers escalation in each direction? These questions need clear answers that everyone understands. Ambiguity creates gaps (things falling between teams) or conflicts (both teams trying to own the same thing). **Shared Tools and Visibility** Both teams need to see what the other is doing. Shared ticketing, shared documentation, shared monitoring. Without this, you end up with two disconnected operations that create more problems than they solve. **Regular Communication** Weekly or fortnightly calls between your internal IT and the MSP relationship manager. Not just reactive problem-solving, but proactive planning and alignment. This is where the real value of partnership emerges. **Clear Escalation Paths** When does the MSP escalate to your internal team? When does your internal team bring in the MSP? What's urgent versus normal? These paths need to be defined and tested. **Trust and Respect** This sounds soft, but it matters. Your internal IT team needs to see the MSP as support, not threat. The MSP needs to respect your internal team's knowledge and role. If either side is territorial or dismissive, the arrangement fails.

**Unclear Ownership** "I thought you were handling that" is the most common phrase in failed co-managed arrangements. Everything needs an owner. If something is shared, there still needs to be a primary owner. **Treating the MSP as Inferior** Internal IT teams sometimes view MSPs as less capable or less important. This creates resistance rather than partnership. The best arrangements treat both teams as equals with different but complementary roles. **Hidden Work** Your internal team handling things that should go to the MSP (because it's quicker than explaining), or the MSP not logging work properly. This undermines the whole model and makes the arrangement seem less valuable than it is. **No Evolution** Your needs change. Your internal team's capability changes. A co-managed arrangement that worked two years ago might not be right today. Regular reviews and willingness to adjust are essential.

If you're currently handling everything internally and considering co-managed support, the transition needs thought. **Start with the Pain Points** What's actually stretching your internal team? Where are the gaps? Start the co-managed arrangement there rather than trying to boil the ocean from day one. **Involve Your Internal IT Early** Your IT manager or team needs to be part of defining the arrangement, not have it imposed on them. They know where help would be most valuable and where they'd prefer to retain control. **Allow Adjustment Time** The first few months of any co-managed arrangement involve learning - both sides understanding how the other works. Expect some friction and be patient with refinement. **Define Success** How will you know if the arrangement is working? Reduced burden on internal IT? Faster response times? Fewer escalations? Define this upfront so you can evaluate properly.