I have worked across real estate, technology, services, communications, robotics, and infrastructure. To an outside observer, this looks scattered. To me, the pattern is consistent.
Every industry I have entered followed the same arc: identify a fragmented or poorly structured market, map the commercial engine, define the operating system, assemble the required assets, build the software and interfaces, create the distribution and communication layers, instrument the operation, and convert the resulting system into a company, platform, or reusable infrastructure.
The surface industry changes. The underlying architecture does not.
This is why I call myself a systems entrepreneur rather than a founder in any single category. The thing I build is not a specific company — it is the system that produces companies. The platform, the operating model, the infrastructure, the distribution, the communications layer — these are the durable assets. Individual businesses are instances of the system.
This insight has practical implications. It means every component should be designed for reuse. A CRM built for one company should be architected to power several. A communications layer built for field operations should serve any venture that involves human communication. An evidence capture system built for AI governance should work for any autonomous system.
The portfolio compounds when the infrastructure is shared.