I recently listened to a panel discussion that was supposed to be about artificial intelligence. Like most technology conversations today, I expected to hear discussions about large language models, autonomous agents, productivity gains, and predictions about how AI will transform industries over the next decade. Those topics certainly appeared, but they were not what stayed with me after the discussion ended. What stayed with me was something much simpler and, in my opinion, much more important. The conversation kept returning to manufacturing, infrastructure, energy, robotics, workforce development, and execution. In other words, it kept returning to building. By the time the panel concluded, I realized that AI wasn’t really the story at all. AI was simply the catalyst exposing a much larger truth: the future will belong to the people and organizations that can take ideas and turn them into reality.

For the better part of the last twenty years, technology has been dominated by software. We have built incredible products, transformed entire industries, and created capabilities that would have seemed impossible only a generation ago. Software has allowed organizations to scale globally, communicate instantly, automate complex processes, and create entirely new business models. I have spent most of my career building software and helping organizations use technology to solve meaningful problems, so this is certainly not an argument against software. Quite the opposite. Software remains one of the most powerful tools ever created. However, somewhere along the way, I think many of us began treating software as the destination rather than the tool. We became fascinated by moving information while paying less attention to the systems responsible for moving everything else. The factories, power plants, transportation networks, supply chains, and physical infrastructure that make modern life possible gradually faded into the background of the conversation. They never stopped mattering; we simply stopped talking about them.

What makes the current AI wave so interesting is that it is forcing us to rediscover the importance of those systems. Artificial intelligence may feel like a software revolution, but the deeper you look, the more obvious it becomes that software is only one layer of a much larger stack. AI requires data centers. Data centers require enormous amounts of electricity. Electricity requires generation, transmission, and infrastructure. Infrastructure requires materials, manufacturing capability, transportation networks, and skilled labor. The further you follow the chain, the more apparent it becomes that intelligence alone is not enough. We also need the capacity to build and sustain the systems that make that intelligence useful. What initially appears to be a conversation about algorithms quickly becomes a conversation about industrial capability.

One of the most striking observations from the panel was how little anyone talked about money. Ten years ago, discussions about growth and innovation often centered on access to capital. Could we raise enough money? Could we secure the necessary investment? Could we attract venture funding or government support? Today, that conversation feels different. The organizations represented on stage were not worried about whether investment existed. In many cases, the capital is already available. Governments are investing. Private industry is investing. Demand is growing. The question is no longer whether we can fund the future. The question is whether we can build it. Can we construct the facilities? Can we train the workforce? Can we deploy the infrastructure? Can we execute quickly enough to meet the moment? The bottleneck is increasingly not capital. The bottleneck is capability.

That realization resonated with me because it mirrors something I have observed throughout my career. Ideas are rarely the limiting factor. Every organization has ideas. Every conference is filled with vision and strategy. Every leadership team can articulate where they want to go and what they hope to become. The difficult part has never been generating ideas. The difficult part has always been execution. It is the ability to consistently transform a concept into a result, to move from intention to action, and to continue moving when the work becomes difficult or uncertain. As technology becomes more complex and the systems we depend upon become increasingly interconnected, that ability becomes even more valuable. Vision matters. Strategy matters. Innovation matters. But none of those things create value until they are translated into outcomes.

As I listened to these leaders describe the future, I found myself thinking about a distinction that often gets lost in technology circles. We frequently talk about innovation as though it originates entirely from software. In reality, many of the most significant advances occur when software intersects with something physical. Robotics is not simply software. Autonomous vehicles are not simply software. Modern manufacturing is not simply software. Energy systems, defense systems, logistics networks, and industrial automation all exist at the intersection of software and hardware. For years, we treated those disciplines as separate worlds. You were either a software company or a manufacturing company. You were either a software engineer or a mechanical engineer. Today, those boundaries are disappearing. The most interesting opportunities increasingly exist where those disciplines converge.

This convergence is one of the reasons I believe the conversation around AI feels so different than previous technology cycles. AI is valuable not because it can generate text or summarize documents. Those capabilities are impressive, but they are not transformational on their own. The truly transformative applications emerge when intelligence is connected to physical systems. When software can improve manufacturing throughput, optimize energy consumption, coordinate supply chains, enhance logistics operations, or enable autonomous robotics, we begin to see meaningful economic impact. The value is not in the model itself. The value is in what the model enables. That has always been true of software, but AI is making the relationship much more visible.

Another theme that surfaced repeatedly throughout the discussion was geography, specifically why so many organizations are choosing to invest in places like Ohio. I’ll admit that I have a natural bias here. I have built my career in Ohio. I have built a company in Ohio. I’ve watched talented people choose to stay, grow, and create meaningful careers here. What I found refreshing was that the reasons these executives cited were not rooted in marketing slogans or public relations campaigns. Their answers were practical. They talked about land, energy, water, transportation infrastructure, universities, manufacturing capability, workforce development, and quality of life. In other words, they talked about the ingredients required to actually build something. They were evaluating their ability to execute, not their ability to create a narrative.

That distinction matters because I think we are entering an era where practical advantages will increasingly outperform perceived advantages. For years, innovation was often associated with specific zip codes. Success seemed tied to proximity. If you wanted to build a technology company, there were a handful of places where everyone assumed you needed to be. Today, many of the organizations building the next generation of manufacturing, robotics, defense, and infrastructure are optimizing for something different. They are optimizing for capacity. They need room to expand. They need access to power. They need transportation networks. They need talent. They need communities where people can build careers, buy homes, raise families, and still have a quality of life worth protecting. Those are not secondary considerations. Increasingly, they are strategic advantages.

Perhaps what excites me most about this moment is that it feels like a renewed appreciation for builders. Not just software developers, although they remain incredibly important. Builders. Engineers. Technicians. Tradespeople. Operators. Project leaders. People who understand how to take responsibility for an outcome and see it through to completion. For a long time, much of the public conversation around technology focused on ideas, disruption, and innovation. Those things matter, but they often overshadowed the people responsible for turning those ideas into reality. The current moment feels different. There is a growing recognition that vision without execution is simply aspiration. Progress requires people willing to do the difficult work of designing, constructing, maintaining, and improving the systems upon which everything else depends.

At augustwenty, we’ve always said that we build valuable things. That wording was intentional. We never wanted to define ourselves solely by a technology, a platform, or a programming language. Sometimes the valuable thing is software. Sometimes it is a process, a system, an experience, or an operational improvement. The medium changes, but the objective remains the same. Create value. Solve meaningful problems. Deliver outcomes. The more I listened to this discussion, the more I was reminded that technology itself is rarely the destination. Technology is the mechanism through which we create something useful for another person. The software matters, but the outcome matters more.

Listening to this panel reinforced something I have believed for a long time. The organizations that will define the next decade will not necessarily be the ones with the most presentations, the most ambitious vision statements, or even the most sophisticated technology. They will be the organizations that can consistently turn vision into reality. They will be the organizations capable of connecting ideas to execution, software to hardware, intelligence to infrastructure, and strategy to outcomes. For a while, I think we forgot how important those capabilities were. Thankfully, as the challenges in front of us become larger and more consequential, we’re beginning to remember. And if the conversations I am hearing are any indication, that renewed appreciation for builders may be one of the most encouraging developments of all.