Every investor pitch starts with the moat question. "What stops Salesforce from building this?" "What stops a well-funded competitor from copying you?" "Where's your defensibility?"

For a 220-vertical SaaS factory, the honest answer is: nothing stops Salesforce from building any individual vertical. What stops them is that they won't bother, because each vertical is too small to matter to a $300B company. That's the moat.

The Salesforce Math

Salesforce has revenue around $32 billion annually. To move the needle on their revenue, a new product line needs to be able to generate at least $100 million annually at some point. That implies a TAM of probably $1B+ and a customer base of hundreds of thousands.

Now look at our verticals:

None of these individually move the needle for Salesforce. Not cheesemaking. Not breweries. Not tattoo shops. Not small-church admin. A Salesforce product manager pitching "let's build a $10M ARR cheesemaking tool" gets laughed out of the meeting because $10M is rounding error at Salesforce's scale.

This is structural. It's not about Salesforce being bad at niches. It's about the math of a giant company being unable to target small markets profitably.

The Mid-Market Gap

There's a mid-market tier of software companies — the Pipedrives, the HubSpots of the world — that could theoretically target smaller TAMs than Salesforce. They don't either, because:

Even mid-market SaaS can't easily enter our markets without disrupting their core business model.

The Indie Maker Threat

The people who could compete with us in a vertical are indie makers. Someone decides to build a beekeeping app over a weekend, ships it on Product Hunt, and gets 50 users. This happens all the time.

The question is: can a solo indie maker sustain the vertical better than we can?

My experience is: no, for most verticals. Here's why:

  1. The indie maker has one app. Their whole life is that app. They hit burnout at month 14 and shut down. We have 220 apps; each one is a 5-10% slice of our attention, which turns out to be more attention than they'd get as an indie's full-time project.
  2. The indie maker lacks the shared infrastructure. We have the template, the Claude wrapper, the deploy pipeline, the auth system, the billing integration. An indie rebuilds all of this for each app.
  3. The indie maker doesn't have catalog presence. Users who discover our catalog discover 219 other apps that might also be relevant to their life. A single indie app doesn't cross-sell itself.

The indie competition is real and we lose some deals to it. But the attrition rate of solo indie apps is much higher than the attrition rate of catalog apps with a team (even a two-person team).

What Defensibility Actually Looks Like

Three concrete things that defend our position:

Catalog breadth. No single competitor builds 220 apps. Someone entering cheesemaking has to rebuild from scratch. We deployed cheesemaking on a Saturday because we have the template.

Brand consistency across niches. Dangercorn has one visual identity across every landing. One tone. One pricing philosophy. Customers trust a catalog more than a random indie maker. This is small, but real.

The self-host tier as trust signal. Every vertical has a public GitHub repo. That's not bluffing. That's the product, available to inspect. It's a trust signal that a lot of indies can't or won't replicate.

The "Just Build It" Risk

The internet is full of "just build it in a weekend" energy. AI coding tools have lowered the bar to shipping a CRUD app. So in principle, anyone could build a cheesemaking tracker over a weekend — the bar isn't expertise anymore.

This is true and also doesn't matter. Building the app once is the easy part. Maintaining it for years, supporting users, fixing bugs, integrating new payment processors, keeping up with security patches, writing the docs, doing the marketing, finding the audience — that's the work. A weekend builder shipping a competitor app does not threaten an established vertical that's been maintained for two years and has actual users. The competitor's app has zero users; the established app has revenue.

The barrier isn't building. The barrier is sustained operation. A solo dev with no users abandoned the project at month 9. A duo with paying customers and a catalog continues indefinitely.

Where the Moat Breaks

Three scenarios where our moat doesn't hold:

A vertical grows out of "small." If cheesemaking goes from $10M TAM to $500M TAM (say, because home cheesemaking becomes a mainstream cultural moment), Salesforce or HubSpot could enter. That's good — we got there first and have a customer base. We don't need to win the $500M TAM to have won. We need to have been the default until someone bigger shows up.

A competitor builds a catalog of 220 apps too. Theoretically possible. Expensive in real terms. Hasn't happened. If it did, the market would split. Both businesses would still work.

AI-generated SaaS becomes truly zero-marginal-cost. If anyone can generate a vertical SaaS in an afternoon, the catalog advantage erodes. But then the differentiation shifts to curation, trust, and operational excellence — which are still real goods we can own.

The best moat is not being worth attacking. If your market is too small for a large competitor to bother with, and too wide for a single indie to maintain, you're in a defensible middle.

Related

The 220-app thesis. TaskRabbit-ignored markets. Why we're not raising. Why self-host reinforces the moat.

What This Means for Customers

The customer-side benefit of niche specificity is rarely discussed in moat conversations. It matters too. A cheesemaker using cheesemaking isn't getting a generic CRM with cheese-themed labels. They're getting a tool whose data model knows what a wheel is, what aging means, what a tasting note structure looks like. The narrowness is the value, not just the moat.

Generic horizontal tools are flexible. They're also indifferent to the specific job they're being used for. If you've ever tried to fit your business into a CRM that wasn't designed for it, you know the friction. Vertical tools eliminate that friction by accepting the cost of being uninterested in adjacent industries.

The moat is also the product. The product is also the moat. They aren't separable. That's the cleanest version of why we're doing this.