Your product was built for humans. But your next million users might not be human at all. Here's why the interface tax is ending and what it means for SaaS founders.
Your product was built for humans. But your next million users might not be human at all. The Shift I Can't Stop Thinking About After years of building SaaS companies, I've shifted focus to building with AI - and building for the AI-native future. Part of that journey has been obsessing over AI visibility: how to get AI systems to recognize, trust, and recommend your startup. The AI Trust Surface framework, confidence scores, topic clustering - all of it was about one question: How do you get AI to find you? But as I've gone deeper into building AI-native tools, I keep coming back to a different question: What happens after AI finds you? Because here's the uncomfortable truth: Getting discovered by AI is table stakes. The real game is whether AI can actually use your product. And most SaaS products? They're completely unprepared for this. The Numbers That Should Terrify SaaS Founders Postman's 2025 State of the API Report surveyed 5,700+ developers globally. Two stats jumped out at me: 89% of developers now use AI in their workflows. But only 24% design their APIs for AI agent consumption. That's a 65-point gap. And it's not closing slowly - it's closing fast. We're watching the fastest shift in software consumption history. Agents are moving from "assistant that helps me use software" to "autonomous systems that use software directly." If your product requires a human to click buttons, you're about to have a problem. The Death of the Interface Tax For 20 years, SaaS companies have charged what I call the "interface tax." Think about it: You don't pay $50/month for the database query. You pay for: The clean dashboard The onboarding flow The notifications The buttons that feel satisfying to click The actual work - the API call, the calculation, the data transformation - costs fractions of a penny. The rest is interface. Here's the brutal realization: AI agents don't need interfaces. They don't need your beautiful dashboard. They don't care about your onboarding. They can't appreciate your button animations. They need one thing: an endpoint that takes a request and returns a result. When agents become the primary consumers of software - and they will - the interface layer becomes worthless. Every SaaS that's essentially "nice UI for a simple function" is running on borrowed time. MCP: The USB-C Moment for AI In late 2024, Anthropic quietly open-sourced something that might reshape the software industry: the Model Context Protocol (MCP). Think of MCP as USB-C for AI agents. Remember when every device had its own charger? Laptop, phone, tablet, camera - all different cables. A nightmare. USB-C unified everything. One cable, every device. MCP does the same for AI-to-software connections. Build one MCP server for your product, and every AI agent can connect to it. No custom integrations per AI tool. No fragmented, brittle connections. Who's already building MCP servers: Block (Square, Cash App) Apollo Replit Sourcegraph Zed These aren't experiments. These are infrastructure companies betting their roadmaps on this standard. If you're building SaaS and not paying attention to MCP, you're going to wake up one day wondering why agents can't use your product while competitors are fully integrated. The Three Questions Every SaaS Founder Must Answer Your survival depends on three things: 1. Can an agent discover what you do? Humans browse websites. They watch demo videos. They read marketing copy. Agents read documentation. They parse API schemas. They look for structured descriptions of capabilities. If an agent can't programmatically understand what your product does, you don't exist to it. This means: Machine-readable API documentation (not just human-readable) OpenAPI/Swagger specs that actually describe your capabilities Structured metadata about what problems you solve This connects directly to the AI Trust Surface work - but it's the next level. It's not just "can AI understand you exist?" It's "can AI understand what you do?" 2. Can an agent authenticate without a human? Here's where most products fail completely. Traditional auth flows assume a human: Click "Sign in with Google" Approve permissions in a popup Get redirected back Agents can't click popups. They can't approve OAuth screens. You need: API keys with granular permissions Service accounts for programmatic access Auth flows that don't require human intervention Yes, there are security concerns - 51% of developers cite unauthorized agent access as a top risk. But the solution isn't blocking agents. It's building proper agent authentication. 3. Can an agent understand your responses? Even if an agent can find you and authenticate, can it actually use you? Predictable, consistent API responses Clear error messages that help agents self-correct Schemas that describe not just the data, but the meaning A human can look at a field called "amt" and guess it means "amount." An agent needs you to be explicit. The New SaaS Stack (Who Wins, Who Dies) Here's...