Managed IT vs. Break/Fix: Which Support Model Actually Fits Your Business?
Key Takeaways
Introduction
Ask most IT buyers to explain the difference between break/fix and managed IT, and you’ll get some version of “one’s reactive, one’s proactive.” That’s true. It’s also incomplete enough to cost you money.
We sat down with Mitch Martinez, Executive Vice President at Derive Technologies, to get past the marketing framing and into how these two models actually behave: in the invoice, in the incentive structure, and in a client’s environment over three years.
Is break/fix just a cheaper version of managed IT?
The first correction Mitch made was structural. “Break fix is just one small piece of what managed IT provides to a customer,” he said. “Break fix is a subset of this greater offering that managed IT is.”
That matters because it reframes the comparison. You aren’t choosing between two support philosophies. You’re choosing between buying one component and buying the whole system.
The component is narrower than most people assume. Break/fix, properly defined, is hardware repair. “You’re not talking about necessarily break fix on software,” Mitch noted, even though the tickets don’t respect that boundary.
His example: a user calls in and says their laptop won’t turn on. Screen is dark. That looks like a broken monitor. It might be a software fault, a driver issue, or a display configuration problem. “Until you diagnose it, you’re not going to know.”
This is the gray area where break/fix contracts get uncomfortable. “Software runs on hardware and hardware is useless without software,” Mitch said. If the fix turns out to be in software, you’ve paid for a diagnostic visit under a contract that doesn’t cover the resolution.
What does managed IT cover that break/fix doesn’t?
The defining characteristic of managed IT is fewer repairs.
“Managed IT encompasses things like proactive monitoring so that you can catch issues before it actually breaks,” Mitch said, “so that you don’t have to go into break fix mode.”
It also covers ground break/fix simply doesn’t reach. Managed IT spans the full ecosystem, including cloud, where there’s no hardware for you to fix at all. “You could be managing things in the cloud and you’re never going to do break fix,” he said, “because the software provider should do the break fix broadly, transparently, and hopefully proactively before you fail.”
Then there’s the security layer. Managed support typically bundles patch management and endpoint protection. Break/fix doesn’t. “With break fix you’re not getting managed security,” Mitch said flatly. For an organization that has spent significant effort building out a security program, that gap is hard to justify.
The other structural difference: SLAs. Pure hardware break/fix can be delivered against a response-time commitment, but it can’t underwrite uptime for a system whose failure modes are mostly software. “You’re not going to get a guaranteed SLA with that,” Mitch said, “unless there’s another entity that has an SLA on software.”
How do the incentives differ?
Here’s the part that doesn’t make it into most vendor decks.
Under a per-incident break/fix arrangement, the vendor’s revenue is a function of your failures. Under managed services, the vendor absorbs the cost of failures. Those are opposite incentives, and they compound over a multi-year term.
Mitch was careful not to oversimplify it, though. Break/fix comes in more than one shape:
- Per-incident. You pay when something breaks. Vendor revenue rises with your downtime.
- Blanket contract. A fixed fee covering a defined fleet, with limits and exclusions. “You’re getting paid to be available and meet an SLA,” Mitch said, closer to the managed model in structure.
- Hybrid. A base fee for help desk and field dispatch capability, plus per-incident charges layered on top.
The per-incident model is where the incentive misalignment bites hardest. The blanket model is the one that’s genuinely comparable to a managed agreement.
Is break/fix actually cheaper?
Break/fix is cheaper. Mitch didn’t dispute that: “break fix is going to cost a lot less than managed IT on the surface.”
His caution was about the word surface. “Over time what people find out is that break fix is actually a more costly approach than the managed IT approach,” he said, “because downtime translates into money and lost money.”
His summary of the model, and the line worth writing down: break/fix is “the least costly and least effective way to manage your fleet.”
The comparison problem is that you can’t run it at signing. A managed agreement is a known fixed monthly cost. A per-incident break/fix arrangement is an unknown. “How do you know how many incidences you’re going to have?” Mitch asked. “There’s no way to compare.”
“Managed services and break fix are an apple and an orange in the traditional sense,” he said. The closest you can get to a real comparison: total managed cost versus a fixed-price break/fix contract, evaluated across one, two, and three years.
When does break/fix still make sense?
This isn’t a piece arguing that break/fix is obsolete. Mitch’s position is more specific than that.
“Break fix is definitely not dead,” he said, “but it’s now much more narrowly focused on those assets that are high ticket items that can’t readily be replaced in its entirety.”
The dividing lines:
- Cost and replaceability. A million-dollar IBM mainframe or AIX system isn’t something you keep a spare of. Neither is a Dell or HPE blade chassis or a Nutanix HCI cluster. “That’s why IBM has a thriving break fix business,” Mitch said. “That’s why HPE and Dell sells pro support for servers.”
- Modular vs. sealed. Enterprise hardware is built to be repaired. A laptop or iPad is “a sealed unit.” Repair economics diverge completely.
- Blast radius. This is the cleanest test. “These are critical items that if they go down, they affect thousands of people. An end device goes down, it’s one person.”
Meanwhile, the top of the market has largely moved on. “The break fix oriented go with the lowest cost just to keep us surviving, that model is usually not embraced by the most well managed organizations.”
The self-insurance alternative
One more model worth knowing, because plenty of organizations already run it: skip the contract on endpoints and buy spares instead.
Mitch’s illustration: 2,000 iPads, no support contract, and 100 spare units held in reserve. That’s 5% of the fleet, rotated in as devices fail. Compare it to paying 10 to 15% of hardware cost for coverage.
Note what this doesn’t cover: the labor to reimage, redeploy, and re-enroll the replacement, which is managed services work, not break/fix work.
What should you ask before your next renewal?
Work through these eight questions before you sign:
- Is this asset replaceable inside my tolerance for downtime? If yes, spares may beat a contract.
- Is it modular or sealed? Modular favors repair contracts. Sealed favors replacement.
- What’s the blast radius on failure? One user, or the majority of your customers?
- Am I buying per-incident, blanket, or hybrid? Only the blanket model compares cleanly to managed services.
- Who owns the software side of my uptime? If nobody does, your SLA has a hole in it.
- Am I getting patching and endpoint security? Under pure break/fix, no.
- Does my support term match my depreciation schedule? If not, one of them is wrong.
- What did unplanned downtime actually cost me last year? Without that number, every cost comparison is a guess.
The Takeaway for IT Buyers
Frequently Asked Questions
What is the difference between managed IT vs. break/fix support?
Break/fix pays a provider to repair hardware when it fails. Managed IT covers the whole environment, including proactive monitoring, patch management, endpoint security, and cloud services, against a defined SLA. Break/fix is one component of what managed IT provides.
Is break/fix cheaper than managed IT?
On the surface, yes. Over a multi-year term it usually costs more, because downtime translates into lost money and pure break/fix does not include patching or endpoint security.
When does a break/fix contract make sense?
For expensive, modular, hard-to-replace infrastructure such as mainframes, blade chassis, and HCI clusters, where a failure affects thousands of people and keeping a spare is not realistic.
How do you compare a managed agreement with break/fix pricing?
Compare total managed cost against a fixed-price blanket break/fix contract across one, two, and three years. Per-incident pricing cannot be compared at signing, because you do not know your incident count in advance.
The Takeaway for IT Buyers
In the managed IT vs. break/fix decision, break/fix isn’t the wrong answer. It’s a narrow one: the right tool for expensive, modular, hard-to-replace infrastructure where a repair contract is genuinely cheaper than a spare.
For everything else, the model you’re really comparing isn’t cheap versus expensive. It’s known versus unknown. And the unknown has a way of getting more expensive the longer you hold it.
Trying to work out which model fits your environment? Derive Technologies helps organizations model the real three-year cost of both. Book a free consultation.