GREAT METRICS ARE NO LONGER ENOUGH

A SaaS company can have strong growth, strong retention, and serious buyer interest—and still receive no private equity offer.

The question has changed:

1. Will this revenue still exist next year?
2. What stops someone from rebuilding the product?

WHY SAAS VALUE IS CHANGING

AI IS NOT MAKING SAAS DISAPPEAR

Einar Vollset’s view is simple: AI is powerful, but it is still software.

That means SaaS companies are not automatically obsolete. Software teams may actually be among the best positioned to deploy AI because they already know how to build, ship, maintain, and improve software products.

AI IS MAKING SOFTWARE FASTER TO BUILD

Inside TinySeed’s portfolio, founders report shipping features in weeks that once took months.

AI can dramatically reduce development time and cost.

That creates opportunity for founders—but it also means basic software functionality can be reproduced much faster by competitors.

WHY FOUNDERS SHOULD CARE ABOUT MOATS

A company is still an asset.

Founders may eventually sell because of fatigue, life changes, opportunity, or a compelling offer.

Even if you never sell, understanding what makes the business valuable helps reveal whether you are building something durable—or something that can easily disappear.

THE TRADITIONAL SAAS MOATS

The traditional SaaS playbook already valued:

1. Deep integrations
2. Strong brand
3. High switching costs
4. Owned traffic channels such as SEO

These still matter. AI changes how defensibility is judged and raises the value of assets that competitors cannot recreate simply by writing better code.

A FEATURE IS NOT A MOAT

Developers often treat a clever feature as defensibility.

But features were never a strong moat—and AI makes them even weaker.

If competitors can reproduce the feature quickly, the real value must exist around it: data, workflow, trust, networks, hardware, integrations, or switching costs.

THE FIVE MOATS BUYERS NOW CARE ABOUT

MOAT 1 — HARDWARE

Hardware once looked like a SaaS disadvantage because it was slower and harder to scale.

Now tightly integrated hardware can increase defensibility.

Replacing the software may also require replacing devices, installations, maintenance processes, employee routines, and physical infrastructure.

WHY HARDWARE BECOMES HARD TO REPLACE

Examples from the TinySeed portfolio include:

1. Digital scales in grocery stores
2. Software inside EV chargers
3. Printers deployed in warehouses

A competitor cannot simply recreate the code and instantly replace a system already embedded inside real-world operations.

THE HARDWARE MOAT TEST

Hardware becomes a moat when it is tightly connected to the value the product delivers.

An ordinary off-the-shelf device with an open API may still be easy to replace.

The stronger moat appears when software, device, installation, workflow, and operational dependency work as one system.

MOAT 2 — TWO-SIDED MARKETPLACE

A marketplace becomes stronger as both sides grow.

More supply attracts more demand.
More demand attracts more supply.

When that loop works, the network itself becomes difficult to recreate because a new competitor must rebuild both sides of the market—not just copy the software.

MARKETPLACE MOATS ARE HARD TO BUILD

The challenge is getting the marketplace started.

Bootstrapping one from zero is extremely difficult unless you already have access to one or both sides.

The software may be easy to build. Creating enough buyers and sellers at the same time is the difficult part.

MARKETPLACE EXAMPLE — TINYSEED

TinySeed works like a marketplace connecting founders and investors.

It had an advantage at launch because there was already access to founders—and eventually investors as well.

The lesson: marketplaces work better when distribution exists before the marketplace itself is launched.

MARKETPLACE EXAMPLE — DYNAMITE JOBS

Dynamite Jobs was built by people who already had access to a remote-work audience through Tropical MBA.

That existing community reduced the marketplace cold-start problem.

The moat was not simply the job-board software. It was access to the people needed to make the marketplace useful.

MOAT 3 — SYSTEM OF RECORD

The hardest software to remove is often where the business actually runs.

Messages, approvals, states, decisions, coordination, history, and shared context accumulate inside the product.

Eventually the software becomes more than a tool. It becomes part of the company’s operating infrastructure.

WHY COLLABORATION CREATES STICKINESS

Ten identical user accounts create limited organizational dependency.

But ten people coordinating work, sending approvals, exchanging messages, updating statuses, and making decisions inside one platform create something much harder to move.

The accumulated coordination becomes part of the moat.

SLACK IS THE SIMPLE EXAMPLE

Teams may complain about Slack and even experiment with alternatives.

But years of messages, channels, habits, integrations, relationships, and team coordination make switching difficult.

Slack is no longer only chat software. It becomes part of the organization’s operating memory.

HOW A SYSTEM OF RECORD FORMS

A system of record grows when important work starts happening inside the product:

1. Communication
2. Approvals
3. Status changes
4. Historical records
5. Team coordination
6. Business context

The more operational history accumulates, the more difficult migration becomes.

MOAT 4 — EXCLUSIVE, FRESH DATA

A strong data moat captures information competitors cannot easily reproduce.

The strongest version is continuously refreshed.

A one-time copy becomes stale while the original product keeps receiving new information, building history, expanding coverage, and improving the value of its dataset.

THE DATA MOAT TEST

The moat weakens if someone can export the complete dataset, timestamps, history, and structure through an API.

The stronger model is:

Data flows in.
Value is created from it.
The continuously refreshed dataset cannot simply be cloned and moved into a competing application.

FRESHNESS IS PART OF THE MOAT

Imagine a database that continuously tracks companies, technologies, markets, or transactions.

Copying the database once does not recreate the business.

