The clearest sign it’s time to leave your IT provider: you find out about problems from your staff instead of your provider. Add recurring fixes that never touch the cause, conversations that always end in a quote, and documentation only they can read — and you’re not describing bad luck. You’re describing a model. Some of it is fixable. Some of it is the business you’re paying for.
None of the seven signs below is about a bad week. Everyone has outages; everyone misses a ticket. These are patterns — and patterns in a service relationship are rarely accidents. They’re usually the model doing exactly what it was designed to do.
1. You learn about problems from your staff, not your provider.
Your team notices the shared drive is gone. Someone emails the provider. A ticket gets opened. That sequence — staff first, provider second — tells you nobody is actually watching the environment.
A managed environment works the other way around: the provider sees the failing drive, the expiring certificate, the strange login, and you hear about problems in the past tense, already handled. If the news always travels from your office to theirs, you’re paying for a fire department and calling it management.
2. The same problem keeps coming back.
A printer that drops off the network every month. A remote-access setup that needs the same restart every Friday. Each visit fixes the symptom, closes the ticket, and leaves the cause exactly where it was.
That’s not always incompetence. Under a per-incident model, it’s rational behavior — the recurring problem is recurring revenue. But even under a flat fee, repeat fixes mean nobody is asking why. Last year’s break shouldn’t come back this year. If it does, someone is patching holes with more patches.
3. Every conversation ends in a quote.
You ask a question; a proposal arrives. You mention a problem; a product appears. Over time the relationship stops feeling like advice and starts feeling like a pipeline — because it is one.
Watch for the tell: things get added, and nothing ever gets subtracted. A real advisor’s recommendations sometimes cost you nothing, and occasionally save you money. If the last three recommendations all carried a price tag from the same vendor lineup, the advice and the sales motion are the same department.
4. You’ve stopped calling about the small stuff.
This one hides in your own behavior. Staff live with the flaky monitor, the slow login, the workaround — because reporting it means a ticket, a wait, and re-explaining the setup to a stranger.
That learned silence is expensive. Small frictions multiply across every employee, every day, while the provider’s dashboard reads all-quiet the entire time. Support your people avoid using isn’t support. It’s a line item you’re paying monthly for.
5. Nobody but them knows how your environment works.
Ask yourself one question: if the relationship ended tomorrow, what would you actually have? Passwords, configurations, licensing, how systems connect — if the answers live only in your provider’s heads and tools, you’re not a client. You’re a hostage.
Undocumented environments don’t happen by accident. Documentation is the first deliverable of a well-run engagement, and it belongs to you. The test is easy: ask for your documentation this week, and watch what happens.
6. The person who knew your business keeps changing.
The engineer who understood your setup left. The account manager has changed twice. Each new face starts from zero — asking questions you answered two years ago, re-learning decisions that had reasons behind them.
Advice compounds only with continuity; churn resets it. Sometimes churn is growing pains. Sometimes it’s what happens after an acquisition, when the firm you hired quietly becomes a different firm with the same logo. Either way, you’re the one paying the re-learning tax.
7. They can’t help you answer the questions your clients and insurer are asking.
Cyber insurance renewals, client security questionnaires, a bank asking how data is protected — these landed on every business in the last few years, and they’re business-development questions now, not IT trivia.
Someone has to answer them in writing, with confidence, and stand behind the answers. If your provider’s response is a shrug, a delay, or “we’ve got antivirus,” you’ve outgrown them — or more precisely, the questions have.
Before you leave: some of this is fixable.
Here’s the honest part most switching articles skip. Several of these signs are worth raising before you walk.
Recurring problems (sign 2), staff who’ve gone quiet (sign 4), and revolving contacts (sign 6) are sometimes resourcing problems that a decent firm will fix once a client puts it in writing: here’s the pattern, here’s what has to change. Give them that chance. Switching has real costs in attention and disruption, and a repaired relationship keeps its history — which is worth something.
Two of these, though, are structural. A provider whose every conversation ends in a quote (sign 3) is showing you its business model. One that controls your documentation (sign 5) is showing you its retention strategy. Models don’t change because a client complained.
Whatever you decide, do one thing first: read your contract’s exit terms — notice period, data return, what you’re on the hook for — so the decision is yours to make, on your own schedule.
One bad month is noise; patterns are the model. Raise the fixable ones — recurring problems, staff who’ve stopped calling, revolving contacts — directly and in writing, and give the firm a real chance to respond. But if every conversation ends in a quote, or you couldn’t leave because only they know how your environment works, that’s not a service problem. That’s the design — and opting out of it is your call to make.
A few fair questions
Should we tell our provider we’re evaluating alternatives?
If you’ve raised the patterns in writing and given them a fair window, you don’t owe more than your contract’s notice terms. Professional providers see transitions regularly and handle them like adults — and a competent incoming provider will manage that handoff so you aren’t refereeing it.
What does switching actually involve?
Done right, it’s a sequence, not a leap: map the environment first, document everything, build in parallel, cut over quietly. We walk through how we run that sequence — including who owns the documentation — on our managed IT page.
What if only two or three of these signs apply?
The count matters less than the category. Three fixable signs are a conversation with your provider. One structural sign is a conversation with the market — and a reason to know which questions separate an advisor from a vendor before you start it.
If some of this reads uncomfortably familiar, book a conversation. Bring the pattern you’re seeing and you’ll get a straight read on whether it’s fixable where you are. Sometimes the honest answer is “raise it with your provider first” — and if that’s the answer, we’ll give it to you.
