The hidden cost of reactive IT: what break-fix really costs your business

Reactive IT support has one genuine advantage: the pricing looks honest. Something breaks, someone fixes it, you pay for the fix. No monthly fee for a quiet month. It feels like only paying for what you use.

The problem is what "what you use" leaves out. The invoice records the cost of the repair. It does not record the cost of the breakage: the hours the fault existed before anyone was fixing it, the people who could not work while it did, the same fault returning next quarter because the symptom was fixed and the cause was not, and the security exposure accumulating quietly between visits. Reactive IT is not cheap. It is invoiced narrowly.

Across our client base, businesses that move from reactive support to a managed, strategic approach see ticket volumes fall by 64 per cent on average. That number is worth a moment, because tickets are not an IT metric. Every ticket is an interruption: a person who stopped working, asked for help and waited. A 64 per cent reduction is not the IT getting fixed faster. It is nearly two thirds of the interruptions never happening.

The two ledgers

Every IT arrangement runs two ledgers. The visible one is what you pay the provider. The hidden one is what the organisation pays in lost time, and with reactive support the hidden ledger is always the bigger one, for a structural reason: reactive support starts the clock at the moment of failure. The fault has to happen, be noticed, be reported and be scheduled before anyone begins fixing it, and every one of those stages happens on your payroll, not the provider's invoice.

The hidden ledger has four recurring lines. Downtime, the obvious one, when systems people need are unavailable. Degradation, the sneaky one, when everything technically works but slowly, and thirty people lose ten minutes a day to it indefinitely. Recurrence, when the same fault returns because break-fix economics reward closing the ticket, not eliminating the cause. And risk, the deferred one: unpatched systems, ageing hardware run to failure, and no one watching for the attacks that modern threats actually use, which we covered in our guide to detection and response beyond antivirus.

Do the arithmetic on your own numbers

You do not need a consultant's report to size your hidden ledger. Take one real incident from the last year and cost it honestly:

People affected, multiplied by hours affected, multiplied by the loaded hourly cost of those people. Then add anything the outage directly stopped: orders not taken, work not billed, a deadline missed. Then add the recovery overtime and the provider's emergency call-out rate, which is routinely a multiple of planned rates.

As an illustration only: a fault that stops ten people working for four hours, at a conservative £25 per hour loaded cost, is £1,000 in wages for no output before a single pound of lost revenue, emergency call-out fees or customer goodwill is counted. Now count how many incidents like that you had last year, add the daily drag of the degradation line, and compare the total with the cost of the support model that prevents most of them. For most businesses past a handful of staff, the comparison is not close. The reactive model does not avoid the cost of IT support. It relocates the cost into your payroll, where nobody itemises it.

The incentive problem nobody mentions

Here is the structural truth underneath all of this, and it is not an accusation of bad faith, just economics: a break-fix provider is paid when things break. Prevention is, quite literally, against their commercial interest. Root-cause elimination shrinks their revenue. Ageing kit that fails often is a good customer. None of this requires anyone to behave badly; the model produces the outcome on its own.

A managed agreement inverts the incentive. The provider is paid a fixed amount whether things break or not, which makes every failure their cost as well as yours, and prevention their profit as well as yours. That inversion, not any particular tool, is what people are actually buying when they buy managed IT: a provider whose commercial interest finally points the same direction as theirs.

What "strategic" actually changes

The 64 per cent does not come from working harder on tickets. It comes from work that means tickets never get raised, and it is worth being concrete about what that is, because "proactive" has been marketed to death.

Monitoring and maintenance: systems watched continuously, patches applied on schedule, faults caught and fixed before users hit them, which converts emergencies into maintenance windows. Root-cause discipline: when something does break, the question is why, and the recurring faults that generate a disproportionate share of tickets get engineered out instead of endlessly re-fixed. Lifecycle planning: hardware replaced on a schedule driven by risk and budget rather than run to failure at the worst possible moment, with the costs forecast years ahead instead of arriving as surprises. And strategy itself: a technology roadmap reviewed with the business, so IT spending moves from a series of distress purchases to a plan, and the question changes from "what broke this month" to "what should we build next".

Security runs through all four, because the biggest line on the hidden ledger is the incident that has not happened yet. Reactive arrangements almost never include anyone actually watching for modern attacks, and the cost of that gap stays at zero right up until the day it becomes the largest number your business has ever seen.

Our CTO Tom Goldsmith puts the whole model in one thought: "We have built our support services around efficiency. The more efficient our support is, the more of that efficiency we can pass to the customer, but it comes with a caveat: the organisation must follow a strategic approach. When there is a documented strategy, not only do we keep costs low for us and for our customers, we have far more impact on their organisation with technology." That caveat is the honest part. The 64 per cent is not something a provider does to you; it is something a provider and a business do together, and the documented strategy is the mechanism.

The honest caveat

Managed support costs more on the visible ledger. A business with three staff and simple needs may genuinely be fine with a good reactive arrangement and a sensible backup, and a provider who tells you otherwise is selling, not advising. The break-even arrives faster than most owners expect, though, because the hidden ledger scales with headcount: every additional person is another person interrupted when things fail. If your team is past roughly a dozen people, if IT problems are a recurring topic in management meetings, or if you have had one incident this year whose honest arithmetic frightened you, the reactive model is already the expensive one and the invoices just have not said so.

Where to start

Run the arithmetic above on your own last year: incidents, hours, people, honest rates. If the number surprises you, get in touch and we will do the comparison properly with you, your actual ticket history and incident pattern against what a managed agreement would cost and prevent. Worst case, you leave with an itemised picture of your hidden ledger, which is more than most businesses ever have.

Frequently asked questions

What is the difference between reactive and proactive IT support?

Reactive, or break-fix, support responds after something fails and charges per incident. Proactive, managed support continuously monitors, patches and maintains systems to prevent failures, for a fixed fee. The practical difference is where the clock starts: after the failure has already cost you time, or before it happens.

How much does IT downtime cost a small business?

Cost it per incident: people affected, times hours affected, times loaded hourly pay, plus any revenue or deadlines directly lost and any emergency call-out fees. Even a modest incident affecting ten people for half a day typically runs to four figures before lost revenue is counted, which is why reactive support is rarely as cheap as its invoices suggest.

Is managed IT support worth it for a small business?

Above roughly a dozen staff, usually yes, because the hidden costs of downtime scale with headcount while the managed fee is predictable. For very small teams with simple needs, a good reactive arrangement can be reasonable. The honest test is the arithmetic on your own incidents, not anyone's sales material.

How much does proactive IT support reduce problems?

Across our client base, organisations moving from reactive support to a managed, strategic approach see ticket volumes fall by 64 per cent on average, which represents interruptions to staff that simply stop happening, on top of faster resolution of the issues that remain.