The Ghost in the Discovery Call
The Ghost in the Discovery Call

The Ghost in the Discovery Call

The Ghost in the Discovery Call

When the person selling you the future has never touched a cable.

The headset was pressing into my left temple, a dull, rhythmic throb that matched the flickering of the overhead fluorescent tube. On the other end of the line, the ‘Senior RDS Solutions Architect’-a title that usually costs at least $157,000 a year in overhead-was asking me if our servers were running on a Linux kernel. There was a long, ringing silence. I looked at the 47-inch monitor in front of me, displaying a complex web of Windows Server instances, and I felt a sudden, sharp clarity. This person had never touched a real infrastructure in their life. They were reading from the same 17-page PDF that I had downloaded three minutes before the call started. It is a peculiar kind of vertigo, realizing that the person you are prepared to hand $57,000 to for licensing advice is essentially a glorified search engine with a more polished accent.

I reached down and grabbed my shoe. A spider, thick-legged and ambitious, was traversing the baseboard near my feet. I didn’t think about it; I just swung. The thud of the leather sole against the wood was final. One less intruder in my space, but the one on the phone was still talking, unaware that I had just committed a small act of violence while he explained the ‘revolutionary’ benefits of the cloud-first transition. It’s funny how we prioritize these digital intrusions-the licensing audits, the compliance checks, the vendor calls-while the physical world just continues its messy, unscripted collapse.

I put my shoe back on, feeling the slight dampness of the carpet, and tried to focus on the architect’s voice. He was currently struggling to explain why 127 User CALs wouldn’t solve a connectivity issue that was clearly a DNS misconfiguration.

The Great Disconnect: Sociology Over Physics

This is the Great Disconnect. We have accepted the ‘Sales Engineer’ as a legitimate pillar of expertise when, in reality, it is often just pre-sales confidence wrapped in a branded fleece vest. The credentialing of enterprise software is fundamentally broken because it rewards the memorization of SKU lists rather than the calloused hands of actual implementation.

Sound is honest because it can’t hide its reflection. If a room is poorly designed, the echo will tell on you every single time. Software licensing is the opposite. It is designed to be a hall of mirrors where the echo is the point.

– Oliver K.-H., Acoustic Engineer

You ask a simple question about per-user vs. per-device allocations, and you get a 37-minute dissertation on ‘value-added ecosystems.’ It’s a defensive crouch. If they admit they don’t know how the licensing server actually interacts with the domain controller during a 7-day lease renewal, the illusion of authority vanishes. And in the world of high-stakes enterprise sales, the illusion is the only thing with a high margin.

[The echo is the point.]

The Apprenticeship Reversed

Expertise Gap Widening

73% Gap

27%

The ratio of practitioners to script-readers is inverted.

I’ve spent the last 17 years fixing things that ‘experts’ said were impossible, and I’ve realized that the democratization of software sales has created a massive expertise gap. Buyers have to become experts precisely because they can’t trust the sellers anymore. It’s a reversal of the traditional master-apprentice relationship. Now, the apprentice has the checkbook and the master has a script.

There is a specific kind of frustration that comes with knowing more than the person who is supposed to be guiding you. It’s like watching a pilot check the manual to see where the landing gear switch is while the plane is 700 feet above the tarmac. You start to wonder if the entire industry is just a series of nested scripts…

I told the specialist I’d give him 7 minutes to find the answer. He took 27. When he came back, he quoted a section of the EULA that had been deprecated 7 years ago.

The Cost of Brute Force vs. Surgical Precision

Vendor Recommendation

$77,000

Complete Infrastructure Overhaul

VS

Practitioner Fix

7 Minutes

Registry Key Correction

That’s not a glitch; that’s a lack of fundamental competence. It’s what happens when you let people who have never built a server manage a server budget.

[The hertz never lies.]

The Practitioner Mandate

🔨

Earned Knowledge

Through failure, not documentation.

🧩

Unique Systems

Deserve surgical fixes, not scripts.

🛑

Refusal to Stop

“Circle back” is not an answer.

We need experts who don’t just read the PDF, but who could have written it-or, better yet, who can tell you why the PDF is wrong. The expertise vacuum is real, and it’s growing every time a ‘specialist’ is minted after a two-day workshop.

If you’re dealing with a complex environment, say, a legacy setup where you need a specific windows server 2016 rds device calto maintain compatibility without breaking your entire CAL chain, the ‘official’ advice is almost always to upgrade everything.

The Price of Subscriptions

I looked down at the dead spider again. It felt like a metaphor for the vendor’s expertise-impressive at first glance, but easily crushed by the weight of a single practical question. We’ve built an entire economy on the idea that the person with the most polished slide deck is the one with the most knowledge. But knowledge is sticky. It’s messy. It’s something you get on your hands when you’re digging through event logs at 2:17 in the morning.

We accept that things will be broken, that the advice will be wrong, and that we will ultimately have to fix it ourselves. We pay a premium for the privilege of being ignored. It’s a Stockholm syndrome where the captor is a multi-billion dollar software conglomerate and the ransom is paid in annual maintenance fees.

I ended the call with the specialist after 47 minutes of circular logic. I didn’t get the answer I needed, but I did get a clear understanding of the terrain. I was on my own. I went back to the logs, back to the raw data, back to the things that don’t have a marketing budget. I found the conflict in 7 minutes. It was a registry key that had been overwritten by a group policy update 17 days prior. A simple fix. A practitioner’s fix.

👟

Taking Control

I took my shoe off and looked at it. A bit of spider guts on the heel. A small price to pay for a little bit of control over my environment. In the end, we are all just trying to make sense of the noise, hoping that the person on the other end of the line knows at least half as much as they pretend to. But hope is a poor strategy for infrastructure. I’d rather trust the hertz. I’d rather trust the shoe.

The pursuit of genuine expertise over scripted authority.