The Case for Language-Native Software — Robert Englander

The Case for Language-Native Software

2026

A while back, I wrote that the future of software might be conversational rather than autonomous. I still think the central observation was right, but since then I’ve become increasingly convinced I was looking at it through the wrong lens.

The word conversational turns out to be doing more harm than good. When people hear it, they think of chatbots and back-and-forth — they picture ChatGPT, they picture a conversation. When I ask a retirement planner to show the effect of delaying Social Security until seventy, I want fulfillment: I state intent, the system figures out what I mean and executes. A conversation might happen if intent is unclear. It isn’t the point.

Conversational software treats dialogue as the interaction model. Language-native software treats human language as the interface — you express intent, the system resolves it and runs the right deterministic operation. Chat is one path when ambiguity needs clearing; most valuable interactions are closer to a command than a conversation. That distinction explains several things the industry’s chatbot-and-agent obsession doesn’t.

I Think the Industry Learned the Wrong Lesson

When ChatGPT landed, most people fixated on the fact that you could talk to software. Understandable — it was the most visible part. You typed a question, the system answered, you refined, it answered again. It felt different because it felt like a conversation.

I don’t think the conversation was the important part. I think the important part was that millions of people experienced software that could understand instructions in natural language .

Conversation is a mechanism. Natural language understanding is a capability.

That distinction gets clearer once you look past chat apps. Take business intelligence: for decades, users learned where reports lived, how dashboards were organized, which screen had which metric. Now imagine asking, “Show customer churn by region for the last four quarters.”

Nothing about that requires a conversation. The system just needs to know what you mean and give you the answer. Same pattern in scheduling, financial planning, healthcare, design tools, dev environments — in each case, the value is understanding intent . The conversation is optional.

The False Choice Between Traditional Software and Agents

A lot of AI discourse is framed as traditional software versus autonomous agents. Traditional: rigid, menu-driven. Agents: adaptive, intelligent. One follows instructions; the other pursues goals.

Agents are seductive — describe a goal, walk away, let software fill in the details. If that worked reliably, it would strip a ton of friction out of how we use computers. What keeps bothering me is that this framing assumes execution is the hard part. In many domains, I’m not sure it is.

Databases execute instructions remarkably well. So do tax packages, schedulers, reporting engines. Execution is often the easy part. The hard part is deciding which instruction should run in the first place . A retirement planner can run thousands of projections; figuring out which one the user wants is often harder. A reporting system can answer thousands of questions; figuring out which question they’re actually asking is often harder. Language models fill that gap — they connect what the user means to what deterministic software can execute.

The industry often treats more reasoning as inherently better. Sometimes it is. An agent that keeps thinking after intent is clear has stalled; it hasn’t committed yet. That problem shows up again when conversation becomes the default interface.

The Evolution of Interfaces

We’re so focused on AI that we sometimes miss the longer pattern. Software interfaces have been evolving for decades. Early systems made you think in machine terms. Command lines were a step up — symbolic instructions instead of purely physical ones. GUIs were another: menus, windows, buttons, direct manipulation. Less memorization, less translation burden on the user. Each step made software more accommodating.

Natural language feels like the next step in that line. For decades, users learned the application’s language — navigation, workflows, forms, commands, config screens. You had a goal; you mapped it onto the interface. That stuck around because machines couldn’t reasonably interpret human language. Now they can — well enough, anyway, that the relationship is worth rethinking.

Natural Language and Chat Are Different Things

“Navigate to the nearest charging station.” “Show churn by region for the last four quarters.” “Move the launch to October and show every milestone that changes.” Natural language in each case; conversation in none.

Distinguishing natural language from chat is only half the picture. The industry also tends...