What is the Break/Fix Model?
Last updated: April 9, 2026
Definition
The break/fix model is a reactive IT support approach where businesses contact a service provider only when equipment or software fails, paying per incident with no ongoing maintenance contract or monitoring. Under this model, there are no Service Level Agreements (SLAs), no continuous oversight, and no preventive measures. The provider arrives, diagnoses and repairs the issue, bills for time and parts, and leaves until the next failure occurs.
Key Facts
- Also known as: Fee-for-service IT, reactive IT support, pay-as-you-go IT
- Category: IT Service Management
- Related concepts: Managed services (the proactive alternative), co-managed IT (hybrid model), Remote Monitoring and Management (RMM), Professional Services Automation (PSA)
- Incentive structure: Provider revenue increases when more failures occur, creating misaligned incentives between provider and client
How the Break/Fix Model Works
A business experiences an IT failure (hardware malfunction, software crash, network outage, or security incident) and contacts a technician or service provider. The provider schedules a visit or remote session based on their availability, with no guaranteed response time. Upon arrival, the technician diagnoses the problem, often without prior knowledge of the client's environment, which extends troubleshooting time. Once the issue is identified, the technician repairs or replaces the failed component, tests the fix, and then bills the client for labor hours and any parts used.
There is no continuous infrastructure monitoring between service calls, so emerging issues (failing hard drives, misconfigured backups, outdated patches, unauthorized access attempts) go undetected until they cause visible failures. The client receives an invoice after each incident but no proactive reports on system health, security posture, or preventive actions taken. This creates an operational pattern where small problems escalate into major outages because no one is watching for warning signs.
Why the Break/Fix Model Matters
The break/fix model creates costly misalignments between provider incentives and client outcomes. When providers profit from failures rather than uptime, there is no financial motivation to implement lasting fixes or preventive measures. A survey by Kaseya found that 51% of technicians identified break/fix as their most time-consuming activity (Kaseya Global MSP Benchmark Survey).
For business owners and operations leaders, the core risk is financial unpredictability. A quiet month costs nothing, but a ransomware attack or server failure can generate bills totaling thousands of dollars while employees sit idle. Response times depend entirely on the provider's current workload, meaning a critical Friday afternoon outage might not get addressed until Monday. Organizations evaluating IT support models should understand that break/fix trades upfront cost predictability for significantly higher long-term costs when failures occur, which is why many transition to managed IT partnerships with defined Service Level Agreements.
Break/Fix vs. Managed Services
| Aspect | Break/Fix | Managed Services |
| Primary function | Reactive repairs after failures occur | Proactive monitoring and preventive maintenance |
| Cost structure | Per-incident billing (time and parts) | Flat monthly fee with SLA |
| Monitoring | None between service calls | Continuous 24/7 infrastructure oversight |
| Response time | Depends on provider availability | Guaranteed by Service Level Agreement |
| Provider incentive | Revenue increases when failures occur | Revenue depends on system uptime |
The key difference is incentive alignment. Break/fix providers profit from failures, while managed service providers profit from preventing them through continuous monitoring and proactive maintenance.
Common Misconceptions
Break/fix is not more cost-effective because you only pay when something breaks. Major incidents (ransomware, server failures, extended outages) generate unpredictable bills that often exceed the annual cost of managed services, and the lack of monitoring allows small issues to escalate into expensive emergencies.
Break/fix does not give you control over IT spending. While there are no monthly fees, costs are highly variable and impossible to budget accurately, creating financial risk that managed services eliminate through predictable monthly pricing and SLA-backed response guarantees.
Frequently Asked Questions
Break/fix bills per incident with no monitoring or SLAs, creating unpredictable costs. Managed services charge flat monthly fees with continuous monitoring and guaranteed response times. Co-managed IT support pairs an MSP with your internal IT staff to share responsibilities while maintaining predictable costs.
Break/fix providers earn more revenue when equipment fails, discouraging lasting solutions. Managed service providers profit from system uptime through recurring subscriptions, directly aligning their financial success with client stability and creating motivation to prevent failures proactively.
Providers must restructure billing to recurring subscriptions, deploy Remote Monitoring and Management (RMM) and Professional Services Automation (PSA) tools, draft Service Level Agreements, and educate clients on proactive value versus reactive firefighting.
