Choosing how to buy technical help usually comes down to two models: managed IT services for small business, sold as a subscription across the year, or break-fix support, paid only when something breaks. The second looks cheaper on a spreadsheet, largely because the spreadsheet ignores what happens to the business while a system is down.
Break-fix support is not irrational. For a very small company with simple needs, occasional hourly help can be reasonable. The problem appears as the business grows and technology becomes embedded in daily work: the true cost of failure stops being the repair invoice and becomes lost output, delayed orders and rushed decisions.
This comparison looks at both models through the same lens: total cost of ownership rather than the number at the bottom of an invoice. The goal is not to declare a winner, but to show which costs are visible, which are hidden, and which are simply deferred.
What Each Model Actually Buys
A break-fix arrangement buys labour. You describe a problem, someone diagnoses it, and you pay for the time and parts involved. There is no ongoing relationship, no monitoring, no preventative work, and no assumption that anything will be maintained between incidents.
A managed arrangement buys an outcome plus a share of responsibility. The fee typically covers monitoring, user support, patching, backup oversight and a security baseline, with agreed windows for how quickly issues are acknowledged. You are paying for problems that never happen as much as for the ones that do.
How Break-Fix Spending Really Accumulates
The invoice is only one line in the accounting. Four others usually go unmeasured, and together they tend to outweigh it.
Downtime
When a critical system fails, the cost is measured in idle staff, missed deadlines and customers who cannot be served. Break-fix arrangements are structurally slower because diagnosis starts after the failure is reported, not before it is detected. A managed arrangement usually notices the problem first and often fixes it before users are affected at all.
Productivity drift
Slow machines, failing drives and recurring application errors rarely trigger a support call. People work around them: they restart, they wait, they use a second device. Nobody logs the minutes, so nobody sees the aggregate. Preventative maintenance addresses those small frictions as a matter of routine rather than waiting for a dramatic failure.
Unexpected expenditure
Break-fix spending is lumpy. A quiet quarter can be followed by a month in which three systems fail at once, with emergency rates attached. That unpredictability is a budgeting problem as much as a cash problem, pushing replacements to the worst possible moment.
Internal management burden
Someone inside the business has to notice the problem, find a technician, explain the environment, approve the work and check the invoice. That person is often a senior manager or administrator whose time is already committed elsewhere, so the cost is real even when it never appears in a technology budget.
Reactive purchasing
When hardware fails without warning, replacements are bought under pressure, with little time to compare options. Planned replacement cycles generally produce better value and fewer surprises.
What the Managed Fee Contains Beyond Labour
It is tempting to compare a monthly subscription with an average repair bill and conclude the subscription costs more. That comparison misses the tools and processes bundled into the fee.
- Continuous monitoring that detects failing drives, capacity limits and stopped backup jobs.
- Documented inventory so nothing depends on the memory of one person who may leave.
- Patch discipline that closes known weaknesses before they are exploited.
- Verified backups with a tested recovery path rather than an assumption that copies exist.
- Predictable billing that makes technology a fixed line item instead of a variable shock.
- A named escalation route for the day something serious goes wrong.
Comparing Total Cost Honestly
A fair comparison requires you to add four invisible categories to the break-fix column: the value of lost working hours, the premium paid for emergency response, the internal time spent coordinating repairs, and the cost of replacing equipment early.
On the managed side, add the cost of scope you did not include. A subscription that covers workstations but not the server, or that excludes a specialised application, still generates unexpected charges. An unfair comparison in either direction usually comes from ignoring the same category of cost.
When Break-Fix Still Makes Sense
There are genuine cases for paying as you go. A firm with one or two computers, no shared server, and work that lives entirely in cloud applications has little infrastructure to maintain. A business in its final year before closing may not benefit from a long-term arrangement. A company with a strong internal team may need only occasional specialist help.
The signal that the model no longer fits is repetition. If the same class of problem returns, if failures interrupt revenue, or if internal staff spend meaningful time coordinating repairs, the arrangement is costing more than the invoices suggest.
Frequently Asked Questions
Is a managed service always cheaper than paying per incident?
No. It is usually more predictable and often cheaper once downtime and internal time are counted, but a very small business with minimal infrastructure may genuinely spend less on occasional hourly help. The right answer depends on how much of your revenue depends on systems staying up.
Can we mix both models?
Frequently, yes. Many organisations keep routine support and monitoring on a subscription while treating upgrades, migrations and office moves as separately quoted projects. That structure keeps the recurring fee stable and puts large, irregular work where it belongs.
How do we justify the switch to a finance-minded owner?
Frame it as risk transfer and budget smoothing rather than a technology purchase: a fixed monthly cost replaces an unpredictable mix of repair bills, emergency rates, lost productivity and unplanned hardware purchases.
What if we already have someone part-time?
Then the question becomes division of labour. An internal generalist can handle day-to-day requests, physical tasks and vendor coordination, while an external arrangement supplies monitoring, security oversight, documentation and holiday cover. The overlap is usually smaller than either side expects.
The Decision in One Sentence
Break-fix optimises for the lowest possible invoice in a quiet month; managed support optimises for the lowest total disruption across the year. Which one suits you depends on how expensive an outage would be, not on how cheap a repair looks today.
This article is general information about support models and is not professional, financial or legal advice. Costs and requirements vary by organisation, so seek qualified guidance before changing your arrangements.