None of these will show up on an invoice. All of them show up in how your week actually goes.
Most IT relationships don’t end because something broke. They end quietly, a year or two after the business has changed shape and the support around it hasn’t. The provider that was a great fit at 60 people is still doing the same things at 150. The tickets still close. The lights are still on. But the job has gotten bigger than the relationship, and nobody’s said so out loud.
At this size, that gap is worth naming early. Below are seven signs we hear about most often from IT directors and operations leads at organizations in the 100-to-300 range, the ones who already have a managed services provider and are quietly wondering whether it’s still the right one.
1. You’re the one who finds the risk, not them.
Every provider will say they monitor your environment. The real test is what they’ve told you about, unprompted, in the last few months. Aging hardware nobody flagged until it started throwing errors. A licence renewal that snuck up on the budget. A backup job that’s been silently failing for weeks. We worked with a fast-growing community organization whose server hardware was already limiting performance well before anything failed outright. Because someone was actually watching that infrastructure day to day, we modernized it on our own timeline instead of theirs, including the systems holding records the organization considered culturally significant, without losing a single one in the move. That’s the difference between a provider who reacts well and one who’s actually watching.
Here’s what that looks like on our end. Every client environment runs through a live Client Portal that tracks device health, backup jobs, and vulnerabilities continuously, alongside 24/7/365 monitoring, not a checklist someone works through when they get a chance. The standard we hold ourselves to is simple: you shouldn’t be the one telling us something’s wrong. If a client is finding their own risks, that’s a sign the monitoring behind them isn’t doing its job.
2. Every specialized project sends you shopping for another vendor.
At 60 people, one strong generalist can cover most of what you need. At 150 or 200, you’re generating problems that require real depth: network design across multiple sites, physical security integration, cloud architecture decisions, compliance requirements tied to a specific industry. If your provider’s response to anything outside day-to-day support is “let us find someone for that,” you’re already paying two vendors to do one job, you just haven’t noticed because the invoices arrive separately.
Having that range in-house matters for one practical reason: it takes work off your plate. When we designed a warehouse WiFi network for Lekker Foods, a food distribution company, we were working around freezer units, loading docks, and metal racking that all interfere with signal, using the same account team that already knew their business. When a municipal government needed its surveillance system upgraded, our status as a Verkada Gold Partner meant that project ran through people who already understood the client’s environment, not a new firm starting from zero. A growing legal practice we modernized needed new firewalls, identity management, and phone systems all at once, and got all three from the same team in one coordinated plan instead of three separate procurement processes. That’s what the breadth is actually for: one relationship to manage instead of three, and nobody new to bring up to speed every time a project falls outside a generalist’s comfort zone.
Learn more about our end to end services and IT Solutions
3. Your reports are a list of what happened, not a picture of where you stand.
Ticket counts and uptime percentages tell you a provider was busy. They don’t tell you whether your exposure is trending up or down. Ask your provider a different question: who, right now, can open the folder with your financial records or your HR files, and why. If the honest answer takes more than a few minutes to produce, that’s not a small gap. Permissions tend to grow the way most things do at this size, one request at a time, over years, until nobody remembers granting most of them. A monthly ticket report will never catch that, because it was never built to.
We took on a private company whose SharePoint access had grown exactly that way, one request at a time, over years, until nobody could say with confidence who could reach the client contracts folder. Nobody had done anything wrong. We rebuilt the permission structure so the answer to that question became obvious again, and it’s the same reason our quarterly business reviews are built around a risk trend, not a ticket tally. A report that only tells you what already happened is easy to produce. One that tells you where you actually stand takes more work, and it’s the work that’s supposed to justify the relationship.
4. One person’s calendar is your disaster recovery plan.
Ask yourself honestly: if your main contact left tomorrow, would the relationship survive the transition, or would you be starting over? A lot of smaller providers run on one or two senior technicians who carry the institutional knowledge in their heads. That’s fine until it isn’t. A provider built for organizations your size usually has some depth to it: engineers who’ve been there for fifteen or twenty years working alongside people who joined last year, so the knowledge doesn’t leave the building when one person does.
This is deliberate on our end. Our engineers include people who’ve been with the company for over 30 years, working next to hires who came through our co-op program last year, plus a dedicated account manager and a provincial help desk staffed with full-time analysts and field technicians across BC. Ninety of our people are full-time, supporting communities across the province, and that structure exists specifically so a client relationship never depends on one person’s availability. If we lost a technician tomorrow, the account, the history, and the plan would still be there on Monday.
5. IT gets invited to fix things, never to plan things.
There’s a specific moment worth noticing: does your provider ever get asked into a conversation about where the business is headed, or only into the one about what just broke? A provider who understands your business well enough to sit in on strategic planning, and to say something useful once they’re there, is operating as a partner. One who only appears once a ticket is open is operating as a vendor, no matter what the contract calls the relationship.
We build for that seat at the table on purpose. Every managed services client gets a dedicated account manager whose job includes IT roadmap development and quarterly business reviews alongside day-to-day escalations. For clients weighing something like AI adoption, we run a guided discovery session that looks at strategy, data, and workforce readiness before any tool gets purchased, so the strategic conversation happens ahead of the buying decision.
6. You’ve learned to translate their explanations before you can use them.
This one’s easy to miss because you adapt to it without noticing. If you find yourself rephrasing what your provider told you before you can repeat it to your CFO or your board, that’s not a you problem. A provider worth keeping can explain a technical decision in terms a business owner already understands, without you doing the translation work in between.
One of our clients put it simply: they value being able to pick up the phone and talk to someone who speaks to them in language they understand, not a script. That’s the standard we hold our account managers and field technicians to. You’ll work with people who know your name and your environment, and who explain a decision the way they’d explain it to their own leadership team, because most of them have sat in that seat too.
At our core “We are the people behind technology”
7. The relationship only works as long as nothing changes.
Growth tends to be the thing that exposes this one. A new office, a shift to hybrid work, an acquisition, a new compliance requirement: any of these will show you fairly quickly whether your provider’s model was built to flex or just to maintain. We work with a law firm running about 30 people across three locations, with staff who are fully remote, partly remote, and constantly travelling between offices. It’s a genuinely complicated setup, and the fact that it simply works, day to day, without anyone thinking about it, is the actual measure of whether a provider has kept pace with the business or just kept the lights on.
We’ve seen the same test play out from the infrastructure side. Another growing legal practice came to us running on aging servers and an outdated phone system that couldn’t keep up with a fast-paced caseload. We rebuilt the network security, moved their phone system to Teams Voice, modernized identity management, and containerized their key applications for scalability, all as one coordinated plan rather than a series of one-off fixes as each piece aged out. The firm came out of it with a foundation built to keep absorbing growth, so the next expansion or acquisition doesn’t mean starting the rebuild over again.
Meet the team
<insert new video>
So what now?
None of these on their own means it’s time to make a change. Most are minor and easy to live with individually. Together, they usually mean the relationship has stayed the same size while the business kept growing around it, and that kind of gap tends to widen on its own if nobody addresses it.
The organizations that get ahead of it aren’t usually in crisis. They’re just paying closer attention to which of these seven sound familiar, and deciding it’s worth a conversation before a bigger problem forces one.
Recognize a few of these?
Tecnet works with growing BC organizations who need a technology partner sized for where the business is headed. We’ve been doing this since 1974, long enough to know the difference between a provider that’s busy and one that’s actually watching.