Seven signs your business has outgrown its current IT support

Seven signs your business has outgrown its current IT support

Good IT support should keep everyday work moving and help you make informed decisions about risk and investment. A provider that suited a smaller business may struggle once you add locations, extend trading hours or become more dependent on cloud systems. These seven signs help distinguish an isolated service failure from a relationship that needs to change.

1. The same problems keep generating tickets. Staff repeatedly lose access to shared files, printers stop working after updates, or the same application needs restarting every week. Each ticket gets closed, but the disruption returns. The issue is not necessarily slow support: it is the absence of investigation into the underlying cause.

Ask your provider to review the past three months of tickets and group recurring issues by service, device and cause. Request a named owner, a proposed permanent fix and a completion date for the most disruptive problems. Some fixes require investment, but your provider should explain the options. If repeated workarounds remain the only response, assess providers that can demonstrate a structured problem-management process.

2. One person holds all the knowledge

You ask for a change and hear, ‘Wait until our technician is back.’ Nobody else seems to know how your finance application connects, where the backups run or who manages your domain. Friendly, knowledgeable technicians are valuable; dependence on one person is a business continuity risk.

Ask what would happen if your usual technician became unavailable tomorrow. Another authorised engineer should be able to locate current documentation, understand critical dependencies and follow recovery procedures. Sensitive records belong in a secure, access-controlled system, not a personal notebook or an unprotected spreadsheet.

If documentation is incomplete, agree on a deadline to close the gaps. You do not need unrestricted administrator access for every employee, but the business needs a secure way to retain control if the support relationship ends.

• Request an inventory of key systems, suppliers, licence owners and renewal dates.
• Confirm who controls your domain registrar, DNS, cloud tenant and backup accounts.
• Ask for evidence that another engineer can support your critical systems using the documentation.

3. You cannot see what you are paying for

Invoices arrive reliably, but service reports do not. You cannot tell whether ticket volumes are rising, systems are being patched or recurring issues are being resolved. A list of completed tasks is not enough if it gives you no basis for decisions.

Request a concise monthly report and a regular service review. Focus on outcomes: response and resolution performance against agreed targets, repeat incidents, ageing tickets, patch exceptions, backup failures and outstanding risks. Averages can hide serious delays, so ask to see breaches and unresolved high-priority issues separately.

Reports should explain what needs your attention, who owns the next action and when it is due. Check that definitions are clear: an automated acknowledgement is not the same as an engineer starting work. If the provider cannot supply reliable information from its own systems, you will struggle to hold it accountable or justify future spending.

4. Support hours no longer match your business

Your Auckland office may close at five, but warehouse dispatch, hospitality operations or overseas customers may not. If a critical outage outside office hours goes into a queue until morning, the support arrangement no longer matches the business.

Check the agreement rather than relying on the phrase ‘24/7 support’. Monitoring, security investigation, telephone answering and hands-on remediation are different services. A network operations centre (NOC) may detect an outage without having authority to fix it; a security operations centre (SOC) may escalate an alert without providing full incident recovery.

Map your genuinely critical services and operating hours, then ask the provider to explain a realistic after-hours incident step by step. Confirm any exclusions and additional charges in writing. If the coverage gap cannot be closed, make it a firm requirement when comparing alternatives.

• Who receives an urgent call, and who can begin technical work?
• How is severity agreed, and what response target applies?
• Who can authorise emergency changes, and who keeps your team informed?

5. Security and recovery rely on reassurance

‘Everything is backed up’ and ‘we handle security’ are not evidence. Warning signs include no record of restore testing, unclear responsibility for security alerts, former staff retaining access, or administrator accounts without appropriate multi-factor authentication.

Ask for a review of access controls, patching, monitoring and recovery arrangements. It should identify exceptions as well as completed work. For backups, distinguish a successful backup job from a successful restore: choose a business-critical workload and request a documented recovery test with clear success criteria.

Agree how much data loss and downtime the business can tolerate, then check whether the recovery arrangements support those limits. Include cloud services rather than assuming the software vendor covers every recovery need. For businesses handling personal information, clarify how suspected breaches are escalated so you can assess obligations under New Zealand’s Privacy Act 2020. Repeated inability to demonstrate these controls is a strong reason to seek another provider.

6. Every change becomes an unexpected project

A new starter needs equipment tomorrow, a server reaches end of support, or a licence renewal arrives without warning. Some surprises are unavoidable. A constant stream usually means nobody is maintaining a forward view of your technology.

Ask for a rolling 12-month roadmap covering equipment replacement, software support dates, renewals, security priorities and planned business changes. It should separate essential risk reduction from optional improvements, with indicative budgets and dependencies. Your accountant or finance manager should be able to use it for planning.

For significant projects, expect a defined scope, accountable project manager, acceptance criteria and a rollback or contingency plan. An office move, for example, needs coordination between connectivity, equipment, suppliers and staff communications—not just a technician booked for moving day. If your provider can only react to requests, you may need a partner with stronger planning and project-management capability.

7. Accountability and ownership are unclear

Your support provider blames the internet company; the internet company blames the firewall. Meanwhile, staff cannot work. Another warning sign is discovering that contracts, subscriptions or key accounts are held in ways that make leaving difficult. Your provider cannot control every supplier, but it should define who coordinates diagnosis and escalation.

Before deciding to leave, put the service gaps in writing. Ask for an improvement plan with named owners, measurable outcomes and review dates. A constructive response may save the relationship; vague promises, repeated missed commitments or resistance to sharing business records suggest it is time to compare providers.

Choose a replacement against the gaps you have identified, not just the monthly fee. Ask prospective providers, including CoreTech, to explain their support coverage, reporting, security responsibilities and transition process in writing.

• Check notice periods, termination terms and responsibility for any remaining project work.
• Arrange a secure transfer of documentation, configurations, licences and privileged access.
• Agree on overlap, escalation contacts and rollback arrangements before switching support.
• After handover, remove old access and confirm monitoring, backups and support channels work.