The Most Expensive IT Problems Are Never Technical

I've been on both sides of the desk. Years in sales before I ever touched a switch, then IT and networking, and now running PointerTech with my co-founder. That order turned out to matter more than I expected, because the hardest lesson of building an IT services company had nothing to do with hardware.

It has to do with what happens after the fix.

The ticket that taught me

Early on, we handled a network issue for a client. Intermittent drops, the kind of problem that's annoying to reproduce and easy to underestimate. We found it, fixed it, closed the ticket. Clean work. I was proud of it.

Two weeks later I learned the client was unhappy. Not with the fix. The fix held. They were unhappy because for three days their team had no idea what was going on, whether it was being worked on, or when it would end. From our side, we were heads-down solving it. From their side, we had gone dark.

The network was fine. The relationship wasn't.

What sales taught me that IT didn't

In sales, silence kills deals. You learn early that people can handle bad news, delays, even mistakes, as long as they're not left guessing. Somehow, when I moved into IT, I forgot this. Technical work rewards deep focus, and deep focus feels like an excuse to stop communicating.

It isn't. A client who hears "we've isolated it to the firewall config, expect a fix by Thursday" on day one experiences a completely different outage than a client who hears nothing until Thursday. Same downtime. Same fix. Wildly different trust.

So we changed how PointerTech operates. Every open issue gets a status update on a schedule, even when the update is "still investigating, here's what we've ruled out." Especially then. "Here's what we've ruled out" sounds like nothing, but to a client it's proof that someone competent is on it.

The uncomfortable part

The reason this lesson was expensive is that no metric caught it. Our resolution times were good. Tickets closed. Uptime looked great on paper. If you only watched the dashboard, we were doing everything right.

The gap showed up in quieter ways. Slower replies from the client. A second opinion they didn't mention until later. You don't lose IT clients in one dramatic moment. You lose them in the silence between updates, one unanswered "what's the status?" at a time.

What I'd tell anyone running technical work for other people

Your clients can't evaluate your technical work. Most of them genuinely can't tell a great fix from a mediocre one. What they can evaluate, with total precision, is how it felt to work with you while things were broken.

That's not a reason to do worse technical work. It's a reason to stop treating communication as the soft part of the job. In services, it is the job. The config change takes twenty minutes. The trust takes years, and it compounds or erodes with every incident.

I came into this industry through a side door, from sales, and for a while I treated that background as something to live down. Turned out it was the most useful qualification I had. Not because it made me better at closing deals, but because it taught me what silence costs.

If you're technical and you've been ignoring this side of the work, start small. Pick one open issue today and send an update nobody asked for. Watch what it does.

Etamar Levy is the co-founder of PointerTech, an IT and networking services company built on the idea that technology problems are people problems first.