Co-managed IT vs fully outsourced IT: who does what
In co-managed IT, your in-house team keeps the users, the help desk and daily priorities, and an outside provider takes defined infrastructure work such as servers, network, backups and patching, under one written responsibility matrix. In fully outsourced IT, the provider runs and repairs everything in scope and you keep only the decisions: budget, priorities and risk. Co-managed needs internal IT staff to work, and fully outsourced fits when you have none or do not want to hire.

Two models, one difference
Both models involve an outside provider and a monthly agreement. The difference is the line between what your people do and what the provider does.
In fully outsourced IT, the line sits at the edge of operations. The provider runs and repairs the servers, network, accounts and backups in scope. Your company decides, approves and pays.
In co-managed IT, the line runs through the middle of the IT function. Your own team does part of the daily work, and the provider does the rest.
This post compares these two at task level. For the wider picture, including an in-house team, an embedded onsite lead and a fractional CIO, see outsourced IT vs in-house.
Who does what, task by task
The split below is how these models are commonly arranged and how our own two services are scoped. The exact rows are set in each agreement.
| Task | Co-managed: your team | Co-managed: provider | Fully outsourced: your company | Fully outsourced: provider |
|---|---|---|---|---|
| Daily user requests and help desk | Does it | Takes escalations | Reports issues | By agreement, or a separate help desk service |
| Joiners, movers and leavers | Does it, or requests it | Infrastructure-side changes | Approves and requests | Does it |
| Laptops, printers and desk-side support | Does it | Not in scope | Local arrangement | By agreement |
| Servers and virtualization | Follows changes | Administers | Approves changes | Administers |
| Firewalls, switches, VPN and Wi-Fi | First-level checks | Administers | Approves changes | Administers |
| Patching and maintenance windows | Agrees the windows | Does it on assigned systems | Agrees the windows | Does it |
| Backup checks and restore tests | Receives results | Does it | Receives results | Does it |
| Monitoring and alerts | Handles user-facing alerts | Handles infrastructure alerts | Informed of incidents | Handles alerts |
| Hard incidents and outages | Opens the escalation | Owns the infrastructure incident | Makes business decisions | Owns the incident |
| Projects: migrations, new sites, refreshes | Sets priorities, takes part | Delivers, as a separate project | Approves and funds | Delivers, as a separate project |
| Vendor coordination | Business applications | Infrastructure vendors | Signs contracts | Coordinates |
| Documentation and credentials | Owns the vault, both write | Writes to your systems | Owns the vault | Writes to your systems |
| Budget and roadmap | IT manager leads | Advises | Leadership decides | Advises |
Two things stand out. In both models, changes to the environment are projects, priced apart from the monthly work. And in both models, the vault and the documentation belong to you.
What stays with you in every model
Some things cannot be handed over, whatever the contract says.
- Decisions about risk. How long an outage the business can tolerate, and what it will pay to shorten it.
- Approvals. Who may have access to what, and who signs off a change to a critical system.
- Ownership of accounts. Domain registrations, cloud tenants, licence agreements and administrator credentials in your company’s name.
- A named contact. Someone inside the company who the provider reports to and who can say yes or no.
A company that outsources everything and names no internal contact has not removed the IT job. It has left it empty.
How co-managed IT works day to day
Co-managed IT stands on one document: the responsibility matrix. It lists every system and task with exactly one owner, your team or the provider. It is part of the agreement and is reviewed when the environment changes.
The typical failure of this model is the gap between the columns, where each side assumed the other was doing something. A matrix with one owner per row closes that gap.
A normal week looks like this. Your help desk handles tickets. One of them turns out to be a storage problem on a virtual host. Your administrator opens an escalation, and an engineer who already knows the environment takes it. Meanwhile the provider runs the patch window agreed for that month and sends the restore test result to your IT manager. A monthly review covers what was done, what is at risk and what should move between columns.
This is different from staff augmentation. A contractor supplied by the hour works under your direction, and the responsibility stays with you. In a co-managed arrangement the provider takes responsibility for a defined scope and reports on it.
Our co-managed IT services follow this shape. Your team keeps the help desk, the users and daily priorities. Shai Goldenberg, our CTO, with senior infrastructure engineers he works with, takes servers, network, backups, patching and the hard incidents.
How fully outsourced IT works day to day
With no internal IT team, the provider is the IT function for the systems in scope. It administers servers and network, checks backups and tests restores, patches on a schedule, manages accounts and access, coordinates vendors and owns incidents. Your contact inside the company approves changes and receives a regular report.
The typical failures here are different. One is a provider that only reacts, fixing what breaks and never reporting on risk. Another is a provider that holds your administrator accounts and documentation, which makes leaving hard. Both are avoided in the agreement, not afterward.
Our outsourced IT support covers server and network administration, monitoring and patching, backups with restore tests, user accounts and access, and incident response for the systems named in the agreement. It is aimed at mid-size and large organizations. It is not a fit for a small office that wants break-fix help for a handful of computers, and we do not run a staffed operations center watching screens overnight. Coverage hours and response times are written into each agreement.
Which model fits
| Your situation | Likely fit |
|---|---|
| A capable IT manager or small team, stretched thin, with server work losing to tickets | Co-managed |
| One administrator who holds everything, with no cover for holidays or illness | Co-managed |
| Strong user support in-house, thin on infrastructure and backups | Co-managed |
| No internal IT staff, and no plan to hire | Fully outsourced |
| The IT person resigned and the company runs on a part-time technician | Fully outsourced, or co-managed after a hire |
| You cannot list what you run or who has administrator access | An assessment first, then decide |
The last row is more common than it sounds. If nobody can list the servers, the backups and the accounts, any monthly price is a guess. A fixed-scope assessment produces the inventory, a ranked list of risks and a costed plan, and the model follows from that. This is the first phase of our IT consulting services, and the deliverables are yours to use with any provider.
What to put in the agreement
- The systems and tasks in scope, named, with one owner per row
- Coverage hours and response times, by severity
- The escalation path: who opens it, who takes it, and how it is tracked
- How backups are checked, how often restores are tested and who sees the results
- Maintenance windows and how they are agreed
- What counts as a project and how projects are priced
- Where documentation and credentials live, and who can read them
- Named accounts with multi-factor authentication for every person on both sides
- The monthly report: what it contains and who receives it
- Exit terms: notice period, handover and removal of access
Most of these items are also the working parts of a service desk process, described in what is ITSM.
Moving between the models
The two models are stages as often as they are alternatives.
From fully outsourced to co-managed. The company grows and hires an IT manager. User support and daily priorities move to the new hire, and the provider keeps the infrastructure. The matrix is rewritten, and nothing else has to change.
From co-managed to fully outsourced. The only administrator leaves. The provider’s column widens to cover the gap, for a period or for good, because it already knows the environment.
Both moves are simple when documentation, diagrams and credentials sit in your own systems, and when everyone works under a named account. They are painful when knowledge sits in one person’s head or in a provider’s private tools. This is the practical reason for the ownership rules above.
What we offer, and what we do not claim
Both services at Goldenroz are monthly retainers quoted after an assessment. We do not publish a monthly figure, because the price depends on which systems are in scope and on coverage hours. One-off projects start at $25,000 at a fixed price per phase.
These are new retainer offerings, and we have no published client results for them. We hold no vendor partner status or certifications, and we do not resell hardware or licences. Shai ran IT for four years at an industrial company with about 400 users, where he managed the help desk and did the server, network and Microsoft 365 projects himself, so he has worked on both sides of the line this post describes.
What to do next
Copy the task table above and write a name beside each row for your company today. Rows with no name are your gaps. If most of the names are your own staff and the gaps are in infrastructure, read about co-managed IT services. If there are few internal names at all, start with outsourced IT support. Both begin with an assessment, and the first one-hour scoping call is free.