Outsourced IT vs in-house: models and what they cover
There are five common ways to run IT: an in-house IT manager or team, a fully outsourced managed service provider, co-managed IT that splits work between your staff and a provider, an embedded lead from a vendor who is on site several days a week, and a fractional or virtual CIO for strategy. They differ in who is present, who carries responsibility for outcomes, and how deep the available skills are. Most mid-size organizations combine two of them.

The question behind the question
“Should we outsource IT” is too broad to answer. The useful questions are narrower. Who answers when a user cannot work. Who is accountable when the backup fails. Who decides what gets replaced next year. Who is physically in the building. Different models give different answers, and a combination is normal.
What the IT function includes
Before comparing models, list the work. An IT function covers roughly these responsibilities, whether one person does them or twenty.
| Area | Examples |
|---|---|
| User support | Passwords, laptops, printers, onboarding and offboarding |
| Infrastructure | Servers, virtualization, storage, network, Wi-Fi, internet lines |
| Cloud and email | Microsoft 365 or Google Workspace, identity, file sharing |
| Security | Patching, endpoint protection, multi-factor authentication, access reviews, incident response |
| Continuity | Backup, restore tests, disaster recovery planning |
| Projects | Migrations, office moves, hardware replacement, new systems |
| Vendors and licenses | Contracts, renewals, escalations with suppliers |
| Planning | Budget, roadmap, risk register, reporting to management |
This table is also a fair summary of IT manager responsibilities. In a small company one person is expected to cover all eight rows. That expectation is the root of most IT problems: no single person is strong in all of them, and nobody covers them during a holiday.
The five models
In-house IT manager or team
An employee, or a team, who works only for you.
Strengths. Knows your people, your applications and your history. Present every day. Aligned with your priorities and available for the small requests that never become tickets.
Limits. One person is a single point of failure for knowledge and for availability. Skills are bounded by that person’s background, and specialist work such as a firewall migration or a storage replacement comes up too rarely to stay sharp on. Senior people are hard to recruit and hard to keep interested in a small environment.
Fits when. Daily support volume fills the role, or IT is close to the core of what the business does.
Managed service provider
An outside company that runs IT for a monthly fee under a written scope. Our own version is described on the managed IT services page.
Strengths. A team instead of one person, so there is cover for absences and a broader range of skills. Monitoring, patching and backup checks run as routine. The fee is predictable, and scope and response times are in a contract.
Limits. The provider is remote most of the time and serves other customers. It knows your infrastructure better than your business. Anything outside the written scope is a separate project, so the scope document matters more than the sales conversation.
Fits when. You want infrastructure and security run to a standard, and there is no need for a senior person in the building every day.
Co-managed IT
Your internal IT person or team stays, and a provider takes defined parts of the work.
Strengths. Keeps business knowledge in-house and adds depth where it is missing: infrastructure, security tooling, after-hours cover or projects. Gives a lone IT person a second opinion and holiday cover.
Limits. The boundary must be explicit. “They thought we were doing it” is the typical failure. It needs a responsibility matrix and a regular joint review.
Fits when. You have capable internal staff who are stretched, or who are strong with users and applications and thinner on infrastructure.
Embedded onsite IT lead
A senior person from a vendor who works at your premises on fixed days each week and runs the IT function: priorities, projects, suppliers and the work of any junior staff. The person is a vendor, not an employee. This is how our onsite IT support is structured.
Strengths. Presence and seniority without a full-time senior hire. The lead sits in management meetings, sees problems first-hand and directs existing staff. The vendor stands behind the role, so absence and specialist work are covered by colleagues.
Limits. Not there every day. On the off days, urgent matters go through remote cover or your junior staff. Costs more per day than an employee, for fewer days.
Fits when. The organization is complex enough to need senior direction on site, with servers, several sites or production systems, and the work does not fill five senior days a week.
Fractional or virtual CIO
A senior technology leader for a few days a month. The role is planning and governance: roadmap, budget, vendor choices, risk, and translating between management and technical staff. See virtual CIO services.
Strengths. Management gets an informed counterpart who is not selling a specific product. Decisions get made on purpose and written down.
Limits. Does not fix anything hands-on. Needs someone else, internal or external, to carry out the plan.
Fits when. Day-to-day IT runs acceptably and the gap is direction: nobody owns the three-year view, the budget is reactive, or a large decision is coming.
The models side by side
| In-house | Managed provider | Co-managed | Embedded onsite lead | Fractional CIO | |
|---|---|---|---|---|---|
| On site | Daily | Rarely or scheduled | Internal staff daily | Fixed days each week | Occasional |
| Daily user support | Yes | Usually, remote | Internal staff | Directs it, may not do it | No |
| Infrastructure depth | Depends on the person | Team | Provider | Lead plus vendor colleagues | Advises only |
| Strategy and budget | If senior enough | Sometimes, as an add-on | Shared | Yes | Yes, the core of the role |
| Cover for absence | No, unless a team | Yes | Partly | Through the vendor | Not applicable |
| Cost structure | Salary and employment costs | Monthly fee by scope | Salary plus fee | Monthly fee by days | Monthly fee by days |
| Main risk | Single point of failure | Scope gaps, distance | Unclear boundary | Gaps on off days | Plan without execution |
What drives the cost of each model
Published price lists for IT services are rarely comparable, because the scopes differ. Drivers are more useful than figures.
In-house. Salary is the visible part. Add employment costs, recruitment, training, tools and the cost of cover during leave. Also count the outside specialists an in-house generalist still needs for projects.
Managed services. Users and devices, servers and sites, coverage hours, response time commitments, included on-site visits, the security tooling in the bundle, and the condition of the environment at the start. An old, undocumented environment costs more to take on. Check whether projects, hardware and licenses are inside the fee. In most agreements they are not.
Co-managed. The provider’s share of the scope, and how much after-hours responsibility it takes.
Embedded lead. The number of days per week, the seniority of the person, and whether remote cover between visits is included.
Fractional CIO. Days per month and the deliverables: a roadmap, a budget, a quarterly review, vendor negotiations.
Goldenroz does not publish a retainer price, because the answer depends on the assessment. Managed IT is a monthly retainer quoted after an assessment, and one-off projects start at $25,000 at a fixed price per phase.
How to choose
Work through these in order.
- Count the support load. If users generate enough requests to occupy a person all day, you need someone present daily, employed or contracted.
- Look at what breaks. Repeated infrastructure incidents, failed backups and overdue replacements point to missing depth. That is a provider or co-managed gap.
- Check for direction. If nobody can show next year’s IT budget and the reasons behind it, the gap is leadership. That is an embedded lead or a fractional CIO.
- Test the single point of failure. Ask what happens if your IT person is unreachable for two weeks. If the answer is uncomfortable, add cover and documentation whatever else you decide.
- Decide presence. Some environments, such as production floors, clinics and multi-building sites, need hands on site. Others run well remotely.
Common combinations: an internal help desk person with a managed provider for infrastructure, an embedded lead directing junior internal staff, or a fully managed service with a fractional CIO reporting to management.
What to put in the agreement
Whichever outside model you choose, the contract should state:
- Systems and sites in scope, and what is explicitly out
- Coverage hours and response times by severity
- On-site days or visit frequency
- Routine tasks and their frequency. Our server maintenance checklist is a reasonable baseline for the infrastructure part
- Who owns accounts, credentials, licenses and documentation. It should be you
- Reporting: what you receive each month
- Exit terms: notice period, handover of documentation and passwords
A provider that will not hand over administrator credentials and documentation on request is a risk, however good the service is.
What to do next
Fill in the responsibility table at the top of this post with a name beside each row. Rows with no name, or with the same overloaded name eight times, show which model you need. If the gap is senior direction and presence, read about onsite IT support. If it is routine operations, start with managed IT services. Shai Goldenberg, our CTO, leads each account. This is a new retainer offering without a staffed operations center, and we say so before you sign. The first one-hour scoping call is free.