Break-fix IT support means paying per job when something breaks; managed IT means a flat monthly fee covering monitoring, helpdesk, patching and backup. The structural difference is incentive: a break-fix provider earns when things fail, while a managed provider carries the cost of recurring faults. Managed IT suits businesses with a server, staff who cannot work without their systems, or client data they must prove is protected.
The comparison
| Break-fix / hourly | Managed IT | |
|---|---|---|
| You pay | Per job, when something breaks | A flat monthly fee |
| Cost pattern | Predictable per job, unpredictable per year | Predictable per year, higher in a quiet month |
| Who finds the problem | You do, usually when it stops someone working | Monitoring does, often before anyone notices |
| Recurring faults | Billed again each time | Root cause chased at the provider's cost |
| Patching & backups | Whoever remembers | Scheduled, monitored, restores tested |
| Response commitment | Best effort, or a callback window | Contracted target by priority |
| Documentation | Rarely anyone's job | Asset register maintained, and it's yours |
| Suits | Simple setups, low downtime cost | Servers, dependent staff, compliance obligations |
The incentive problem
This is the part worth understanding, and it is not a criticism of break-fix providers — most are perfectly honest. It is structural.
Under break-fix, a provider earns when your systems fail. Nobody is deliberately leaving problems in place, but nobody is being paid to prevent them either. Investigating why a fault keeps returning is unbillable work, so it tends not to happen.
Under a managed agreement the incentive inverts. A recurring fault costs the provider time they have already been paid for, so chasing the cause becomes the commercially rational thing to do. That single difference is what most clients actually notice after switching — not the response times.
Five questions that decide it
- What does an hour of downtime cost you? If the answer is "not much", break-fix is probably fine and we'll say so.
- Do you run a server, or anything you can't trade without? If yes, someone should be watching it.
- Have you watched a backup restore? Not whether backups run — whether you've seen one come back. If not, that's the gap.
- Do you hold client data you'd have to account for? Health providers, financial services and anyone handling identity documents are in a different position.
- Is the same thing breaking repeatedly? That's the clearest signal. Repeat faults under break-fix are repeat invoices.
A middle option people forget
It is not strictly binary. Plenty of businesses keep hourly support for day-to-day issues but pay separately for the things that genuinely need to be ongoing — monitored backups, security baseline maintenance, and patching.
That covers most of what actually damages a small business without a full managed agreement. If a monthly fee looks like more than you need, it is worth asking about.
What people get wrong about this decision
Six assumptions that push businesses into the wrong arrangement in both directions.
“We hardly ever have problems, so managed would be a waste”
Usually counting the problems that got reported. Most businesses have no visibility of what their staff work around daily and never mention.
What we do Count the time actually lost rather than the tickets raised. Businesses convinced they have few problems are frequently the ones with the most unreported ones, because nobody has ever asked.
“Managed is more expensive”
Usually true in a quiet month and usually not over a year. The comparison people make is against what they spent on support, not against what the problems cost.
What we do Compare a full year including the hours staff lost. The honest answer is sometimes that managed is not worth it yet, and we would rather say so than sell it.
“Pay-as-you-go means we only pay when something breaks”
Usually accurate, and it also means nobody is being paid to stop things breaking. Patching, monitoring and backup verification do not happen on their own.
What we do Recognise what is not being done rather than only what is not being billed. The cheapest arrangement is the one where nobody is watching, right up until the moment that matters.
“We’d be locked in”
Usually a fair concern given how this industry has often worked. Long terms with exit fees are common and they are not universal.
What we do Read the term and the exit. Our managed agreements are month-to-month, because we would rather earn the next month than hold a business to a three-year contract it regrets.
“We’ll get slower service if we’re not managed”
Usually partly true and worth stating honestly. Managed clients have a contracted response target and after-hours cover; everyone else gets our best effort — a callback usually the same business day, and a booked visit.
What we do Know what you are getting either way. We publish both so the difference is visible before you choose rather than discovered during an outage.
“We have someone here who handles it”
Usually often true, and the question is what happens when that person is on leave, unwell or leaves. It is usually a dependency rather than an arrangement.
What we do Work out whether the business survives that person’s absence. A capable internal person and a support arrangement are complementary, not alternatives.
What this looks like in practice
Representative engagements, drawn from real work with identifying detail removed — we don’t name clients without written permission.
Telling a business it did not need managed IT yet
The situation
A business of nine people asked to move onto a managed agreement, having been told by another provider that it was overdue. Everything was in the cloud, there was no server, and the machines were three years old.
What we found
There was very little to manage. No server, no on-premises infrastructure, a well-configured Microsoft 365 tenancy and nine modern laptops. Their actual support consumption over the previous year, reconstructed from invoices, was around eleven hours. A managed fee would have cost roughly three times that for capability the business did not currently need.
What we did
Recommended staying on hourly support, with three specific pieces of one-off work: multi-factor authentication everywhere, backup for the Microsoft 365 data, and documentation of the environment. Set out the point at which managed would start making sense — a server, more staff, or a compliance obligation.
The outcome
The business stayed on hourly support for two more years and moved to managed when it took on a server and grew past twenty people. It moved to us, which is the part that makes the original advice worth having given.
The arithmetic that went the other way
The situation
A business of twenty-six people was on hourly support and sceptical of a monthly fee. The directors asked us to justify the difference, expecting the answer to be about convenience.
What we found
Reconstructing twelve months of invoices showed the support spend itself was already close to a managed fee. The larger number was elsewhere: the same three categories of fault had recurred throughout the year, each time fixed and never traced to a cause, and staff time lost to them ran to several days a month. Nobody had been engaged to find root causes, so nobody had.
What we did
Set out both figures — the support spend and the estimated lost time — alongside a managed fee, and named the three recurring faults with what it would take to eliminate each.
The outcome
The business moved to managed and the three recurring faults were resolved within the first quarter. The decision was made on a number rather than on a promise, which is the only basis on which it should be made.
Questions Gold Coast businesses ask us
What's the difference between managed IT and break-fix?
Break-fix means paying per job when something goes wrong; managed IT means a flat monthly fee covering monitoring, helpdesk, patching and backup. The structural difference is incentive — a break-fix provider earns when systems fail, while a managed provider carries the cost of recurring faults, which makes chasing root causes the rational thing to do.
Is managed IT worth it for a small business?
It depends on what downtime costs you. Managed IT makes sense once you have a server, staff who genuinely can't work without their systems, or client data you'd need to prove is protected. Below that, hourly support often represents better value and we'll say so rather than sell around it.
Which works out cheaper?
Over a quiet year, break-fix. Over a typical year, managed IT usually — and that's before counting staff hours lost to problems nobody prevented. The stronger argument for managed isn't cost, it's predictability and who's responsible for recurring faults.
Can we start with break-fix and move to managed later?
Yes, and most of our managed clients did exactly that. Working together on an hourly basis first is a reasonable way for both sides to find out whether the relationship works before committing to anything monthly.
Is there something between the two?
Yes, and it's underused. Keeping hourly support for day-to-day issues while paying separately for monitored backups, patching and security baseline maintenance covers most of what actually damages a business, without a full managed agreement.
What should we watch out for in a managed agreement?
A minimum term, a per-ticket charge sitting behind the words "unlimited support", no written response target, and no clarity about what happens to your documentation if you leave. All four are worth resolving before signing.
Not sure which you need?
The free review answers it — including when the answer is that you don't need us monthly yet.