An employee’s laptop won’t start ten minutes before a client call. The office manager digs through old emails looking for the phone number of whoever fixed the printer last year. It takes two hours just to get a callback, and the technician can’t come out until tomorrow.
Nothing else in the office is affected. But the employee is idle for a day, the client call gets rescheduled, and the invoice will carry a same-day emergency rate.
None of this is unusual. It’s what break-fix IT support looks like in practice, and it’s why the real cost of this model rarely shows up until someone adds it all up.
What Break-Fix IT Support Actually Looks Like
Break-fix is the pay-per-incident model: nothing happens until something stops working, then a call gets made, and a bill follows. There’s no ongoing monitoring, no maintenance schedule, and usually no standing relationship with a technician who already knows the systems involved.
In practice, that means the same cycle repeats every time something breaks: a problem appears, someone searches for who to call, there’s a wait for a callback and then a wait for an appointment, the issue gets patched, and a bill arrives. Nothing is diagnosed beyond the immediate symptom, because nobody is being paid to look further than that.
Reactive Model vs. Managed Model
| Break-Fix (Reactive) | Managed IT |
| Problems are discovered after they’ve already caused downtime | Monitoring often catches problems before they cause downtime |
| Response time depends on a technician’s availability that day | Response is faster, since it isn’t a one-off relationship |
| Pricing is unpredictable, often at emergency rates | Pricing is flat and predictable month to month |
| No one is accountable for a problem that keeps recurring | Root-cause fixes are part of the relationship, not an upsell |
| Hardware and software aging isn’t tracked by anyone | Lifecycle and replacement needs are planned in advance |
| Security is addressed after an incident, not before one | Security is monitored on an ongoing basis |
Why the Invoice Isn’t the Real Cost
The repair bill is the easiest part of break-fix to see. It’s also the smallest part of what it actually costs.
The fuller number includes the repair itself (typically billed at a higher rate than a managed contract, since there’s no ongoing relationship or volume pricing), the downtime while the issue waits to be addressed, and the wages paid to employees who are idle during that time.
A simple way to estimate it: (employees affected × average hourly wage) + estimated lost revenue per hour + the repair cost itself, multiplied by how long the outage actually lasts — including the time spent waiting for a callback, not just the repair.
Industry research puts the average cost of downtime for small and mid-sized businesses somewhere between $8,000 and $25,000 an hour once lost revenue, idle staff time, and recovery work are included; Datto’s State of the Channel Report puts the SMB average closer to $8,000 an hour. A single afternoon outage can outweigh what a full month of managed IT would have cost.
Not Every Business Needs to Move Away from Break-Fix Immediately
Break-fix isn’t automatically the wrong choice. It can be reasonable for a very small operation with minimal technology dependence, a one-time project, or a business that genuinely goes long stretches without touching its systems. The calculation changes once a business depends on email, shared files, a website, or a point-of-sale system to operate day to day — which describes most small and mid-sized businesses.
Which Businesses Should Reconsider Break-Fix First
Break-fix is usually worth reconsidering when:
- IT support is being called more than once or twice a quarter
- the same issue keeps coming back instead of getting resolved
- an outage of a few hours would meaningfully disrupt revenue or client work
- nobody can say with confidence when the last backup ran, or whether it succeeded
- no one is tracking when hardware or software is nearing end of life
- the business is growing and IT complexity is increasing faster than anyone has time to manage
Break-Fix, Managed IT, and Co-Managed IT Are Not the Same Thing
The terms get used loosely, but they describe different relationships:
| Approach | What Happens | Example |
| Break-fix | Support is provided only after something fails, billed per incident | A server crashes and a technician is called in to restore it |
| Managed IT | A flat monthly fee covers ongoing monitoring, maintenance, and support | Continuous monitoring flags a failing hard drive before it fails completely |
| Co-managed IT | An internal IT person or team is supplemented with outside monitoring, tools, or specialist support | An internal admin handles daily requests while an outside partner covers after-hours monitoring and security |
Where Break-Fix Gets Riskier
The gap between incidents is where break-fix creates the most risk, because nothing is being watched in between visits. Worth asking:
- Who is watching for security threats between service calls?
- Who is tracking how old the server or network equipment actually is?
- If a breach happened this week, how long before anyone would notice?
- Does the business have any compliance or client-contract obligations that assume active monitoring?
- None of these have a good answer under a pure break-fix model, because nobody is being paid to watch for them.
When Outside Help Makes Sense
The right model usually depends less on company size and more on how dependent the business is on its systems, and how much internal capacity already exists:
- Managed IT tends to make sense for a business with no internal IT staff that depends on its systems daily.
- Co-managed IT tends to make sense when there’s already an internal IT person, but they need after-hours coverage, specialist security support, or backup during time off.
- Break-fix can still make sense for a business with very low technology dependence and no internal IT need beyond occasional, isolated issues.
How Techmentum Approaches Managed IT
At Techmentum, the starting point isn’t a sales pitch for a monthly contract — it’s an honest look at how often a business is currently calling for help, what those incidents are actually costing, and whether the pattern points to genuine risk or just occasional bad luck.
From there, the right fit might be a full managed IT plan, a co-managed setup alongside an existing IT person, or simply a recommendation to keep doing what’s already working. The goal is to match the support model to how the business actually depends on its technology, not to assume every business needs the same plan.
If your team is calling for IT help more often than it used to, or a recent outage cost more than expected, Techmentum can walk through what a managed IT plan would actually look like for your business.
Schedule a free consultation with Techmentum.
Frequently Asked Questions
Is break-fix IT support cheaper than managed IT?
It’s cheaper only in the short term and only if nothing goes wrong. Once downtime, emergency labor rates, and lost productivity are factored in, most businesses that depend on their technology daily end up paying more with break-fix over time.
What’s the difference between break-fix and managed IT?
Break-fix is reactive — support happens only after something breaks, billed per incident. Managed IT is proactive — a flat monthly fee covers ongoing monitoring, maintenance, and support aimed at preventing problems before they cause downtime.
How much does IT downtime cost a small business?
Estimates vary by size and industry, but small and mid-sized businesses commonly see costs in the range of $8,000–$25,000 per hour once lost revenue, idle staff time, and recovery work are included.
Is break-fix ever the right choice?
Yes, for businesses with very low technology dependence, infrequent IT needs, or one-time projects. It becomes a harder case to justify once a business depends on its systems to operate day to day.
What is co-managed IT?
Co-managed IT combines an internal IT person or team with outside support — typically for after-hours monitoring, specialist security work, or backup coverage — rather than replacing internal IT entirely.
