In 1986, a structural engineer stood on a pier in the Chesapeake Bay, squinting at a hairline fracture in a concrete pylon. He was distracted by the wind and the fact that his thermos had leaked coffee into his glove.

When his assistant asked for the width of the crack to record in the log, the engineer muttered, “Call it three millimeters.” He didn’t use a caliper. He didn’t even get out of the boat. He just looked at it and gave a number that felt right for the moment.

By 1992, that three-millimeter figure was the “historical baseline” in the city’s infrastructure database. By 2004, when the crack was measured at three-point-one millimeters, a six-figure repair project was authorized because the “rate of decay” had supposedly spiked. The entire project was predicated on a number that originated in a soggy glove and a distracted mind.

The Laundered Logic of Procurement

We do this every day in business, but we pretend we don’t. We treat numbers like they are biological entities that grow more respectable with age. In reality, numbers are laundered by the system until they look like measurements.

Take Fabio. Fabio is a mid-level IT administrator for a regional logistics firm. He’s good at his job, but he’s currently three hours deep into a server migration that should have taken ninety minutes.

His phone rings. It’s the procurement lead, someone who thinks “The Cloud” is literally a weather formation. They need to know how many Remote Desktop Services (RDS) licenses to include in the quarterly budget forecast. Fabio hasn’t done the headcount yet. He hasn’t audited the shift rotations or the new contractor pool in the warehouse.

“I don’t know,” Fabio says, rubbing his eyes. “About forty? Give or take.”

– FABIO, IT Administrator

The “about” dies right there. The “give or take” is left on the cutting room floor. Within three weeks, that forty appears in a budget document. Two months later, it’s in a renewal template. A year later, it’s in a compliance report.

By the time the next audit cycle rolls around, Fabio is gone, but the forty remains. It has become an objective truth. Nobody remembers that it was birthed in a moment of exhaustion and uncertainty. It has been laundered by the system until it looks like a measurement.

Planting Ghosts in the Ledger

I’ve seen this from the other side. As an insurance fraud investigator, I spend my life looking for the seams where reality meets the “reported figure.” I have to admit, I haven’t always been the paragon of precision myself.

Years ago, I was investigating a claim involving a flooded basement full of high-end furniture. I saw a pair of lounge chairs that looked like authentic Eames pieces. I’d seen a price tag on something similar once-it started with a two. I wrote down “estimated value: $2,400 each” without checking the labels or the serial numbers.

I was wrong. They were decent knock-offs worth maybe four hundred dollars total. But because my report went into the claims system with my “authority” attached to it, that twenty-four hundred dollar figure became the anchor for the entire settlement negotiation.

The insurance company spent weeks defending a number I’d pulled out of thin air while trying to avoid stepping in a puddle. I felt the weight of that error when the adjusters started arguing about “depreciation percentages” based on my initial lie.

Systems are designed to strip away nuance. A database doesn’t have a column for “Fabio’s Gut Feeling.” It has a column for “Quantity.” When you enter a number, the system assumes you have performed the labor required to arrive at that number.

It assumes there is a receipt, a measurement, or a calculation behind the digit. When there isn’t, you are essentially planting a ghost in your company’s ledger.

This happens with alarming frequency in the world of software licensing, particularly with Windows Server environments. A sysadmin gets a notification that the 120-day RDS grace period is expiring. There’s a sudden, frantic need to get legal.

They have to decide between User CALs or Device CALs. They have to figure out if the thirty-two people in the sales office all need their own license, or if the ten shared kiosks in the warehouse are the better way to count.

Setting Fire to Company Cash

In the heat of that moment, people reach for “forty.” It’s a nice, round, safe-looking number. But licensing isn’t a “safe-looking” game; it’s a “did-you-pay-what-you-owe” game.

If you buy forty when you need sixty, you’re out of compliance. If you buy forty when you only need twenty-two, you’ve just set fire to a stack of company cash that could have gone toward better hardware or a decent coffee machine.

The problem is that once you buy those forty, you will almost certainly buy forty more at the next renewal. Why? Because the forty is the baseline. No one wants to be the person who says, “Actually, we’ve been over-licensed for three years because Fabio was tired one Tuesday.” It’s easier to just keep the ghost alive.

The Permanent Structural Flaw

This is why I’ve become obsessed with tools that force the “why” before the “what.” In my personal life, I’m currently staring at a half-assembled sideboard from a Swedish furniture giant. I’m missing three cam-locks and a very specific dowel.

I could “estimate” that a similar screw from my junk drawer would work. I could force it. But I know that the moment I do, that “estimate” becomes a permanent structural flaw in the house. I’ll be sitting at dinner three years from now, and the top will sag because I didn’t want to drive back to the store for a fifty-cent part.

In the digital space, the equivalent of that fifty-cent part is a proper calculation. When you’re dealing with something as notoriously Byzantine as Microsoft licensing, you can’t afford to be Fabio. You need a way to translate your messy, human office environment into a clean, defensible number of licenses.

Killing the Ghost

This is where specialized resources become the barrier between a guess and a fact. Instead of looking at a monitor and guessing how many people might be logging in simultaneously, IT managers should be using a dedicated

RDS CAL Store

to run the numbers.

A calculator doesn’t have “off days.” It doesn’t have “about forty” in its vocabulary. It takes the variables-the number of devices, the number of users, the version of Windows Server-and spits out a number that has a pedigree.

When you use a tool like that, you aren’t just getting a number; you’re getting a receipt for your logic. If an auditor or a CFO ever asks why you bought exactly thirty-five licenses instead of a round forty, you can point to the logic. You can show the math. You’ve killed the ghost before it ever had a chance to haunt the budget.

We often mistake “speed” for “efficiency.” Fabio thought he was being efficient by giving a quick answer so he could get back to his migration. In reality, he was being the opposite. He was creating a tail of technical and financial debt that would follow the company for years.

It’s about recognizing that every number we report is a seed. If we plant a guess, we grow a thicket of confusion that eventually someone has to hack through. If we plant a calculated, verified figure, we grow a system that actually makes sense.

The Ten-Minute Difference

I think back to that engineer on the Chesapeake Bay. If he’d just taken thirty seconds to pull a tape measure out of his pocket, the city might have saved half a million dollars. If I had checked the labels on those chairs, I wouldn’t have spent weeks feeling like a fraud in a suit.

And if you take the time to audit your server users before the grace period runs out, you won’t be the person defending a “forty” that never really existed.

The next time someone asks you for a figure under pressure, resist the urge to be helpful with a guess. Say, “I’ll get back to you with the actual number in ten minutes.” Those ten minutes are the most valuable time you’ll spend all week. They are the difference between a measurement and a myth.

The Cost of a Guess

The ghost of a guess eventually haunts the ledger where the bill must be paid.

When you finally get that real number, the relief is palpable. It’s like finding that missing dowel for the sideboard. Suddenly, everything fits. The top sits flush. The drawer doesn’t stick.

You realize that the pressure to “just give a number” was entirely internal. Most of the time, people would rather wait ten minutes for the truth than spend ten years repeating a lie.

So, use the calculators. Audit the workstations. Count the humans. Don’t let the “forty” in your life become a ghost that nobody is allowed to question.

Because eventually, someone will question it, and you’ll want to be the one who has the measurement in your hand, not just a soggy glove and a memory of a ham sandwich.