Eighty-one percent of enterprise project delays are retroactively blamed on technical execution, even when the underlying cause was a procurement decision made by someone who never had to actually install the software.

It is a quiet, bloodless statistic, but it carries a weight that ruins weekends and ends careers. I’ve been thinking about this a lot lately, mostly because I spent twenty minutes this morning prying a jagged splinter out of my thumb. It was a tiny thing, almost invisible, but the way it throbbed made it impossible to focus on anything else.

It reminded me that in systems-whether they are biological or digital-the smallest foreign object, if forced into a space where it doesn’t belong, will eventually cause the entire organism to fever. In the world of IT infrastructure, those splinters are usually called “savings.”

The Spreadsheet as a Finished Story

Karim knew the fever was coming. He sat in a glass-walled conference room three weeks ago, watching his manager, Dave, scan a PDF of three different quotes for Remote Desktop Services licensing. Dave is the kind of person who views a spreadsheet as a finished story rather than a set of variables.

To Dave, a CAL-a Client Access License-is a commodity, like bulk paper clips or bags of salt for the water softener. If Vendor A offers it for X and Vendor B offers it for half of X, Vendor B is the moral and logical winner.

“It’s the same product, Karim. Microsoft is Microsoft. Why would we pay a premium for the exact same string of characters?”

– Dave, Infrastructure Manager

Karim tried to explain the difference. He talked about the “grey market,” about keys that are sold three times over, about the sudden, catastrophic deactivation that happens when an audit hits or a server refresh triggers a validation check. He talked about the value of having a human being on the other end of a phone line when the terminal server starts throwing “No License Server Available” errors at 3:00 AM on a Monday.

Dave didn’t hear him. Dave heard “IT wants a bigger budget for the same result.” He clicked send. He approved the bargain-basement reseller whose website looked like it had been designed in a fever dream in 2004.

Fourteen days later, the “instant delivery” promised by the reseller had turned into a forty-eight-hour email chain involving a guy named ‘Steve’ who only seemed to work between the hours of 2:00 AM and 4:00 AM in a time zone nobody could identify.

When the keys finally arrived, two out of the five packs wouldn’t activate. The error codes were cryptic, the kind of digital shrug that tells you the license has already been exhausted elsewhere. Karim spent his Tuesday night-and most of his Wednesday morning-trying to reach Steve. Steve had vanished. The support inbox was a black hole that returned nothing but automated “Delivery Status Notification (Failure)” pings.

When the buyer and user are different, the market optimizes for whoever clicks ‘approve.’

A Fundamental Glitch in Corporate Logic

This is where the split incentive reveals its teeth. Dave, the buyer, had already banked his win. On his quarterly report, he had successfully “reduced infrastructure licensing costs by 42%.” That was a line item. It was a victory. It was a bullet point in a performance review.

Karim, the user of the decision, was the one left holding the bag of broken activations and angry department heads who couldn’t get their remote teams logged into the Windows Server 2022 environment.

Parker N.S., a veteran aquarium maintenance diver who spends more time underwater than he does on dry land, once told me something that stuck: “When you’re thirty feet down in a shark tank with a cracked acrylic panel, you don’t care how much the purchasing department saved on the sealant.”

Parker’s life depends on the integrity of the materials someone else bought. In IT, we aren’t usually in danger of being eaten by sharks, but we are in danger of being eaten by the “post-mortem.”

In the meeting that followed the failed deployment, the word “cheap” never entered the conversation. Dave sat at the head of the table, looking disappointed. He didn’t talk about the reseller. He talked about “execution hurdles.” He talked about “unexpected technical friction.” He looked at Karim and asked, with a straight face, why the implementation had been so rocky.

It was a masterclass in redirection. By framing the failure as a “technical” problem, Dave successfully moved the spotlight away from the “procurement” problem. The savings stayed on his side of the ledger; the costs were moved to Karim’s side, disguised as “inefficiency.”

The Hidden Tax of the Bargain

This is the hidden tax of the bargain. You don’t pay it in dollars; you pay it in blood, in time, and in the slow erosion of your sanity. When you buy from a source that doesn’t provide real, hands-on setup guidance or perpetual, non-expiring licenses, you aren’t actually saving money.

You are just taking out a high-interest loan that your IT department will have to pay back under duress. Reliability isn’t a luxury; it’s a form of insurance against the “Dave” in your office.

I’ve seen teams lose an entire week of productivity because they tried to save three hundred dollars on a set of RDS CALs, only to realize too late that they had no path to resolution when the keys failed. They didn’t have a built-in calculator to verify their needs; they didn’t have a partner who understood the difference between a User CAL and a Device CAL for a mixed environment.

Find Your Tweezer

If you are the person who actually has to make the system work, your greatest ally is a vendor who realizes their job doesn’t end when the credit card clears. You need someone like

RDS CAL Store,

where the delivery is actually instant and the support isn’t a phantom named Steve.

The reality of modern business is that we are all, to some extent, at the mercy of people who prioritize the immediate “win” over the long-term “work.” I’ve made this mistake myself. I once bought a “professional grade” pump for a project because it was sixty dollars cheaper than the one I knew was good.

It worked for three days. When it died, it took out a three-thousand-dollar control board with it. I spent the next forty-eight hours explaining to a client why their system was down, while the “sixty-dollar saving” sat in the trash, mocking me.

Make the Invisible Visible

We have to stop letting procurement be a vacuum. If you’re an admin, you have to find ways to quantify the “Fix-It Tax.” You have to show that the $2,000 saved on a dodgy license reseller resulted in $8,000 of lost billable hours and three days of downtime. You have to make the invisible visible.

Because otherwise, the Daves of the world will keep clicking ‘go with this one,’ and you’ll keep being the one in the meeting, explaining why the “execution” failed, while the ghost of a discount haunts the room.

I finally got that splinter out this morning. It took a pair of tweezers, a steady hand, and a fair amount of swearing. My thumb still hurts, a dull reminder of what happens when something that shouldn’t be there gets forced in. I’m hoping Karim finds his own version of tweezers. I’m hoping he realizes that his time and his peace of mind are worth more than a discount key from a dead-end website.

The Reputation of Support

In the end, we get the systems we deserve, or rather, the systems we are willing to fight for. If we don’t demand quality in the sourcing, we can’t expect quality in the service. It’s that simple, and that difficult.

The next time someone forwards you a quote that seems too good to be true, don’t just look at the bottom line. Look at the support link. Look at the delivery window. Look at the reputation of the people standing behind the product. Because when the server goes dark and the boss starts asking questions, “Steve” won’t be there to help you. You’ll be on your own, prying out the splinters of someone else’s “good idea.”