When IT Support Is the Problem

I've walked into decorated goods businesses where the IT support relationship was the single biggest constraint on what the business could do. Not the ERP. Not the staff. The IT support company — a provider that didn't understand the software, blocked integrations for vague reasons, took days to respond to critical issues, and billed hourly for problems that kept recurring because the root cause was never fixed.

The owner had been with them for years. The relationship felt too embedded to change. And so the business carried on, working around the IT support rather than with it.

The Warning Signs

The clearest indicators that your IT support is a problem rather than a solution:

• "We don't support that software." If your IT provider doesn't support your ERP or production management system — the core of how your business operates — that's a fundamental gap. Generic IT support that handles Windows and printers but not the systems you actually depend on isn't fit for purpose.
• "That's a security risk." Used as a veto without explanation. There are genuine security considerations with integrations and cloud tools. But "security risk" said without specifics is often a way of avoiding work the provider doesn't know how to do.
• Response times measured in days. If a critical system issue takes more than 2 hours to get a response during business hours, the service level doesn't match the support you need.
• The same problems keep recurring. An IT support company that fixes symptoms without addressing root causes will bill you indefinitely for the same recurring issues. If you've reported the same problem more than twice, ask why the root cause hasn't been resolved.
• You don't know what you're paying for. An IT support arrangement you can't explain — multiple invoices, unclear scope, ad hoc billing — is usually a sign the relationship was never scoped properly.

What Good IT Support Looks Like

Good IT support for a decorated goods business has a few defining characteristics:

It understands your stack. Not just Windows, Office, and the router — but your ERP, your B2B portal, your production management tool, and how they connect. When an integration has a problem, your IT support should be able to investigate it. If they can't, they shouldn't be your first call for systems issues.

It's proactive. Monitoring that flags problems before they cause downtime is standard in a good managed IT service. You shouldn't be calling your IT provider because something has already broken — they should be calling you to let you know there's a risk before it materialises.

Response times are defined and contractual. Critical issue (business is down): 30-minute response, same-day resolution. Standard issue: 4-hour response, next business day resolution. These should be in writing and consistently delivered.

Pricing is predictable. A fixed monthly fee for a defined scope of support means you know what you're spending. Per-hour billing creates a perverse incentive for slow resolution and discourages you from calling when you should.

Evaluating Your Current Provider

Before deciding to change, answer these questions about your current provider:

1. Do they support all the business-critical software you run — including the ERP and any specialist tools?
2. Have they proactively identified and fixed a risk in the last 12 months, or do you only hear from them when something is already broken?
3. What was the last critical issue, and how long did it take to resolve from the moment you called?
4. Have you reported the same problem more than twice in the last year?
5. Can you describe, clearly, what you're paying each month and what that covers?

If more than two of these produce unsatisfactory answers, the relationship is worth reviewing.

Switching Without Disruption

The main reason businesses don't switch IT support providers is fear of the transition. The fear is understandable. A poorly managed handover can cause disruption. A well-managed handover almost never does.

The key is documentation. Before any handover, you need a complete IT estate document: all hardware, all software licences, all credentials (stored securely), network configuration, backup arrangements, and any vendor contracts. Without this, the new provider inherits a black box and spends their first months discovering what's there rather than improving it.

A good incoming provider will insist on a discovery process before taking over the relationship. They want to know what they're taking on. If they don't ask for it — if they're willing to take over without understanding the estate — that's a warning sign about how they operate.

The outgoing provider should cooperate with the handover. Most MSA or IT support contracts include an obligation to cooperate. If yours doesn't, or if your current provider is obstructive during the transition, that tells you something about how they've been operating throughout the relationship.

Common Questions

What should good IT support look like?

It understands your business software, is proactive rather than reactive, delivers defined response times contractually, and charges a predictable fixed monthly fee. If any of those four aren't true for your current provider, the relationship is worth reviewing.

What are the signs your IT support is holding you back?

They don't support your core business software. They block integrations without explanation. Response to critical issues takes hours. The same problems keep recurring. You don't know what you're paying for each month.

How do you switch without disruption?

Document your full IT estate before the handover: hardware, software, credentials, network, backups. A good incoming provider will insist on a discovery process. A clean handover document makes the transition almost entirely risk-free.