There’s only so much time in the day.
Even the most capable internal IT teams can reach a point where keeping the business running takes up the time they had intended to spend improving it.
The answer isn’t necessarily to replace what’s already working. It may be to strengthen the team you already have.
That’s where co-managed IT support comes in.
What is co-managed IT support?
Co-managed IT support is an arrangement where a business retains its internal IT team while working with an external managed service provider (MSP) to share agreed responsibilities.
The external provider can take ownership of particular systems, provide additional engineering capacity or offer specialist expertise when required.
Unlike fully outsourced IT, the internal team remains an active part of the business’s technology operations and decisions.
The arrangement is tailored around what the existing team does well and where additional support would make the greatest difference.
For organisations with established IT personnel, this provides another option between recruiting additional employees and outsourcing their IT entirely.
When does an internal IT team need additional support?
An internal IT team may already understand the organisation’s systems, people and priorities better than any outside provider.
That knowledge has significant value.
However, having a capable team doesn’t automatically mean having enough capacity to address every requirement.
Consider an IT manager responsible for a business’s existing infrastructure. They understand the environment and maintain a reliable service, but a planned network upgrade has been repeatedly postponed because routine operational work takes priority.
Recruiting another employee might help, but it may not be the most suitable solution for a project requiring specialist engineering expertise.
In this situation, co-managed support could allow the IT manager to retain oversight of the environment while an external partner helps plan and deliver the upgrade.
The objective isn’t to reduce the role of the internal team. It’s to give them the resources to move work forward without compromising their existing responsibilities.
Signs co-managed IT may be worth considering
A shared support arrangement is worth exploring when an organisation finds that:
- Important improvements are repeatedly delayed by operational demands.
- Technical issues regularly require expertise outside the team’s usual specialisms.
- The business depends heavily on the availability of one or two individuals.
- Internal IT needs additional capacity without handing over complete responsibility.
- Management wants greater clarity around ownership, support coverage and longer-term technology planning.
None of these circumstances necessarily indicates poor internal performance.
They may simply show that the business’s requirements have moved beyond what its current resources were designed to accommodate.
How does co-managed IT work alongside an existing IT team?
The most important part of co-managed IT isn’t the number of engineers available. It’s how responsibility is organised between the two teams.
A successful arrangement starts by understanding the existing environment, current processes and the work the internal team wants to retain.
From there, both parties can agree which responsibilities will remain in-house and which will be shared or transferred to the external provider.
What does each team actually manage?
The following is an illustrative division of responsibilities. The exact arrangement should be agreed before support begins.
| Responsibility | Internal IT team | External IT partner |
|---|---|---|
| IT strategy | Leads business priorities and decisions | Provides technical advice and recommendations |
| End-user support | Handles agreed internal requests | Provides agreed overflow or escalation |
| Infrastructure | Maintains ownership and visibility | Monitors or manages agreed systems |
| Cybersecurity | Approves policy and risk decisions | Supports agreed technical controls and monitoring |
| Projects | Defines requirements and approves changes | Provides engineering and delivery capacity |
| Reporting | Reviews performance and priorities | Supplies agreed service data and recommendations |
One organisation may prefer to retain its entire service desk internally while outsourcing specialist escalations.
Another may want its internal IT manager to focus on technology planning while an external team takes responsibility for routine support and maintenance.
Neither approach is inherently better.
What matters is that every responsibility has a clear owner and that both teams understand when work should be escalated, reviewed or approved.
Can an external IT provider use our existing systems?
In many cases, yes.
A co-managed IT partner may be able to work with an organisation’s existing ticketing platform, documentation, monitoring systems and change-management processes.
This can reduce the need for employees to follow separate support procedures or duplicate information between teams.
However, compatibility should be confirmed during the initial assessment. Not every provider supports every tool or operating model.
Businesses should establish how access will be controlled, what information can be shared and which actions require internal approval.
For example, an external engineer may be authorised to investigate an infrastructure alert, but a change affecting a business-critical application may still require approval from the internal IT manager.
Clear boundaries allow additional expertise to be introduced without sacrificing visibility or control.
Co-managed IT vs fully managed IT: what’s the difference?
Both arrangements involve an external technology provider, but they differ in how responsibility is allocated.
| Co-managed IT | Fully managed IT | |
|---|---|---|
| Internal IT team | Remains actively involved | May not be required |
| Operational responsibility | Shared according to agreement | Primarily held by the provider |
| IT decisions | Business retains oversight with internal leadership | Business retains strategic authority, provider manages agreed delivery |
| Support model | Selected functions or shared workload | Wider ongoing support |
| Suitable for | Businesses with existing IT capability | Businesses seeking comprehensive outsourced management |
Co-managed IT is often appropriate when a business wants to retain its existing people and knowledge while adding specialist resources.
Fully managed IT may be more appropriate when an organisation wants a provider to take responsibility for most day-to-day IT operations.
The distinction is not simply about company size.
It comes down to the organisation’s existing capabilities and how much operational responsibility it wants an external partner to assume.
How much does co-managed IT support cost in the UK?
Co-managed IT pricing varies because the amount of responsibility assigned to an external provider can differ significantly between organisations.
Common approaches include a fixed monthly agreement, a per-user fee, pre-agreed engineering hours or a combination of ongoing support and separately priced projects.
Published UK provider estimates vary considerably. For example, Connection Technologies has published a £25–£60 per-user monthly range for some co-managed arrangements, while Stratiis describes a broader £25–£100+ range depending on requirements.
These are third-party published estimates, not Cirrus quotations or independently verified market averages.
Actual costs depend on the services included.
A business requiring specialist escalation for its existing IT team will have different requirements from one seeking broader infrastructure management and ongoing security oversight.
What should you check in a quotation?
Rather than comparing monthly fees alone, establish:
- Which systems and users are covered.
- Which services are included or excluded.
- Whether project work is quoted separately.
- The agreed support hours and escalation arrangements.
- Who pays for additional licences and software.
- What happens when requirements change.
Two proposals can appear similar in price while offering substantially different levels of service.
A clear scope allows the business to compare them properly.
Is co-managed IT better than hiring another employee?
That depends on the problem the organisation is trying to solve.
Recruitment can be the right choice when there is enough consistent work to justify another permanent role, particularly where the business requires someone to be present on-site or deeply involved in internal operations.
Co-managed IT may be more appropriate when an existing team requires access to skills that are difficult to cover through a single additional hire.
For example, the expertise needed to improve network resilience may differ from the knowledge required to manage Microsoft 365 security or deliver a complex infrastructure project.
An external IT partner can provide access to different specialists under an agreed arrangement.
However, co-managed IT is not automatically cheaper or more effective than recruitment.
The decision should consider the volume of work, required expertise, availability, business knowledge, management requirements and total cost of each option.
What should happen when co-managed IT support begins?
A good partnership needs a clear starting point.
Before taking responsibility for any part of an organisation’s technology, an external provider should understand the current environment and how the internal team operates.
1. Understand the existing environment
The initial review should establish which systems the organisation uses, who currently manages them and where technical or operational risks may exist.
It should also identify work the internal team wants to continue owning.
2. Agree on responsibilities
Both teams should know who receives support requests, who investigates incidents and who approves significant changes.
Shared responsibility needs to be documented rather than assumed.
3. Establish access and communication
Appropriate permissions, escalation paths and communication arrangements should be agreed before live support begins.
Access should be limited to what is necessary for the work being performed.
4. Review performance together
Once the arrangement is operating, regular reviews should consider whether the additional support is helping the internal team meet its priorities.
Useful measures might include unresolved tickets, time spent on agreed improvement work, escalation performance and recurring issues.
The aim is to assess the quality of the partnership, not simply the volume of work completed.
When might co-managed IT not be the right choice?
Co-managed IT is not the answer to every technology challenge.
If a business has no internal IT capability and wants a provider to take full responsibility for ongoing operations, a fully managed agreement may be more suitable.
If the organisation only needs assistance with one clearly defined piece of work, a standalone project may be a simpler option.
And if the primary requirement is a permanent, on-site member of the internal team, recruitment may offer greater long-term value.
A good technology partner should be prepared to discuss these alternatives rather than recommending the same service to every business.
How to choose a co-managed IT provider
When evaluating potential partners, look beyond the range of services listed on their website.
Ask how they will work with your existing people.
Will they accommodate your current systems? How will responsibilities be documented? Who will own an issue when it crosses between internal and external teams?
It’s also worth understanding the provider’s experience with environments similar to yours, their approach to security, their reporting arrangements and how they handle specialist engineering requirements.
Most importantly, establish whether the relationship will give your internal team greater capacity without creating an additional layer of management work.
The objective is to build an arrangement that strengthens the business’s existing capability.
Working together with Cirrus Technology Solutions
At Cirrus Technology Solutions, we believe the answer isn’t always to change what you have. It’s about making more of it.
Our approach begins with understanding your existing environment, the people responsible for it and where additional support could make a meaningful difference.
Whether the requirement involves ongoing IT management, infrastructure expertise or support with a planned project, the aim is to establish clear responsibilities and a working relationship that complements your business.
We focus on building partnerships around the way organisations operate, rather than expecting every organisation to fit the same support model.
Already have an internal IT team but need additional support?
Let’s discuss how your current IT arrangements work and where Cirrus could add value.
Frequently asked questions
Can co-managed IT work with a single internal IT manager?
Yes. Co-managed support can complement a single IT manager by providing agreed engineering expertise, escalation support or additional operational capacity while the internal manager retains oversight.
Does co-managed IT mean losing control of our systems?
No. The arrangement should define responsibilities and permissions clearly. The business retains authority over its technology decisions and agrees which activities the external provider is authorised to perform.
Is co-managed IT suitable for businesses with multiple locations?
It can be. An external partner may help an internal team maintain agreed technology standards, provide remote assistance and coordinate engineering support across locations. The exact coverage needs to be confirmed in the agreement.
Can we keep our existing IT suppliers and software?
Often, yes. A co-managed provider can potentially integrate with existing suppliers and platforms. Compatibility, contractual responsibilities and required access should be assessed before onboarding.
Do we need to outsource our helpdesk?
Not necessarily. Some organisations retain first-line support internally and use an external provider for specialist escalation. Others choose to share or transfer particular support responsibilities.
How long does co-managed IT onboarding take?
There is no universal timeframe. Onboarding depends on the complexity of the environment, available documentation, security requirements and the responsibilities being transferred. A provider should agree a realistic transition plan after reviewing the systems involved.