The SaaS Leak: Why Operations are Moving from Fixed Subscriptions to Disposable Leverage

The Rise of the SaaS Leak

At a recent roundtable hosted by Anthropic and Balderton Capital, a group of practitioners shared a trend that should make every SaaS founder uncomfortable. They weren't just using AI to write code faster; they were using it to systematically dismantle their third-party software stack.

Teams are beginning to rip out established "point solutions"—tools for incident management, auth, project tracking, and customer triage—and replacing them with custom versions built in a single weekend.

We call this the "SaaS Leak."

For a decade, the operational mandate was: Buy whenever possible; build only if it’s your core product. That was sound advice when a simple internal tool required a six-month roadmap and a dedicated squad. But in the age of Claude Code and agentic engineering, the friction of "building" has vanished, while the friction of "generic SaaS" has become a bottleneck.

The SaaS Leak happens when a company realizes that their expensive, 500-feature software subscription is actually making their team work harder just to fit into a "standard" workflow.

The Problem with "Generic" Excellence

Most SaaS companies win by being "good enough" for the widest possible audience. They build for the "average" company. But your competitive advantage doesn't live in the average parts of your business; it lives in the quirks, the specific logic, and the unique way your team handles a crisis or a customer.

When you use a generic tool for a specific operational workflow, you pay two prices:

1. The Subscription Tax: The literal monthly cost per seat.
2. The Workflow Tax: The time your team spends "working around" the tool—manual data entry, clicking through ten screens to do one task, or exporting data to Excel because the tool’s reporting doesn't quite fit.

The SaaS Leak is the process of reclaiming that "Workflow Tax."

From Permanent Assets to Disposable Tools

In our previous analysis of Build vs. Buy, we argued that companies should build "Force Multipliers" and buy "Systems of Record."

The SaaS Leak takes this a step further by introducing the concept of Disposable Software.

Traditionally, "Custom Software" meant a multi-year commitment. You built it, you maintained it, you upgraded it. It was a heavy asset. Today, if a senior engineer can prompt a functional triage bot or a custom incident dashboard into existence in four hours for $12 in tokens, that software doesn't need to live forever to be "worth it."

If it solves a bottleneck for six months and then becomes obsolete because your process evolved, you haven't lost a $100k implementation fee. You just turn it off and build the next iteration.

Software is moving from an "Asset" mindset to a "Utility" mindset. You don't buy a permanent shovel; you 3D-print the exact tool you need for the hole you're digging today.

Where to Let the Leak Happen

To manage the SaaS Leak effectively, you need to know which parts of your stack should remain "Fixed" and which should be "Fluid."

1. The Fixed Basement (Systems of Record)

Do not build your own basement. These are the tools where the value is in the ecosystem, the security, and the data integrity.

• Keep Buying: Gusto, Salesforce, Stripe, Slack.
• Why: You aren't building a competitive advantage by having a custom payroll engine. You’re just inheriting a massive compliance headache.

2. The Fluid Layer (Connective Tissue)

This is where the leak provides the most leverage. Look for the "gaps" between your big platforms.

• Example: The Triage Engine. Instead of an expensive AI Support Platform, build a custom agent that sits between your shared inbox and your CRM. It categorizes tickets based on your actual historical data, not generic intent models, and drafts responses that follow your specific brand voice.
• Example: The Decision Harness. If your team spends 10 hours a week in spreadsheets trying to decide which inventory to buy, build a tool that pulls from your ERP and runs your specific proprietary logic.

The New "Build" Criteria

When deciding whether to "leak" a SaaS tool into a custom build, ask three questions:

1. Does the SaaS tool force us to change our process to fit its UI? If yes, build.
2. Is the "maintenance" of a custom version just logic updates, or is it infrastructure? If it’s infrastructure (security, hosting, compliance), keep buying. If it’s just logic (how we categorize a lead), build.
3. Can we ship a 'v1' that provides value in under 48 hours? With modern agentic tools, if you can't see a working version in a weekend, you're over-engineering it.

The Operational Intelligence Era

The goal of the SaaS Leak isn't to save money on subscriptions (though your CFO will be happy). The goal is Operational Intelligence.

When you own the "Connective Tissue" of your business, you own the data and the logic that makes you fast. You stop being a "Salesforce Shop" or a "Zendesk Shop" and you start being a company that uses custom intelligence to move faster than the competition.

The era of "one-size-fits-all" software is ending. It’s time to start building the 10% of code that gives you 90% of the leverage.

---

At FM, we help operational leaders identify high-leverage opportunities and build the custom tools that power them. If you’re tired of your team working around your software instead of with it, let's talk.