Ask three managed IT services providers how they would cover your business and you will get two very different shapes of answer. One takes the whole function off your hands. The other stands alongside the people you already employ. Both are sold as managed IT support.
Co-managed IT support splits an IT function between an internal team and an external provider, with each side owning a defined part of it. Fully outsourced support hands the entire function to the provider, service desk and all. The gap between the two models is rarely about the monthly figure. It is about who holds the knowledge, who carries the risk, and how fast your technology can change direction when the business does.
This guide sets the two side by side: what each one actually covers, how the money behaves over three years rather than twelve months, where security accountability lands, and the questions that separate a sound fit from an expensive mismatch.
Table of contents
- What Co-Managed IT Support Actually Means
- What Fully Outsourced IT Support Covers
- Cost: How Co-Managed IT Support and Outsourcing Compare
- Control, Speed and Institutional Knowledge
- Security and Compliance Under Each Model
- When Co-Managed IT Support Is the Right Choice
- When Fully Outsourced IT Support Wins
- How to Run the Decision Without Guesswork
- Making the Model Work After You Sign
- Co-Managed IT Support FAQs
What Co-Managed IT Support Actually Means
The name does a lot of work, and it gets stretched. Co-managed is not a discounted version of outsourcing, and it is not contractor staffing. It is a deliberate division of one IT function between two organisations that each remain accountable for a named part of it.
The split-responsibility model
In a co-managed IT support arrangement, the provider and the internal team divide the estate by layer, by task or by time. The provider might own patching, backup administration and after-hours cover while your staff own applications, projects and the user relationship. The dividing line is written down, and both sides work from the same ticket queue rather than two separate ones.
What stays with your internal team
Whatever depends on knowing your business tends to stay in-house: the line-of-business applications, the odd integration nobody else understands, the relationships with department heads, and the judgement calls about what matters this quarter. Keeping that internal is the point of the model rather than a compromise within it.
What the provider brings to the table
The provider supplies the things that are uneconomic to build for one organisation: a 24-hour service desk, monitoring and alerting platforms, patch and vulnerability tooling, specialist engineers you would never keep busy full time, and the process discipline that comes from running the same playbook across many clients. Good co-managed IT support is bought for capacity and depth, not for cheapness.
Where the boundary usually sits
Three boundaries work well in practice: by tier, where the provider takes first-line and your team takes third; by domain, where the provider takes infrastructure and your team takes applications; and by clock, where the provider covers evenings, weekends and holidays. Trouble starts when the boundary is described in adjectives instead of tasks, so co-managed IT support needs a written responsibility matrix from day one.
What Fully Outsourced IT Support Covers
Full outsourcing takes the opposite position. One organisation is responsible for everything technical, from a forgotten password to the three-year roadmap, and your side of the arrangement becomes governance rather than delivery.
One provider, one accountable party
The strongest argument for full outsourcing is that there is nowhere for a problem to hide. When email, the network and the finance system are all in scope, nobody can argue about whose fault the outage is. That single line of accountability is worth real money to a business that has spent years refereeing between suppliers.
The service desk becomes the front door
In a fully outsourced model the provider’s help desk is where every request begins. Users lose the colleague down the corridor and gain a documented process, a ticket reference and a response target. Some organisations find that trade liberating; others discover how much informal support their internal person had been absorbing without anyone logging it.
Strategy, procurement and vendor management
Mature outsourcing contracts also include the advisory layer: budget planning, lifecycle refresh, licence optimisation and vendor management across your other suppliers. This is where a virtual CIO or account technology strategist earns their fee, and it is the part buyers most often forget to specify before they sign.
What you hand over in exchange
You give up direct control of priorities. Your request joins a queue governed by contractual targets rather than by a conversation across the desk. You also give up the accumulation of internal knowledge, because after two years the deepest understanding of your estate sits inside another company. Neither is fatal, but both are real, and co-managed IT support exists largely to avoid them.
Cost: How Co-Managed IT Support and Outsourcing Compare
Price is the reason most of these conversations start and the worst reason to settle them. The two models put money in different places, and a straight comparison of monthly figures will mislead you almost every time.
The salary line versus the invoice line
Full outsourcing converts salaries into a single invoice, which is attractive on a spreadsheet and simple to forecast. Co-managed IT support keeps payroll and adds an invoice on top, so the headline number looks worse. The fair comparison is total cost of the outcome, including recruitment, training, holiday and sickness cover, tooling licences and the productivity lost when something waits three days for attention.
Per-user and per-device pricing under both models
Both models are usually priced per user or per device, but the rate differs sharply because the scope does. A fully outsourced seat carries the whole service; a co-managed seat carries only the layer the provider owns. Compare the rate against the responsibility matrix rather than against another quotation, because a cheaper co-managed IT support rate almost always means a narrower slice of work.
The costs people forget in co-managed IT support
Two teams need coordination, and coordination is not free. Budget for the management overhead of the internal lead who runs the relationship, shared tooling licences that may be charged per endpoint, and the time it takes for both sides to learn each other’s habits. Co-managed IT support that nobody manages internally drifts into duplicated effort within a quarter.
The costs people forget in full outsourcing
Out-of-scope work is the usual surprise. Project rates, onboarding fees, hardware procurement margins and the cost of anything sitting in the grey area between support and change all land outside the monthly figure. Ask for last year’s out-of-scope invoices from a comparable client before you accept the headline price as the real one.
A three-year view rather than a monthly one
Model both options over thirty-six months with headcount changes, one office move and one security incident included. That exercise usually shows full outsourcing cheaper in year one and the gap narrowing afterwards, while co-managed IT support absorbs growth more gently because you are only buying the additional capacity rather than the whole seat again.
Control, Speed and Institutional Knowledge
Cost decides the shortlist. Control usually decides the winner, because it determines what daily life feels like once the contract is signed and the novelty has worn off.
Who owns the technology roadmap
Under full outsourcing the provider proposes the roadmap and you approve it, which works well when your technology is ordinary and badly when it is a competitive differentiator. With co-managed IT support the roadmap stays with your team and the provider supplies delivery capacity, so strategic intent and execution remain in different hands by design.
How fast you can change direction
Contracts are built for stability, and stability is the enemy of a sudden pivot. A change of priority in a fully outsourced arrangement often means a change request, a revised statement of work and a fortnight of paperwork. Co-managed IT support lets you redirect your own people immediately and renegotiate only the provider’s share, which is a genuine advantage in a business that reorganises often.
Where institutional knowledge lives
Every estate accumulates undocumented reality: the server that must restart in a particular order, the supplier who only answers a personal mobile. Fully outsourcing puts that knowledge in the provider’s systems, which is fine until the relationship ends. Co-managed IT support keeps a copy of it inside the business, which is the quiet reason many finance directors accept the higher headline cost.
The bus-factor problem cuts both ways
A single internal engineer who knows everything is a risk. So is a provider whose only competent account lead resigns. Whichever model you choose, insist on documentation standards, a shared configuration record and named deputies, then test them by asking someone unfamiliar with the estate to follow the runbook.
Security and Compliance Under Each Model
Cybersecurity is where the difference between the models stops being a management preference and starts being a governance question. Regulators and insurers care about who is accountable, not about how the work is divided.
Who is accountable when an incident happens
Outsourcing the work never outsources the duty. Your organisation remains responsible for the breach even when the provider caused it, so the contract must define detection, notification timescales, containment authority and who may take a production system offline at three in the morning. Co-managed IT support makes this harder to write and more important to get right, because two parties can each assume the other is watching.
Evidence, audits and cyber insurance
Insurers and frameworks such as Cyber Essentials ask for evidence: patch levels, backup test results, multi-factor coverage, privileged account reviews. Decide early who produces that evidence and in what format. A well-run co-managed IT support arrangement assigns each control to one named owner and reports on it monthly, rather than leaving a shared spreadsheet nobody updates.
Identity, privilege and the joiner-mover-leaver process
Shared administration is the sharpest edge of the model. Two teams holding privileged credentials doubles the attack surface unless privileged access is brokered, time-bound and logged. Agree who creates accounts, who approves elevation and who removes access on the day someone leaves, then audit it quarterly rather than trusting the process.
Data protection duties do not transfer
Under UK data protection law you remain the controller and the provider is a processor, whichever model you pick. That means a written processing agreement, defined sub-processors, and clarity about where data sits. Co-managed IT support does not reduce the paperwork; it just means the controller has staff who can actually read it.
When Co-Managed IT Support Is the Right Choice
Some situations point clearly at one model. Co-managed IT support fits organisations that already have competent internal people and a reason to keep them, rather than those hoping to save money by keeping a smaller team.
You have capable people and not enough of them
The most common driver is depth, not skill. One or two good engineers can run an estate competently until holiday, illness, a project or a Friday afternoon incident stretches them past breaking point. Co-managed IT support adds elastic capacity underneath your existing people without asking them to hand over the work they are good at.
Coverage gaps rather than capability gaps
If your problem is nights, weekends, multi-site cover or the fortnight in August when everyone is away, you have a coverage problem. Buying a whole outsourced service to solve it is expensive. Buying overnight monitoring and first-line cover through co-managed IT support solves the actual gap for a fraction of the price.
Regulated, specialist or heavily customised environments
Manufacturing lines, clinical systems, legal case management and bespoke platforms all resist generic support. Providers can learn them, but slowly and at your expense. Keeping the specialist knowledge internal while outsourcing the commodity layers is usually the cheaper and safer split.
Growth without adding headcount
A business adding twenty users a year eventually needs a second engineer it cannot quite justify. Co-managed IT support absorbs that growth incrementally, letting you scale the provider’s share up and down while the internal role stays stable. It also buys time to see whether the growth is permanent before you commit to a permanent salary.
When Fully Outsourced IT Support Wins
The opposite case is just as clear, and pretending otherwise leads to co-managed arrangements with nobody internal to co-manage them, which is the worst of both worlds.
No internal IT at all
If nobody in the building owns technology, there is no team to share the work with. Appointing an office manager as the internal half of a shared model creates an accountability gap rather than a partnership. Full outsourcing, with a named account manager and a quarterly review, is the honest answer.
One overloaded generalist
Where a single person handles everything and is drowning, the choice depends on what you want them to become. If the goal is to free them for projects and business-facing work, co-managed IT support works. If the goal is to let them return to their original job entirely, outsource the lot.
Predictability matters more than control
Some boards value a fixed, forecastable number above flexibility, particularly during acquisitions or when finance is tightening. A fully outsourced contract with clear service levels delivers that predictability better than any hybrid, because there is one number and one accountable supplier.
Multi-site, shift-based or out-of-hours demand
Organisations running warehouses, care homes, hospitality or twenty-four-hour operations need cover no small internal team can sustain. Rota depth is exactly what a provider sells, and buying the whole service is often simpler than stitching cover around two employees who also deserve a weekend.
How to Run the Decision Without Guesswork
Most businesses choose on instinct and a price list. A structured comparison takes a fortnight and removes most of the regret, because it forces both models to answer the same questions.
Map the work before you map the model
List everything the IT function does over a typical quarter, then mark each item with who does it now, how often it happens, and what it costs when it goes wrong. That inventory is the only honest basis for deciding which layers to keep. Fitting co-managed IT support around a guess produces a responsibility matrix that collapses at the first serious incident.
Score coverage, capability and continuity separately
These three failures look identical from the outside and need different fixes. Coverage is about hours, capability is about skills, continuity is about what happens when a person leaves. Score each on your inventory, because coverage gaps favour co-managed IT support while capability gaps across every layer usually favour outsourcing.
Put both models to the same scope
Give every bidder the same document and ask each to quote both ways. Comparable quotations expose how differently providers define first-line, what they consider a project, and which tooling they charge for. Any provider who cannot price a co-managed IT support option is telling you something useful about their operating model.
Test the exit before you test the entry
Ask how a handover back to you would work, what documentation you would receive, how long tooling access continues and what the data extract looks like. A provider comfortable with the question is comfortable with the relationship. Weak exit terms hurt far more under full outsourcing, where everything you know sits on their systems.
Making the Model Work After You Sign
The model matters less than the operating rhythm around it. Plenty of co-managed arrangements fail because nobody defined the join, and plenty of outsourced ones fail because nobody attended the reviews.
Define escalation in both directions
Everyone documents how tickets escalate to the provider. Few document how they come back. Write the return path explicitly: which issues route to the internal team, at what point, and with what context attached. Co-managed IT support lives or dies on that handover, and it should be a rule rather than a habit.
Share the tooling and the source of truth
Two teams working from two systems will contradict each other in front of users within a month. Agree one ticketing platform, one asset and configuration record and one documentation library, with both sides writing into it. Shared visibility is what separates genuine co-managed IT support from a provider you occasionally email.
A review cadence that changes something
Monthly operational reviews should examine trends rather than ticket counts: recurring faults, unpatched estate, the boundary disputes of the last four weeks. Quarterly reviews should adjust the responsibility matrix. If nothing has moved in the split after a year, either the design was perfect or nobody is paying attention, and it is rarely the first.
Moving between the two models later
The choice is not permanent. Businesses commonly outsource fully, hire an internal lead as they grow, then shift to co-managed IT support with the same provider. Others go the other way after a retirement. Building the responsibility matrix as a document you expect to revise makes that transition an amendment rather than a re-tender.
Co-Managed IT Support FAQs
Short answers to the questions buyers ask most often once the shortlist is down to two.
Is co-managed IT support cheaper than outsourcing?
Usually not on the monthly invoice, because you keep salaries and add a provider. It frequently wins on three-year total cost where the internal team is already productive, and it almost always loses where the internal team is a single overloaded generalist.
Can a small business use co-managed IT support?
Yes, provided one named person internally owns technology as a real part of their job. Below roughly fifteen users that person rarely exists, and full outsourcing is the more honest arrangement. The test is ownership, not headcount.
Does co-managed IT support work with our existing provider?
Often, but check the contract. Many agreements assume full scope and price accordingly, so moving to a shared model means a re-scope rather than a discount. Providers built around fixed processes sometimes struggle to share a queue with your staff.
How long does switching between models take?
Plan for six to twelve weeks from signature to steady state: two for discovery and documentation, two for tooling and access, then a supervised handover period. Rushing the documentation stage is the single most reliable way to make the first month painful.
What happens to our internal team?
Under a shared model they generally move up the value chain, spending less time on password resets and patching and more on projects, applications and business relationships. Say so early and explicitly, because staff who suspect they are training their replacement will not cooperate with the handover.
