As AI agents become primary software users, SaaS companies like Salesforce are building "headless" versions where the API is the UI. This fundamentally breaks the traditional B2B SaaS business model based on pricing per human user, forcing a shift towards consumption-based, agent-native pricing models.

The next generation of software may lack traditional user interfaces. Instead, they will be 'API-first' or 'agent-first,' integrating directly into existing workflows like Slack or email. Software will increasingly 'visit the user' rather than requiring the user to visit a dashboard.

When a major platform like Salesforce prioritizes headless APIs, it's a bellwether moment. It signals a recognition that AI agents will become primary "users," driving demand for API-first access and creating a new wave of automation use cases.

Karpathy's home automation agent ("Dobby") replaced six different apps by interacting directly with smart device APIs. This suggests a future where users interact with a single agent, and software products must expose agent-friendly APIs to survive, as their bespoke UIs become irrelevant.

The number of AI agents will soon vastly exceed human employees. This requires a fundamental shift in software development, prioritizing API-first design, reliability, and machine-to-machine interaction over traditional human-centric user interfaces.

As users increasingly rely on AI agents, traditional graphical user interfaces will become obsolete. SaaS products must evolve to offer conversational interfaces that other agents can interact with directly. The primary user will shift from a human clicking buttons to another AI sending messages.

In a world where AI agents perform tasks, the value of a SaaS product is no longer its user-friendly interface but the robustness of its APIs. The core differentiator becomes the proprietary business logic, security, and data governance embedded within the API layer.

Users will stop interacting with countless individual apps and websites. Instead, they'll communicate with a personal AI agent that handles tasks by interfacing with services via APIs, making traditional graphical user interfaces obsolete.

A major architectural shift is underway: instead of embedding AI features into a product, companies should treat AI as an external agent that uses the product via a CLI or API. This simplifies integration and better aligns with AI's capabilities.