The Ashton Solutions Blog - Ashton Solutions

IT Isn't a Commodity. It Just Gets Bought Like One.

Written by Jim Abbott | 11/18/26, 11:59 AM

"IT is a commodity." A business owner said that to me recently. He's right about how much of our industry sells IT. He's wrong about what it costs him to buy it that way.

Last week I met the owner of a manufacturing company. He’s in his early 30s, bought the business about 18 months ago, and he's doing exactly what a good new owner should do: looking at every line item and asking whether it's earning its keep. He’s also working to find trusted resources who can educate him on areas in which he doesn’t yet have a great deal of knowledge.

I introduced myself as someone who provides business technology consulting and managed IT. He didn't hesitate.

"That's a commodity. I just re-signed with the company that was here when I got here. It's not that important."

I've heard some version of that sentence for years. And honestly, I understand where it comes from.

How IT Became a Commodity

By my count (and I have a spreadsheet to back it up) there are roughly 200 IT providers in greater Cleveland, and a lot of them sell the same thing the same way: a per-user price, a help desk number, a list of tools, and a promise of 24/7 monitoring and proactivity. When every proposal looks the same, the only thing left to compare is the price.

That's what a commodity is. Corn. Steel. Road salt. The product is identical no matter who you buy it from, so you buy from whoever is cheapest or most convenient.

Our industry did this to itself. Providers raced each other to the bottom, stopped talking about outcomes, and started talking about seat counts. Business owners took the hint.

So when an owner tells me IT is a commodity, I don't think he's naive. I think he's been taught to see it that way.

Yes, Some of IT Really Is a Commodity

Let's be fair. Parts of what we do are interchangeable. Microsoft licenses cost what they cost. A laptop is a laptop (not really). An internet circuit is an internet circuit. Resetting a password is not an art form.

If that were all IT was, buying on price would be the right call.

But none of those things is what actually protects your business. What matters is everything that happens around them:

  • Who knows how your environment is actually built, and has it documented?
  • Who notices that a backup has been quietly failing for three weeks?
  • Who tells you the server running your ERP is past end of life before it dies on a Tuesday morning with a full production schedule?
  • Who is asking where your business is headed, and whether your technology can get you there?
  • When something does go wrong, who answers the phone, and do they already know your systems?

Those answers are different with every provider. That's the opposite of a commodity.

The Tell

Here's the part of that conversation that stuck with me.

Toward the end of our time together, I mentioned a few of the organizations we work with. His whole posture changed. He was genuinely excited to hear who we support, to the point that he said, "A reference from one of them would get me to switch to you right now."

Think about that for a second. Nobody asks for a reference before buying road salt. You don't call another company to ask how their steel supplier handled a crisis.

You ask for references when the quality of the work matters, when the people matter, and when the wrong choice costs you something real. In that moment, he wasn't shopping for a commodity. He was shopping for judgment, and for proof that someone he respects had already put that judgment to the test.

He already knew IT wasn't a commodity. He just hadn't had a reason to say it out loud.

What Commodity Thinking Costs a Manufacturer

For a manufacturer, none of this is abstract.

Downtime stops the floor. When the ERP goes down, the network drops, or a machine on the line loses its connection, it isn't an inconvenience. Orders stall. People stand around. Shipments slip. Concern grows among clients. A provider that costs a little less each month can cost a lot more in a single afternoon.

Security isn't optional anymore. Attackers go after manufacturers because they know downtime is expensive and the pressure to pay is high. They also know that many manufacturers have the same mindset that IT doesn’t really matter. Customers are asking about your security. Insurers ask harder questions at every renewal. "Good enough" IT tends to fall apart the moment someone asks you to prove it.

Knowledge walks out the door. In a lot of acquired businesses, the real knowledge of how IT works lives in one person's head. Sometimes that person is on staff, sometimes at the provider. If it isn't documented, you don't own it. Documentation isn't glamorous, but it's the reason problems get solved fast instead of slowly.

Technology should follow the business plan. An owner 18 months in usually has a plan: grow, add a line, make an acquisition, improve margins, maybe sell someday. Every one of those depends on technology. A commodity provider keeps the lights on. It doesn't sit down with you to build a six-month, one-year, and three-year roadmap tied to your budget.

And if a sale is ever part of the plan, know that a buyer's diligence team will take a hard look at your IT. Commodity IT rarely gets through that review without a remediation line item attached to it.

This Isn't About Switching

Here's where I may surprise you. I told that owner to stay with his current provider until his contract is up next year.

Partly because changing providers well takes planning. It's not something you do on the strength of one conversation. And partly because he works with one of the better providers out there.

That's what makes this story worth telling. He has a good partner, and he still describes them as a commodity. That tells me the problem isn't only the provider. It's how the relationship is being used.

If you treat your IT provider like a utility, you'll get a utility. If you expect a partner who understands your business and pushes you to plan ahead, the good ones will step up. The others will show you pretty quickly that they can't.

Questions to Ask Before Your Next Renewal

Whoever you work with, these are worth asking:

  1. When did we last review our technology against our business plan, not just our ticket history?
  2. Is our environment documented well enough that someone new could support it tomorrow?
  3. When were our backups last tested with an actual restore?
  4. What are the three biggest risks in our environment today, and what's the plan for each?
  5. What needs to be replaced in the next 12 to 36 months, and is it in the budget?
  6. If we were hit with ransomware tonight, what happens in the first hour? Who calls whom?
  7. When I call, does the person who answers know who we are?

If your provider answers those clearly, congratulations. You don't have a commodity. Hang on to them.

If the answers are vague, it's worth a conversation before you sign again. (We put together a longer checklist for evaluating your current IT provider if you want to go deeper.)

Where Ashton Stands

We've been doing this since 1994, and some of our client relationships go back decades. We're not going to win the race to the bottom, and we're not trying to.

What we do try to win on is how it feels to work with us. When clients describe Ashton, they tend to use the same four words: prompt, personable, persistent, and polite. That doesn't happen with a commodity. It happens when people know your environment, know what's at stake, and take ownership of the outcome.

IT isn't a commodity. Don't let anyone, including your provider, sell it to you like one.

Start with a conversation. Talk to an expert at Ashton.