Managed IT Services vs In-House IT vs Break-Fix: How to Choose
There are three common ways to run IT for a small or mid-sized business. Managed IT services charge a regular fee for ongoing support and maintenance. An in-house team employs IT staff directly. Break-fix support pays someone by the hour when something goes wrong. Many businesses end up with a mix: an internal person for day-to-day needs and a managed provider for specialist and out-of-hours work.
The right choice depends on how many people you support, how complex your systems are, and how much downtime you can tolerate. This guide compares the three models so you can match one to your situation.
Key takeaways
- Break-fix is cheapest when little goes wrong, but it has no preventive maintenance and costs are unpredictable.
- Managed IT services give predictable costs and broad expertise, and they include the maintenance that prevents outages.
- In-house IT gives the most control and on-site presence, but one or two people rarely cover security, networking, backups, and support equally well.
- Co-managed IT, an internal person plus a managed provider, often suits growing businesses best.
- Whatever you choose, check that backups, patching, and monitoring have a named owner.
The three models at a glance
| Break-fix | Managed IT services | In-house IT | |
|---|---|---|---|
| How you pay | Per hour or per incident | Fixed monthly fee, often per user or device | Salaries, training, and tools |
| Cost predictability | Low | High | High, but with hiring costs |
| Preventive maintenance | Rarely included | Included | Depends on staff capacity |
| Range of skills | Varies by technician | A team with different specialisms | Limited to the people you hire |
| Out-of-hours cover | Usually extra or unavailable | Often included for monitoring | Requires on-call arrangements |
| On-site presence | When booked | Scheduled or when needed | Every day |
| Knowledge of your business | Low | Builds over time | Highest |
Break-fix support
With break-fix, you call a technician when something stops working and pay for the time spent fixing it.
- Works well when
- you have a handful of staff, no servers, cloud-based tools, and you can tolerate a day of disruption.
- The provider earns more when things break, so there's no incentive to prevent problems
- Nobody owns backups, patching, or security between incidents
- Costs spike at the worst moments, such as after a ransomware attack
- Each technician may need time to learn your setup again
Managed IT services
A managed service provider (MSP) takes responsibility for an agreed list of services for a regular fee. That list usually includes monitoring, patching, backups, security tools, and a help desk.
- Works well when
- you rely on IT to operate, have 10 or more staff or a few servers, and want predictable costs without hiring a full team.
- Preventive work is part of the contract, so the provider benefits when nothing breaks
- Access to specialists in security, networking, Linux, Windows Server, and cloud
- Monitoring and alerting can run around the clock
- Documentation and processes stay with the contract, not with one person
- Less day-to-day presence than an employee, unless on-site days are included
- Quality varies widely between providers, so the contract and SLA matter
- Projects outside the agreed scope cost extra
In-house IT
An in-house team means hiring IT staff as employees.
- Works well when
- you have enough users and systems to keep several specialists busy, strict requirements for on-site presence, or bespoke systems that need deep internal knowledge.
- Full control over priorities
- Immediate on-site help
- Deep knowledge of your business and its people
- One person can't be an expert in everything, and can't be available all the time
- Holidays, sickness, and resignations leave gaps
- Recruiting, training, and tools add cost on top of salaries
- Knowledge often lives in one person's head rather than in documentation
Co-managed IT: the hybrid option
Co-managed IT pairs an internal IT person or team with a managed provider. A common split looks like this:
- Internal staff: user support, on-site needs, business systems, and supplier relationships
- Managed provider: monitoring, patching, backups, security tooling, and specialist projects
- Shared: documentation, change planning, and incident response
How to choose
Answer these questions honestly:
- How long can you operate without IT? If the answer is hours rather than days, break-fix is too risky.
- Who checks backups and installs security updates today? If nobody owns it, you need a model that assigns it.
- How many specialisms do you need? Count security, networking, servers, cloud, and user support. A single hire rarely covers all of them.
- Do you need someone on site every day? If so, in-house or co-managed makes sense.
- How predictable must costs be? Managed and in-house models are easier to budget than break-fix.
What to check in a managed IT contract
If you choose a managed or co-managed model, compare providers on these points:
- Which systems and services are included, and which are billed as projects
- Response and resolution times by priority, and the hours they apply to
- How often backups are restore-tested, and whether you get the results
- Patch timelines, especially for critical updates. Cyber Essentials, for example, fails any assessment where high-risk or critical updates aren't installed within 14 days (IASME)
- Who owns the documentation and admin credentials if you leave
- What reporting you receive each month
Frequently asked questions
Is managed IT cheaper than hiring an IT person?
Often, for smaller businesses, because a managed fee buys a team's range of skills for less than one full salary plus tools and training. As you grow, the comparison shifts. Get quotes for your actual user and device count rather than relying on averages.
Can I switch from break-fix to managed IT gradually?
Yes. Many businesses start with monitoring, backups, and patching under a managed agreement, then add help desk support once they see the results.
What happens to my data and passwords if I leave an MSP?
A good contract states that documentation, admin credentials, and configuration belong to you and are handed over at the end of the agreement. Check this before signing.
Next step
If you're weighing up these options, an infrastructure review maps your current setup and shows which model, or mix, fits your size and risk. You can also start with our list of the IT services a small business actually needs.