AI Is Making SaaS Optional

READ THE FULL EPISODE PAGE: https://devmesh.tech/podcast/saas-vs-ai-part-2-revenge-of-the-swe SaaS isn't dead. But what happens when the people who know a business best can build the software they need themselves? In Episode 29 of System Prompt, Peter and Val return to SaaS vs. AI for an unscripted sequel: Revenge of the SWE. They debate whether agents become interfaces to existing SaaS products or replace some of those products entirely. From an accountant building tools with Claude Code and SQLite to small businesses recreating only the features they use, the question isn't simply whether AI can write code. It's who understands the process, validates the outcome, and maintains the result. The conversation explores software engineering, domain expertise, deterministic workflows, harnesses, MCP, AI operations, local inference, and the challenges of organizational data and persistent memory. They also discuss frontier subscriptions versus local models, AI devices, and why AI-generated answers still need scrutiny. This is a riff, not a prediction that every SaaS company disappears. The cost of code is changing. The cost of judgment is another story. • SaaS as the engine behind agents, or something agents replace • Domain experts building their own software • Claude Code, SQLite, and small internal applications • CRUD applications and custom alternatives • Engineering beyond writing application code • Deterministic workflows, validation, and TDD • Harnesses, MCP tools, and specialized agents • AI Ops: runtimes, hosting, access, and reliability • Local inference economics and AI hardware • Data quality, context, memory, and relevance • Questioning AI-generated plans and answers KEY TAKEAWAYS THE AGENT MAY REPLACE THE INTERFACE OR THE APPLICATION Val sees agents operating SaaS through integrations. Peter asks when a business can skip a product and build only what it needs. Both may happen, depending on the workflow. DOMAIN EXPERTISE CHANGES THE EQUATION An accountant or operations lead knows the requirements and exceptions. AI can lower the implementation barrier, but verifying the result still matters. THE COST OF CODE HAS COLLAPSED. THE PRICE OF JUDGMENT HAS NOT. Generating software is easier. Deciding what should exist, whether it works, who can access it, and how to maintain it still requires engineering judgment. AI OPS IS STILL SOFTWARE ENGINEERING Someone must own runtimes, harnesses, integrations, memory, evaluations, and infrastructure, whether inference is local or hosted. MEMORY IS NOT JUST STORAGE Saving information is one thing. Knowing what is relevant, outdated, or worth retrieving for a particular task is harder. CHAPTERS 00:00 Intro and an Off-the-Cuff Episode 01:05 Anthropic, AI Sentience, and the Pope 03:20 SaaS vs. AI: The Debate Returns 08:17 When the Accountant Becomes the Builder 11:41 Does AI Change the Need for UI/UX? 14:00 Deterministic Paths and AI Costs 17:36 The Value of Domain Expertise 19:02 Local Models and the Future of Copilot 22:18 Harnesses and Specialized Agents 26:16 AI Devices and Distributed Inference 30:37 AI Ops, Data Quality, and Validation 34:03 AI Gadgets Versus Your Phone 37:37 Small Businesses and Bespoke Software 41:36 CRUD, Rails, and SaaS Alternatives 45:40 The Cost of Code vs. the Price of Judgment 48:41 Have We Solved AI Memory? 53:24 SaaS, Copilot, and the Cost of AI 58:28 Local Models and What's Next 1:01:01 Closing Thoughts