Break/fix support bills for time when something fails, so costs are low in quiet months and unpredictable overall. Managed IT charges a recurring monthly fee, usually per seat (per user), to keep systems running, so costs are steady and the provider is paid to prevent failures. Which costs less depends on how much downtime, emergency work and unmanaged risk you currently absorb.
Both models are legitimate. The question is which one fits the way your organization depends on technology, and the honest way to answer it is with your own numbers rather than a vendor's.
What is the difference between break/fix and managed IT?
Break/fix is reactive and transactional. When a laptop fails, email stops or the network goes down, you call a technician, who fixes it and bills the time and parts. Between calls, nobody is responsible for your systems.
Managed IT is ongoing and contractual. A provider monitors, patches, backs up and secures your environment continuously for a recurring fee, typically set per seat (per user), and handles most support requests within that fee. The provider is responsible for your systems between problems, not only during them. Our managed IT buyer's guide covers what that responsibility normally includes.
How do the incentives differ?
This is the difference that matters most, and it is structural rather than a question of anyone's honesty.
| Factor | Break/fix | Managed IT |
|---|---|---|
| Provider earns more when | Things break | Things keep working |
| Prevention work is | Billable only if you request it | Part of the fee |
| Patching and monitoring | Usually not done unless requested | Continuous |
| Cost in a quiet month | Low or zero | The monthly per-seat fee |
| Cost in a bad month | Emergency rates, often at the worst time | Usually covered by the fee |
| Knowledge of your environment | Rebuilt on each call | Documented and retained |
| Budget predictability | Low | High |
A break/fix technician can be excellent and still be working in a model that pays nothing for the problem that never happened.
How do you compare the true cost?
Fill in this worksheet with the last 12 months of your own figures. Estimates are fine; the point is to make the hidden costs visible.
Step 1: Direct IT spend under break/fix.
- Technician invoices for the year: ____
- Emergency or after-hours premiums within those invoices: ____
- Replacement hardware bought because of a failure rather than on a plan: ____
Step 2: The cost of downtime.
- Hours staff could not work because of IT problems: ____
- Multiply by an average loaded hourly cost per affected person: ____
- Revenue or billable time lost during outages, if any: ____
Step 3: The cost of internal time.
- Hours a manager or employee spent troubleshooting, calling vendors or chasing fixes instead of doing their job: ____
- Multiply by that person's loaded hourly cost: ____
Step 4: Risk you are carrying.
This part is harder to put a number on, but list it anyway:
- Are systems patched on a verified schedule?
- Has a backup been restored in the last 12 months?
- Is multi-factor authentication on email and remote access?
- Is there a current record of devices, accounts and admin credentials?
Each "no" is a risk that a break/fix arrangement is not being paid to address. A single ransomware incident, lost laptop or failed server without a working backup can cost more than several years of either model.
Step 5: Compare.
Add Steps 1 to 3. That is what break/fix actually cost you last year. Compare it with a managed IT quote for the same scope, and then weigh the Step 4 risks that a managed agreement would address. Our article on what drives managed IT pricing explains how to get quotes you can compare fairly.
When is break/fix the right choice?
Break/fix can be sensible when:
- The organization is very small, with a handful of devices and nearly everything in reputable cloud services.
- Technology failures cause inconvenience rather than lost revenue.
- No customer, insurer, regulator or contract requires documented security controls.
- Someone internal is capable of and responsible for routine maintenance.
If all four are true, paying only for what breaks may cost less, provided someone is still making sure backups work and accounts are protected.
When does managed IT make more sense?
Managed IT usually wins when:
- Downtime stops revenue, billable work or operations.
- You handle information that others require you to protect, such as patient records, financial data or controlled defense information.
- You have received a security questionnaire, cyber insurance application or contract clause you could not answer confidently.
- Your IT knowledge sits with one person.
- The same problems recur because nobody owns the underlying cause.
Organizations that have an internal IT person but not enough capacity or specialist skill often land in between: co-managed IT keeps ownership in-house while a provider covers monitoring, security and overflow.
What should you do next?
Complete the worksheet. If Steps 1 to 3 already approach the cost of a managed agreement, or Step 4 has more than one "no," the conversation is worth having.
To see where your environment stands before you decide, request an IT and security assessment.