One looks cheap until something goes wrong. The other looks expensive until you understand what’s actually included. Here’s how to do the math for your situation.
Every small business owner I talk to has some version of the same question: "Do I really need to pay a monthly fee for IT, or can I just call someone when something breaks?"
It's a fair question. The break-fix model — pay for help only when you need it — is intuitive. It feels efficient. Why pay for a service every month when nothing's broken?
After 30+ years in this industry, I can tell you the honest answer: it depends. And the math is usually not what people expect when they run it properly. Let's work through it together.
Break-fix is simple: something breaks, you call someone, they fix it, they send you a bill. No contract, no monthly commitment. Sounds great on paper.
The hidden costs show up in a few ways most people don't count:
A competent IT technician charging break-fix rates in most markets runs $125–$200 per hour. Some are less; good ones in major metro areas charge more. That's for a single technician showing up (or remoting in) to fix one thing. If it takes two hours to diagnose and fix a problem that was building for months because nobody was watching, that's $250–$400 for that one incident. Have three or four of those a year and you're already at $750–$1,600 annually before you've touched anything truly serious.
The worst IT problems don't happen at 2 p.m. on a Tuesday. They happen Friday at 4:30 p.m. or Monday morning when your whole team shows up and nothing works. Most break-fix providers charge premium rates for evenings, weekends, and truly urgent calls — 1.5x to 2x the standard rate. So that $150/hour problem just became a $225–$300/hour problem.
This is the one that really stings. If your server goes down and it takes six hours for someone to diagnose and fix it, you're not just paying for six hours of IT labor. You're paying for six hours of your staff sitting idle, customers who couldn't reach you, orders that didn't get processed, and the stress that ripples through the rest of the week.
A conservative estimate for a 10-person business: $150/hour in lost productivity (figuring each person is worth roughly $15/hour in lost output, not their salary). Six hours down costs you $900 in lost productivity — before you pay the IT bill. For larger businesses or ones where downtime means lost sales directly, the number gets much worse.
This is the fundamental structural problem with break-fix. Nobody's monitoring your systems between calls. That server that's been running at 95% disk capacity for three months? Nobody notices until it fills up completely and everything stops. The hard drive that's been throwing warning signs in its event logs for six weeks? Nobody's reading those logs. Break-fix is reactive by definition — you're always responding to problems, never preventing them.
Managed IT — also called an MSP, or Managed Service Provider model — works on a flat monthly fee. In exchange, the provider takes on responsibility for keeping your systems healthy, not just fixing them when they fail.
When people see a quote for $800 or $1,500 a month, the first reaction is often "that seems like a lot." But let's look at what that fee usually covers, because most of these items have hard costs if you buy them separately:
Your systems are watched 24/7 by automated tools that flag problems before they become outages. Disk space filling up? Alert. A server service that stopped responding? Alert. A backup that didn't complete? Alert. You'd pay $50–$200/month just for monitoring software if you bought it on your own — and then someone still needs to be watching the alerts.
Windows updates, third-party software updates, security patches — all of this happens on a managed schedule, tested before it rolls out so it doesn't break things. On your own, this is either ignored (dangerous) or done manually and inconsistently (also dangerous). Good patch management prevents a significant percentage of security incidents.
A solid managed IT arrangement includes endpoint protection (real modern security, not just antivirus), DNS filtering to block malicious sites before they load, and often email security scanning. Buy those tools separately for a 10-person business and you're looking at $100–$300/month in licensing alone.
Someone's actually checking that your backups completed successfully. Not just that the software ran — that real data was captured and can actually be restored. This alone is worth significant money when you consider what a failed backup costs you in a crisis.
Your employees can call or email for support on day-to-day issues — printer problems, password resets, software questions — without each call generating a separate invoice. In a break-fix world, every support call costs you money. In a managed world, it's included.
When your internet goes down or your Microsoft 365 has a problem, someone else calls and sits on hold with the vendor. That might be you in a break-fix world. In a managed world, it's handled.
Let me run through a realistic year for a small business on each model. This isn't a worst-case scenario — it's the kind of year that happens to small businesses regularly.
That's $4,890–$6,890 for a pretty average year — and it assumes nothing truly catastrophic happened. A server failure requiring hardware replacement or a serious data breach would push this dramatically higher.
On the surface, $10,800 versus ~$2,890 looks like managed IT loses badly. But that's comparing the IT bill alone, not the full cost. When you add the productivity losses and factor in the cost of a bad year — one server failure, one ransomware hit, one extended outage — the break-fix total climbs past $10,000 fast.
And here's the thing about managed IT: the cost is predictable. You budget $900/month and that's your number. No surprise invoices. No emergency rate calls at 2x. No month where an unexpected problem wipes out your IT budget for the rest of the quarter.
I said at the start that the answer depends, and I meant it. There are situations where break-fix is genuinely the right answer, at least for now.
Very small businesses with minimal IT infrastructure. If you have three employees, everyone uses cloud-based software, no on-site servers, and your biggest IT risk is a laptop dying, break-fix is probably fine. Your downside is manageable and your IT needs are simple.
Businesses where IT is truly incidental to operations. A sole proprietor who works primarily with physical goods and uses only basic cloud tools has different needs than a professional services firm where employees are billing by the hour and can't work if systems are down.
As a short-term bridge. If you're in between providers, if you're evaluating your options, or if you're not ready for a managed relationship yet, break-fix isn't catastrophic. Just go in with eyes open about the risks.
If any of these describe you, managed IT is worth the math exercise:
If you're in this category and running break-fix, you're self-insuring against risks that could genuinely threaten your business. That might be a bet you're comfortable with — but it should be a conscious decision, not a default.
If you're evaluating managed IT proposals or trying to decide whether to make the switch, here are the questions that will tell you if the deal is actually good:
What's included in the monthly fee — specifically? Get a written list. Monitoring, patch management, helpdesk, security tools, backup monitoring — which of these are included, and which generate extra charges? "Unlimited support" that excludes server work or project work isn't really unlimited.
What are the response time commitments? There should be defined SLAs: critical issues get a response within X hours, non-critical within Y hours. If there's no SLA, there's no accountability.
What happens when something truly big goes wrong? Major project work — server replacement, a migration, recovering from a serious incident — often falls outside the flat fee. Understand what triggers an extra charge before you're in a crisis.
Do you own your own documentation, passwords, and licenses? This is crucial. A good managed provider builds you up; a bad one makes you dependent. We've written about this in the context of vendor lock-in — it applies here too.
What's your IT assessment process? A provider who wants to sign you up without understanding your environment isn't thinking about your business — they're thinking about a recurring revenue line. You want someone who asks questions first. See our IT Buyer's Guide for more on evaluating providers.
Break-fix isn't inherently bad. Managed IT isn't inherently expensive. The question is whether you're doing the full math — including downtime, productivity loss, and the cost of a bad year — or just comparing the monthly invoice to zero.
The businesses we see struggling most with IT costs are usually paying too much for break-fix, not too much for managed services. They're paying $4,000 in a quiet year and $15,000 in a bad year, and they think they're saving money because there's no monthly retainer. The number looks different in hindsight.
The businesses that made the switch to managed IT and felt burned were usually sold a managed contract that didn't actually include much. They paid a monthly fee and still got invoiced every time something real happened. That's not managed IT — that's a retainer with a lot of carve-outs. Read the contract carefully.
If you want to know where you actually stand, sit down and add up last year's IT costs honestly: every invoice, your best estimate of hours lost to outages, and what you're currently spending on security tools, backup software, and licenses. Then compare that number to what a well-structured managed contract would cost. The answer usually tells you what to do.