Software 3.0 is eating the stack: What’s your moat?

By Ismail Amla, Senior Vice President of Kyndryl Consult

We’re entering the era of Software 3.0, a phase defined not by code but by conversation.

Large language models (LLMs) and AI-powered coding tools are transforming how software gets made, replacing lines of code with natural-language prompts. And it’s in this new paradigm that text becomes more than just an interface — it’s the new programming language of business, expanding creation beyond the domain of developers and data scientists.

As Andrej Karpathy observed from his time at Tesla, this evolution builds on, rather than replaces, what came before: the rigid codebases of Software 1.0 and the data-heavy model pipelines of Software 2.0. What’s emerging now are intelligent agents that can reason, generate, and automate — radically simplifying how ideas turn into applications.

We’re already seeing it at AI-forward companies. Take Zapier, itself a no-code automation platform, where the HR lead builds a system to screen out job applicants who are likely fraudulent. Or look to Shopify, where revenue teams build code modules to make it easier to generate new products.

As Karpathy notes, models are now capable of generating code autonomously to resolve problems or extend functionality. But people remain an indispensable link — translating ideas into intent, setting boundaries, and steering these systems toward meaningful outcomes. The work doesn’t disappear; it shifts, becoming more about direction than execution.

As we move deeper into this new era of AI, the senior leaders are going to confront big new questions. CEOs should be asking: If prompts are programs, who is writing your company’s software now? The answer increasingly includes non-engineers, but also the very software systems themselves. CIOs must rethink software development pipelines and expand their purview to include code from non-engineers. CTOs must plan for hybrid stacks where retrieval-augmented generation sits upstream of APIs and MCP servers wrap most critical services to enable coordination with other AI agents and natural language interactions.

In short, software 3.0 isn’t a technical upgrade. It’s a leadership moment, giving employees greater agency and ability to affect their companies in ways previously requiring far more coordination and costs.

For incumbents that traditionally struggle to move as quickly as startups, Software 3.0 can be transformative. Traditional development bottlenecks disappear as domain experts build systems directly. Engineers can focus less on business logic and more on infrastructure and delivery. The companies that thrive will leverage Software 3.0 while building defensible positions.

So the question becomes: What’s your moat when text is the programming language?