Beyond UX/UI
Software isn't going away. The way we operate it is. Every menu, form, toggle and dashboard turns into a sentence, and almost nobody has written down what those sentences sound like. That's the matrix below.
Most of the AI-versus-SaaS debate asks whether software survives. It survives. The data, the rules and the actions underneath all stay. What ends is the way we operate it: the menus, the forms, the toggles, the dashboards.
Part 1 of this series looked at the data layer and found records that existed only because machines couldn't read. This part looks at the layer you touch. The interface existed only because machines couldn't listen.
You wanted to tell the software "invoice Acme for the March work, net 30." It couldn't understand a sentence, so it gave you four screens and eleven clicks instead. Every menu is a list of verbs you pick from because the machine can't guess your intent. Every form is a sentence broken into fields because nothing could extract them. That was the deal for forty years, and it was always a workaround for one missing capability: understanding language.
I'll admit a personal stake here. I've always struggled with interfaces. Menus don't stick, icons don't parse, I lose the button I used yesterday. Talking to software through AI, and through MCP connectors especially, feels like a liberation. I don't think I'm the exception. I think I just felt the tax earlier than most.
Now the machine understands language, and the interesting question isn't whether the interface changes. It's what each widget actually turns into. Everyone repeats "chat replaces the UI." Nobody has written down the sentence that replaces each widget. Some are one-off questions, some are standing instructions, some are a single word, and a few widgets don't translate at all. Here's the full mapping.
| The widget | The job it did | What you say instead |
|---|---|---|
| Listed every action the software could do, on screen at all times, because it couldn't guess what you wanted | Send the contract to Acme.You state the goal, the software finds its own verb. And when you're lost: what can you do here? | |
| One box, one noun | Where's the Acme agreement? The deck I sent Marco in April.Description replaces navigation | |
| One field per piece of information, because nothing could pull them out of a sentence | Invoice Acme €12,000 for the March work, net 30.One sentence fills ten fields. The AI asks back only what's missing: from which entity? | |
| A list of allowed values you had to read through | Usually nothing. The AI picks the valid value on its own. You speak only when the choice is really yours: make it euros | |
| Ticking items one by one, capped by what fits on screen | Everyone who hasn't replied in ten days.A condition selects the set, at any size | |
| Preferences frozen into switches | Always ask me before anything above €10k goes out.Said once, remembered. Settings become standing instructions | |
| A calendar so you couldn't enter an invalid date | Next Thursday. End of Q3. | |
| Moving a card across a board to change one field | Move Acme to negotiation. | |
| The software walking you through its steps, one screen at a time | Set up the campaign, and check with me before it goes live.The steps run; you see the checkpoints | |
| Setting continuous values by hand | 20% cheaper.Rough values translate fine. Tuning a color or a sound doesn't; there the hand stays | |
| Answers computed in advance, to questions someone guessed you'd ask, refreshed on a schedule | Two sentences replace it. The specific question: what was CAC last week?And the standing brief: every Monday, tell me what changed in the pipeline and what needs attention.The dashboard becomes a saved prompt | |
| Rows and columns for scanning state at a glance | Show open deals above €50k by close date.The grid still appears. It just appears on demand, shaped by the question | |
| Everything about one customer, one layout for every user | Everything on Acme, latest first.You get the view you asked for, not 30 fields to scroll past | |
| A red dot, with no explanation attached | Tell me if any client goes quiet for two weeks.Alerts become sentences too, and they arrive with the reason attached | |
| One click to commit an action | Approve. Send it.The commit survives as a single word, because committing money or a signature should never be ambient | |
| Compressed commands for the trained hand | Nothing yet. ⌘K takes 200 milliseconds, a sentence takes seconds. For anything done fifty times a day, the shortcut still wins | |
| The one view a whole team looks at together | Nothing yet. Two people can't point at a view that was generated for one of them. The meeting screen stays | |
| Direct manipulation: Figma, the fader, the scrub bar | Nothing. You can't say a brushstroke. The hands keep this one |
scroll the table sideways →
Read the third column top to bottom and two patterns show up. Specific questions replace lookups: the search, the grid, the record page all become show me X
, answered on demand and shaped by the question. And standing sentences replace configuration: the setting, the alert and the Monday briefing are all instructions you say once and the software keeps. The dashboard is the clearest case. It doesn't map to one query; it splits into the specific question and the recurring brief, which is a better dashboard than the one it replaces, because nobody guessed your questions at design time.
The table has three rows where the answer is "nothing," and each has its own reason. The approve moment stays a deliberate act, because committing money or a signature needs to be unambiguous and attributable. The shared screen stays, because a team needs one stable view to point at. And the canvas stays, because some work lives in the hands: continuous, real-time control that language is too slow and too serial to carry.
Everything else in the table is a matter of time, not of principle. The shortcut row is the honest one: for high-frequency work, clicking still beats talking on speed alone. That advantage shrinks as the tools get faster, which is why this shift runs through enterprise software first, where the interfaces are disliked and used weekly, and reaches the creative tools last.
A traditional interface is built once, for the average user, and shared by everyone. A generated one is built per question. That kills more than the widgets.
Nobody says "go to Settings, then Billing" anymore, because there is no Settings, then Billing. The training courses, the onboarding tours and the "where is the button" tickets all served the fixed screen, and they go with it. So does the muscle memory: ten years of knowing where things live was the real switching cost of enterprise software, and nobody accumulates navigation skill in software they don't navigate. And so does the seat. Per-seat pricing counted screens with humans in front of them; remove the screen and there's nothing left to count, which is why the vendors are all repricing at once.
Design doesn't disappear, it moves. Someone still decides what a confirmation looks like and which choices deserve a question instead of a silent default. But the work shifts from drawing layouts to defining the vocabulary the AI composes from, and the tool description the model reads becomes the new UX writing.
The record was a copy we typed because machines couldn't read. The interface was a workaround we clicked because machines couldn't listen. Both go for the same reason, and what's left is software you talk to: a few standing instructions, questions answered on demand, and one word, said out loud, when something real is about to happen.