SaaS

What Makes SaaS Defensible in the Age of AI?

In a talk co-written with Einar Vollset, Rob Walling explains how records, permissions, and customer trust can make a SaaS business harder to replace.

Listen to the audio analysis

Create your own

Written for builders and creators.

Imagine a rival builds an issue tracker that looks as good as yours.

Editor's note

Why this matters now

A rival can build an issue tracker with the same screens as yours. Replacing Jira at a company with years of tickets, several teams and a web of integrations is a different project. The rival has to offer a way to move how the company works.

Rob Walling uses Jira in a MicroConf talk on SaaS moats developed with Einar Vollset. Their examples give founders a way to look past the feature list. Which records, permissions and responsibilities would a customer have to move to buy from someone else?

The source

What it says

Distilled from the original. The notes above and below are the editor's own.

Faster Competitors and Fewer Paid Seats

AI can help a competitor build comparable features faster. A customer building an internal replacement may only need to reproduce the few features their team actually uses.

Demand can change too. Einar Vollset later uses HubSpot to illustrate the risk for software sold by the seat. A marketing team that automates some of its writing may buy fewer user accounts even if it produces the same amount of work. Companion episode

Records, Permission and Trust

  • System of record. A Jira customer may be able to export its tickets quickly. The harder work is carrying over the audit trail and workflow rules and reconnecting the tools that read or update those records.
  • Permission to act. Stripe Connect can execute a payment. A competing dashboard can reproduce the information, while getting a customer to authorize it to move money is a different step.
  • Trust in the result. Walling describes relying on Gusto for payroll filings without checking each one himself. A replacement would have to earn his trust with a task where an error matters.

Editor's note

What to do with this

Pick a customer who renewed recently. Ask what would happen during the first week of a switch. Which records would the new system need on the first morning? Which action would the buyer hesitate to hand over? A long migration and a hard-to-earn permission are different reasons to stay. If the customer expects trouble moving audit history, look at which records their teams rely on to make decisions. If they hesitate to delegate an action, look for ways to make it more reliable and easier for them to audit.

For how these questions come up in a sale, see what one SaaS buyer valued about an AI-exposed business.

The original

The Only SaaS Moats Left in 2026

Rob Walling and MicroConf · 18 October 2026

All posts