Guide IT Management

In-house IT or an MSP: costs, trade-offs and how to choose

Choosing between an in-house IT team and a managed service provider (MSP) takes more than comparing salaries with monthly fees. The decision depends on how complex your systems are, how much on-site support you need, the hours you need covered, the risks involved and the responsibilities you want to keep in-house. This guide compares the in-house, outsourced and hybrid models, including costs, skills, service levels and governance.

29 May 2026
Updated 18 November 2026
7 min read
Key takeaways
  • An MSP is not automatically cheaper than in-house IT. Compare the same scope: the same users, hours, services, tools and projects
  • Build the in-house cost from its components (salary, employer National Insurance, pension, benefits, equipment, training, tools and cover) rather than a universal multiplier
  • Relying on one IT person creates a dependency risk during holidays, absence and departure; documentation, shared access and backup support reduce it
  • Headcount helps estimate demand and cost, but the right model depends on complexity, system criticality, on-site needs, regulation and management capacity
  • When choosing an MSP, contracted scope, demonstrated competence, security controls, ownership of your accounts and exit terms matter more than the monthly fee

The real cost of in-house IT

Salary is only part of the cost of an internal IT role. To compare options fairly, add up each component for the role you actually need.

  • Gross salary. Base pay for the role, level and region.
  • Employer National Insurance. 15% on earnings above the secondary threshold of £5,000 a year in 2026/27, before any Employment Allowance your business can claim.
  • Workplace pension. Auto-enrolment requires an employer contribution of at least 3% of qualifying earnings; many employers pay more.
  • Holiday and absence. Statutory paid holiday (5.6 weeks for a full-time employee) is already inside the salary. The extra cost is the cover you need while the person is away.
  • Benefits, equipment and training. Health cover or other benefits, a laptop and phone, courses and certifications.
  • Recruitment. Agency fees or internal time, usually a one-off cost each time the role is filled.
  • Tools. Ticketing, remote monitoring and management (RMM), endpoint protection and backup, which an internal engineer still needs.

Count each item once. Applying a multiplier on top of a component list double counts, and holiday pay should not be added again when it is already in the salary. Ask your payroll provider or accountant to validate the figures for your situation.

Beyond cost, a single IT person creates three structural issues.

Single-person dependency. When one person holds most of the knowledge and access, holidays, sickness and departure all create a gap. How serious that gap is depends on how well systems are documented, whether administrator access is held securely by the business, whether someone else has the skills to step in, and whether support contracts are in place with key suppliers. Plan cover and knowledge transfer before you need them.

Breadth gaps. A capable generalist can handle support requests, basic network issues and Microsoft 365 administration. One person is unlikely to have deep expertise in security monitoring, cloud architecture, compliance and infrastructure all at once. The need for specialist knowledge grows as your technology becomes more complex.

Coverage hours. One employee covers normal working hours, minus holidays and training. If you need out-of-hours monitoring or response, it has to be arranged separately, through an on-call arrangement or an external provider.

No universal multiplier

Rules of thumb such as "salary times 1.35" hide too much. Employer charges, pension schemes, benefits and cover arrangements differ between employers. Build the figure from the components above and write down each assumption so it can be checked.

What an MSP proposal should include, three cost scenarios with the same scope and how to evaluate a provider before you sign are covered in How to cost and choose an MSP.

Five things to compare directly

1
Cost
Compare total annual cost for the same scope. In-house: pay, employer charges, benefits, equipment, training, tools and cover. MSP: the fee plus extra visits, projects, additional hours and services outside the contract.
2
Expertise
In-house: one person's skills, supplemented by training or external specialists. MSP: access to a wider team, but check which competences are actually in the contract. Operational support experience does not show capability for security programmes, architecture, audits or compliance.
3
Service levels
Both can work to documented targets for response, restoration, resolution and communication. An MSP can meet a response target and still restore service slowly, so check what is measured. Targets such as P1 within 1 hour, P2 within 4 hours and P3 next business day are examples, not a market standard.
4
Business knowledge
In-house: deep understanding of systems, history and users, built over time. MSP: builds context over months; good documentation shortens the transition.
5
Accountability
In-house: targets are enforced through management, and performance management follows internal processes. MSP: the contract defines service levels, remedies such as service credits, and how to escalate, change or end the service.

Four models at a glance

1
Internal IT
Strongest fit: complex or critical systems, frequent on-site needs, and enough work for a team whose members can cover each other. Main limitation: highest fixed cost; a small team depends on a few people and still needs external specialists.
2
MSP
Strongest fit: standardised, largely cloud-based environments, distributed staff and a need for predictable support coverage. Main limitation: support is limited to the contract, on-site presence and business context can be thin, and someone in the business still has to manage the provider.
3
Hybrid: internal + MSP
Strongest fit: businesses that need someone on site with business knowledge, plus wider coverage and tooling. Main limitation: higher total cost, and roles need clear boundaries to avoid gaps or duplication.
4
Virtual IT manager (vCIO) + MSP
Strongest fit: businesses that need IT leadership, planning and supplier oversight but not a full-time IT manager. Main limitation: part-time availability, and day-to-day support quality still depends on the MSP.

