Software should be temporary by default

One of the strangest assumptions in software is also one of the least questioned:

Tools are permanent.

You choose a CRM, configure it, train people around it, and build workflows inside it. Then your needs change, but the tool remains, so the work bends around the software because leaving is harder than staying.

That is a philosophy, not just a feature problem, and I think it is backwards.

What if software were temporary by default?

Not disposable, temporary.

That distinction matters.

Disposable means cheap and careless. Temporary means the tool has not earned permanence yet.

I started thinking about this while building agent workflows that could generate interfaces from intent. You describe what you need to do. The system creates the smallest useful surface for that job. You use it. Then a judgment gets made: did this tool earn a place in the permanent system, or should it disappear?

The default answer should be disappear.

That sounds aggressive only because we are used to software procurement working the other way around: browse categories, pick the closest fit, accept the assumptions baked into the product, then spend months negotiating with the mismatch.

Agent-generated software lets us invert that.

You start with the specific need. The system knows your stack, your data structures, your design language, and the architectural decisions already in place. It can generate the smallest interface that supports the actual workflow instead of forcing the workflow into a prebuilt category.

Most of those interfaces should not live forever.

That is the point.

When the default is temporary, persistence becomes meaningful. A tool that remains is no longer something you forgot to cancel; it becomes something that proved useful enough to become part of the system.

Over time, the surviving tools begin to form relationships.

A form shares a schema with a log, the log connects to a tracker, and the tracker produces a dashboard.

Nobody sat down and bought a CRM. A CRM-like system emerged from repeated intent, useful interfaces, and a memory layer that understood which pieces deserved to persist.

That is the product I am more interested in.

Not the first generated interface, but the system that decides which interfaces deserve to exist.

This is where ephemeral software becomes more than a novelty. It changes the relationship between people and tools. Instead of committing to a tool and hoping it fits, you let tools audition for permanence against real work.

If they help, they stay; if they do not, they disappear without guilt.

Software should not assume it belongs in your life forever. It should earn that right.