Your IT manager doesn't need replacing - they need backup
Your IT manager doesn't need replacing - they need backup.
Co-managed IT services should allow an internal IT manager or team to flourish, while retaining ownership of technology strategy and business relationships.
Co-managed IT services allow an internal IT manager or team to retain ownership of technology strategy and business relationships, while an MSP provides agreed capacity, specialist expertise, monitoring, service desk support, project resources, or out-of-hours cover. The aim of an MSP in a co-managed arrangement isn’t to replace internal IT, but rather to make the existing function stronger and less dependent on one or two overstretched people.
Every organisation eventually reaches a point where “the IT person” becomes “the IT department”, and while their job title may change over time, in our experience, it’s the workload that usually gets there first.
A capable IT manager can find themselves handling user support, Microsoft 365, devices, networks, suppliers, security, backups, budgets, projects, and maybe the occasional gap in their calendar to understand why the meeting-room screen is not working - or try to solve what is (to me) one of life’s greatest mysteries: why that printer doesn’t print. They also have to understand what the business is trying to achieve and turn that into a sensible technology plan.
So, what we’re saying is that it’s not one role - in some cases, it’s not even two roles. It’s a mash-up of multiple roles, sharing a calendar and the same 8 hours in a working day.
Now, when the pressure becomes visible, outsourcing is often floated as a potential answer, but this opens the door to a potential dilemma of: ‘Do we keep everything in-house, or do we hand the whole function to a provider?’.
But for many SMEs and mid-market organisations, neither extreme is necessary. Your IT manager, as it goes, actually doesn’t need replacing. They just simply need help. And that sweet spot is exactly where co-managed IT services fit.
What are co-managed IT services?
Co-managed IT is a shared delivery model that keeps your internal IT manager or team at the centre of the function, retaining the organisational knowledge, stakeholder relationships and decision-making that are difficult to reproduce from outside. A managed service provider then wraps around and supports them in clearly agreed, predefined areas.
If you want the broader definition first, our guide to what an MSP is explains how managed services work and where a provider can fit alongside an internal team. In a co-managed model, an MSP’s relationship with you may seem them provide solutions such as:
- first-line service desk or overflow support
- 24.7.365 monitoring and out-of-hours escalation
- cyber security operations and incident support
- Microsoft 365, cloud, networking or infrastructure expertise
- project resource for migrations, upgrades or new sites
- holiday and sickness cover
- documentation, reporting and an escalation path for complex issues
That way, the internal team is able to retain things such as strategy, budgets, stakeholder relationships, application ownership, change approval, and get back to doing work in the areas where the organisation needs them most.
There is no universally defined optimal split - nor is there a guaranteed tried and tested method, and that’s because no two businesses are the same, so no two co-managed relationships can ever be either. In our experience, the best ones have been the partnerships designed around the internal team you have and the pressure they’re carrying.
A capacity problem can look like a performance problem
When projects keep slipping, tickets remain open or known risks sit on a list for months, it is easy to conclude that the internal IT function is underperforming.
And look, sometimes on a rare occasion, maybe that’s true. More often than not, though, what we tend to see is a capable person with more and more pressure and demands on them, making reasonable trade-offs to try and cut through their unreasonable queue, and stay afloat with what’s expected of them.
As to be expected, that means the urgent, reactionary work wins out over anything else, leaving little time to be proactive. That may manifest as a user who cannot log in and needs help now, a failing switch that needs immediate attention, or a supplier who needs an answer before the close of play. The knock-on effect of that is that something strategic - be it a network review, recovery test, an Intune rollout, or a policy update - gets moved to next week… Then next week comes, and what happens? It’s full of its own emergencies and priorities. And before you know it, it’s Thursday, and that week has passed you by, too.
Adding co-managed support changes the look and feel of that, as the routine demand can be shared. Monitoring continues outside office hours, and a specialist can take on work that would otherwise require days of research. It basically allows projects to move without leaving the service desk uncovered.
This is not about making an IT manager do more work - we know all too well that they’re already doing more than their fair share. Co-managed services give them room to do the work only they can do.
Your IT manager holds context that is hard to outsource
No matter how pretty and detailed a neat diagram of your network is, technology doesn’t ever operate that way in the real world. It sits inside reporting lines, customer commitments, old decisions, budget cycles, supplier relationships and a few systems nobody especially likes, but begrudingly still has to use.
One vital aspect of having an internal IT manager in place is that they know which application is genuinely business-critical, even if the asset register suggests otherwise. They probably also know valuable insights into things like which department is about to recruit, which office move is quietly becoming real and why a seemingly simple change will cause trouble at month-end.
A good co-managed partner combines all this with their broader technical capabilities, repeatable service processes, and additional people. Internal IT provides the “why” and the organisational judgement, while the MSP adds more ways to deliver the “how” to form a stronger IT function, rather than two competing ones.
What kind of backup does an internal IT team actually need?
The answer depends on where the constraint sits, but in practice, support usually falls into five areas.
Capacity for day-to-day support
User support is important, but it is also interrupt-driven. Service desk cover or overflow support can absorb routine tickets and handle busy periods while the internal manager focuses on improvements, suppliers, and business priorities. While this can be particularly useful during onboarding peaks, office moves or periods of rapid growth, it also gives users a dependable route to help when the internal team is already dealing with something more serious.
Cover beyond one person's working day
Something as common as annual leave shouldn’t be viewed as a resilience test for internal teams. Co-managed IT can provide monitoring, escalation, and support during holidays, sickness, and outside normal hours, but it also reduces the risk posed when one person becomes the default owner of every system and every incident. The internal manager isn’t called about every alert at 2am - quite the opposite, in fact. A clear escalation process should be implemented, defining what the provider handles, what can wait and when the internal team genuinely needs to be involved.
Specialist depth when the situation demands it
Modern IT spans identity, cyber security, networking, cloud, compliance, backup, device management and business applications, but maintaining deep expertise in every area is unrealistic for a lean team. Working with a co-managed partner gives the IT manager access to specialists when needed, without requiring the business to recruit every capability as a permanent role. That might be an Entra ID review, a network redesign, an incident response decision or support preparing evidence for an audit. The internal manager remains accountable to the business, but with a deeper bench behind them, they feel much more secure.
Resource to move projects forward
Projects are often the first casualty of operational pressure, especially if the people designing the migration are also handling tickets, managing suppliers, and keeping the existing environment running. With an MSP dovetailed into the mix, they can add planning (and delivery resource) for a defined piece of work while internal IT retains business-centric priorities and approvals. This is often a better use of co-managed support than asking the same small team to run business-as-usual while also running a major change programme at full speed.
Better documentation and clearer escalation
The most worrying phrase in a small IT function isn‘t “we have a problem”. Problems are fine. We can solve problems. The one that drives fear into us is when it’s more along the lines of “oh.. well - I think only Sam knows how that works… and they’re away for the next month”. Shared documentation, standard processes, and an external escalation route reduce dependency on individual memory, which also makes future growth, absence and staff changes easier to manage. This links directly to the question of what a modern IT provider should be responsible for. Tools matter, of course, but ownership matters more, and someone needs to know who is monitoring, who responds, who approves changes and who communicates with the business.
Co-managed IT only works when ownership is clear
The word “co-managed” can sound reassuringly collaborative, but it can also become a polite description for confusion if the operating model is vague.
Users shouldn’t be bounced between an internal team and the provider, and security alerts should not wait while both sides assume the other is investigating. Similarly, changes shouldn’t just appear without shared visibility. So what does ‘good’ look like? Well, a good arrangement documents:
- what the internal team owns
- what the provider owns
- where responsibility is shared
- how tickets and incidents are escalated
- who approves changes
- which tools and records both teams use
- how performance, risks and priorities are reviewed
This division should be specific enough to refer back to at any point, whether it’s 3pm on a difficult Tuesday afternoon, a slow Friday afternoon, or in the middle of the night - it’s not just sensible-looking language stuck in a contract and forgotten about.
But remember: it’s not set in stone, and it should also be allowed to change as the dynamic evolves. An organisation may initially need service desk overflow, then add security monitoring or project support later. Co-managed IT is useful precisely because the boundary can move as the team and business evolve.
How do you introduce an MSP without undermining the IT manager?
Start by involving the IT manager in designing the relationship.
That probably sounds obvious, but it’s often where many businesses get the tone wrong. If an MSP appears after a closed-door leadership discussion, even a sensible service can look like a threat. If the internal team is asked where the pressure sits, which work should remain in-house and what good support would look like, the conversation becomes much more constructive.
The provider has responsibilities here, too. They should respect existing knowledge, learn the environment before prescribing changes and be comfortable working through the internal lead. A co-managed MSP should make that person more effective and more credible inside the business, not compete to become the loudest technical voice in the room.
For senior leaders, remember that this is an investment in the internal function, and success is not measured by how much the provider takes away. It’s measured by whether the whole service becomes more resilient, responsive and able to improve.
Signs your IT manager may need backup
The case for co-managed IT is rarely one singular (and potentially dramatic) failure. It’s usually a pattern of things like:
- strategic work being repeatedly displaced by support demand
- projects depend on evenings, weekends or heroic effort
- holidays and sickness create obvious coverage gaps
- complex issues have no dependable escalation route
- documentation exists in one person's head
- security, recovery or compliance work is understood, but keeps slipping
- the business is growing faster than the IT function can absorb
- leaders want better visibility of service performance, risk and priorities
If an internal IT manager is guilty of any number of these, they aren’t the problem. It usually means the operating model has not kept pace with the organisation.
What should you ask a co-managed IT provider?
The best first question put to any prospective MSP shouldn’t be “which tools do you use?”, or “how much do you charge?”. Neither of those matters if you don’t immediately establish how an MSP is going to work with your team, so ask a prospective provider things like:
how do you decide and document responsibilities?
how does your service desk work with internal IT?
how should both teams share documentation and visibility?
what happens during an out-of-hours incident?
which specialist skills are available and how they are engaged?
how are projects scoped without disrupting day-to-day support?
how is the service reviewed and adapted over time?
how do you handle disagreement or challenge a risky decision?
Any provider worth working with should be able to explain the working relationship in practical terms - but if the answer is mostly a product list, you still do not know how the service will operate.
Build around the team you already trust
There are situations where fully managed IT is the right model; for example, a business without an internal function may want an MSP to take broad responsibility for support, infrastructure, security, and planning.
But where a capable IT manager or team is already in place, the more useful question is often not “should we outsource IT?” It’s just “where does our team need reinforcement?”
Perhaps routine tickets are consuming the week. Perhaps there is no safe holiday cover. Perhaps a cloud migration needs skills that the business only needs for six months. Perhaps the security workload has grown beyond what a small team can reasonably monitor.
Start there.
Co-managed IT services from Fifosys are built around the internal function an organisation already has. We agree on what stays with your team, where we take responsibility and how both sides will work across support, monitoring, cyber security, cloud, infrastructure and projects.
Your IT manager should remain the person who understands the business. They should simply have more capacity, better cover and the right specialists behind them when it matters.
Frequently asked questions
What are co-managed IT services?
Does co-managed IT replace an internal IT manager?
What is the difference between co-managed IT and fully managed IT?
Can a co-managed MSP support a one-person IT team?
How do internal IT and an MSP avoid duplicating work?
When should a business consider co-managed IT support?
Build around the IT team you already trust
Co-managed IT can add service desk capacity, monitoring, specialist expertise and project resource around your internal function, with clear ownership on both sides.
Talk to our team
Tell us where your internal IT function is under pressure and we’ll help you work through the right support model.
Co-managed IT services
See how Fifosys works alongside internal IT teams across support, monitoring, cyber security, cloud, infrastructure and projects.