Break-Fix vs Managed IT Services: How to Compare the Real Cost
Break-fix or managed IT services? A cost formula with a worked example, the hidden costs of each model, and a guide to which suits your company.
The short version: Break-fix means you pay for IT work only when something breaks, at the time you ask for it. Managed IT services means you pay a recurring fee for a defined scope that includes ongoing monitoring, updates and support. Break-fix costs less in a quiet month and more in a bad one; managed services trades that variance for a predictable bill. To compare them honestly, add up a year of break-fix spend including downtime, then compare it to the managed fee plus anything outside its scope. The formulas and worked example below show how.
This is for owners and finance leads who are deciding between calling an engineer when needed and signing a monthly agreement. After reading it you can calculate both sides with your own numbers and see which conditions favour each model.
What is the difference between break-fix and managed services?
Wikipedia's article on break/fix (read 28 October 2026) describes it as a fee-for-service method in which the provider bills only for work performed, such as repairs, upgrades and installations. Its article on managed services (also read 28 October 2026) describes a model in which a third-party provider takes ongoing responsibility for managing and maintaining a customer's IT, typically for a flat or near-fixed monthly fee.
Compare them on the points below, each in the same order.
Break-fix
- Trigger for work: a fault or a request from you.
- Who watches for problems: you do.
- Billing: per hour, per visit or per project.
- Cost shape: low when nothing breaks, spiky when something does.
- Provider's incentive: paid when things go wrong; you should still expect good faith, but the commercial incentive is not on prevention.
- Response time: whatever availability the provider has; often no written target unless agreed.
Managed IT services
- Trigger for work: monitoring, schedules and requests.
- Who watches for problems: the provider, within the agreed scope.
- Billing: a recurring fee, commonly per user or per device, plus charges for work outside scope.
- Cost shape: flat and predictable.
- Provider's incentive: fewer incidents lowers its cost of delivering the service.
- Response time: written targets by priority. See what an SLA is.
How do you compare the cost?
The structure below is an example method with assumed numbers, not Brocent data or prices and not market statistics. Replace the assumptions with your own records. All amounts are in plain currency units.
Break-fix annual cost
- Incident cost = incidents per year x average billable hours per incident x hourly rate.
- Minimum charges = number of visits x call-out or minimum fee, if any.
- Project work = project hours x hourly rate (migrations, replacements, setup).
- Downtime cost = expected hours of staff downtime x cost per hour of lost work.
- Major-event allowance = probability of a major event per year x cost if it happens (for example a ransomware recovery or a failed server).
- Total = 1 + 2 + 3 + 4 + 5.
Managed annual cost
- Base fee = users (or devices) x monthly fee per unit x 12.
- Out-of-scope work = hours of work not covered x hourly rate.
- Setup or onboarding fee, if any, spread over the contract term.
- Reduced downtime = break-fix downtime cost x expected reduction (your estimate).
- Reduced major-event allowance: the same probability reduced by the controls the service adds.
- Total = 1 + 2 + 3 + 4 + 5.
Worked example (all inputs assumed)
A 30-person company, using made-up numbers.
Break-fix side:
- 60 incidents per year x 2 hours x rate of 100 = 12,000.
- No minimum charges assumed = 0.
- 8 hours of project work x 100 = 800.
- Downtime: assume 40 hours of lost work across staff at 50 per hour = 2,000.
- Major-event allowance: 20 percent chance x 30,000 = 6,000.
- Total = 20,800.
Managed side:
- 30 users x illustrative fee of 40 x 12 = 14,400.
- 8 hours of out-of-scope projects x 100 = 800.
- No onboarding fee assumed = 0.
- Downtime: assume it is halved by proactive work = 1,000.
- Major-event allowance: assume the chance drops to 10 percent = 3,000.
- Total = 19,200.
In this example the two are close, and managed comes out slightly lower only because of the downtime and major-event assumptions. Change one assumption and the result flips. That is the point: the decision depends on your incident count and on how much an outage costs you. If your records show few incidents and low downtime cost, break-fix can be cheaper. For the real fee, see pricing, not the illustrative number above.
Quick break-even check: managed makes sense when your break-fix incident, downtime and risk costs exceed the managed fee plus its out-of-scope work.
When does each model fit?
Break-fix tends to fit when:
- You have very few devices and users, and little dependence on IT.
- A capable internal person already handles monitoring, patching and backup.
- You need a one-off project, not ongoing care.
- You can tolerate a day or more of downtime.
Managed services tend to fit when:
- Staff cannot work when a system is down, and delay costs money.
- No one internal owns patching, backup checks and security.
- You need predictable budgets and written response targets.
- Customers or auditors ask how your IT is maintained.
- You are growing and each hire would add support load.
A hybrid is possible: managed for the core estate (devices, identity, backup), break-fix or project pricing for specials such as an office move.
What should you ask a provider in either model?
- For break-fix: hourly rate, minimum charge, travel charge, after-hours rate, and whether there is any target for response.
- For managed: scope list, out-of-scope rate, SLA by priority, reporting, term and exit terms. See the MSP selection scorecard.
- For both: who holds the admin accounts, and how your data and documentation come back to you at the end.
Common mistakes
- Comparing a managed fee to a quiet year of break-fix. Use at least two years of invoices, including the bad months.
- Ignoring downtime cost. The invoice is not the only cost of a failure.
- Assuming managed means everything. Read what is out of scope.
- Not tracking incidents. Without a count, you cannot compare.
- Choosing break-fix and then skipping backup and patching, which is what keeps break-fix costs down.
How to check it worked
- After 6 months, repeat the calculation with real invoices and ticket counts.
- Check that repeat incidents fell if you moved to managed.
- Check the monthly report matches the SLA in the contract.
- Confirm you can name each item on the out-of-scope invoices and why it was not in scope.
FAQ
What is break-fix support?
It is IT support billed only when work is done, usually per hour, visit or project, after something breaks or a request is made.
What is the difference between IT services and managed services?
IT services is the broad term for any IT work done by a provider, including one-off repairs. Managed services are a type of IT service where the provider takes ongoing responsibility for a defined scope for a recurring fee.
How much does a managed service provider charge?
Providers commonly charge per user or per device per month, sometimes by tier or by a flat fee. Check the published figures on our pricing page and always ask what is outside scope.
What is the difference between MSP and BPO?
An MSP manages IT services for a customer. BPO is outsourcing a specific business process, such as accounting or contact centre work. Wikipedia's BPO article (read 28 October 2026) defines it as contracting the operations and responsibilities of a specific business process to a third-party provider.
Is break-fix cheaper than managed services?
It can be in a quiet period, and it often is not over a full year that includes downtime and a serious incident. Use the formula above with your own data.
Next step
To see what a recurring arrangement covers, read about our managed services.
Brocent publishes its managed IT support plans with per-user monthly prices for Hong Kong, Singapore, mainland China and the United States, so you can compare before you talk to anyone: see the plans and pricing.
Share:
Ready to take action?
Turn these insights into a roadmap for your business.
Book a 15-minute no-obligation consultation with our APAC IT experts. We'll review your current setup and provide a tailored IT roadmap within 24 hours.
Related services
Free Checklist
10 Critical Checks Before Expanding IT to Greater China
PIPL compliance, network segmentation, bilingual helpdesk setup, and more — everything your IT team needs before Day 1 in China.
Request the checklist →📬 Monthly Asia IT Insights
China compliance updates, cybersecurity alerts, and IT tips for APAC teams — once a month.
No spam. Unsubscribe anytime.
Related Articles
Oct 30, 2026
IT Outsourcing: What to Outsource First, Contract Clauses and an Exit Plan
Oct 30, 2026
IT Support for Small Business: What a 10, 30 and 80-Person Company Needs
Oct 30, 2026
What Is a Managed Service Provider (MSP)? Scope, Pricing Models and 20 Questions to Ask