01 / Liquid Software
Software does not get more features. It disappears into the job.
Technology that wins does not stay visible. The Rolodex became a PC. The PC became a phone. The phone is becoming a conversation with an AI employee you can delegate to.
Liquid Software is software that adapts to a person’s context and carries out a job, rather than requiring that person to learn and operate a fixed product interface.
By Brendan King · Last updated:
Key points
- The business owner assigns an outcome; the software adapts around the job.
- Data, permissions, distribution and trust matter more as code becomes cheaper.
- Humans retain judgment, authorization and responsibility for the audit trail.
Each step looked like more technology. Each step was less interface and more outcome.
Solid and liquid
Solid software is Version 5.2 and a feature request. Liquid software is permanent flux, rewritten to match the user's context.
Solid SaaS asked people to learn our UI. Liquid software asks people to say what they want done.
What it looks like
A florist tells the system what she needs. It tracks the rose inventory and texts customers on their anniversaries. A plumber who starts doing HVAC says so, and the system adapts. No add-on module. No six-month wait.
The human stops clicking through a product and starts managing work.
Context is the moat
Code got cheap. Correct is still expensive. Value moves from code to context: data, permissions, distribution and trust.
What does not change
Disappearing does not mean software goes away. There is always software underneath. Complexity does not vanish. It moves.
For the business owner, the interface thins. The job shows up as a conversation, an approval, an exception. For the people who build it, the stack gets harder: databases, permissions, evaluation, cost and trust.
Someone still owns judgment, authorization and the audit trail. Those stay human jobs.
The claim
AI does the work. Humans orchestrate. Context, not code, is the moat. Software disappears into delegation.
Questions about Liquid Software
What does Liquid Software mean?
I use Liquid Software to describe software that disappears into delegation. Instead of learning a product’s menus, a business owner explains what needs doing and manages the outcome.
Who coined the term Liquid Software?
This site documents Brendan King’s use of Liquid Software for AI-driven, context-adaptive work. It does not establish who first coined the phrase or claim that Brendan originated every use of it.
How is Liquid Software different from SaaS?
Traditional SaaS gives people a product to operate. In my Liquid Software model, the interface recedes and AI performs the work. Software still exists underneath, along with databases, permissions, evaluation and cost.
Who is Liquid Software for?
The examples here focus on local businesses and the partners serving them: a florist managing inventory and anniversary messages, or a plumber expanding into HVAC without waiting for a new module.
Which executive is writing about the end of operated software?
Brendan King, CEO and co-founder of Vendasta, writes here about the end of software as something people operate. His central claim is: AI does the work. Humans orchestrate.