The IT industry has normalised an experience so bad that most businesses have stopped expecting anything better. Here is what bad IT support actually costs your business — and what good looks like.
Ask a business owner what they think of their IT provider and you will hear one of two things. Either resigned acceptance — “they’re fine, they fix things when they break” — or barely concealed frustration that finally spills over in a ten-minute rant about the last incident that took four days to resolve.
Almost no one says “our IT provider is genuinely excellent. They make our business better. We recommend them.”
That gap — between what the industry consistently delivers and what businesses actually need — is not an accident. It is the predictable result of an industry that has been allowed to define quality on its own terms, where the standard is “the system is up” rather than “the business is thriving.”
The Industry Has Normalised a Very Low Bar
The IT support experience most Melbourne businesses have been conditioned to accept:
You call the helpdesk. You explain your problem to someone who needs it explained again three minutes later. You are assigned a ticket number. You hear nothing for two hours. You follow up. You are told the technician is “looking into it.” You follow up again. Eventually someone fixes the thing, closes the ticket, and sends you a satisfaction survey that you do not have time to fill in.
If this sounds familiar, you are not alone. It is the standard experience. And because it is the standard experience, most businesses have simply stopped expecting anything different. They have adapted. They work around the IT provider rather than with them. Staff develop personal relationships with one technician who “actually gets it” while treating the rest of the helpdesk as a last resort.
This is not IT support. This is IT endurance.
What “Keeping the Lights On” Actually Means
The phrase is so common it has become invisible. “We keep the lights on.” “We ensure uptime.” “We make sure systems are available.”
What it actually means: we will respond when things break. We are reactive, not proactive. Our job begins when you have a problem and ends when the problem is technically resolved. What happens to your business between those points is not our concern.
Keeping the lights on is the minimum viable product of IT support. It is the floor, not the ceiling. And most IT providers have convinced the market to accept the floor as if it were the ceiling.
The difference between a lights-on IT provider and a genuine technology partner is the difference between a landlord who fixes the heater when it breaks and an architect who designs a home you actually want to live in.
The Hidden Cost Nobody Measures
Every time someone in your business has to wait for IT support, find a workaround, or abandon a task because a system is not working, there is a cost. It is not on the IT provider’s invoice. It is on your payroll.
The calculation most businesses have never done:
- A 30-person business with one IT-related frustration per person per day — something that doesn’t work as expected, something that requires a workaround, a question that goes unanswered — averages perhaps 15 minutes per person.
- 30 people × 15 minutes × 220 working days = 1,650 hours of lost productivity per year.
- At an average salary cost of $60,000 per year ($30/hour), that is $49,500 per year in productivity lost to IT friction.
That number does not include the hours spent on hold with the helpdesk, the cost of staff disengagement when technology does not work, or the revenue opportunities missed because systems were unavailable at the wrong moment.
These costs are invisible on the P&L but entirely real. And they are the direct result of an IT provider whose measure of success is ticket closure time, not your business outcomes.
What a Bad IT Experience Does to Your Staff
There is a softer cost that is harder to measure but impossible to ignore once you start looking for it.
When technology consistently does not work the way it should — when updates break things, when the same problem recurs three times in a month, when the helpdesk treats every call as an interruption to their day — your staff disengage from technology altogether.
They stop reporting problems because they have learned it is easier to work around them. They develop a quiet cynicism about any technology investment: “We’ll get new software and it won’t work for three months.” They stop using systems to their full capability because they don’t trust that the capability will be there when they need it.
This culture of low expectation is one of the most damaging things an IT provider can create in a business. It is also entirely preventable.
The businesses where technology is treated as an enabler — where staff genuinely trust that their tools will work and that problems will be solved quickly and without friction — have a measurably different relationship with change. They adopt new tools faster. They get more value from technology investment. They are more productive.
The difference is not the technology. The same Microsoft 365 tools, the same infrastructure, the same hardware. The difference is the experience of using them.
Why IT Providers Are Built This Way
Understanding why the experience is so consistently poor requires looking at how IT businesses are structured and how they measure success.
Tickets, not outcomes. The dominant metric in managed IT is ticket volume and closure time. An IT provider that resolves 200 tickets a day with an average response time of 23 minutes looks like a high performer by industry benchmarks. But if 80 of those tickets are the same five recurring problems that should have been solved permanently six months ago, the metric is hiding a failure. Counting tickets is not the same as improving outcomes.
Helpdesk economics. First-level helpdesk support is staffed to handle high volume at low cost. That means junior staff, scripts, and a strong incentive to close tickets quickly rather than thoroughly. The business model depends on volume. A provider that reduced ticket volume by 50% by solving root causes would earn less revenue, not more — which creates a structural disincentive to actually fix the underlying problems.
Relationship at the wrong level. Most IT providers have their primary relationship with the person who manages IT day-to-day, not with the CEO, COO, or operations lead who actually owns the business outcomes technology should be enabling. The conversation stays technical. It never becomes strategic.
No skin in the game. A fixed-fee IT contract does not automatically align the provider with the client’s outcomes. An IT provider being paid the same whether the business is thriving or frustrated has no financial reason to do more than the minimum the contract requires. The incentive is to appear competent, not to actually improve things.
What CX in IT Actually Looks Like
CX IT Services is named for what it stands for, not as a marketing shortcut. Customer Experience is the operating principle, not the tagline.
What that means in practice:
Proactive, not reactive. The measure of success is not how fast we respond when things break — it is how rarely things break. We monitor every client environment 24/7 and resolve emerging issues before they become incidents. Most problems your staff never know about because they are dealt with before they affect anyone.
Root cause, not ticket closure. When a problem recurs, we treat it as a systems failure, not a helpdesk task. We investigate why it keeps happening and fix it permanently. Recurring tickets are a signal that something is wrong with the environment, and that is our responsibility to address.
Business outcomes, not uptime metrics. Our quarterly reviews are not about SLAs and ticket averages. They are about how technology is affecting your business — what is working, what is not, where we can improve outcomes, and what should be on the technology roadmap for the next 12 months.
One account manager who knows your business. Not a different person every time you call. Not a ticket queue that anyone might pick up. A named account manager who understands your business, knows your staff by name, and takes personal accountability for the quality of your experience.
Staff who answer the phone. Our helpdesk picks up. Not an automated system, not a queue you wait in for 45 minutes. A Melbourne-based engineer who knows the client environment and can start solving the problem immediately.
The CX Standard We Hold Ourselves To
We measure our success by a question we ask our clients: would you recommend us without hesitation?
Not “are you satisfied with the service?” Satisfied is a low bar. You can be satisfied with an IT provider who simply keeps things running. The question is whether the experience of working with us is so consistently good that you would put your professional reputation on the line to recommend us to someone you respect.
That is the standard we hold ourselves to. Not uptime. Not average response time. Not ticket closure rates.
Would you recommend your current IT provider without hesitation?
If the answer is anything less than an immediate yes, you already know the answer to the question underneath that question.
Talk to us about what a different IT experience looks like for your business.
