Ask an IT director with four people what they need and few will say “someone to take this off me”. More often they describe covering endpoints, identity, Teams governance, security incidents and a service desk at the same time, with hybrid working having pushed the perimeter out to every laptop and personal phone, and a cyber insurer asking for evidence of controls nobody has time to produce.
That is a capacity problem rather than a competence problem, and outsourcing is designed to solve a different one.
What is co-managed IT?
In a co-managed model, you and the provider agree which parts of the workplace the provider runs, to what standard, and where the boundary sits. Typically that covers unified endpoint management, identity governance, security monitoring and a service desk on defined service levels. Your team keeps architecture, strategy, supplier relationships and anything specific to your business.
The provider supplements the team. It does not sit above it, and it does not replace it.
Two things follow. Your people stay close to the estate, so institutional knowledge does not leave with a contract. And the provider has to be good at working alongside people rather than around them, which is a cultural question as much as a technical one and is worth testing during procurement.
How is co-managed IT different from outsourcing?
The difference is accountability, and it is worth being clear about because the two models are often sold interchangeably.
In full outsourcing, the provider owns the outcome. You define what good looks like, they deliver it, and you manage them against a contract. It works well where IT is not a differentiator, where the estate is standard, and where you do not want an internal team.
In co-managed IT, your team owns the outcome and the provider owns defined parts of the delivery. You keep control and context. You also keep the management overhead, because a co-managed relationship needs someone internally to run it.
Choosing badly in either direction is expensive. Organisations that outsource when they wanted co-managed can find themselves paying change control for things their own team used to do in an afternoon. Organisations that go co-managed when they wanted to hand IT over are disappointed that they still have work to do.
“The question I ask is what the internal team should be spending its time on if the firefighting stopped,” says Martin Summerhayes, Head of Managed and Support Services at Northdoor. “If the answer is a list of things only they can do, because they know the business, co-managed is almost always right. If there is no answer, the organisation probably wants outsourcing and should say so.”
When does co-managed IT work best?
Some reasonably reliable indicators:
- The team is small relative to the estate. One to five people covering endpoints, identity, security and support is the typical profile, and the gap is structural rather than a performance problem.
- Cover falls over at the edges. Holidays, illness and out-of-hours are where a thin team is most exposed, and where a provider’s shift cover is worth most.
- You are paying several vendors for overlapping services. Consolidating them under one accountable provider often saves money and usually saves meetings.
- You cannot evidence controls on demand. Insurers, auditors and increasingly clients want documented proof. Producing it is routine for a provider and a scramble for a stretched team.
- Specialist depth is needed occasionally. Identity, storage or security specialists are hard to justify as permanent hires and easier to access through a service.
- The team is good and you want to keep it. Co-managed removes the work people leave over, rather than removing the people.
It works less well in three situations. If nobody has decided what the IT function is for, adding a provider will not settle it. If the estate is small and stable, you may not need one. And if the aim is to reduce headcount, you are buying outsourcing and should treat it that way.
What does it look like in practice?
The Salvation Army is the example we know best. We have worked with the charity for more than seven years across more than 700 UK locations, running security monitoring and endpoint services alongside the charity’s own team rather than in place of it, as set out in our Salvation Army case study.
The scale is difficult: a small internal team, a large distributed estate including care homes, churches and community centres, sensitive personal data, and the budget constraints any charity works within. What made it work was the operating model rather than any single technology choice. The internal team stayed accountable for the organisation’s IT and kept the relationships only they could hold, while the day-to-day services ran to a defined standard underneath.
The team there describes Northdoor as a “critical friend”, which is a good description of what a co-managed provider should be: close enough to challenge, accountable for delivery, and not trying to sell more technology into every conversation.
What should you ask a provider before signing?
- Where exactly does your responsibility end and ours begin? Written down, per system. Vagueness here is where co-managed arrangements most often fail.
- Who is our named contact, and how senior are they? Named, senior contacts are often among the first things to change when a provider grows or is acquired.
- What happens out of hours? Who is awake, what can they do without approval, and who do they call?
- How do you work with our team day to day? Ask for specifics, such as shared ticket queues, joint stand-ups and access arrangements.
- What reporting will we get, and will it satisfy internal audit and our insurer without us reformatting it?
- Can we start with part of the estate? A provider confident in the service will accept a scoped start.
- What does exit look like, including handover of documentation and configuration?
What this means for your organisation
For most organisations the decision comes down to one question: is the internal team the problem, or is it the amount of ground they are being asked to cover? If it is the second, co-managed is usually the better model. Our modern workplace managed services are built around it, and our managed services cost estimator gives a market-referenced range before you speak to anyone. Our guide to buying managed IT services without committing first covers how to structure a first engagement, and the full range is on our IT managed services page. If you would rather talk it through, get in touch.