
IT outsourcing: five models, and what each one leaves with you
IT outsourcing is not a yes-or-no question but a choice between forms: hand over everything, work alongside your own IT person, give away one area, bring someone in, or have a project done. Each model moves different work out of the building, and the difference really shows in the contract and at the exit.
There are five common forms of IT outsourcing: fully outsourced, co-managed alongside your own IT staff, by area, staff augmentation and project-based. They are not mutually exclusive.
Governance, architecture and ownership of licences, accounts and documentation stay with the organisation in every model. Outsourcing moves work, not responsibility.
The model sets the type of contract: an outcome agreement with service levels, an effort agreement, or an assignment with a handover. The exit belongs in all five.
The five IT outsourcing models
When people say “IT outsourcing”, they usually mean one of these five. On a quote they look alike; in practice they differ mainly in who is responsible when something stops working on a Monday morning.
- Fully outsourced. One provider runs the whole environment: devices, servers or cloud, network and service desk. Nobody inside works on IT any more, but someone still directs the provider.
- Co-managed. Your own IT person or team stays, and a provider takes over an agreed part: the tickets, monitoring outside office hours, patching, or capacity for projects. Both work in the same environment.
- By area. You outsource one domain and keep the rest: only the service desk, only security monitoring, only the network. There are often several providers side by side.
- Staff augmentation. An outside specialist works under your direction, in your team, for an agreed period. You buy capacity and knowledge, not an outcome.
- Project-based. A defined piece of work with a start and an end: a migration, a new site, a rollout. Afterwards the running of it goes back to whoever did it before, or to one of the four above.
They are not mutually exclusive. A common combination is co-managed for day-to-day work, with a project alongside for the migration that has been on the list for two years.
What stays with you in every model
Outsourcing moves work, not responsibility. Three things belong with the organisation in every model, even when nobody inside works on IT any more:
- Governance. Someone who sets priorities, reads the reporting and pushes back on the provider. That need not be an IT person, but it must be someone with time and authority. Without that role, the provider steers itself.
- Architecture and standards. Which cloud, which security baseline, which software may run. A provider may propose; the decision is yours, or you end up with the environment that is easiest for them to run.
- Supplier choice and ownership. Licences, domain names, admin accounts and documentation are held in the organisation’s name. That is the difference between a provider you can replace and one you cannot.
If your organisation falls under NIS2, a fourth applies: the management body remains accountable for the cyber security measures, even when someone else carries them out. Outsourcing changes who does the work, not who answers for it.
Pros and cons of each model
- Fully outsourced. For: one point of contact, one contract, and no dependence on a single colleague who falls ill or leaves. Against: the knowledge of your environment sits outside, and without internal governance you notice late when standards slip. Suits an organisation without its own IT staff and no wish to have them.
- Co-managed. For: your own IT person keeps the local knowledge and short lines, and no longer has to know everything or answer the phone at night. Against: two parties in one environment need tight agreements, or the work nobody enjoys is exactly what gets left. Suits an organisation with one or a few IT people who are stretched.
- By area. For: you start small, pick the specialist per domain, and learn how outsourcing works for you. Against: the seams between providers become your problem; a fault that falls between network and devices has no owner. Suits a clearly bounded bottleneck.
- Staff augmentation. For: fast knowledge or capacity without a permanent hire, working your way. Against: you pay for effort rather than outcome, and the knowledge leaves with the person unless you arrange the handover. Suits a temporary gap or a role you are not ready to fill permanently.
- Project-based. For: fixed scope, an end date and a party held to the result. Against: after delivery something exists that someone else has to run, and that is rarely part of the project. Suits a one-off change.
Where co-managed and partial outsourcing break down
Almost never on the technology. They break down on work each party assumed the other was doing. Four things to settle in advance:
- Who changes what. May the provider make changes without your own IT person, and the other way round? Two parties with admin rights and no change agreement is the fastest route to an outage nobody knew about.
- Who takes the ticket. One entry point for users, with an agreement on passing tickets on. Two phone numbers means users call whoever they like best, and half the tickets are never logged.
- Who keeps the documentation. The network diagram, the list of admin accounts, the agreements with third parties. One owner per document, and that is not automatically whoever wrote it.
- Who calls the third party. When the internet line fails, or software from another vendor: who escalates, and on whose contract?
Put this in a simple split per task (who does it, who decides, who is informed) and review it after a quarter. The first version is never quite right, which is no reason to skip it.
What the model means for the contract and the exit
The model decides what kind of agreement you make, and so what you can enforce.
- Full and by area: an outcome agreement. Response and resolution times, reporting, and what falls outside scope. The exit belongs here too: a handover period, up-to-date documentation, return of admin accounts, and the logging you take with you.
- Co-managed: the same, plus the split of tasks as a schedule. An SLA without that split measures the provider on work that was never clearly theirs.
- Staff augmentation: an effort agreement. You pay for time; you steer the quality yourself, because the specialist works under your direction. Agree how knowledge is handed over when the assignment ends.
- Project-based: an assignment with a handover. Scope, deliverables and acceptance. The trap is that “delivered” means something different from “maintainable”; make the project end with documentation and a handover to whoever runs it.
If the provider processes personal data on your behalf, and a managed service provider almost always does, UK GDPR and the EU GDPR require a written processor agreement. That applies to all five models.
In every model the exit is the part least negotiated and most expensive when it is missing. A provider who will not put leaving in writing is counting on leaving being hard.
How to choose: four questions
- Is there someone inside who can govern, with time for it? If not, set up that role first. Full outsourcing without governance looks simplest and is the hardest to correct.
- Do you want to keep your own IT person? If the reason is local knowledge and short lines, co-managed is the form that protects that role rather than hollowing it out.
- Is the bottleneck one area or the whole environment? If it is mainly tickets getting stuck, or only the security monitoring nobody does, start by area. You can extend later; taking work back is harder.
- Is the need temporary or permanent? A migration or a temporary gap calls for a project or staff augmentation. A permanent task put into either becomes a contract that keeps being extended with no service level on it.
If you are torn between two, choose the one that is easiest to reverse. Going from one area to full outsourcing is a conversation; going from full outsourcing back to running it yourself is a recruitment drive.
Where our work stops
We provide managed IT in full or by area, service desk, cyber security, IT staffing and projects, so in these models we are one of the bidders. That colours this article: read it as the reasoning of a party at the table.
What we do not do: we are not an independent procurement adviser. We do not assess offers from other providers and we do not choose the model on your behalf. What we can do is say, per model, what we would take over, what should stay with you, and where we are not the right party.
And we are not lawyers. We say which arrangements on service levels, handover and exit belong in a contract; the legal review of liability, termination and the processor agreement is for your own lawyer.
Questions we get about this
The five that come back most often.
What is IT outsourcing?
IT outsourcing means placing IT work with an external provider, in full or in part. There are five common forms: fully outsourced, co-managed alongside your own IT staff, by area, staff augmentation and project-based. They differ mainly in who is responsible for the outcome and what stays with the organisation.
What is co-managed IT?
With co-managed IT your own IT person or team stays, and an external provider takes over an agreed part of the work, such as tickets, out-of-hours monitoring or patching. Both work in the same environment. It only works with a written split of tasks: who changes what, who takes tickets and who keeps the documentation.
What are the disadvantages of IT outsourcing?
The knowledge of your environment moves outside, and without someone governing internally you notice late when standards slip. With outsourcing by area, the seams between providers become yours. And if the exit is not in the contract, leaving becomes slow and expensive.
Can you start by outsourcing just one area?
Yes, and it is often sensible when the bottleneck is clearly bounded, such as the service desk or security monitoring. You learn how outsourcing works for you without moving everything at once. Do agree who owns faults that fall between two areas.
Can you advise independently on which model fits, or draft the contract?
No. We deliver in these models ourselves, so we are not an independent procurement adviser and we do not assess other providers’ offers. Nor are we lawyers: we say which service level and exit arrangements belong in the contract, and your own lawyer does the legal review. What we do is say, per model, what we would take over and what we would not.
Further reading
What comes after choosing a model.
Shall we look at what we would take over?
Tell us what happens in house today and where it gets stuck. We will say which part we would take over, what should stay with you, and where we are not the right party.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.