Break-Fix vs MSP: Which IT Support Model Actually Makes Sense for Small Business

Most small business owners end up in one of two camps: they either call someone when something breaks, or they pay a monthly fee to a managed service provider and hope it covers whatever goes wrong. Neither model is automatically better. The right answer depends on how many users you have, what happens when your systems go down, and whether you’re dealing with any compliance requirements.

Let me break down both models honestly, including what they cost and when one stops making financial sense.

What Break-Fix Actually Means

Break-fix is the oldest IT support model in the book. Something stops working, you call a tech, they fix it, they bill you. No contract, no monthly fee, no relationship beyond the work order.

Rates vary a lot by region and specialty, but expect to pay $100–200/hour for a decent independent tech, and $150–250/hour if you’re going through a regional IT firm. Some shops charge a trip fee on top of that. Remote support tends to run a bit cheaper — some providers bill in 15-minute increments for remote sessions.

The appeal is obvious: you only pay when you need help. If your five-person office has reliable hardware, uses cloud apps for everything, and IT problems show up maybe twice a year, a break-fix relationship is probably the right call. You might spend $400–800 a year on IT support. An MSP would charge you $500–750 a month for the same team size.

What a Managed Service Provider Actually Provides

An MSP charges a flat monthly fee — typically per user or per device — in exchange for ongoing monitoring, maintenance, and support. The theory is proactive: they’re watching your systems before problems become outages, applying patches, managing backups, and responding when something goes sideways.

Good MSPs cover:

Remote monitoring and alerting (they know your server is running low on disk before you do)
Patch management for operating systems and common software
Helpdesk access during business hours (sometimes 24/7 for higher tiers)
Backup verification — not just that backups are running, but that they can actually restore
Endpoint security management (antivirus, EDR, sometimes email filtering)
Basic vendor coordination (they deal with your ISP when the internet goes down)

That’s the core stack. Some MSPs bundle in more — Microsoft 365 licensing, VoIP management, security awareness training. Others charge for those separately.

When Break-Fix Is the Right Call

Break-fix works when the cost of downtime is low relative to monthly support fees. Here’s a realistic scenario where it makes sense:

You have four or five users. Everyone works in the office. You’re running Microsoft 365 for email and documents, a cloud-based point-of-sale or accounting system, and basic workstations. Your internet goes down maybe once a year, and when it does, people grab their phones as hotspots and keep working. A server failure would hurt, but it wouldn’t cost you thousands of dollars per hour.

In that situation, paying $500/month for managed services is hard to justify. You’d need roughly 3–5 hours of break-fix work per month just to break even, and a stable small office rarely hits that.

Break-fix also works if you have an internal person — even a part-time one — who handles day-to-day issues and only needs outside help for bigger problems. A hybrid where you self-handle tier-1 issues and call a specialist for infrastructure or security questions is often the most cost-effective model for 10–20 person shops.

When an MSP Starts Making Sense

The calculation shifts when any of these factors are present:

Compliance requirements. If you’re dealing with HIPAA, PCI-DSS, or state-level data privacy laws, you need documented patch management, access controls, and often a written risk assessment. An MSP can own that process. A break-fix tech typically won’t.

Heavy remote work. When half your team works from home, endpoint security gets complicated fast. VPN management, device policy enforcement, and remote wipe capability are things an MSP can standardize. Doing it yourself or relying on break-fix gets messy.

Frequent IT issues. If you’re calling for help more than twice a month on average, you’re probably already spending MSP money on break-fix bills. At that point, the predictability of a flat monthly fee is worth something by itself — budgeting becomes easier even if the annual cost is similar.

A line-of-business application you can’t afford to have down. Manufacturing scheduling software, job dispatch systems, anything where downtime translates directly to lost revenue or penalties changes the math. Monitoring and faster response time have real value.

No internal IT. If nobody on staff has any technical background and you’re calling your nephew when the printer won’t connect, an MSP gives you a real answer on the other end of the line and someone accountable for outcomes.

What an MSP Contract Should Include

A well-written MSP agreement is specific about scope. Look for:

Defined response times. Not “we’ll get back to you soon” but “critical issues responded to within 1 hour, standard requests within 4 business hours.”
Scope of coverage. Exactly which devices and systems are covered. Workstations only? Does the server count? Network gear?
Backup testing. Monthly or quarterly restore tests, in writing.
Patch cadence. When and how patches are applied. Weekly is standard.
Out-of-scope charges. What triggers a separate invoice? New hardware setup, major migrations, and project work usually aren’t included — that’s fair, just make sure it’s defined.
Termination clause. Can you exit with 30 days notice? 90 days? Watch for auto-renewal clauses that lock you in for another year if you miss a window.

Red Flags in MSP Agreements

Vague scope language. “We’ll handle your IT needs” without specifics is a setup for billing disputes. Every service should be named.

No SLA numbers. If response time isn’t in the contract, it doesn’t exist. Don’t accept verbal promises.

Mandatory hardware or software purchases through them. Some MSPs require you to buy workstations, firewalls, or security software exclusively through them at inflated margins. This is a conflict of interest. A good MSP will recommend hardware and tell you where to buy it cheaply.

Long initial terms. A 36-month initial contract from a provider you’ve never worked with is a red flag. Industry standard is 12 months with month-to-month available after that.

Backup as an add-on. If backup monitoring and verification aren’t included in the base price, ask hard questions. This is core to what an MSP should do.

Realistic Per-User Monthly Costs

The range I’ve seen in practice for small business managed services:

Basic monitoring + helpdesk only: $50–80/user/month
Full-stack managed services (monitoring, patching, EDR, backup, helpdesk): $80–130/user/month
Compliance-focused or security-heavy packages: $130–175/user/month

For a 10-person company at the mid-tier, you’re looking at $800–1,300/month. That’s $9,600–15,600/year. It’s a real number. If your current break-fix bills are $2,000/year and your downtime is minimal, switching to an MSP is a lifestyle upgrade you’re paying a premium for. If your break-fix bills are $8,000/year and climbing, an MSP at $10,000/year buys you consistency and accountability.

The Hybrid Option

Not every small business fits neatly into either model. A few arrangements worth considering:

Block hours. Purchase 10 or 20 hours of support upfront at a discount. Draw down the block as needed. Good for businesses that need occasional help but not full managed services.

Co-managed IT. You have an internal IT person or office manager who handles tier-1 issues. The MSP handles infrastructure, security, and anything beyond their skill level. Typically priced at a lower per-user rate because the scope is narrower.

Project-based engagements. Hire an MSP for a specific project — migrating to Microsoft 365, upgrading your network, implementing MFA — and return to break-fix for ongoing support. Works well when your infrastructure is stable and you only need outside help for transitions.

Making the Decision

The simplest framework: calculate what you’re actually spending on IT support annually, including your own time dealing with problems. If it’s under $3,000 and your systems are stable, break-fix is working. If it’s over $6,000 or you’ve had even one serious outage in the past year, start talking to MSPs.

Get quotes from at least two providers. Ask for a sample contract upfront before any meetings. Watch how they handle the question of what’s out of scope — it tells you more about how they’ll treat you as a client than their sales pitch does.