Most businesses only think about IT support after something breaks. By then, the conversation is already reactive—and reactive IT is expensive IT. This guide gives you the framework to evaluate, buy, and manage IT support intelligently, whether you're starting fresh or reconsidering your current provider.
Break-Fix vs. Managed IT: The Real Difference
Break-fix is transactional: something breaks, you call someone, they fix it, they send an invoice. There's no ongoing relationship, no proactive monitoring, and no predictable cost. For very simple environments with rare IT needs, this can work. For anything beyond email and basic devices, it's a risky foundation.
Managed IT (MSP) is relational: you pay a predictable monthly fee and the provider takes ongoing responsibility for keeping your systems monitored, secured, patched, and supported. The incentive structure is different—an MSP earns more when things don't break, because break-fix events consume their labor.
Break-fix rewards the wrong behavior. The more things fail, the more the provider bills. Managed IT inverts this: prevention is profitable for both sides.
The practical difference shows up most in security. Break-fix providers respond to incidents. Managed IT providers (when doing their job properly) catch the conditions that lead to incidents before they happen—unpatched systems, suspicious login patterns, misconfigured cloud settings.
What "Fully Managed" Should Actually Include
The term "managed IT" is used loosely. Before signing anything, confirm which of these are genuinely in scope:
Non-negotiable inclusions:
- Helpdesk support with defined response times — Staff should have someone to call or email when something isn't working, with a written SLA on how fast they'll respond
- Patch management — Operating system and application updates applied on a schedule, not whenever the provider gets around to it
- Endpoint monitoring — Computers and devices actively watched for signs of failure, unusual behavior, or security events
- Antivirus/EDR — Managed endpoint protection on every device, with someone actually reviewing alerts
- Microsoft 365 or Google Workspace administration — User setup, offboarding, license management, and permissions
- Backup verification — Not just confirming that backups are configured, but that they're actually running and restorable
Confirm whether these are included or extra:
- After-hours emergency response (many MSPs charge extra for this)
- Security awareness training for your staff
- Monthly reporting and health reviews
- New user onboarding and device setup
- Line-of-business application support
- Physical hardware procurement
The SLA: Your Safety Net
A Service Level Agreement defines what "support" actually means. Without one, "we'll get to it" is a complete policy. A real SLA specifies:
| Issue Type | Definition | Reasonable Response Target |
|---|
| Critical | Complete outage or security incident affecting the whole business | < 1 hour acknowledgment; active work until resolved |
| High | Significant issue affecting one person's ability to work | < 4 hours acknowledgment |
| Standard | Non-urgent issue or question | Same business day or next business day |
The SLA should also specify:
- Business hours (and what happens outside of them)
- Whether after-hours emergency coverage is included or billed separately
- How to escalate if an issue isn't being resolved in the promised timeframe
- Consequences if SLAs are consistently missed (this is rarely in contracts, but worth asking about)
Pricing Models and What to Expect
| Model | Typical Range | Best For |
|---|
| Per-user managed (fully managed) | $75–$150/user/month | Knowledge workers; standardized environments |
| Per-device managed | $30–$75/device/month | Manufacturing or field teams with many devices per user |
| Flat monthly retainer | $500–$5,000+/month | Defined scope; smaller or simpler environments |
| Break-fix hourly | $100–$250/hour | Very occasional needs; simple environments |
For a typical small business of 10–25 employees, fully managed IT with cloud administration, monitoring, helpdesk, and security runs $1,500–$4,000/month. Businesses with compliance requirements (healthcare, legal, financial) typically pay more because the security and documentation work is more intensive.
Compare this to the cost of a single significant security incident—typically $25,000–$75,000 for a small business when you factor in downtime, recovery, potential regulatory penalties, and reputation damage. Managed IT is risk management, not just tech support.
Red Flags in IT Support Agreements
- Multi-year contracts with heavy exit penalties. Reputable providers are confident enough in their service to offer reasonable exit terms. A 3-year lock-in with 90-day notice and penalty fees is a trap, not a partnership.
- "Unlimited support" with no defined SLA. Unlimited is meaningless without a promised response time. This language exists to sound generous while committing to nothing.
- Pricing that seems too low to be sustainable. $20/user/month almost certainly means reactive-only support with minimal proactive work. Corners are being cut somewhere—usually on security.
- No documentation or asset inventory. A good MSP can tell you exactly what's in your environment within 30 days of onboarding. If they can't, they aren't managing anything—they're just reacting.
- They own your credentials or accounts. Your Microsoft tenant, domain registrar, cloud accounts, and passwords belong to you. Any provider who retains ownership of your accounts has leverage over you and is creating a hostage situation, intentionally or not.
- Vague scope definitions. "We handle everything IT" is not a scope. Get specific lists of what is and isn't included.
⚠️ Most important question to ask any MSP: "If I cancel tomorrow, what do I walk away with, and will you give it to me immediately?" The answer tells you everything about how they view the relationship.
What Good Onboarding Looks Like
The first 30–60 days with a new IT provider establish whether the relationship will work. A disciplined onboarding process includes:
- Full environment inventory — Every device, every software license, every cloud account, and every admin credential documented
- Security baseline assessment — MFA status, patch levels, antivirus coverage, and identity management verified across the board
- Access audit — Who has admin rights, what the current offboarding process is, and whether former employees still have active accounts
- Runbook creation — Documented procedures for common issues, escalation paths, and emergency contacts
- Communication setup — How do your staff reach support? What's the ticketing system? Who's the primary contact?
If an MSP wants to start billing before completing onboarding documentation, that's a warning sign. You shouldn't be paying for managed services until the provider actually understands what they're managing.
When to Switch Providers
Switching IT providers is disruptive, which is why many businesses stay with underperforming ones too long. These are legitimate reasons to make the move:
- Response times consistently miss the agreed SLA
- Security incidents that weren't caught proactively (unpatched systems, breaches from known attack vectors)
- You can't get a clear answer on what's in your environment
- No documentation exists of what has been done or configured
- Staff are consistently frustrated and losing trust in IT support
- The provider resists giving you access to your own accounts or documentation when asked
Before switching: get a full documentation package from your current provider, confirm you have admin access to all your own accounts, and allow adequate transition time (30–60 days minimum) for the new provider to get up to speed before the old one is fully off-boarded.
💡 Talk to Veloxant About Your Situation — Free Consultation
Related Reading