Many small and growing businesses start out with IT support that is reactive by design. Something breaks, someone calls a technician, the problem gets fixed, and normal service resumes. That model — known as break-fix — has served organisations well for decades and still has a role in certain circumstances.
Managed IT operates differently. Rather than waiting for problems to appear, a managed service provider (MSP) takes ongoing responsibility for maintaining, monitoring and improving an organisation’s technology environment. The two models are not simply variations of the same thing; they involve different relationships, different risk profiles and different cost structures.
Understanding the difference helps you make a more informed decision about which model fits your organisation’s current situation.
What is break-fix support?
Break-fix is straightforward: you pay for support when you need it. A device fails, a configuration breaks, a user cannot access a system — you call a technician, pay for the time, and the problem is resolved.
There is no ongoing contract, no retainer and no proactive maintenance unless you specifically request it. The technician’s incentive is to resolve the problem you described, not to look for broader risks or patterns.
This model is predictable in one sense: you only pay when something goes wrong. It is unpredictable in another: you have no control over when that happens or what it will cost.
What is managed IT support?
Managed IT is an ongoing service relationship. The provider takes a defined responsibility for your technology environment — typically covering monitoring, maintenance, security updates, helpdesk support, user management and regular review. You pay a fixed or per-user monthly fee in return.
The managed provider has an incentive to prevent problems rather than just fix them, because their cost of delivery goes up when things break repeatedly. This alignment is one of the practical advantages of the model.
Managed IT also means clearer ownership. Someone is responsible for your environment on an ongoing basis, not just when you call.
Comparing the two models
| Dimension | Break-Fix | Managed IT |
|---|---|---|
| Cost structure | Variable, per-incident | Fixed monthly or per-user fee |
| Proactive maintenance | Rarely included | Central to the model |
| Response scope | The problem you called about | Broader environment awareness |
| Security baseline | Your responsibility to initiate | Included in ongoing service |
| User lifecycle (joiners/leavers) | Ad hoc, when requested | Defined process, regularly handled |
| Documentation | Usually none | Maintained as part of service |
| Scalability as headcount grows | Each new issue is a separate call | Service scales with your users |
| Relationship type | Transactional | Ongoing partnership |
When break-fix is still a reasonable choice
Break-fix can work well in specific situations. If your organisation has very few staff, low technology dependency, and reliable in-house capability for routine tasks, a reactive model may be proportionate. Freelancers, very small partnerships and organisations with a technically capable co-founder or operations lead sometimes find break-fix sufficient, especially if their cloud platforms are straightforward.
The risks become more significant as an organisation grows: more devices, more users, more cloud services, more attack surface. Break-fix does not scale gracefully, and the hidden costs — staff downtime, delayed resolution, security exposure during gaps — often exceed what the model appears to save.
When managed IT is worth considering
There is no fixed headcount threshold, but a few signals suggest the time is right:
- You have no clear owner for IT decisions, security configuration or user access
- New starters or leavers are not handled consistently
- You do not know what devices are active, patched or assigned
- Your cloud platforms are configured the way they were when you first set them up
- A day of downtime would now have a meaningful cost to the business
If several of these apply, the question is not really “managed IT or break-fix” — it is “how quickly do we close the gap?”
Related: How to know when your business needs more structured IT support →
The hidden cost of break-fix
Break-fix invoices are visible costs. The costs that do not appear on an invoice are harder to account for: staff time lost to slow systems, the security gap between incidents, the IT configuration that has drifted since it was last touched, the joiner who had too much access for three months because no one reviewed it.
Managed IT does not eliminate cost — it changes where it sits. Many organisations find that a predictable monthly fee is easier to budget than unpredictable incident costs, and that the proactive maintenance avoids larger problems downstream.
What to ask before choosing a support model
Before deciding, it helps to answer a few practical questions:
- Do we have a clear picture of every device, account and platform currently active?
- Is someone explicitly responsible for security configuration, updates and access changes?
- Are our joiners and leavers handled consistently, with access given and removed promptly?
- When something goes wrong today, is the path to resolution clear?
- What would a day of significant IT disruption cost us in lost productivity or revenue?
If the answers reveal gaps, that is useful information regardless of which support model you choose. An IT Current-State Assessment can give you a clearer picture of where your organisation currently stands before you commit to a direction.
Frequently asked questions
Can we transition from break-fix to managed IT without disruption?
A good managed IT provider will conduct an onboarding process that documents your environment, identifies gaps and introduces changes in a structured way. Transition does not need to be disruptive, but it does require a period of discovery and setup — typically a few weeks.
Is managed IT just a helpdesk with a monthly fee?
No. A helpdesk handles user requests reactively. Managed IT includes proactive maintenance, security management, monitoring, user lifecycle processes and regular reviews — the helpdesk element is one component, not the whole service.
How small is too small for managed IT?
There is no fixed answer, but organisations with fewer than five staff and very simple cloud-only environments may find break-fix sufficient. As soon as IT complexity grows — more users, remote access, device management, compliance requirements — managed IT typically becomes more cost-effective than it first appears.
How do we know if our current support arrangement is actually working?
Ask these questions: Is someone clearly responsible for our IT environment today? Are our devices and accounts documented and up to date? Have our cloud platforms been reviewed in the last 12 months? If the answer to any of these is uncertain, the current arrangement has gaps worth understanding.
Do managed IT providers lock you into long contracts?
Contract terms vary. Twelve-month agreements are common, as managed IT involves setup work and ongoing investment from the provider. Some providers offer rolling monthly terms, particularly for smaller organisations. It is worth clarifying scope, exit terms and renewal conditions before signing.
If you are weighing up your options and would like a clear picture of where your organisation currently stands, an IT Current-State Assessment from OTUSYN gives you a practical, independent view of your environment — including whether your current support model is covering what it should.