This issue explains how SaaS moats shift from data storage to workflow orchestration in an agent-driven world, why comprehensive eval frameworks become key AI IP, and how to pinpoint the smallest viable unit of sellable software. It also highlights pitfalls like fake traction, work whiplash, agentic web readiness, private session recall tools, AI’s impact on cybersecurity incumbents, and startup risk misconceptions.

• SaaS moats are shifting from data storage to agent orchestration—routing tasks, approvals, and logging—as the real lock-in point
• Eval frameworks (measuring tone, accuracy, tool use) are becoming the core defensible IP for AI products, not just quality checks
• There's a "minimum viable unit of saleable software": below a certain cost/time threshold teams hack scripts with LLMs, above it they buy packaged tools
• Traction metrics that impress in pitch meetings often fail due diligence if usage isn't sticky or revenue doesn't scale

The article claims AI agents can autonomously handle repetitive admin work—data entry, billing, insurance claims—for small businesses, freeing owners to serve more customers and improve work-life balance. It uses Lassie, deployed in over 700 medical practices and saving up to 190 hours of labor per month, as proof, and outlines the technical, regulatory, and go-to-market challenges in building and scaling these systems.

• A Menlo Park dentist was found logging 2,400 hours a year on admin, and typical practices spend ~$200K annually on staff for billing/scheduling/claims work
• Lassie, an autonomous admin AI agent, now runs in 700+ medical practices across 49 states, saving an average of 30 hours/month and up to 190 hours/month per office
• The founders built credibility and reliability by doing the admin work themselves (reconciling millions in claims, billing thousands of patients) and onboarding customers in person
• Results include doctors seeing more patients, leaving on time, taking vacations, and one crediting the tool with saving his marriage

The author describes a pattern of prototyping workflows with AI agents then refactoring into code-driven processes, using agents only for tasks that require human-like judgment. A security vulnerability alert system illustrates how webhooks filter and route high-priority issues, delegating owner identification to an agent and formatting alerts via a second agent for reliable Slack notifications.

• Prototyping a workflow fully inside an agent prompt (filtering, assigning, formatting all in one) broke down under load, letting high/medium severity alerts slip through undetected.
• The fix was refactoring deterministic steps (filtering, batching, data extraction) into plain code, reserving agents only for tasks needing human-like judgment, like matching people to code ownership.
• The resulting hybrid pipeline (code filters/batches → agent assigns owners via CODEOWNERS/commits → second agent formats Slack messages) runs reliably without spamming non-critical alerts.
• The author's general pattern—prototype in pure agent, then refactor toward code with only a few targeted agent calls—is framed as producing faster, cheaper, more reliable automation than prompt tinkering or building strict evals.

Learn how to create a code review agent using the Claude Agent SDK, which allows developers to build custom AI agents capable of analyzing codebases for bugs and security issues. The guide provides step-by-step instructions, from setting up the environment to implementing structured output and handling permissions.

• The Claude Agent SDK can be used to build a custom code review agent that scans codebases for bugs and security issues
• The guide walks through the full build process: environment setup, structured output implementation, and permission handling