You still need next month’s information, then the month after that. The ongoing collection engine becomes more valuable than a single snapshot.

EXAMPLES OF DATA MOATS

The transcript points to products such as BuiltWith, fiscal.ai, and DealForma.

Their value depends on information that keeps changing.

A customer does not only need today’s dataset. They need the system continuously collecting, organizing, refreshing, and maintaining that information.

MOAT 5 — HIGH SWITCHING COSTS

Here is the test:

A competitor offers everything you provide for half the price. Does the customer still stay?

If switching creates migration cost, retraining, downtime, operational risk, lost history, or business disruption, customers may prefer to continue paying the incumbent.

MISSION-CRITICAL SYSTEMS CREATE SWITCHING COST

Think about finance software, ERP, or warehouse systems.

A cheaper alternative may exist, but replacing the system can affect approvals, inventory, shipping, reporting, payroll, or financial operations.

For a serious business, the downside risk can be far larger than the subscription savings.

SWITCHING COST IS MORE THAN MIGRATION

Real switching costs can include:

1. Moving data
2. Rebuilding integrations
3. Retraining employees
4. Recreating workflows
5. Changing internal processes
6. Accepting downtime risk

The harder these pieces are to move safely, the stronger the incumbent becomes.

BRAND AND TRUST REINFORCE THE MOAT

Customers are not only buying features.

They are buying confidence that the vendor will remain available, fix failures, answer support requests, and prioritize serious problems.

For mission-critical software, trust in the company behind the product can matter as much as the technology itself.

WHY VIBE-CODED REPLACEMENTS HAVE LIMITS

A technical individual may tolerate spending hours fixing a self-built tool.

A company with employees, customers, payroll, and millions in revenue has a different risk profile.

Saving a small amount on software may not justify the possibility of failure inside a critical business process.

AI-NATIVE SAAS FACES A HIGHER BAR

FAST ARR CAN STILL COLLAPSE

AI products can grow from zero to millions in ARR extremely quickly.

But buyers have also seen fast-growing AI companies collapse just as quickly.

That makes durability more important: what keeps customers paying when models improve, competitors appear, or the underlying technology becomes commoditized?

THE PRIVATE EQUITY QUESTION

Private equity buyers are not only asking whether the company is growing today.

They need confidence in future cash flow.

Their concern is simple: if building software becomes dramatically easier, what prevents another company from recreating the product and taking those customers?

THE INVESTMENT COMMITTEE FILTER

According to the interview, some buyers may refuse to bring businesses without meaningful moats to their investment committee.

That matters because the committee is the group that approves whether the firm can issue an LOI and continue pursuing the acquisition.

THE ZYRATALK CASE

ZYRATALK LOOKED HIGHLY ATTRACTIVE

ZyraTalk was an AI voice-agent business serving industries such as HVAC.

According to Einar, it had strong growth, strong retention, integrations, and significant market interest.

By traditional SaaS metrics, it looked like the kind of company that should attract many acquisition offers.

22+ BUYER MEETINGS

During the sale process, ZyraTalk reportedly held roughly 22–23 management meetings with interested buyers.

That is a high level of engagement.

Based on the company’s metrics and the number of meetings, Einar expected an avalanche of letters of intent from potential acquirers.

ZERO PRIVATE EQUITY LOIS

Not a single private equity firm submitted an LOI.

The company itself was not weak. Growth and retention were strong.

The issue was durability. Buyers were evaluating whether the revenue would survive and whether another AI company could rebuild enough of the product to threaten the business.

ZYRATALK STILL SOLD

ZyraTalk ultimately sold to EverCommerce, described in the transcript as a large public strategic buyer.

The acquisition became a competition between strategic buyers rather than private equity.

The case shows how the same SaaS business can look very different depending on the buyer’s strategic logic.

THE QUESTION BEHIND ALL FIVE MOATS

Every moat answers the same two questions:

1. A year from now, will this revenue still be here?
2. What prevents another company from rebuilding the product and taking the customer?

Growth proves demand today.

A moat gives buyers confidence about tomorrow.

THE SAAS MOAT CHECKLIST

1. HARDWARE

Ask:

Does replacing our software also require replacing hardware, installation, devices, or physical operating processes?

The more deeply your product connects software to the real world, the harder it becomes for competitors to replace you simply by recreating your application.

2. MARKETPLACE

Ask:

Does every new participant make the product more valuable to other participants?

A true marketplace moat becomes stronger as supply and demand reinforce each other. Competitors then need to reproduce the network itself rather than merely reproduce the software interface.

3. SYSTEM OF RECORD

Ask:

Are customers storing messages, approvals, decisions, workflows, history, and organizational context inside the product?

The more business activity that lives inside your system, the more disruptive migration becomes—and the less likely customers are to leave casually.

4. EXCLUSIVE DATA

Ask:

Are we collecting unique information that becomes more valuable over time?

Could a competitor export everything and reproduce it tomorrow?

The strongest data moat comes from information that is difficult to obtain, continuously refreshed, historically useful, and deeply integrated into the product.

5. SWITCHING COSTS

Ask:

If a competitor offered the same features at half our price, would customers move?

If migration threatens operations, data, integrations, workflows, training, reliability, or revenue, the customer may stay because switching risk matters more than the money they could save.

BUILD BEYOND FEATURES

AI makes software faster and cheaper to build.

So defensibility increasingly has to exist beyond the code itself.

Build products that become embedded in operations, relationships, proprietary data, customer trust, physical systems, and recurring workflows.

The goal is to become difficult to replace.