Managed IT vs. Break-Fix Support: What’s the Difference?

When a computer stops working, the immediate question is who can help. The broader question is how the business wants to manage technology between problems. Should someone take responsibility for agreed routine care, or should the business request help when it is needed?

Managed IT and break-fix are labels for different working arrangements, not guarantees of quality. Providers use them differently. The written scope, responsibilities, and support commitments matter more than the name on the proposal.

What break-fix usually means

In a break-fix arrangement, you request assistance for a particular issue or task. A provider may investigate, estimate the work, and charge under an agreed project or time-based arrangement. Examples might include resolving a printer problem, replacing a failed computer, or addressing a software issue.

That can be useful when needs are occasional and someone inside the business already coordinates routine maintenance. It can also be appropriate for a defined project that sits outside an ongoing agreement.

Do not assume a provider is checking your computers between requests. Unless the agreement says otherwise, identifying maintenance needs and deciding when to ask for help may remain the business’s responsibility. Availability and scheduling also need to be understood before an urgent situation occurs.

What managed IT usually means

An ongoing arrangement assigns specified recurring tasks to a provider. Depending on the contract, these might include device inventory, update management, health monitoring, maintenance reporting, or a defined amount of support.

Those tasks are not universal inclusions. One proposal might cover only Windows computer maintenance, while another includes broader administration. A monitoring tool may generate alerts, but an alert does not establish who reviews it, when they respond, or what remediation is included.

Ask the provider to describe the operational process behind the tool. Who handles an alert? During which hours? What requires your authorization or a separate charge? An ongoing subscription should not be mistaken for unlimited help or guaranteed prevention of disruption.

Compare responsibilities before comparing prices

Start with a simple list of the technology the business depends on: computers, email, business applications, connectivity, and shared information. Then identify who currently handles each area.

Compare proposals against that list. Look for gaps and overlaps, especially if a software vendor, internet provider, internal employee, or another IT company remains involved. A computer-maintenance agreement may not include resolving every problem with a specialist accounting application.

For example, a small administrative office might want scheduled device care but retain its existing application support contract. The useful conversation is about coordination and escalation, not replacing every relationship with one label.

Understand the cost structure

Break-fix costs depend on the work requested and the charging arrangement. An ongoing service can make agreed recurring tasks easier to budget for, but it does not make all technology costs fixed.

Ask about onboarding, additional devices, replacement hardware, licensing, project work, travel, and tasks outside scope. Find out how changes are approved and how either party can end the agreement. Do not compare only the headline monthly amount when the included work differs.

A lower price may reflect a narrower service rather than a bargain. A larger package may include work your business does not need. Evaluate the fit, not simply the number of listed features.

Keep maintenance, backup, and cybersecurity distinct

Monitoring and patch management can form part of broader technology care. They do not automatically provide a backup service, a recovery plan, comprehensive cybersecurity, or regulatory compliance. Those areas need their own requirements and explicit responsibilities.

Ask where important information is stored, who manages backup and recovery, and who coordinates a suspected security incident. Do not assume that installing a remote-management agent answers those questions.

If your business handles sensitive or regulated information, establish the relevant requirements with appropriately qualified advisers before selecting services. A general maintenance proposal should not be treated as an assurance that those obligations have been met.

Questions worth asking either provider

• Which devices and tasks are covered, and which are excluded?
• Who owns routine maintenance between support requests?
• What support hours and response commitments are actually agreed?
• Is emergency or after-hours work available, and on what terms?
• What access will the provider need, and how is it authorized?
• How are changes, recurring issues, and completed work reported?
• What happens to accounts, documentation, and tools when the arrangement ends?

Request plain-English answers. If a term such as “proactive” or “fully managed” is used, ask what action it represents in your environment. A useful agreement makes expectations clearer before problems occur.

Choose the arrangement around the business

Break-fix may be reasonable where needs are limited and responsibilities are already clear. Ongoing care may be worth exploring where routine tasks lack a dependable owner or multiple computers need coordinated maintenance. Some businesses use a combination.

Amminist is developing a Managed Technology offering focused on practical computer monitoring and maintenance. Capabilities, tools, support availability, pricing, and responsibilities remain subject to validation and a written agreement; it is not presented as an operational 24/7 managed service.

For now, start with a conversation about your environment and priorities. Our technology checklist for businesses with 5–25 computers can help you prepare without committing to a particular platform or support model.