Break/fix vs managed IT: which one is really cheaper?

An honest comparison of break/fix and managed IT for small business: the visible bill, the invisible bill, and a simple way to work out your own answer.

This is the question we get asked more than any other, usually by an owner who has just paid a painful hourly bill and is wondering if there is a better way. We sell managed IT, so you might expect the answer to be one-sided. It is not. Break/fix is genuinely right for some businesses. Here is the honest version of both sides, without quoting figures, because every business is different.

The visible bill and the invisible bill

Break/fix has one bill, and you can see it: the invoice when something gets fixed. Managed IT has one bill too: the fixed monthly fee. Comparing those two numbers is tempting and misleading, because the real cost of break/fix is mostly invisible.

The invisible bill is everything that happens around the breakdown. Staff standing around unable to work while they wait. Sales that did not happen because the system was down at the wrong hour. The owner's evening spent on the phone trying to describe a problem in a language that is not theirs. And in the worst cases, data that never comes back. None of that appears on an invoice, but it is all real cost.

The incentive problem nobody mentions

Under hourly billing, your IT provider earns more when your systems break more. That does not make them dishonest; most are decent people doing good work. But the arrangement points the wrong way. Nobody is paid to prevent the problem, so prevention quietly slides down the list. A fixed monthly fee flips the incentive: we do best when your systems simply run, because every problem costs us time we have already been paid to avoid.

When break/fix genuinely makes sense

We will say it plainly: if you are very small, have no shared systems, keep nothing critical that you could not replace, and can comfortably absorb a day or two of downtime, break/fix can be the rational choice. A sole trader with one laptop and everything in the cloud does not need a managed plan. The moment you have a team relying on shared files, email, phones and line-of-business software, the maths usually changes. The honest tipping point is dependence: the more your day's revenue depends on systems being up, the worse a pay-per-breakdown arrangement fits.

Work out your own downtime cost

You can estimate your invisible bill without any dollars at all. The method is simple: count hours lost multiplied by people affected, over a year.

1. Think back over the past year and list the times IT stopped someone working: the slow laptop, the email outage, the printer saga, the afternoon the internet died.
2. For each one, estimate how many hours were lost and how many people were affected.
3. Multiply hours by people for each event, then add them up.
4. Add the owner's own hours spent chasing, waiting and worrying, because those count too.

A worked example with no dollars: an eight-person office loses its shared drive for half a day. That is four hours times eight people, so thirty-two working hours gone in one event. Add a slow computer that steals twenty minutes a day from one person, and over a year that is roughly eighty more hours. Two or three events like the first one plus the daily dribble, and a small office can quietly lose several hundred working hours a year. However you value an hour of your team's time, that is the number to compare against the cost of preventing it.

What predictable billing does for budgeting

Beyond the downtime maths, a fixed monthly fee changes how IT feels in the business. It becomes a known line in the budget instead of a nasty surprise that lands at the worst time. Planning replaces reacting: replacements are scheduled before failures, and the February panic invoice disappears. Most owners tell us the predictability alone was worth the switch.

There is a people cost worth counting as well, and it does not show up in any tally of hours. Reliable tools are part of how a workplace feels. Staff who battle slow computers and flaky systems every day get frustrated, and frustration is one of the quiet reasons good people start looking elsewhere. When the technology simply works, nobody thanks IT, but everyone notices the difference in their day.

It also changes your relationship with your provider. Under break/fix, you think twice before calling, because every call costs money, so small issues go unreported until they become big ones. Under a managed arrangement, calling is already paid for, so problems get raised early when they are still cheap and easy to fix. That single behaviour change prevents a surprising amount of pain.

Questions to ask before switching

• What is included in the monthly fee, and what is quoted separately?
• Is there a minimum term, and what happens if we want to leave?
• How fast do you respond, and is that written down?
• Are backups monitored and restore-tested, or just running?
• Who do I actually talk to when something goes wrong?

How switching actually happens

It is less dramatic than people fear. We covered the whole process in our September post, "What managed IT support actually includes (and what it doesn't)", but the short version is: we document your systems, take over quietly in the background, and your team notices only that things start getting fixed faster. There is no big-bang changeover and no downtime weekend.

If the invisible bill from your own tally surprised you, it is worth a conversation. We will look at your setup, tell you honestly whether managed IT fits, and if it does, everything is covered by a fixed monthly fee with project work quoted separately.

And if your tally came out small, that is a fair result too. We would rather tell you to stay on break/fix and hear from you when the business grows than sell you something you do not need yet.

• break/fix
• managed it
• small business
• budgeting