Ten years ago, the question was whether every company needed to become a tech company. Most of them said yes, hired a CTO, and bought some cloud infrastructure. Now the question is sharper: does every person in your company need to be able to build?
The answer is not yes. But it is closer to yes than it was two years ago.
What AI actually changed
The barrier to building software was never creativity or business logic. It was syntax, frameworks, debugging, and the ten thousand small things you need to know just to get something running. AI coding assistants have not eliminated that complexity — but they have dramatically compressed the time it takes a non-expert to navigate it.
A product manager who could previously describe what they wanted but could not build it can now, with a well-specified prompt and a few hours of iteration, prototype it. A marketer can build their own analytics dashboard. An operations person can automate a workflow that previously required a developer ticket and a three-week wait.
This is not replacing developers. It is redistributing access to the ability to build.
The new baseline
What is changing is the baseline expectation for technical literacy in knowledge work. Not everyone needs to be able to ship production code. But increasingly, the people who can read code, write a working prompt, understand what an API does, and debug a simple script are the people who move faster, depend less on others, and create more value.
In a company where AI tools are available to everyone, the limiting factor is not access — it is the ability to use them effectively. And effective use requires a model of how the underlying technology works.
What builders should do
If you are a developer, this is not a threat — it is a forcing function. When non-technical colleagues can handle the routine requests, your value concentrates in the things that actually require deep expertise: systems architecture, performance at scale, security, complex integrations, the decisions that cannot be undone.
If you are a non-technical professional, this is your unlock. Pick one domain — a spreadsheet you automate, a simple web page you build, a data pipeline you wire together — and go deeper than you think you need to. The goal is not to become a developer. The goal is to stop waiting for one.
The company that wins
The organizations that will move fastest in the next five years are the ones where the technical and non-technical distinction is most blurred. Not because everyone codes, but because everyone has enough technical fluency to close the gap between an idea and a working thing.
A developer in every company? Maybe not. But a building mindset in every team? That is already becoming the differentiator.