Ask a finance director what the company spends on IT support and you will usually get a precise answer. Ask what an hour of unplanned downtime costs the business and the room goes quiet. That asymmetry, knowing the cost of the fix but not the cost of the failure, quietly shapes how thousands of mid-market firms buy technology support, and it explains why so many of them are still paying for IT the way they paid for it in 2015.
The traditional model is familiar: keep a small internal team, or a local supplier on an hourly rate, and call them when something breaks. It feels prudent because the invoices are small and intermittent. But the model prices the visit, not the outage. The engineer’s four hours on site might cost a few hundred dollars; the sales team locked out of the CRM for those same four hours costs a multiple of that, and nobody books it to the IT line.
Downtime is no longer a back-office problem
A decade ago, a server outage inconvenienced the office. Today the office is the stack: payments, scheduling, client files, phones and the front door badge reader all sit on the same infrastructure. When it stops, revenue stops with it. IBM’s most recent Cost of a Data Breach research put the global average cost of a breach at US$4.88 million, but the headline number is almost beside the point for a 60-person firm. The relevant figure is smaller and closer to home: the payroll run that misses its window, the tender that cannot be submitted, the client meeting where the demo will not load.
What has changed is not just dependence but expectation. Clients who get same-day answers from their bank and their courier do not distinguish between “our systems were down” and “we let you down.”
Break-fix rewards the wrong behaviour
The deeper problem with hourly IT support is structural: the supplier earns more when things go wrong. There is no incentive to patch aggressively, retire ageing hardware, or spend an unbilled afternoon hardening the firewall, because prevention cancels future revenue. Few suppliers act on that incentive cynically, but the economics still leak through in small ways: the ticket closed rather than the root cause fixed, the warning sign noted rather than escalated.
Managed service agreements invert this. When support is a fixed monthly fee, every incident is a cost to the provider, and prevention becomes the profit model. The provider now wants exactly what the client wants: fewer tickets, older problems solved permanently, and infrastructure boring enough to be forgettable. This is the quiet reason the managed services model has spread from enterprise IT down through the mid-market: not fashion, but aligned incentives.
What the mature buyers are asking for
Talk to firms that have made the switch and a pattern emerges in what they negotiated. The contracts that work tend to share four features.
Response commitments in minutes, not “business days.” A service level agreement is only meaningful if it is measured and reported. Buyers increasingly ask to see a provider’s actual response-time record, not the number printed in the brochure.
Named accountability. The single most common complaint about outsourced IT is anonymity: a different voice on every call, context lost each time. Firms now ask who, by name, owns their account, and how many other clients that person carries.
Security folded in, not sold separately. Endpoint protection, patching discipline, backup verification and staff phishing awareness are no longer add-ons; they are the baseline. A support contract that treats security as an upsell is a contract from the last decade.
Proof of prevention. The best providers arrive at quarterly reviews with a list of the incidents that did not happen: the disk replaced before it failed, the licence renewed before it lapsed. That report is the product.
This shift is most visible in dense small-business economies that run on lean headcounts. Rezolva, for instance, operates as an IT service provider Singapore SMEs retain on a fixed monthly fee, built around exactly this structure: named engineers, contractual response times and prevention-first reporting for firms too small to justify a full internal IT department but too dependent on their systems to gamble on break-fix.
The in-house question, answered honestly
None of this means internal IT teams are obsolete. Past a certain size, or in sectors with unusual compliance burdens, in-house capability is irreplaceable. The honest framing for a mid-market board is not “in-house versus outsourced” but “what must we own, and what should we rent?” Strategy, vendor selection and data governance are hard to delegate. Patching, monitoring, helpdesk and out-of-hours cover are hard to justify owning when a specialist can spread the cost of tooling and 24-hour rotas across fifty clients.
The firms that get this right usually keep one technically literate owner inside the business, someone who can hold a provider to account, and contract the operational layer out. The ones that get it wrong either outsource judgement along with operations, or keep a two-person team heroically on call for systems that deserve a ten-person bench.
Three questions before you renew anything
For a leadership team reviewing its IT arrangements this year, three questions cut through most of the noise. First: if our main system went down at 9am on our busiest day, what is the realistic cost by lunchtime, and does our current support model reflect that number? Second: does our supplier earn more or less when we have problems? Third: when did we last see evidence, not assurance, that our backups restore and our patches are current?
If the answers are uncomfortable, that discomfort is information. The bill for IT support arrives monthly either way. The only choice a business actually gets to make is whether it pays for prevention or pays, eventually and at a far worse exchange rate, for repair.
Article received via email
