The Floor and the Door

Software that disappears needs more engineering, not less. The screen gets thinner. The stack under it gets harder.

I said in a memo to my team that technology that wins does not stay visible. It disappears into the job. The Rolodex became a PC. The PC became a phone. The phone is becoming a conversation with an AI employee you can delegate to.

It is easy to nod at that. The next question is where the software goes. I have a two-word answer. Down.

The button that said Chat

I looked at an AI employee screen in our own product. The main button on it said Chat.

That one word was the whole problem. Chat is how you operate an AI. You open it, you ask, you read the answer, you ask again. The owner is still the one doing the work. We had built a nicer way to operate software and called it an employee.

An employee takes a job. You say what you want done, what the limits are and when to tell you. Then you go and do something else.

If the default button on an AI employee is Chat, we have not shipped an employee. We have shipped a persona on top of a chatbot.

Two layers

When the front of the software thins out, the back has to carry more. So there are two layers, and they should not be mixed.

The first is the system of record. The customer list, the inbox, orders, billing, bookings, reviews, listings. These are ledgers. They hold the data and they take the actions. They are the hands and feet. They are not going away.

The second is the AI employee. It lasts. You can delegate to it. It knows the business and it can be given a routine. It is the one that runs the first layer.

What changes is who the first layer is built for. For years we built it for a person clicking through screens. Now its main user is an employee that was handed a job in a conversation. The screens become the employee's workplace. The owner looks in on them the way you check a ledger.

The system of record is the floor. The delegation engine is the door.

Why the floor matters

An AI employee that cannot touch the ledger is not an employee. If it cannot update the system of record, it is not a worker. It is a suggestion box.

That is the second mistake I see. People bolt an assistant onto the side of an app. It reads the screen, drafts something, and hands the work back to a person to type in. The agent has been forced to work like a human. An agent forced to work like a human is a wasted agent.

The better design gives the employee direct, safe access to the same actions the screens use. Same data. Same rules. The screen is how the owner looks over its shoulder.

What the owner sees

At the door, the owner sees very little. That is the point. There is no dashboard to learn. There are four things.

• A conversation, where the job is given.
• An approval, when the employee needs a decision.
• A number, which says how the work is going.
• An exception, when something went wrong.

And there is a state. The employee is idle, thinking, working, waiting, blocked or done. Anyone who has managed a person already knows those six words. There is no manual.

What the builder sees

The builder gets the opposite. Under one quiet conversation sit databases, permissions, evaluations, cost, trust and the routing between models. That is the iceberg.

So software does not disappear. The work of making it simple moves to the people who build it. I would rather carry that work than hand it to every customer.

There is a real tension here and I will not pretend there is not. The floor looks like more SaaS: more fields, more tools, more reliability. The door looks like less UI. Both are correct. Starve the floor and the employee has nothing to stand on. Starve the door and you ship a prettier way to operate AI. That is the opposite of disappearing.

The front desk

Enterprises have departments. Small businesses have a front desk.

A small business owner is the sales team, the support team and the bookkeeper in one day. They do not want five apps with five assistants. They want one place to say what needs doing. That is a strong reason for the door to be one conversation, and for the floor under it to be as reliable as a ledger.

The test

I give my product teams one acceptance test. Open the app as a small business owner. If you have to type before anything useful happens, the screen fails.

And I watch one number: whether people delegate ongoing work or chat for help. If chatting wins, the product is still teaching the wrong habit.

The limit

I should state the limit. Someone still owns judgment. Authorization, audit and reverse remain human jobs. A conversation is a good front door. It does not replace the lock.

The line between using software and building software has been moving toward the user since the spreadsheet. It keeps moving. It does not vanish into magic. Each time it moves, someone has to do the hard part underneath.

I intend for that to be us.

The system of record is the floor. The delegation engine is the door.