// Guide · Decision
Managed services or break-fix: where the real difference sits
The difference is not technical. It lies in what triggers the work — and in where the understanding of your environment lives between two visits.
// The core idea
Two models, one distinction
At first glance break-fix and continuous care look like two price tags on the same product. In fact they differ on a single point, and everything else follows from it: under the first model, work begins when a person notices something. Under the second, it begins when a system reports a state — usually a good deal earlier.
Where work only happens on request, no picture of the environment survives between visits, so every incident starts with reconstruction. Where care is continuous, that picture exists already, because maintenance and monitoring need it to function. What such a standing arrangement looks like in practice is set out on our page about managed IT services.
This article helps you place yourself. It puts both models next to each other, names five questions that settle the choice in practice — and says plainly in which situations break-fix remains the correct answer.
// Side by side
What sets the work in motion
Scope is not what separates the models. The trigger is — and so is what happens to the knowledge in between.
The report is the trigger
- Work starts when somebody in the building notices a problem
- Between two orders, nobody is looking at the systems
- Replacements are sourced once the device has already failed
- The bill arrives at precisely the least convenient moment
- The setup is re-explained at the start of every visit
The system state is the trigger
- A threshold raises a flag before staff notice anything
- The environment stays documented between visits
- Hardware renewal sits in an annual plan
- Maintenance happens in windows agreed in advance
- The setup is known, so diagnosis starts much further along
// Placing yourself
Five questions that settle the model
Answer them for your own business. The more often the second answer applies, the more expensive reactive working becomes.
-
How long can you work without IT?
Half a day without your order system is a different proposition from half a day without email. The shorter the outage you can absorb, the worse the fit with a model that only starts after the failure.
-
Who here knows how the IT is built?
If that question points at one person who also catches colds, the risk is already high regardless of what the technology is doing.
-
When was a restore last tested?
If no date comes to mind, maintenance is not currently happening — under a reactive model, nobody has actually been asked to do it.
-
How often does the same fault return?
Recurring symptoms point to a cause that never gets addressed in a single call-out, because what is being paid for there is the effect.
-
Do you have to produce evidence?
Audits and data protection requirements ask for records covering a period of time. Records like that do not emerge from isolated visits.
// Transition
What a switch actually involves
Changing model is a takeover rather than a switch you flip. These four steps sit in between.
Make the estate visible
Devices, contracts, accounts and open issues get recorded. It is the least comfortable phase and the one that saves the most time later.
Prioritise the findings
Whatever reduces risk happens straight away. Whatever would disrupt the business moves into a planned window. Some items are deliberately left alone.
Set up monitoring
Only once systems report their own state can care deliver more than a single call-out would. Before that, any commitment on response times would be hollow.
Put maintenance on a rhythm
Updates, checks and reports get fixed dates. From here the work shifts from repair towards prevention.
// The other way round
When break-fix stays the better choice
Continuous care is not an end in itself. In these situations buying help case by case is the sensible option — and a provider who will not say so is selling rather than advising.
- The business can keep working for several days without the systems in question
- There is in-house IT staff who own maintenance and monitoring already
- The environment is small, recent and documented end to end
- No obligations apply that would require continuous records
- A move or refit is imminent that will replace the environment anyway
// Common questions
What people ask when comparing the models
01 What does break-fix actually mean?
Break-fix describes buying help case by case: something stops working, somebody calls, an engineer attends or dials in, and the work is billed by the hour. Between two visits there is no engagement and therefore no obligation on anyone to look at your systems.
02 Is break-fix automatically the cheaper option?
In a quiet year, yes. In a bad one, distinctly not. The invoice lands exactly when something has already stopped, which is the moment the damage is largest. A company with little dependency on IT can carry that risk deliberately.
03 Can the two models be combined?
That is a common arrangement. Servers, network and backup sit under continuous care because an outage there stops everyone; individual workstations or side projects stay on an hourly basis. The one requirement is an unambiguous line between the two, so nobody hunts for the owner during a fault.
04 What happens to documentation under break-fix?
As a rule, none is produced. Every visit starts by reconstructing how things are wired together, and that understanding leaves again with the closed invoice. This, rather than the technology, is where the long outages come from.
05 How do we know break-fix is no longer working for us?
By repetition. When the same fault keeps returning, when nobody can say when a backup was last verified, or when a single outage starts moving appointments in the business, the threshold has been crossed.
06 Do we lose control of our IT under a support contract?
Only if the contract lets that happen. As long as licences, agreements and administrator accounts stay in your name and documentation is handed over on request, what changes is who does the work, not who owns it.
Go deeper
All guides
Which model matches your exposure?
We look at how long your business can run without which systems, then work out which parts belong under continuous care and which can safely stay reactive.