The "we only call IT when something breaks" trap
Across New Zealand, the most common approach to IT for small and medium businesses is: use a tech person you know, call them when something breaks, pay their hourly rate to fix it, and move on. It feels like cost control. It feels prudent. It isn't — and the maths is straightforward once you look at it.
When a business has no monitoring on its systems, problems brew invisibly. A server's hard drive degrades slowly. A security patch goes uninstalled for months because no one's applying it. A backup job silently fails for three weeks before anyone notices. None of these show up on anyone's radar until they become catastrophic failures — and catastrophic failures are expensive in ways that go well beyond the IT bill.
What downtime actually costs
A small NZ business with ten staff losing a full day to a server failure isn't just paying an IT bill. It's losing a day of productivity across ten people. If that business turns over $1.5M a year, a full day of downtime is roughly $6,000 in lost output — before you add the emergency IT callout, the data recovery attempt, or the cost of catching up on work that didn't happen. A critical server failure that requires data recovery from backup — if a backup exists and works — routinely costs $3,000 to $10,000 in IT labour alone.
Managed monitoring, patching, and backup verification costs a fraction of that, per month, for every month. The business that hasn't had a major failure yet isn't lucky — they're operating on borrowed time.
What a good IT relationship actually looks like
The IT relationships that work well for NZ small businesses have a few things in common. First, there's continuity — the same person or team who knows your setup, your history, and your business. When something goes wrong, you're not explaining your infrastructure to someone who's never seen it before. Second, there's proactivity — your IT provider tells you about issues before you're affected by them, because they're monitoring. Third, there's transparency — you know what you're paying for, and you can see evidence that it's working.
The worst IT relationships are the ones where the provider only hears from you when there's a crisis, fixes the immediate problem, charges by the hour, and disappears. Those providers have no incentive to prevent problems — problems are their revenue. It's not necessarily malicious; it's just the wrong business model for the client.
Is managed IT worth it for a small business?
The breakeven is usually around three to five staff. Below that, a business might genuinely be better off with a good break-fix relationship and careful manual processes for things like backups. Above that, the complexity grows faster than most owners realise — more devices, more software, more users, more ways for things to go wrong — and the cost of unmanaged risk starts to outweigh the cost of managed support.
We're happy to give you an honest assessment of where you sit. If break-fix genuinely makes sense for your size, we'll tell you that. If managed support would save you money in the long run, we'll show you the numbers. Our IT support service page has more detail on what managed support includes.
A note on SLAs
When evaluating IT providers, ask about SLAs — service level agreements. Specifically: what response time is guaranteed for a critical failure? And what happens if they miss it? Many IT providers in NZ have SLAs on paper that are never enforced and never discussed with clients. An SLA is only meaningful if there's a consequence for missing it and a mechanism for tracking it. Ask to see their ticketing system's average response times for your size of business. If they can't produce that data, the SLA is decorative.