I see your IT leaks. And I can't look away.

I have a few annoying habits.

Especially annoying for those who don't want to see it...

One of them: I spot IT waste faster than you can say “change request.”

I see it in dashboards that no one trusts but everyone exports to Excel.

In servers that run 24/7 for an application that mainly... waits.

In licenses that happily continue for users who are long gone.

In “just” adding an extra environment, because cleaning up is a hassle.

And in cloud resources that you don't use, but dutifully pay for every month—like a subscription to guilt.

And then there's habit number two. Which is even more annoying to some.

I can't keep my mouth shut.

Not because I like to talk or want to be right.

But because I see too often that companies pay money so that a supplier can hide problems that they could also solve.

Much of today's IT is too slow, too expensive, and too complex.

In this blog, we're going to talk about too expensive.

Not “a little awkwardly expensive.”

But structurally expensive.

By expensive, I mean: you pay much more than you get in return.

Twice as expensive is the rule rather than the exception.

Ten times as expensive is not uncommon.

And yes... I also encounter a hundred times as expensive. Sometimes even a thousand.

The strange thing is: no one consciously chooses this. It just happens. Step by step. With every “quick fix,” every new tool, every upgrade “because it has to be done,” and every environment that no one dares to shut down anymore.

So: if you like throwing money out the window, that's fine. Your choice.

But let me know where and when.

I'll be happy to catch it.

Patch Tuesday is not maintenance. It's gambling.

Most software rolled out today isn't just “a little messy.”

It's structurally substandard.

Why? Because time-to-market and “look what we've built” are more important than: does it work, will it continue to work, and can people work with it normally?

Take Windows Update. Patch Tuesday increasingly feels like roulette.

In May 2025, a Windows 10 security update (KB5058379) triggered BitLocker recovery on certain systems because a process crashed and Windows went into Automatic Repair mode. Good luck if you don't have your recovery key handy.

In April 2025, Microsoft also warned of BSODs with a secure kernel error after updates (including KB5055523). “Known Issue Rollback” is the band-aid solution.

And in March 2025, Microsoft saw a significant increase in RDP disconnects after security updates (KB5053598). Handy, especially if your business runs on “just a little remote access.”

Hello? Who's paying the double bill here?

The point is not that bugs exist. That's inevitable.

The point is that we have come to accept them as normal. And that we then work around them with extra tooling, extra processes, extra “monitoring,” extra people.

It's like solving a leaky faucet by putting a bigger bucket under it.

And then there's the security angle. That's even more painful.

In July 2024, a faulty CrowdStrike content update crashed Windows systems. A security product that causes the crash itself: that's an expensive kind of irony.

Palo Alto had a critical PAN-OS vulnerability (CVE-2024-3400) that allowed unauthenticated code execution in certain configurations.

Cloudflare had an outage in November 2025 due to a bug in the generation of Bot Management feature files.

Trend Micro had to release patches in 2025 for critical Apex One zero-days (command injection) with reports of exploitation.

Tell me which CIO or IT manager is happy to foot the bill.

Bad software is not an IT problem.

If you don't take action, it's a waste production factory. And that's exactly what more and more companies are doing, fortunately.

Best practices without context are costly myths.

A major cause of IT costs is not “the cloud.” Or “licenses.”

It is complexity.

And especially: the wrong complexity for your scale.

Think of your organization as a village that is slowly growing into a city.

With 10 houses and one intersection, it works fine without rules. Everyone looks left, then right, and drives on. No problem.

But what if it grows to 100 houses? Then you suddenly need priority signs.

With 1,000 houses, you get cyclists, children, suppliers, rush hours. Then bike paths and clear routes make sense.

And if you're Amsterdam, you can't avoid a traffic plan: traffic lights, priority routes, separated traffic flows, dynamic management. Without that, it becomes chaos.

But turn that logic around.

If you install bike paths, traffic lights, a traffic control center, and a team of traffic engineers in that village of 10 houses, no car will drive any faster.

You're mainly buying bureaucracy, maintenance, coordination, tooling, and meetings. And you're creating problems you didn't have before. And the bill for all this beauty is mounting.

That's exactly what happens in IT.

We set up enterprise architecture for an application with 40 users.

We build a Kubernetes cluster “because it scales so well” for a workload that fits perfectly on one decent VM.

We add layers “for governance” and then spend months filling in the gaps between those layers.

And in the meantime, your costs are rising: more specialists, more management, more incidents, more dependencies. Everything becomes significantly more expensive without you noticing, even a simple change.

On the other hand, if you are Amsterdam but you're still driving around with village rules, you're also paying. Only differently: with traffic jams, breakdowns, fires, and an IT team that is constantly pushing instead of steering.

The conclusion is simple:

Complexity is not a badge of honor. It is a choice of scale.

And before you adopt best practices, frameworks, or “recommended architectures,” first test one thing:

Does this fit our scale... today?

I'll point out the leak. You turn off the tap.

Unnecessary IT costs are rarely “bad luck.”

They are almost always the result of one thing: choices that once seemed logical... but that no longer fit your scale, your team, or your ambitions.

And the annoying thing is: you only see it when someone points it out to you.

I am that someone.

I cut through layers. Through “best practices.” Through stacks of tools. Through architecture that sounds impressive in a meeting. And I ask one simple question:

What do you really need — and what have you accidentally ended up maintaining?

Because that's where the leak is.

Not in “more budget.” Not in “another dashboard.”

But in unnecessary complexity, duplication of work, and systems that are expensive to maintain.

Free money.

 

Shall I come and (kindly) annoy you?

Schedule a no-obligation 30-minute call.

You won't get a sales pitch. No 60-page report.

But you will get a sharp diagnosis:

• where the waste is

• what choices are causing it

• what is the fastest, safest route back to simple and affordable

Know where the money is leaking.

How you can stop it.

I'm seriously coming to bring you free money.

Guarantee: once you hear the amounts, you won't find me annoying anymore ;)