Should You Become a Builder?

For most of the software era, creating a digital product required specialized skills, substantial capital, and significant time. Building software was often impossible without engineers, development teams, or outside contractors. That reality has changed.

Whether using AI app builders, no-code platforms, low-code tools, or more traditional software development approaches, creating software has become dramatically more accessible. Today, many can build websites, mobile applications, databases, workflows, automations, portals, dashboards, and integrations with a fraction of the effort previously required.

The implications are significant. Creating software is no longer limited to software companies. Many can build operational software themselves, e.g., digital health, fintech, insurance, industrial IoT, logistics, supply chain, property management, and education to name a few. This has introduced a new decision that many never previously had to consider: “Should you become a builder?”

At first glance, the answer may seem clear. If software can be created more quickly and at lower cost than before, why not build it yourself? The question becomes more interesting when viewed through a different lens. The decision is not simply about whether software can be built. The decision is about where your time, energy, and expertise create the greatest value.

For some, building is exactly the right choice. Technology may be central to the vision. The process of building may be enjoyable. Direct control may be important. Rapid experimentation may create strategic advantage. Learning the underlying systems may be part of the objective itself. In these situations, building can create value.

But building is not a value-generating decision simply because it is possible. The important question is what happens to the activities that do not receive that time and attention. Consider a professional, provider, consultant, operator, or organization launching a new program. Time can be invested in building software. The same time could be invested in business planning, financing, business development, and related activities. Or simply generating revenue to fund the initiative.

Neither choice is inherently right or wrong. The decision depends on where the greatest value is created. This principle applies across industries. A coach may create the greatest value through program development and client engagement. An educator may create the greatest value through curriculum and instruction. A consultant may create the greatest value through expertise and client relationships. A wellness organization may create the greatest value through outcomes, operations, and growth.

In each case, software may be important. But software may not be the primary source of differentiation. This is where many discussions about AI-assisted development become incomplete. The conversation often focuses on what technology can do. Far less attention is given to opportunity cost. Every hour spent designing workflows is an hour not spent elsewhere. Every hour spent creating automations is an hour not spent elsewhere. Every hour spent learning development tools is an hour not spent elsewhere. It does not make these activities bad investments. It simply means they compete with other possible uses of time.

The decision becomes even more nuanced because building delivers benefits beyond the software itself. Many who choose to build gain a deeper understanding of their operations. They learn where workflows break. They gain insight into customer journeys. They discover inefficiencies that might otherwise remain hidden. They develop technical intuition that improves future decision making. These benefits can be valuable even when the resulting software is eventually replaced or evolved.

At the same time, not everyone enjoys building. Not everyone wants to spend their time thinking about workflows, integrations, prompts, databases, and system design. For many, technology is a means to an end rather than the end itself. There is nothing inherently superior about either perspective.

Building also shapes future decisions. Like learning golf without instruction, it is possible to make substantial progress independently but also develop tendencies that are harder to correct later. Similarly, early assumptions, patterns, and architectural decisions often become embedded in the resulting system. Some prove effective. Others may become constraints that are more difficult to unwind as the system evolves.

The rise of AI-assisted development has not created a universally correct answer. It has simply expanded the available options. Perhaps the most useful question is no longer: "Can I build this?" Many now can. A better question may be: "Is building this where my time creates the greatest value?" The answer will be different for different people, organizations, and situations. This is precisely why it is worth asking.