Headcount is not a decision boundary

Headcount helps estimate support demand and cost, but it does not decide the model. Technology complexity, how critical your systems are, support needs, the need for physical presence, regulation and management capacity matter more. Two illustrative scenarios with the same headcount:

  • A 60-person consultancy working remotely on Microsoft 365 and SaaS applications, with no specialist equipment, can often be well served by an MSP with a clear contract and one person internally who owns the relationship.
  • A 60-person medtech manufacturer with laboratory systems, production equipment and regulatory obligations may need someone on site, controlled change processes and specialist knowledge, which points towards internal IT or a hybrid model.

When in-house makes sense

In-house IT tends to fit when systems are complex, varied or spread across sites, when downtime is costly, and when there is enough work to sustain a team whose members can cover each other. A team of several people also reduces single-person dependency.

Regulated environments can push towards in-house competence. Financial services firms, healthcare providers and operators of critical infrastructure may need direct internal control over certain activities and decisions. Check what your regulator and your own risk assessment require rather than assuming either model is ruled out.

Proprietary or legacy systems that depend on deep institutional knowledge, and sites that need daily physical presence, such as production environments, also favour in-house staff.

When an MSP makes sense

An MSP often fits when the environment is largely standard: Microsoft 365, laptops, cloud storage and common business applications. Breadth of coverage and predictable support then matter more than deep in-house knowledge of bespoke systems.

Distributed and remote teams are strong candidates. When staff work from several locations or from home, the need for on-site support can fall and remote management becomes the main support channel.

Businesses that have experienced coverage gaps, a growing queue of open support requests or dependency on one or two people can benefit from the structured coverage an MSP provides. The same applies when predictable costs matter for budgeting, or when out-of-hours monitoring is needed but cannot be staffed economically. Our IT service desk guide covers how to organise support without a full team.

The hybrid model

The hybrid model places an IT manager or IT lead in-house while an MSP handles day-to-day support. The internal person owns the supplier relationship, procurement and planning, manages the MSP contract and keeps institutional knowledge. The MSP handles support requests, monitoring, patching and first-line response.

The main risk is unclear role boundaries. Define who does what in writing: security policy sits with the internal lead; alert triage and response sit with the MSP within the agreed scope; procurement decisions go to the internal lead with MSP input; starters and leavers follow a shared, documented checklist.

A variant is a virtual IT manager (vCIO) combined with an MSP. A part-time external IT lead sets priorities, manages the roadmap and holds the MSP to its contract, without the cost of a full-time hire. Cyvra provides this kind of independent IT leadership and does not sell MSP services. Our IT strategy roadmap shows how that planning work fits together.

Frequently asked questions

Is an MSP always cheaper than in-house IT?

No. It depends on equivalent scope: the users, hours, services, tools and projects you need, and what each option includes and excludes. An MSP fee can look lower until extra visits, projects and out-of-scope work are added. An internal hire can look cheaper until tools, cover and training are counted. Compare the total annual cost of each option for the same scope; the IT budget guide helps set that baseline.

When is in-house IT worth keeping?

In-house IT is worth keeping when systems are complex or critical, when daily on-site presence is needed, when deep knowledge of specific or legacy systems matters, or when you want direct internal control over certain activities. Many businesses keep at least one internal role and add an MSP for wider coverage and tooling.

Can you have a virtual IT manager and keep an MSP?

Yes. A virtual IT manager (vCIO) provides planning, budgeting and supplier oversight on a part-time basis, while the MSP continues to deliver day-to-day support. Agree in writing which decisions sit with the vCIO and which with the MSP, and review service performance against the contract regularly. The IT strategy roadmap shows the planning side of that role.

Ryland Deakin
About the author
Lead Consultant, Cyvra · CISM · CompTIA Security+ · MCP

Ryland has delivered cybersecurity, compliance, and IT management programmes for regulated organisations across the UK and the Netherlands for over 20 years. View full profile

Talk to Cyvra

Find out what IT model fits your business

We are an independent consultancy and do not sell support contracts. We assess your current setup and help UK businesses decide what mix of in-house and managed support makes sense.

Disclaimer: This article is for general informational purposes only and does not constitute legal, regulatory, or professional advice. Cyvra makes no warranty as to the accuracy or completeness of this content, which may not reflect the most current regulatory developments. Readers should seek independent legal and regulatory advice appropriate to their specific circumstances. Cyvra accepts no liability for any loss arising from reliance on this content.