Break-fix isn’t a bad model. For a two-person business with a couple of laptops and everything in Microsoft 365, paying someone by the hour when something goes wrong is the right call. Nobody needs a monthly agreement to manage four devices.

The problem is that nothing announces the moment it stops working. There’s no letter in the post. Costs drift up, small risks accumulate, and the change is only obvious in hindsight. These are the five signs that usually show up first.

1. Downtime is becoming normal

If “it’s playing up again” is a regular phrase in your office, you’re paying for the same problems repeatedly instead of fixing root causes.

This is the clearest signal, because break-fix has no incentive to find root causes. A technician is paid to restore service and move on, which is exactly what you want in the moment. But the printer that jams weekly, the machine that needs a reboot every morning, the shared drive that disconnects: each is a small bill and a small interruption, and nobody is being paid to ask why.

Add it up before you dismiss it. Half an hour of lost work, twice a week, across five people, is well over a hundred hours a year.

2. Bills are unpredictable

Hourly break-fix means your worst months cost the most — exactly when you can least afford it. Flat-fee managed IT makes budgeting simple.

The less obvious cost does more damage: an hourly bill discourages you from calling. People put up with things. They work around the broken process rather than raise a ticket, because a ticket has a price attached. Problems get reported late, when they’re bigger.

Under a flat fee, calling early costs nothing, so people do it.

3. Nobody is watching proactively

Patches, backups and security alerts need someone watching every day, not just when you call. Without that, small issues become outages.

Think about what has to go right, silently, every week: patches install, backups complete, antivirus definitions update, disks stay healthy, licences stay current. Under break-fix, nobody is watching any of it. You find out a backup has been failing for three months at the exact moment you need it.

Most serious IT failures announce themselves well in advance: a disk reporting errors, a backup job failing every night, a certificate approaching expiry. Those warnings get logged whether or not anyone looks at them.

4. Security keeps getting deferred

MFA, backups and hardening rarely make the cut when you only pay for emergencies. That’s a growing risk as attacks get more automated.

Security work is preventative by definition, so it never competes well against a broken thing in front of you. Under break-fix it stays permanently at the bottom of the list; there’s always something more urgent.

Meanwhile the expectations have moved. Cyber insurers now ask direct questions about MFA and backups. Larger clients push security requirements down to their suppliers. If you handle personal information, you are already expected to take reasonable steps to protect it. None of that waits for a convenient quarter.

5. IT decisions are reactive

You’re making technology choices under pressure rather than to a plan. A managed partner gives you a roadmap and someone accountable for it.

Reactive decisions are expensive decisions. A laptop that dies unexpectedly gets replaced with whatever is in stock, at retail, configured in a hurry. Planned, the same replacement is chosen on merit, bought at a sensible price, and set up before anyone is waiting on it.

The same applies to bigger moves: a server reaching end of life, an operating system going out of support, an office relocation. Handled to a plan they’re unremarkable. Handled at the last minute they’re expensive and disruptive.

So what changes?

In practice, the differences between the two are:

  • Monitoring and patching run continuously, so most issues are dealt with before anyone notices them.
  • The cost is flat, which means calling early is free and budgeting is simple.
  • Security baselines are maintained rather than revisited after an incident.
  • Someone is accountable for the plan — what gets replaced when, and what it will cost.

Is it worth it at your size?

Sometimes not. If you’re very small, stable, entirely cloud-based and have no compliance obligations, break-fix may still be the sensible option, and we’ll tell you so.

The tipping point is usually somewhere around five to ten staff, or earlier if you handle sensitive data, have client security requirements, or simply cannot afford a day offline.

If two or more of these sound familiar, start by adding up what last year’s outages, overtime and emergency callouts cost you. That figure is more useful than any quote.