Return to Learn

How Toronto SMBs Spot a Bad IT Provider: 10 Red Flags

How Toronto SMBs Spot a Bad IT Provider: 10 Red Flags

Most Toronto businesses don't leave their IT provider over one catastrophe. They leave after months of recurring issues, unclear ownership, and support costs that climb while nothing measurably improves. If your team keeps asking "why does this keep happening?", this checklist is for you.

Why this matters more than the monthly invoice

A weak IT provider costs you far more than their line item suggests. Downtime lasts longer because nobody owns the incident. Security gaps stay open because patching is inconsistent. Staff lose hours to problems that should have been prevented, and leadership slowly stops trusting IT recommendations altogether.

Cheap support is expensive. The bill just arrives somewhere other than the invoice.

10 red flags — and the question to ask about each

1. SLA language is vague

If your agreement says "best effort" without defined response and resolution targets by priority level, you have no recourse during a critical incident.

Ask them: "What is your guaranteed response time for a high-priority issue, in writing?"

2. Everything is reactive

If the same problems resurface monthly, you're paying for firefighting rather than prevention. Modern managed IT means automated patching, proactive alerting, and monitoring across servers, network and Microsoft 365 — so issues surface before your staff notice them.

Ask them: "What did your monitoring catch last month before it affected us?"

3. Nobody owns escalation

During a major incident, one person should own communications, vendor coordination and next actions. When ownership is unclear, incidents drag on while everyone waits for someone else.

Ask them: "Who is the named escalation owner when systems go down at 2am?"

4. Security is sold as an add-on

Multi-factor authentication, endpoint protection, patching standards and backup monitoring are baseline in 2026 — not occasional upsells. A provider treating them as premium extras is quietly transferring risk onto you.

Ask them: "Which security controls are included in our current plan, and which are extra?"

5. Documentation is thin or stale

If environment documentation, admin access records and network diagrams are incomplete, both incident response and any future transition become high-risk. If only one technician truly understands your setup, that's a single point of failure with a pulse.

Ask them: "Can you send us current network diagrams and an asset inventory this week?"

6. Reporting stops at "tickets closed"

Ticket volume tells you nothing about whether things are improving. You need trend reporting: recurring root causes, risk posture, and performance against service targets over time.

Ask them: "Are our recurring root causes trending down quarter over quarter?"

7. Surprise line items

One of the most common complaints we hear is some version of "our IT guy kept charging extra every month and we never knew why." If an "all-inclusive" agreement still generates regular surprise invoices for routine support, the scope is probably unclear by design.

Ask them: "What specifically falls outside our monthly fee?"

8. Backups are "green" but never tested

A dashboard showing successful backups means very little if restores are never actually performed. Plenty of businesses discover their backup was unusable at the worst possible moment.

Ask them: "When did you last perform a test restore, and can we see the result?"

9. No roadmap conversation

If your provider never discusses lifecycle planning, budgeting, licensing or risk-reduction priorities, you have support — not technology leadership. Quarterly planning should be routine.

Ask them: "What's on our IT roadmap for the next 12 months?"

10. Communication degrades under pressure

This is the clearest signal of all. Good providers communicate more clearly during incidents, not less. If updates become vague or slow exactly when an outage is running, that tells you how the relationship performs when it matters.

The five-minute scorecard

Answer honestly. Three or more "no" answers means your setup needs review:

  • Do we have defined response and resolution targets in writing?
  • Do we receive meaningful monthly service and risk reporting?
  • Is backup restore testing documented and scheduled?
  • Is there a clear escalation owner for critical incidents?
  • Are recurring root causes trending down each quarter?
  • Do our invoices consistently match the agreed scope?
  • Would we survive losing our provider's single most knowledgeable technician?

The local question Toronto businesses forget to ask

Remote support handles most issues, but not all of them. Network faults, hardware failures, Wi-Fi problems and new-site setups sometimes need someone physically present, same day. National providers and offshore help desks often can't deliver that reliably in the GTA.

Ask them: "If we need someone onsite in Vaughan or downtown Toronto tomorrow morning, what happens?"

When it's genuinely time to switch

Not every frustration warrants a change. These four do:

  • Repeated critical incidents with no root-cause correction
  • Security controls still inconsistent after multiple reviews
  • Support quality that depends on one individual rather than a process
  • Leadership no longer trusting the provider's recommendations

How to switch without chaos

A controlled transition protects you from the gap between providers, which is where most damage happens:

  1. Inventory systems, licences and every admin access path
  2. Export documentation and establish credential ownership in your name, not theirs
  3. Validate backup and recovery before cutover, not after
  4. Set a communication plan for staff and leadership
  5. Run a 30-day stabilisation period post-transition

Insist that admin credentials and documentation belong to your business. A provider reluctant to hand those over has just answered several of the questions above.

What good actually looks like

A capable IT partner makes reliability improve and risk decrease over time — and can show you the evidence. Response targets are written down. Restores are tested. Documentation is current and yours. Someone owns the phone at 3am.

MapleOps supports more than 100 businesses across Toronto and the GTA with a Canadian team and genuine 24/7 coverage for critical systems, including overnight. If you want to know where you actually stand, our free IT health check reviews your security, backup, licensing and Microsoft 365 posture and gives you a written report — yours to keep whether or not you hire us.

Related reading