Guide
Managed IT vs Break-Fix IT Support
Break-fix support reacts when something fails. Managed IT adds planning, monitoring, security review, and ongoing improvement.
By Austin Hadley, Founder and Chief Executive Officer Published Updated
Break-fix support reacts when something fails. Managed IT adds planning, monitoring, security review, and ongoing improvement.
Support models
Break-fix support is usually purchased when a specific problem occurs. It can fit organizations with limited technology, capable internal ownership, and tolerance for variable response and cost. The provider resolves the requested incident, but routine maintenance, monitoring, documentation, and planning remain the customer’s responsibility unless separately arranged.
Managed IT uses an ongoing agreement with a defined service scope. Depending on the contract, it may include a help desk, monitoring, patch coordination, security reviews, vendor management, documentation, and planning. The term is broad, so compare written responsibilities and exclusions rather than the label alone.
- Document covered users, devices, locations, applications, hours, and request types.
- Clarify response targets, escalation, after-hours work, projects, and third-party costs.
- Identify responsibilities that stay with internal staff in either model.
Cost and risk
Break-fix spending varies with incidents and projects, which can look economical during quiet periods but becomes unpredictable during outages. Managed services typically make recurring support costs more predictable, though projects, hardware, licenses, or out-of-scope work may still be billed separately. Compare the total expected cost, not only the monthly fee or hourly rate.
Risk depends on prevention and recovery as well as response. Ask who tracks warranties, capacity, backups, unsupported systems, recurring incidents, and vendor dependencies. A predictable invoice has limited value if the agreement does not define measurable operating work.
- Compare recurring fees, included labor, project rates, licenses, hardware, and termination terms.
- Estimate the business impact of downtime, delayed support, and lost staff productivity.
- Require reporting that connects maintenance and recurring issues to business priorities.
Security impact
Neither billing model guarantees security. Effective security requires named ownership for identity, updates, backups, endpoint protection, network policy, vulnerability remediation, alerts, incident response, and user guidance. Confirm which controls the provider performs, which it only recommends, and which remain entirely with the customer.
Review how the provider protects its own access. Ask about individual technician accounts, multi-factor authentication, least privilege, logging, credential storage, personnel changes, subcontractors, and incident notification. Require a clear offboarding process that returns documentation and removes remote access.
- Map each important security control to an accountable customer or provider owner.
- Confirm alert handling, evidence retention, escalation, and incident communication.
- Review administrative access and remove stale tools and accounts when the relationship changes.
Choosing a fit
Choose based on operational needs: number of users and sites, application criticality, internal skills, support hours, compliance obligations, growth, and tolerance for downtime. Some organizations use a hybrid approach, retaining internal leadership or specialized projects while contracting defined monitoring and user-support responsibilities.
Before signing, establish a baseline inventory and define the first 30 to 90 days. Agree on onboarding, documentation, urgent contacts, priorities, reporting, open risks, and how service quality will be reviewed. Exit terms should cover data and configuration return, access removal, and reasonable transition assistance.
- Ask for a written scope, responsibility matrix, service targets, exclusions, and pricing schedule.
- Check experience with the systems and business constraints actually in your environment.
- Review the relationship regularly using outcomes, recurring issues, risk reduction, and user experience.