Managed IT vs break-fix: which actually costs less?

This is one of the most common questions we hear from growing businesses. It is also one of the most frequently answered badly — usually by an IT provider with an obvious commercial interest in one of the options.

So let us be upfront: we sell managed support. We also do project work and break-fix for clients who prefer it. The honest answer is that managed support is usually cheaper over time for businesses that depend on IT daily, but not always, and not for every stage of a company's life.

Here is how to think about it properly.

What the two models actually mean

Break-fix is exactly what it sounds like. Something breaks, you call someone, they fix it, you pay for the time and parts. There is no ongoing relationship, no monitoring and no prevention. You are buying a repair, not a service.

Managed IT is a fixed monthly arrangement. In exchange, the provider takes responsibility for keeping agreed systems running: monitoring, patching, backups, endpoint protection, helpdesk and regular review. You are buying continuity, not a repair.

The confusion comes from comparing the two as if they are the same purchase at different prices. They are not. One is a transaction; the other is insurance plus maintenance plus a service desk.

The invoice is not the cost

A break-fix invoice for a server repair might be smaller than a year of managed support. But it captures only the visible cost. The rest is spread across the business in ways that never appear on an IT invoice:

• Downtime. If email is down for half a day, what does that cost in lost sales, delayed invoicing and idle staff?
• Staff time. Someone internal becomes the first line of support — usually a capable person who is being paid to do a different job.
• Repeat visits. Break-fix rewards fixing the symptom, not the cause. The same problem returns, and so does the invoice.
• Recovery costs. Restoring data after ransomware, rebuilding a failed server or recreating lost work is dramatically more expensive than preventing it.
• Opportunity cost. Projects that would improve the business get postponed because IT is always in firefighting mode.

Managed support has its own hidden costs — you pay whether or not you use it. That is the trade: predictable cost and lower risk in exchange for paying during quiet months.

An illustrative comparison

Consider a 30-person professional services firm with one server, a shared file store, Microsoft 365 and a mix of laptops. Nothing is monitored. Backups run nightly but have never been tested.

Break-fix path: a drive fails in the server. The firm calls a technician, who confirms the RAID did not rebuild properly and the last usable backup is older than expected. Staff cannot access client files for a day and a half. There is an emergency call-out charge, replacement drives, after-hours labour to restore, and several people working late to reconstruct the missing week. Nobody can bill that time.

Managed path: the same drive failure is detected by monitoring before it becomes an outage. A replacement is scheduled, the array rebuilds, and the backup is verified as part of a quarterly restore test. There is a hardware cost and some coordination, but the business day is largely unaffected.

The break-fix invoice might still be lower in isolation. Add the lost billable hours, the recovery labour and the client goodwill, and the picture usually reverses. Now imagine the same comparison with ransomware instead of a failed drive.

When break-fix genuinely makes sense

We are not going to pretend managed support is always right. Break-fix can be the sensible choice when:

• The business is very small — a handful of users with simple, low-dependency needs.
• IT is not operationally critical. If email goes down for a day and nobody outside notices, the economics are different.
• You have capable internal IT and only need specialist help occasionally.
• You are in a short-term or transitional situation — a temporary office, a wind-down, or a system being replaced soon.
• You need a one-off project rather than ongoing cover. A network refresh or migration is a project regardless of your support model.

The problem is that many businesses start here and never revisit the decision, even after they have grown into a shape where the model no longer fits.

When managed support earns its keep

Managed support tends to make clear financial sense when several of these are true:

• Staff depend on email, file access and line-of-business software every working hour.
• You handle client data, payments or personal information.
• You have compliance, insurance or customer-security requirements to evidence.
• Nobody internally owns IT, or the person who does is stretched across other responsibilities.
• You are growing and want standards in place before headcount makes ad-hoc support unmanageable.
• You have suffered a significant incident and want to reduce the chance of a repeat.

In these situations, the value is not only in the tickets answered. It is in the incidents that never happen, the licence that gets renewed before it lapses, and the fact that someone is thinking about the environment between crises.

The hybrid most SMBs actually use

In reality, the choice is rarely binary. A sensible arrangement often looks like this:

1. Core managed cover for the things that must not fail: backups, patching, endpoint protection, email security, monitoring and helpdesk.
2. Project work quoted separately for migrations, upgrades, office moves and security improvements.
3. Hardware and licensing procured as needed, with renewals tracked.

This gives predictable running costs without pretending that every piece of work fits inside a monthly fee. It also keeps the scope honest: you can see what is covered and what is a separate decision.

Questions to ask either provider

Whether you choose managed or break-fix, these questions will tell you a lot about what you are buying:

• What exactly is included, and what is billed separately?
• What are the response and resolution targets, and what happens if they are missed?
• Will you document our environment, and do we own that documentation?
• How do you handle after-hours incidents?
• Can you show evidence of backup restore testing?
• What is the notice period, and what happens at handover?
• Who will actually be working on our account — the person in the sales meeting, or someone else?

A provider that cannot answer these clearly is a risk in either model.

The bottom line

Break-fix is cheaper until something significant goes wrong. Managed support costs more in the quiet months and less when it matters. For a business that runs on email, files and client data, the second is usually the better bet — not because managed support is inherently superior, but because the downside of being unprepared is disproportionately large.

The worst outcome is not choosing either model. It is drifting along with no model at all: no monitoring, no tested backups, no clear owner, and an informal arrangement that only gets attention when something breaks.