I’m Not Anti-Spending. I’m Anti-Ambiguity.

Business owners spend money all day long: payroll, insurance, equipment, software, vehicles, professional services. Spending money is part of running a company.

But put a significant IT recommendation in front of someone and you may hear something like this:

“It’s hard to replace something that ain’t broken.”

We heard that recently in a customer conversation, and we think the customer had a point.

The equipment was working. Nobody was complaining about it, and there had not been an outage. From the customer’s perspective, the recommendation sounded a lot like: this thing is getting old, so we think you should buy a new one.

That is not much of a business case.

People who work in IT naturally think about manufacturer support dates, warranty status, security updates, expected hardware life, replacement lead times, and what happens if a critical device fails. A business owner may not have any of that context unless we provide it.

If all of that gets compressed into “it’s old,” we are asking the customer to trust the conclusion without giving them enough information to make the decision.

In this case, the conversation changed when the recommendation became more specific. Instead of treating age as the reason to replace the equipment, the discussion shifted to finding the manufacturer’s actual end-of-support date and planning around that.

The customer’s reaction changed immediately:

“That is a genius idea right there. I love it.”

Then:

“Let’s do that.”

Same equipment. Same eventual expense. But now the customer had a reason, a timeline, and a way to plan for it.

Three Questions Every IT Recommendation Should Answer

Before approving a significant technology expense, a business leader should be able to get clear answers to three questions:

1) Why does this need to happen?

“Because it’s old” is rarely enough.

Maybe the device is no longer receiving security updates. Maybe the warranty is ending. Maybe capacity is becoming a problem. Maybe failure would create unacceptable downtime. Maybe there is a compliance requirement or a known support deadline.

The point is to identify the actual business reason behind the recommendation.

2) When does it need to happen?

Not every legitimate IT need is urgent.

Some things should be addressed immediately. Others belong in next year’s budget. Still others simply need a date when everyone agrees to review them again.

A recommendation becomes much easier to act on when the customer knows whether “replace this” means this month, this year, or sometime before a known support deadline.

3) What happens if we wait?

This is where the real tradeoff becomes clear.

If waiting six months changes very little, say that.

If waiting means operating without security updates, losing manufacturer support, or increasing the risk of a costly outage, say that too.

The goal should not be to make every technology issue sound urgent. The goal is to make the consequences of waiting understandable.

Sometimes the Right Answer Is “Not Yet”

This is something IT providers, including Kosh, have to be willing to say.

Not every aging piece of technology needs to become this month’s project.

Sometimes the right recommendation is to replace something now. Sometimes it is to budget for next year. Sometimes it is to establish a trigger and keep watching it.

A useful IT roadmap should help separate what needs action now from what simply needs a plan.

That recent customer conversation was a useful reminder for us. When someone pushes back on an IT expense, the answer is not always to explain the technology harder. Sometimes we have not made the decision clear enough yet.

Business owners are not necessarily anti-spending.

They are anti-ambiguity.

---

Disclaimer

The information contained in this communication is intended for limited use for informational purposes only. It is not considered professional advice, and instead, is general information that may or may not apply to specific situations. Each case is unique and should be evaluated on its own by a professional qualified to provide advice specifically intended to protect your individual situation. Kosh is not liable for improper use of this information.