The corners never align. You tuck one side into the other, smoothing the elastic until the cotton gathers into a lumpy, defiant ball that looks nothing like the crisp rectangle in the tutorial video. I spent twelve minutes on the bedroom floor last Tuesday trying to master the geometry of a fitted sheet, and eventually, I just rolled it into a cylinder and shoved it into the back of the linen closet. It is a small, ordinary failure of form and function.

It is the realization that some things are designed to be difficult to fold, not because the physics are impossible, but because we lack the specific patience required to outlast the material.

This feeling of being outmatched by a simple object is exactly what it feels like to buy enterprise software in the modern age. It is 4:40 PM on a Friday. Marcus is sitting in a chair that has lost its lumbar support, staring at a server rack through a glass partition. He has a contractor starting on Monday morning.

The contractor needs to remote into the environment to begin a database migration. Marcus has the server, he has the hardware, and he has the bandwidth. What he does not have are the Remote Desktop Services Client Access Licenses (RDS CALs).

The Commodity Question

Marcus opens a browser tab. He types “how much is an RDS CAL for Windows Server 2022” into the search bar. This is a reasonable question. It is a commodity request. He is not asking for a bespoke cloud architecture designed by a team of architects in black turtlenecks.

He is asking for a SKU-a digital permission slip that exists in millions of instances across the globe. Forty-five minutes later, Marcus is on his third website, and he is staring at a form. The form has twelve fields.

It wants to know his company’s annual revenue. It wants to know how many employees work in his HR department. It wants his phone number, his corporate email address, and a “preferred time for a brief introductory discovery call.”

None of these variables change the code that Microsoft generated for that license. The revenue of his company does not alter the bits and bytes of the CAL. But the market has decided that the price is a secret. In this ecosystem, the real cost isn’t just the dollar amount on the invoice; the cost is the afternoon you have to burn just to find out what that dollar amount is.

The Regulatory Shadow

“The goal of that obfuscation isn’t to ensure safety; it’s to filter out the people who aren’t desperate enough to pay whatever Larry decides to charge.”

– Ethan K.-H., Building Code Inspector

Ethan tells me that this is a classic “regulatory shadow.” In his world, if you want to build a deck, the rules are written down in a book. You follow the rules, you pay the fee, you get the permit.

But occasionally, a municipality will intentionally obfuscate the “ancillary impact fees.” You can’t find them on the website. You have to go down to the basement of City Hall and talk to a guy named Larry who only works on Thursdays.

In the world of IT procurement, “Request a Quote” is the digital equivalent of Larry’s basement. Everyone assumes this opaque pricing exists to handle genuine complexity. We tell ourselves that because server environments are diverse-ranging from Windows Server 2016 to the newest 2025 builds-that a human must intervene.

This is a convenient fiction. The complexity is real, but it is solvable by a calculator, not a salesman. The opacity exists because a confused buyer is a more profitable buyer. If you don’t know the baseline price, you can’t argue with the “value-added” markup.

If you look at the aggregate data of procurement cycles, the average B2B buyer now spends 17 hours in research for every $1,000 spent on software. In plain human terms, that is like working two full days for free just for the privilege of handing a vendor your money.

This is the tax we pay for the “privilege” of being sold to. We have normalized the idea that our time is a renewable resource that vendors are allowed to harvest at will.

The inventory of a standard IT closet is a study in specific particulars. There are the Cat6 cables with the snagless boots, the rack-mounted UPS units with their lead-acid batteries, the Cisco switches with their blinking amber lights, and the Dell PowerEdge servers running dual Xeon processors. Everything has a part number. Everything has a physical reality.

The End of a Hostage Situation

When a market normalizes “request a quote” for a commodity item like a license, it has quietly decided that your Friday afternoon at 4:40 PM belongs to them. They want to put you into a CRM. They want to assign you a lead score. They want to see if you’re a “whale” or a “minnow.”

This is why transparency in this niche is so jarring. It’s the same feeling you get when you walk into a mechanic’s shop and the prices for a brake job are actually painted on the wall instead of whispered behind a clipboard. It changes the power dynamic.

By providing a built-in CAL calculator and instant delivery, they are acknowledging a truth that the rest of the industry tries to hide: the buyer usually knows exactly what they need, they just need someone to stop standing in the way of the transaction.

If Marcus knows he has 20 users who need to hit a Windows Server 2022 Remote Desktop environment, he doesn’t need a “discovery call.” He needs 20 User CALs and he needs them before he leaves for the day so he can enjoy his weekend without the specter of a failed Monday morning hanging over his head.

The Map vs. The Gatekeeper

We should talk more about the “setup guidance” aspect of these transactions, too. In the Mitchell-esque tradition of detailing the mundane, consider the actual process of installing a CAL. You open the Remote Desktop Licensing Manager. You right-click the server. You select “Install Licenses.” You enter the agreement number.

It is a sequence of clicks that takes three minutes if you have the right numbers, and three days if you don’t. When a vendor provides that guidance upfront-identifying whether a Device CAL (best for shift workers sharing a kiosk) or a User CAL (best for individuals on multiple devices) is the right fit-they are performing a service.

But that service shouldn’t be a gatekeeper. It should be a map. You don’t hide the destination just because you’re offering a map.

A 15-Minute Peace

Marcus eventually found what he needed. He bypassed the “Quote Engines” and the “Strategic Account Managers.” He found a place that treated his time as if it had a value equal to the product being sold. He bought the 20-pack.

He received the email while the sun was still hitting the top of the server rack. He entered the keys. The green checkmarks appeared in the Licensing Manager. He didn’t have to talk to Larry in the basement. He didn’t have to explain his company’s revenue to a stranger. He just did his job.

There is a specific kind of peace that comes from a 15-minute turnaround. It’s the same peace I feel when I finally give up on the fitted sheet and realize the bed stays made regardless of how the spare linen looks in the closet.

It’s the realization that the “correct” way of doing things-the way the industry insists upon-is often just a set of hurdles designed to justify the existence of the hurdles themselves. In a world of perpetual subscriptions and “price on request,” a perpetual license with a clear price tag is an act of rebellion.

It recognizes that for the IT admin, the system engineer, or the small business owner, the “value” isn’t in the conversation. The value is in the access.

I think about that lumpy fitted sheet in my closet. It’s still a mess. It’s still a failure of the “prescribed” method. But the door is closed, the bed is comfortable, and I didn’t spend my entire evening fighting with the elastic.

There is a point where you have to decide what your time is worth. In the world of RDS licensing, that point usually comes right around 4:45 PM on a Friday, when you realize that the most expensive thing in the room isn’t the server-it’s the silence of a vendor who won’t give you a price.