Inaugural Briefing: Why I Think Out Loud Here

Not a magazine. Not a how-to guide. More like a notebook with the door left open.

I am not writing here as an analyst handing out grades from the stands. I write in order to think. Some people think while talking, some while walking. I think while writing. This blog is simply the place where that happens in public.

If a thought turns out to be useful to someone, that genuinely pleases me. But the starting point is plain curiosity. Why does one company earn money effortlessly while an almost identical one goes under doing the same thing? What happens to work once software starts acting on its own? And who actually carries the responsibility when a machine decides? Questions like these do not let go of me. So I follow them, thoroughly, with numbers, and with a certain pleasure in taking things apart until they become simple.

The Question I Always Ask

My background is in accounting. That leaves a mark, though not the one people expect. What it mainly leaves behind is a question you can never switch off again: "Can you back that up?"

The question is uncomfortable. It ruins beautiful stories, polished pitch decks and half of all strategy buzzwords. But it is the reason the analyses here look the way they do. Numbers first, opinion second. Understand first, judge later. And when something surprising is left standing at the end, it is not because it sounds provocative, but because the arithmetic led there.

Between the Worlds

The most interesting problems of our time rarely sit inside a single discipline. They arise at the transitions, where four worlds talk past each other.

Technology speaks in systems and interfaces. Business administration speaks in margins and processes. Economics speaks in incentives and markets. And governance speaks in accountability and evidence.

Each of these languages is coherent on its own. But a company adopting AI has to speak all four at once, and that is precisely where most of them fail. That transition fascinates me. I like translating in both directions: deep enough to understand the details, and simple enough for anyone to follow. That is my benchmark. Whatever I cannot explain in plain language, I have not yet understood myself.

How I Think

Three habits run through everything published here.

First, I think in processes. Behind almost every outcome, good or bad, there is a sequence that somebody once built that way. Whoever sees the sequence also sees where it jams.

Second, I like turning the obvious upside down. The most interesting question is rarely "How does everyone do it?" but "What would happen if you did it exactly the other way round?" Sometimes the result is nonsense. Sometimes it is the actual answer.

Third, an analysis is only finished for me once the question "And what follows from that?" has been answered. Anyone can describe. It gets interesting at the consequences, meaning what you should decide differently, build differently, or better leave alone.

What Appears Here

Analyses of business models, artificial intelligence, platform economics and capital, from the finance perspective described above.

And, increasingly, a second thing: workshop notes. I experiment privately with AI agents, my own servers, my own systems, my own mistakes. Not because I am a software developer, but because I am convinced you only truly understand a technology once you have built it, paid for it and repaired it yourself. These notes from my own workshop get their place here, including the things that go wrong.

An Invitation

This is a space for thinking, not a broadcasting tower. If you find a thought useful, good. If you want to disagree, even better. The best pieces on this blog will probably be the ones that grew out of a contradiction.

Welcome to Ludwig Insights.