Why I build in two worlds
Physical infrastructure and digital products seem like completely different worlds. They are not.
There is a moment when you realize that everything you do is actually the same thing.
For me, it was somewhere in an airport — I can’t remember which one, after enough travel they start to look alike — when I was simultaneously working on a procurement document for a water infrastructure project in Southeast Asia and on the code for one of my digital projects.
Two laptop windows. Two worlds, I always thought.
But in that moment, I saw it: I was doing exactly the same thing.
Infrastructure is infrastructure
A PPP project — a public-private partnership for a bridge, a water treatment plant, a port — works like this: you bring a public need and private capital together, structure the risks, and build something that lasts for decades without requiring your daily attention.
That is also what a good digital product does.
You build a system. You structure the logic. And when done right, it works while you sleep.
The materials are different — concrete versus code, procurement procedures versus product design — but the underlying logic is identical: building systems that sustain themselves.
What most people miss
People who work in public infrastructure often view digital products as something intangible. Too fast, too volatile, no physical substance.
People in the tech world look at public procurement and see bureaucracy. Too slow, too many layers, too little innovation.
Both groups are wrong.
What they miss: the principles are universal. Governance, risk allocation, long-term value creation — these are not concepts that belong to concrete or to software. They belong to the act of building something that outlasts the people who conceived it.
Why I do both
Not because I want two careers. But because the combination gives me something most people in either field lack: distance and perspective.
When I’m stuck in the complexity of a procurement process, the part of my mind that works on digital products thinks in systems, in scalability, in user experience. That helps.
When a digital project risks becoming too abstract, my background in physical infrastructure reminds me that something must ultimately work for real people, in the real world, over the long term.
That interplay is not accidental. I cultivate it deliberately.
This is not an identity crisis
People sometimes ask me: “But what are you, exactly?”
Advisor. Founder. Builder. Those kinds of answers.
The real answer is simpler: I build infrastructure. The nature of the material is secondary.
Physical or digital — it always comes down to the same thing: creating something that delivers value without constant attention. Something scalable. Something others can use long after you’ve moved on to something else.
That is what drives me. On both sides of the screen.