What SaaS Ideas AI Cannot Replace - Always-On, Hardware Access, and Persistent State
What SaaS Ideas AI Cannot Replace
The feeling that "Claude Code can build anything, so what is left to build?" is common. But it misses what AI coding tools fundamentally cannot do.
Claude Code can write you a script. It cannot run a background service 24/7. It cannot access your screen. It cannot listen to your microphone. It cannot manage a fleet of devices.
The Surviving Categories
Always-on services. Anything that needs to run continuously - monitoring, alerting, background processing, scheduled tasks. A script runs once. A service runs forever. That gap is the business.
Hardware access. Screen capture, camera feeds, microphone input, Bluetooth devices, USB peripherals. AI coding tools operate in a terminal. They cannot see or interact with hardware.
Persistent state. User accounts, historical data, cross-session memory, collaborative state. Each Claude Code session starts fresh. A SaaS product remembers everything.
Multi-user coordination. Team features, shared workspaces, permissions, real-time collaboration. AI tools are single-player by nature.
Where Desktop Agents Fit
Desktop agents sit at the intersection of "AI-powered" and "needs hardware access." They need to see the screen, hear the microphone, and control the mouse - things a coding agent in a terminal cannot do.
This is why Fazm is an application, not a script. The value is not in the code (which Claude could write) but in the persistent, always-available, hardware-connected runtime that makes desktop automation possible.
Fazm provides the always-on, hardware-connected runtime that AI coding tools cannot. Open source on GitHub. Discussed in r/ClaudeCode.