Support contract or break-fix? Which model fits your business
SCRAM Consulting Editorial Team · Updated: May 2, 2026
Direct answer
Break-fix is reactive: you pay per technician-hour when something fails, with no continuous contract. A support contract is proactive: fixed monthly fee with defined coverage (remote, on-site, preventive, monitoring, SLA). Break-fix fits when your infrastructure is non-critical and you have fewer than 3-4 incidents per year. A contract fits when a failure impacts production, your internal IT team is small, or you need spending predictability. Calculate your annual break-fix cost over the last 24 months — if it exceeds the annual fee of a comparable contract, you are already paying contract-level money without receiving the proactivity benefits.
Key numbers
Incidents avoided by an active contract with preventive and monitoring
Annual incidents at which a contract already matches break-fix economically
Invoice history to sum to calculate your real break-fix cost
Gap over the contract fee at which migrating becomes the right call
Quick takeaways
- Break-fix = reactive, pay per incident. Contract = proactive, fixed fee with defined coverage
- Break-fix fits if your infrastructure is non-critical and you have <3 incidents/year
- Contract fits if a failure impacts production or you need spending predictability
- Practical rule: if your annual break-fix cost exceeds the contract fee, you are paying contract money without the benefits
- Hybrid model (contract + break-fix overage bucket) exists — useful for mixed critical/non-critical stacks
If your infrastructure is critical and you choose break-fix because it is cheaper, it is not whether the incident hits — it is when, and how much.
SCRAM Consulting Editorial Team
How break-fix works
Break-fix is the oldest IT support model: you have a go-to provider you call when something fails. The provider sends a technician (remote or on-site), diagnoses, repairs, and bills you for hours worked plus parts. No continuous contract, no written SLA, no preventive maintenance. Every incident is transactional.
Apparent cost: low when nothing happens. Real cost: unpredictable and high when an incident occurs — technician-hour rates range from US$45 to US$140 depending on specialization, with 2-4 hour minimums and surcharges for night and weekend work.
When break-fix fits
- Non-critical infrastructure: test environments, office equipment with no production impact
- Small companies with <15 endpoints and low annual incident rate
- Competent internal IT teams that only need point support from a specialist
- One-off projects: installation, migration, upgrade where ongoing relationship doesn't apply
How a support contract works
A contract is a continuous services agreement with fixed monthly or annual fee. Defines written scope (what equipment, what software, what hours), response and resolution SLA per severity level, and coverage of the core components: unlimited remote, on-site on demand, scheduled preventive, proactive monitoring, patches, manufacturer escalation, reports.
Apparent cost: high because you pay even when "nothing happens". Real cost: predictable and lower than break-fix once you exceed 3-4 incidents/year because it includes prevention that avoids 80% of incidents.
When a contract fits
- Production-critical infrastructure: ERP, database, clinical systems, manufacturing lines
- Small or absent internal IT team: you need continuous reinforcement, not firefighting
- Regulatory compliance: ISO 27001, data protection, industry-specific requiring documented maintenance
- Spending predictability: annual IT budget without surprises from major incidents
- Multi-site where you need uniform SLA across different geographies
Side-by-side comparison
| Criterion | Break-fix | Support contract |
|---|---|---|
| Model | Reactive (when it fails) | Proactive (continuous) |
| Cost | Variable, per technician-hour | Fixed monthly/annual |
| SLA | "As soon as possible" | Contractual with consequences |
| Preventive | No | Yes (monthly/quarterly) |
| Monitoring | No | Yes (24/7 per plan) |
| Predictability | Low | High |
| Tickets covered | Pay-per-use | Unlimited or high cap |
| Night/weekend coverage | Surcharge | Included in 24/7 plans |
| Reports | Per-incident invoice | Monthly with KPIs |
| Suitable for critical | No | Yes |
How to calculate which fits you
Pull your IT support invoices from the last 24 months. Add it all up: technician-hours, parts, travel, urgency surcharges. Divide by 24 to get your real average monthly spend.
Request a contract quote with coverage equivalent to your current infrastructure. Compare:
- If your real break-fix monthly is more than 30% below the contract fee, break-fix is still right for you
- If it is within ±20%, the contract is the better choice because you add preventive, monitoring and SLA at the same cost
- If your real break-fix monthly exceeds the contract fee, you are already paying contract money without receiving the benefits — migrate as soon as possible
The hybrid model
Companies with mixed stacks can combine: contract for critical infrastructure (ERP servers, core network, cybersecurity) + break-fix or hour-bank for everything else (office endpoints, printers, peripherals). Reduces total cost versus full contract while keeping SLA where it matters.
Some providers offer "contract with overage hours" where the base covers the critical stack and overages are billed per hour. Useful when your non-critical equipment volume is high but unpredictable.
Bottom line
No model is universally better. Break-fix fits non-critical infrastructure with low incident volume and a competent IT team. A contract fits critical infrastructure, spending predictability, regulatory compliance, or multi-site. The hybrid model works for mixed cases.
The most expensive mistake is choosing break-fix because it looks cheap when your infrastructure is actually critical: when the major incident hits (ransomware, storage failure, core network outage), you pay in downtime hours far more than you would have paid in contract fees. The simple rule: if one hour of downtime costs you more than one month of contract, you already have the answer.
SCRAM Consulting Editorial Team
Quick visualization
Typical annual incidents (index base 100 = pure break-fix)
Pure break-fix
100
Contract with preventive + monitoring
20
80% of incidents avoided with active scheduled preventive and proactive monitoring
What matters when deciding
Hourly cost of downtime
If one hour of downtime costs more than one month of contract fee, the "which model fits" question already has its answer.
Real annual incident volume
Add invoices from the last 24 months divided by 24. If it exceeds a contract monthly fee, you are already paying for a contract without receiving one.
Budget predictability
Break-fix is variable and discretionary; a contract is fixed and plannable. Decide which weighs more for your CFO.
Regulatory compliance requirements
ISO 27001, data-protection regulations and industry-specific rules typically demand documented maintenance. Break-fix produces no recurring evidence.
Internal IT team capacity
If your team handles daily operations, selective break-fix helps. If not, a contract with preventive + monitoring avoids 80% of incidents.
Quick case studies
Corporate law firm
120 attorneys · Mexico City
Challenge
Pure break-fix model for years. Ransomware encrypted active case files on a Friday; in one week of remediation plus advisory they paid the equivalent of 14 months of a contract with IR coverage.
Solution
Migration to a contract with monthly preventive, 24/7 NOC monitoring, managed patching, and an Incident Response addendum. Immutable backups as a contractual obligation on the provider.
Outcome
Zero major incidents in the 18 months that followed; monthly reports now include compliance evidence required by their professional insurance.
Private hospital
180 beds · Guadalajara
Challenge
Mixed stack: PACS and HIS critical 24/7 + ~600 office, exam-room and admin endpoints. Full-coverage contract was expensive; pure break-fix gave no SLA on what was critical.
Solution
Hybrid model: contract with P1 SLA 1h/4h for hospital core (PACS, HIS, network, security) + prepaid prefer-rate hour bag for everything else.
Outcome
TCO -22% versus full contract, same SLA on what actually moves clinical operations.
Frequently asked questions
Is a contract always more expensive than break-fix?
No. Companies that honestly compare their 24-month break-fix discover they already spent the equivalent of a contract, without receiving preventive, monitoring, SLA or reports. The "contract is expensive" feeling comes from comparing against months without incidents, ignoring the months with major incidents that drove the real spend.
Can I get break-fix with preferred-rate coverage without a full contract?
Some providers offer "prepaid hour banks" with discounted rates. It sits between pure break-fix and a contract: you pay upfront for a volume of hours at a discounted rate, without contractual SLA or preventive. Useful for companies that want a better rate without an annual commitment.
What happens with equipment under manufacturer warranty?
The manufacturer warranty (Dell ProSupport, HPE Foundation Care) covers manufacturing defects on that brand of equipment. It does not include configuration, software, logical layer, or equipment from other brands. Works well combined with a contract or break-fix from your integrator for the rest of the stack.
Should I switch from break-fix to a contract after a major incident?
Yes, that is when the decision is clearest. Before the incident the fee is hard to justify; after the major downtime the ROI of a contract is obvious. The right question is not 'when to switch?' but 'how many more incidents do I want to pay for before switching?'.
Are there alternatives to these two models?
Yes, two relevant ones: (1) Internal support with dedicated staff, fits companies with >100 endpoints and enough volume to justify in-house IT headcount; (2) Co-managed IT, where you combine your internal team with a provider that brings certified specialists in specific areas (network, security, cloud) without replacing anyone. For mid-market with a small IT team, co-managed with a contract is usually the right combination.
Citations and references
- 1
IFRS 16 — accounting treatment of service contracts (support) versus lease or purchase
Grupo Modelo, FEMSA, Bayer, Chedraui and Hertz trust SCRAM. Let's talk about your project.