The Question I Get Asked Most Often

There's a question I get asked almost every week, for 25 years now, in a thousand variations: "Is it worth fixing, or should I replace it?" Sometimes pointing at a computer, sometimes a server that hangs every morning, sometimes an entire network that's been "sort of working" for years. The question sounds simple. The person in front of me reasonably expects a short answer: "fix it" or "replace it." And every time, I resist the temptation to give it that way.

Not because I want to sell something more expensive. Quite the opposite: because the quick answer, whichever it is, has a decent chance of being wrong.

Why the question isn't what it appears to be

Early in my career, I thought the answer was purely technical: calculate the repair cost, calculate the replacement cost, compare them, state the number. It took several years to understand that this logic, however reasonable it sounds, answers the wrong question. Because the real question hiding behind "is it worth fixing?" is almost never just about the machine. It's about something bigger, which the client themselves often hasn't put into words yet.

What actually decides it

Over the years, I've settled on four questions that interest me far more than the age or price of the equipment.

The pattern of failure, not the failure itself

A single failure tells you almost nothing — they happen, on new and old equipment alike. What interests me is the pattern: is this the first time in five years, or the third time in three months? A machine that starts failing more often isn't giving you a problem — it's giving you a trend, and trends, unlike isolated incidents, almost always continue.

What exactly hangs on it

An old machine doing a supporting task doesn't carry the same weight as an old machine that a business's daily operation depends on. The exact same age, the exact same repair cost, can mean "fix it without worry" in the first case and "don't risk it" in the second. The question "what stops if this fails completely tomorrow?" often answers better than any technical spec.

The real cost of time, not just money

Repair cost is easy to write down on paper. Harder — but just as real — is the cost of slow operation, of waiting, of the disruption that will come back in a few months. A cheap patch that costs you half an hour of delay every day, for a year, has already cost far more than the replacement you avoided.

Where the business is heading, not where it stands today

This is the question the client themselves rarely asks, and I consider it the most important of all. A business preparing to grow — a new location, new hires, a new volume of work — has a different equation than one that simply wants to keep going steadily as it is. The same repair that's a wise choice for the second can be a delay of the inevitable for the first.

Why I resist the short answer

I could, honestly, always give the quick answer. I'd save time, maybe a few difficult conversations too. But I'd be betraying the one thing I actually have to offer after 25 years in this field — which isn't knowledge of how a machine gets fixed, but the ability to ask the four questions above before answering the first one. A client doesn't need me to know more about their own business than they do — they need someone who will ask them the right things, so their own answer comes out clear.

And there's one more reason, a more personal one. I've seen, more than a few times, what happens when someone gives the short answer without the right questions: a business that replaced something that didn't need replacing, or — worse — kept something that should have been replaced long ago, because someone said "it's still holding up" without asking what depended on it. The rush toward an answer is often more expensive than the decision itself.

The lesson behind the question

If there's one thing I'd keep from 25 years of these conversations, it's this: good technical advice is rarely a technical answer. It's a conversation about the business, disguised as a question about a machine. Whoever answers only the machine misses the point. And whoever learns to hear the real question underneath the spoken one rarely gives the wrong answer — even when that answer isn't the one their conversation partner expected to hear.

That's, ultimately, the work I do every day with MyeliTech: not saying "fix it" or "replace it" at first glance, but sitting down, asking, and arriving at an answer that fits your specific business — not a generic recipe. For businesses in Drama, Serres, Kavala, and across Greece.

If you have something in front of you asking you this same question, let's talk it through together — before you answer it in a hurry.