The most important technology is not always the technology people talk about the most.
Very often, the opposite happens.
A technology becomes truly important when people stop thinking about it and simply depend on it.
Cloud computing is a good example. APIs are another. Payments, identity, authentication, mapping, logistics data and countless other layers now sit quietly behind products we use every day. Most end users never see them. Yet without them, entire businesses stop working.
That shift from product to infrastructure is something I find particularly interesting.
Infrastructure is not necessarily glamorous. It is usually judged by a different standard: reliability, interoperability, trust and the amount of friction it removes.
When it works, it disappears.
When it fails, everyone notices.
This matters because the next generation of businesses will be built on increasingly complex stacks of data, automation and machine intelligence. The visible application may get the attention, but its quality will depend on the layers underneath it.
AI makes this even more obvious.
People focus naturally on models and interfaces, but a useful AI system also depends on clean data, permissions, identity, context, auditability and dependable connections to the systems where work actually happens.
The same logic applies in mobility.
A vehicle is becoming a connected data object long before the industry has fully agreed on how that information should be stored, shared, verified and trusted across its lifecycle. Manufacturers, fleets, repair networks, insurers, leasing companies and future owners all interact with fragments of the same asset, but the underlying record is still fragmented.
That creates a classic infrastructure problem.
The opportunity is not simply to create another dashboard. It is to create a trusted layer that makes other products, decisions and transactions better.
I have learned to look at technology opportunities through that lens.
Does this product solve one task, or can it become a system others depend on?
Does it add another interface, or does it remove friction between existing systems?
Does its value increase as more participants use it?
Can it become invisible infrastructure rather than remain a visible tool that users must constantly think about?
The strongest infrastructure businesses tend to have a few things in common.
First, they solve a problem that repeats. Infrastructure becomes valuable through frequency. If a problem happens once a year, the economics are different from a problem embedded in thousands of daily interactions.
Second, trust matters. A system that sits underneath critical business decisions cannot be approximately reliable. It must earn confidence over time.
Third, integration matters as much as invention. Great infrastructure rarely replaces everything around it. It connects systems that already exist and makes them work better together.
Finally, infrastructure compounds. Once a layer becomes part of the workflow, replacing it becomes costly. Not because users are trapped, but because the system becomes woven into how value is created.
For founders, this changes how we should think about defensibility.
A beautiful interface can be copied. A feature can be reproduced. Distribution can shift quickly.
But a trusted layer connected deeply to customers, partners, data and operations can become much harder to replace.
That does not mean every startup should try to become infrastructure. Most should not.
But it is worth asking a more ambitious question when you build technology: are you creating something people use, or something other systems can eventually rely on?
The next generation of major companies will include both.
My bet is that some of the most valuable ones will be the technologies nobody notices anymore, because they have become part of the foundation.