Economic moats and defensibility

At $500M ARR, there are two types of founders. The first built a moat—a structural advantage that makes their business harder to compete against than anyone else. The second did not. The first will survive a new competitor entering the market. The second will watch a well-funded competitor with slightly cheaper unit economics steal all their customers and destroy the business.

A moat is not product quality. It is not a bigger feature set. It is not a famous brand (though brand can be part of a moat). A moat is a structural advantage that gets harder to compete against as you scale, not easier.

When a competitor looks at your business and says, “I could build a better version of that,” and they might be right—they have no moat. They have a product. When a competitor looks at your business and says, “I could build a better version, but it would not matter because their customers are locked in,” or “I would have to build the same network they built,” or “I cannot match their economics,” then you have a moat.

Most founders do not think about moats until it is too late. They ship a product, customers love it, they scale to $100M ARR, and then a competitor with a better-funded sales team or a lower CAC undercuts them and wins. The founder says, “but our product is better.” That is exactly the problem. They confused product excellence with competitive defensibility.

The moat paradox: what makes a business defensible

There is a paradox in moats: the things that make a business defensible are rarely the things that make it initially successful.

At $1M ARR, the businesses that win are the ones with the best product-market fit. They ship the best product, find the right customer segment, and grow by word of mouth or sales. Product quality matters enormously. Distribution matters. Unit economics matter. But moats do not exist yet.

At $100M ARR, the businesses that survive are the ones with the strongest moats. Not the ones with the best product anymore (many products are good). The ones with structural advantages that make them harder to displace. A competitor with a 90% product and a strong moat will beat a competitor with a 95% product and no moat.

The paradox: the behaviors that build moats at scale are often the opposite of the behaviors that build product-market fit at launch.

At launch, you want agility. You want to talk to customers directly, move fast, iterate on feedback. Building a moat means taking on structure that slows you down—designing for network effects, building integrations that lock customers in, or optimizing for scale rather than speed.

At launch, you want focus. You want to pick one customer segment and win it completely. Building a moat might mean expanding to multiple segments, reducing unit economics in the short term but building a network that compounds.

At launch, you want simplicity. You want the simplest product that solves the customer’s problem. Building a moat might mean adding complexity—APIs, integrations, ecosystem plays—that make you stickier but add friction.

Because of this paradox, most founders end up on one of two paths:

Path 1: Build for product-market fit, then retrofit a moat. You ship a great product, find customers, scale to $50M ARR, and then realize you have no moat. At that point, a well-funded competitor can enter and beat you. Your only option is to pivot to a defensible model (build network effects retroactively, move upmarket to smaller addressable market but higher switching costs, or sell to a larger company before the competitor arrives). Many companies end up here.

Path 2: Build for moat from the start, at the cost of early speed. You ship a product that is intentionally designed to build switching costs, or designed to have network effects, or designed to drive scale economies. You grow more slowly at first because the design is heavier. But by $100M ARR, you have defensibility and the business is insurable. Slack took this path—the product was designed around teams (lock-in) and channels (network effects) from day one, not added later.

The best founders think about moats early, even if they do not prioritize them over product quality. They ask: “which moat am I building?” If the answer is “none,” they either accept the risk (and plan for an exit before competition commoditizes the category) or they pivot the business model to include a moat.

Types of moats: a taxonomy

There are six main types of moats. A business can have one or more, and the strongest businesses have multiple moats stacked.

Moat 1: Network effects

Network effects is when the product gets better as more people use it. Slack is more valuable with more people because there are more channels, more conversations, more integrations. Facebook is more valuable with more people because there are more friends and more posts to see. This creates a flywheel: more users → more value → more users.

Network effects create defensibility because a competitor cannot win by building a slightly better product. They have to build a network from scratch. If Slack has 500,000 teams using it, a new chat competitor cannot win by being 10% better. They have to convince all those teams to leave and build a new network. That is hard.

When network effects work: When the product’s value is primarily driven by the network, not the product itself. Marketplaces (Uber, Airbnb) have network effects because a marketplace is more valuable with more supply and more demand. Social networks (Facebook, Twitter) have network effects because a social network is more valuable with more friends. Software that enables collaboration (Slack, Figma) has network effects because collaboration tools are more valuable with more collaborators.

When network effects do not work: When the product’s value is primarily driven by the product, not the network. A video editor is not more valuable with more users. A note-taking app is not more valuable with more users (unless notes are shared). A code editor is not more valuable with more users (unless code is shared in real-time). Single-user products do not have network effects.

Quantifying network effects: The key metric is retention and expansion at the team/network level. If you add more users to a Slack workspace, does the workspace become stickier? (Yes—more channels, more conversations, more integrations.) If you add more sellers to Airbnb, does the marketplace become stickier? (Yes—more supply, lower wait times, faster bookings.) If network effects are present, expanding within existing customers should be cheaper and stickier than acquiring new customers.

Network effects in different models:

• Direct network effects: The value of the network is directly proportional to network size. A phone is worth more when more people have phones (you can call more people). Slack is worth more when more people are on Slack (you can collaborate with more people). This is the strongest type of network effect.
• Indirect network effects: The value increases when complementary offerings increase. A gaming console is more valuable when more game developers build games for it (not because more people own consoles, but because more games are available). iOS is more valuable when more app developers build for it. This is a weaker moat than direct network effects, but still a moat.
• Two-sided network effects: The value of the network depends on supply and demand on both sides. Uber is valuable to drivers because there are many riders. It is valuable to riders because there are many drivers. This creates a flywheel: add drivers → riders are happier → more riders sign up → drivers are happier → more drivers sign up. This is the most defensible type of network effect because it requires balancing two sides.

Moat 2: Switching costs

Switching costs is when it is expensive or disruptive for customers to move from your product to a competitor. Salesforce has switching costs because you have stored 10 years of customer relationship data in Salesforce. Switching to a competitor means migrating that data, retraining your team, rebuilding integrations, and risking data loss. The cost is huge.

Switching costs create defensibility because a competitor has to offer so much value that it is worth the pain of switching. If Salesforce is 90% as good as a new competitor, the switching cost is so high that the customer stays. The new competitor has to be 200% as good to be worth the switch.

When switching costs work: When customers invest heavily in using your product and it becomes embedded in their workflow. CRM systems (Salesforce) have high switching costs because teams spend thousands of hours entering data, configuring workflows, and training. Email systems (Gmail, Outlook) have high switching costs because email addresses are used everywhere. Infrastructure platforms (AWS) have high switching costs because applications are built on top of them.

When switching costs do not work: When customers can leave with minimal pain. Free consumer apps have no switching costs (you can delete and install a competitor with two taps). Commodity products have no switching costs (if all paints are similar, switching is painless). Services where the customer does not invest have no switching costs (a customer who has used your tool twice can try a competitor).

Quantifying switching costs: The key metric is churn when a competitor enters the market. If your churn stays flat, you have high switching costs. If your churn spikes (as a competitor’s marketing increases), you have low switching costs.

Another metric is Net Revenue Retention (NRR). If NRR is > 120%, customers are using more of the product over time and becoming more locked in. That is a signal of increasing switching costs. If NRR is flat or declining, switching costs are probably low (customers are not getting more invested in the product).

Types of switching costs:

• Data switching costs: If your product stores the customer’s valuable data, switching means migrating that data. If the data is messy or in a custom format, migration is expensive. Salesforce, Slack (conversation history), and Notion (linked documents) all have high data switching costs.
• Integration switching costs: If your product integrates with many other tools (Salesforce integrates with 500+ third-party apps), switching means rebuilding those integrations. The customer stays because the ecosystem is too expensive to rebuild.
• Workflow switching costs: If your product becomes part of the customer’s daily workflow, switching means retraining the entire team. If 100 people have spent 100 hours each learning Salesforce, that is 10,000 hours of training required to switch. The cost is prohibitive.
• Contractual switching costs: Some products have long-term contracts with penalties for early termination. This is the weakest switching cost because it is not structural; it is just a legal contract.

Moat 3: Scale economies

Scale economies is when your cost per unit decreases as you scale. Stripe benefits from scale economies because the cost to process a $1,000 transaction is the same as the cost to process a $1 transaction. But Stripe’s infrastructure cost per transaction decreases as they process more volume. At year one (1B transactions), they might have a 2% cost. At year five (100B transactions), they might have a 0.5% cost. The competitor cannot match this until they also have 100B transactions.

Scale economies create defensibility because you can sustain lower prices than competitors who are smaller. If Stripe can charge 1.5% and still be profitable, and a new competitor charges 2%, Stripe can just lower their price to 1.4% and the competitor cannot compete.

When scale economies work: When the unit cost genuinely decreases with volume. Payment processors (Stripe, Square) have scale economies because transaction processing has high fixed costs (infrastructure, fraud detection, compliance) and low marginal costs. Cloud infrastructure (AWS, Google Cloud) has scale economies because data centers are cheaper to operate at larger scale. Marketing platforms have scale economies because the cost to develop a new feature is split across millions of customers.

When scale economies do not work: When the unit cost is constant regardless of scale. Consulting services have no scale economies (an hour of consulting is always worth X regardless of how many consultants you have). Physical products sometimes have no scale economies if labor costs dominate (artisanal goods). Services where you hire people linearly with customer growth have no scale economies.

Quantifying scale economies: The key metric is gross margin at different scales. Plot your gross margin over time. If margin is improving as revenue grows, you have scale economies. If margin is flat or declining, you do not.

Another metric is fixed cost as a percentage of revenue. If you have $1M in annual fixed costs and $10M in revenue, you have 10% fixed cost. At $100M revenue, you have 1% fixed cost. That leverage is a scale moat.

How scale economies compound:

The strongest businesses have compounding scale economies. Stripe is the example:

• Year 1: Process $1B in transactions. Infrastructure cost is 2%. Charge customers 2.9% + $0.30.
• Year 5: Process $100B in transactions (100x). Infrastructure cost drops to 0.5% due to better systems. You can charge 1.5% + $0.10 and still be more profitable than year 1. A new competitor at $1B scale cannot undercut you.

This is defensible because the competitor has to reach your scale to match your costs. But by the time they do, you have moved further ahead.

Moat 4: Brand

Brand is when customers will choose your product over a competitor’s, even if the competitor is similar or cheaper. Luxury brands (Hermès, Rolex) have strong brand moats. Customers buy the brand, not just the product. Professional services firms (McKinsey, Goldman Sachs) have brand moats. Customers pay a premium for the reputation.

Brand creates defensibility because a competitor has to spend huge amounts to overcome the incumbent’s reputation. A new smartphone brand has to spend billions to compete with Apple because Apple’s brand is so strong.

When brand works: When the customer buys the brand, not the product. Luxury goods, professional services, and consumer brands (Coca-Cola, Nike) all have brand moats. The product might be similar, but the brand carries a premium.

When brand does not work: When the customer buys the product, not the brand. Enterprise software (CRM, ERP) has weak brand moats. Customers buy the best product, not the best brand. Commodities (commodity semiconductors, steel) have no brand moats. Customers buy on price.

Important caveat: Brand is the weakest moat in B2B software. Most B2B customers will switch to a competitor if the competitor is significantly better or cheaper. Brand matters but is secondary to product and price.

Quantifying brand: The key metric is brand premium—how much more do customers pay for your product vs a competitor’s similar product? Coca-Cola has a 20-30% brand premium (customers will pay more for Coca-Cola than for a private-label cola). A B2B software company has a 5-10% brand premium if it exists at all.

Another metric is brand recall. If you ask customers what CRM they use, do they say “Salesforce” or do they have to think? High brand recall is a sign of a strong brand moat.

Moat 5: Data

Data is when you have information that makes your product better or your predictions more accurate. Google’s search ranking algorithm benefits from having indexed the entire web. Netflix’s recommendation engine benefits from having watched millions of user preferences. Your competitor cannot build a competing search engine or recommendation engine because they do not have the data.

Data moats create defensibility because the competitor has to acquire the data from scratch, which might be impossible or might take years.

When data works: When data is proprietary and accumulated over time. Financial data (Bloomberg) has a data moat because they have spent 40 years collecting financial data that is hard to replicate. Medical data (insurance companies, hospitals) has a data moat because they have accumulated patient records. Usage data (Google, Facebook) has a data moat because they have captured user behavior.

When data does not work: When data is commoditized and easy to access. Stock prices are widely available, so no data moat. Weather data is widely available. Customer lists are sometimes available for purchase. If the data is easy to acquire, it is not a moat.

Quantifying data: The key metric is proprietary data advantage—how much better is your product because of the data you have? If your recommendation engine is 5% better than a competitor’s because of data, that is a weak moat. If it is 50% better, that is a strong moat.

Another metric is time-to-replicate. How long would it take a competitor to accumulate the same data? If a year, the moat is weak. If ten years, the moat is strong. If never, the moat is permanent.

Moat 6: Regulatory barriers

Regulatory barriers is when the government or a regulatory body creates barriers to entry. Banks have regulatory moats because it is illegal to open a bank without a charter. Pharmaceutical companies have regulatory moats (patents) because the government gives them exclusive rights to sell a drug. Telecom companies have regulatory moats because it is expensive to build out infrastructure and the government controls licenses.

Regulatory moats create defensibility because a competitor cannot enter the market without jumping through regulatory hoops that are expensive and time-consuming.

When regulatory barriers work: When the government has explicit barriers to entry. Pharmacies have regulatory moats (you need a license to dispense certain drugs). Accountants have regulatory moats (you need a CPA license to sign certain documents). Brokers have regulatory moats (you need a license to trade securities). These are strong moats.

When regulatory barriers do not work: When the government does not have explicit barriers. Most SaaS companies do not have regulatory moats. Most consumer products do not have regulatory moats. Regulatory moats are rare in software because software is easy to copy.

Quantifying regulatory moats: The key metric is cost to comply. If it costs $1M and 2 years to get a regulatory license, that is a strong moat. If it costs $100k and 2 months, that is a weak moat.

Diagnostic: which moat are you building?

Before anything else, ask: which moat does my business have (or should have)?

Here is a table by business model:

For your business:

1. Identify your business model. Are you a marketplace, a SaaS company, a network, an infrastructure platform, a consumer app, a supply-side business?
2. Identify the primary moat. What moat is most relevant for your model? Marketplaces need network effects. Enterprise tools need switching costs. Infrastructure needs scale economies.
3. Assess your current moat. Do you have this moat today? How strong is it? Can you measure it?
4. Create a moat roadmap. What would it take to build this moat? What investments are required? What metrics should you track?

Founder mistakes: confusing product excellence with moats

The classic mistake is assuming product quality creates a moat.

Mistake 1: “Our product is so good that competitors cannot catch up”

This is the most common founder mistake. A founder builds an amazing product, customers love it, and they think: “competitors cannot copy this quickly; we have a moat.”

This is almost always wrong. Given enough time and resources, competitors can copy your product. If your moat is product quality, it is a weak moat. A well-funded competitor with a better team can catch up in 12-18 months. Or they can acquire an existing product and rebrand it. Or they can hire your entire team.

Product quality is table stakes, not a moat. Slack’s original product was not superior to Hipchat or Lync; it was good, but not dramatically better. What made Slack defensible was (1) switching costs—teams organized around Slack channels and conversations, making it expensive to switch—and (2) network effects—integrations with other tools, making the Slack ecosystem valuable. The product quality got them to critical mass; the moat protected them.

Example: A founder built a note-taking app that was objectively better than Evernote. Faster, simpler, more flexible. Users loved it. The founder thought: “Evernote is slow and bloated; they cannot copy us.” But Evernote noticed the threat and shipped a faster version. The founder’s competitive advantage evaporated because it was based on product quality, not a moat. The founder’s only exit option was to sell to Evernote.

How founders fail: They ship a great product, get traction, and assume defensibility follows. They focus on building more features instead of building moats. By the time they realize there is no moat, a funded competitor has arrived.

Mistake 2: “We have switching costs because customers love us”

Switching costs are not about love; they are about pain. A customer can love your product but have low switching costs if they have not invested heavily in it.

Low switching costs: A customer has used your design tool for 3 months. They have created 10 projects. If a competitor’s tool is better, they can export the projects and switch with one afternoon of work. Switching costs are low.

High switching costs: A customer has used your design tool for 3 years. They have created 1,000 projects, all with custom components, all with integrations to their CI/CD pipeline, all with team members who have 500 hours invested in the tool. Switching means migrating 1,000 projects, retraining the team, and rebuilding all the integrations. Switching costs are high.

The difference is investment, not love. A customer can love you and have low switching costs. A customer can dislike you and have high switching costs.

How founders fail: They assume customer retention = high switching costs. But retention might be because the product is so good that no alternatives exist, not because switching would be expensive. When a competitor enters with a similar product, churn spikes and the founder realizes there were no switching costs.

Mistake 3: “We will build the moat after we achieve product-market fit”

This is the delayed-moat fallacy. A founder ships a product, gets to $10M ARR, and thinks: “now that we have product-market fit, let’s add the moat.” But by then it is often too late.

At $10M ARR, your customer base is already acquired and the window to lock them in has closed. If Slack wanted to add network effects after launch, they would have to retroactively design channels and integrations for existing customers. Or they would have to release a product redesign that re-acquired all the customers.

The strongest moats are built from day one. Slack was designed for team channels (lock-in via workflow) from launch. Stripe was designed for simple integrations (lock-in via ecosystem) from launch. Figma was designed for collaboration (network effects within teams, lock-in via workflow) from launch.

Retrofitting a moat is possible but expensive. Notion had no switching costs at launch; documents were easy to export. By $100M ARR, they retrofitted switching costs through deep embedding and integrations. But it took years of work and they had to overcome customer reluctance to lock in.

How founders fail: They prioritize product excellence and growth over moat-building. By the time they realize there is no moat, they have a $50M ARR business that is vulnerable to a better-funded competitor.

Mistake 4: “Network effects are a moat; we will build a network”

Network effects are powerful, but they are misunderstood. Most founders overestimate the likelihood that they will build true network effects.

True network effects require three things: (1) the product must be better with more users, (2) the user must see the network (they must interact with other users), and (3) there must be network switching costs—if I leave, I lose my network.

Many products have one or two of these but not all three. A productivity tool might be better with more users (more templates, more integrations) but the user does not see the network (they use the tool alone). That is not a network effect.

Example: A founder built a collaboration tool and thought it would have network effects. “The more teams that use it, the more integrations we can build, the more valuable it becomes.” But the user (a team) does not see or care that other teams are using the tool. The tool is not more valuable because thousands of teams exist. The network does not create switching costs. A competitor can build the same integrations and the user can switch painlessly.

That is not a network effect; that is a scale economy (we can build integrations faster because we have more users). The founder confused the two.

How founders fail: They design for network effects but end up with a product that has no real network. Or they assume network effects exist when they do not. Or they build network effects that are too weak to prevent a competitor from entering.

Mistake 5: “Our moat is our team”

A founder’s competitive advantage is often the team. “Our team is so good; we can outrun any competitor.” This is not a business moat; this is a founder moat. The moment the team leaves or is hired away, the moat disappears.

A real business moat survives a team change. If your CTO leaves to start a competitor, the new CTO should be able to maintain the business. If they cannot, you do not have a structural moat; you have a team-specific advantage.

Example: A founder built a fintech startup with a world-class team of quants. The secret sauce was the team’s ability to price derivatives. The founder thought: “our moat is our team; they are the best in the world.” But if the top 5 quants leave to start a competitor, the moat disappears. The founder is left with an empty product and no defensibility.

A real fintech moat would be (1) scale economies (the more transactions, the better our pricing), (2) data (we have 10 years of transaction history that informs our pricing), or (3) switching costs (customers have integrated our system into their trading desk). Any of these would survive a team change.

How founders fail: They believe in the team as a moat and do not build a structural advantage. When the team leaves or burnout sets in, the business is vulnerable.

How to build moats at scale

Moats are not accidents. They are built intentionally. Here is how:

Build moats aligned to your motion

Different motions benefit from different moats. Choose the moat that fits your model, not the moat you wish you had.

Product-led growth needs switching costs or network effects.

Why? Because in PLG, you do not have a sales team to prevent customers from leaving. Your only defense is that leaving is expensive or your product is better because of the network. Build switching costs by embedding the product deep in workflows (Figma documents embedded in design systems, Notion databases embedded in team knowledge) or design network effects (Slack channels are more valuable with more members).

Sales-led growth needs switching costs or scale economies.

Why? Because in sales-led, you have high CAC and you need long payback periods. The only way to sustain that is to make customers sticky (switching costs) or to be so much more efficient than competitors that you can undercut them (scale economies).

Marketplace growth needs network effects and switching costs.

Why? Because marketplaces need supply and demand to balance. If you can create a virtuous cycle (more buyers → more sellers → more buyers), network effects create defensibility. And if supply and demand data becomes locked in, switching costs follow. Airbnb’s switching costs are that supply (listings) and demand (bookings) are locked into their platform.

Build moats intentionally from day one

Do not assume moats emerge. Design for them.

If you want network effects, design the product to show the network. Make it so customers see the value of more users. Slack shows you all the channels and all the people; the network is visible. Figma shows you all the projects and all the collaborators; the network is visible. If your product hides the network, network effects will not emerge.

If you want switching costs, design for embedding. Create integrations that lock customers in. Create data stores that are expensive to migrate. Create workflows that are hard to replicate in a competitor’s product. Notion designed documents as deeply relational (links, backlinks, relations) so that exporting and importing into a competitor is painful. That created switching costs.

If you want scale economies, design for cost reduction. Stripe’s payment processing is designed to handle billions of transactions at minimal cost. AWS is designed for multi-tenant infrastructure that costs less per unit as volume grows. The design choice enables the moat.

Build moats by compounding them

The strongest businesses have multiple moats that reinforce each other. Slack has switching costs (teams are locked in) and network effects (more integrations for more teams). Stripe has scale economies (lower fees at higher volume) and switching costs (integrations and infrastructure dependency). Notion has switching costs (data lock-in) and network effects (more templates and use cases for more users).

When moats compound, they become very hard to disrupt. A competitor has to overcome multiple defensibility layers, not just one.

How to compound:

• Switching costs + network effects: Lock customers in AND make the product better with scale. Example: Slack channels are hard to migrate, and they become more valuable as more people join.
• Switching costs + scale economies: Lock customers in AND use their data to improve your model. Example: Stripe’s integrations lock customers in, and their transaction volume allows them to reduce fees and improve fraud detection.
• Scale economies + network effects: Use scale to improve the product AND the product becomes more valuable with more users. Example: Netflix’s scale allows them to produce more content, which makes the platform more valuable, which attracts more users, which funds more content.

Protect against moat erosion

Moats degrade. A network effect can be disrupted if a competitor creates a larger network. Switching costs can be eroded if a competitor makes migration painless. Scale economies can be disrupted if a new technology allows smaller competitors to reach scale faster.

Monitor your moat continuously. Track the metrics that measure your moat strength. For network effects, track engagement and expansion rate (are existing users adding more users?). For switching costs, track churn (does it spike when competitors enter?). For scale economies, track unit cost (does it improve over time?).

If you see degradation, act fast. Slack saw competitors trying to reduce switching costs (by building better APIs and migration tools), so they invested in integrations and ecosystem to increase lock-in. Stripe saw competitors trying to match their fee structure, so they improved their fraud detection (data moat) and their developer experience (switching costs) to stay ahead.

Real examples: moats in action

Example 1: Slack—switching costs and network effects

Slack is the canonical example of built-in defensibility.

Switching costs: Slack teams organize around channels (not direct messages, not threads in email). Every message, conversation, and decision is in a channel. A team that has spent a year in Slack has thousands of conversations, decisions, and context in channels that are searchable and linked. Exporting that to a competitor means losing the searchability and the context. The team would have to retrain on a new system.

Additionally, Slack integrates with dozens of tools (GitHub, Jira, Salesforce, etc.). Those integrations are baked into workflows. A team that has Slack bots posting deployment notifications from GitHub has automated processes that would have to be rebuilt in a competitor.

Switching costs are intentional by design: Slack channels are the way you use the product, and once you have years of conversations in channels, leaving is expensive.

Network effects: More teams adopting Slack means more integrations. More integrations means Slack becomes more valuable (more tools are automatically posted to Slack). This creates a flywheel: add team → Slack becomes more valuable → more teams join.

Also, if I use Slack at Company A and Company B, I use the same client and shortcuts. Muscle memory and habit mean I am locked in. If I switch companies, I immediately want Slack because I already know how to use it.

Moat strength: Very strong. Slack’s revenue growth has been defended against competitors (Microsoft Teams, Google Chat) because the switching costs are high. Even though Teams is built into Microsoft’s stack, customers stick with Slack because of the ecosystem and the years of context.

Example 2: Stripe—scale economies and switching costs

Stripe is an example of scale economies compounding into defensibility.

Scale economies: Stripe’s unit cost (cost to process a transaction) decreases as transaction volume increases. At launch, Stripe was not cheaper than existing payment processors (Square, Authorize.net). But over time, Stripe’s infrastructure became more efficient. They can now process billions of transactions at lower unit cost than competitors who process billions of transactions, but at lower scale.

This allows Stripe to have lower fees than competitors without sacrificing margin. A startup payment processor cannot compete on fee because they do not have Stripe’s infrastructure efficiency.

Switching costs: Stripe’s integrations lock customers in. An e-commerce platform that integrates Stripe’s APIs (for payouts, tax calculation, subscriptions, radar fraud detection) has built Stripe into their platform. Switching means rewriting all those integrations. The switching cost is high.

Moat strength: Very strong. Stripe’s scale moat allows them to charge lower fees while maintaining margins. Their switching cost moat protects them from competitors entering with “even lower” fees. A competitor would have to build Stripe’s infrastructure (impossible without $10B+ revenue) and match their fee structure (not profitable at scale).

Example 3: Notion—switching costs (retrofitted)

Notion is an example of switching costs being built retroactively and reinforced over time.

At launch: Notion’s moat was weak. It was a flexible database tool, but switching to Coda or Fibery or any other tool was painless. Data was easy to export.

Retrofit (2019-2021): Notion realized they needed switching costs. They added deep relational features (links, backlinks, properties across databases). They added advanced formulas, rollups, and relations. They added API integrations. Over time, Notion databases became deeply relational and expensive to migrate. A team that has spent a year building a complex knowledge base in Notion (with thousands of linked documents, custom properties, and integrations) would lose functionality in a competitor’s tool.

2022-present: Notion added AI and made the product more integrated. The switching costs increased further.

Moat strength: Moderate-to-strong. Notion’s switching costs are now high enough to defend against competitors. But Notion can never completely lock customers in (since documents can be exported), so the moat is always a bit vulnerable. But combined with brand and product excellence, Notion is defensible.

The asymmetry: same product with/without moat

To see the difference between a moat and no moat, imagine two identical products:

Product A: No moat

• Launch at $99/month
• Find 1,000 customers in year one
• Competitor launches at $79/month (10% cheaper, 80% as good)
• 20% of customers switch because the competitor is cheaper
• You drop price to $79 to compete
• Another competitor launches at $59/month (5 years ahead of you in efficiency)
• Another 20% of customers switch
• You drop price to $59
• Margin collapses and the business becomes unprofitable
• You exit for a low price or shut down

Product B: With moat (switching costs)

• Launch at $99/month
• Find 1,000 customers in year one
• Customers embed the product in workflows, lock in data, and integrate with other tools
• Competitor launches at $79/month (10% cheaper, 80% as good)
• 2% of customers switch (the rest face too high a switching cost)
• You keep pricing at $99/month; churn stays flat
• Another competitor launches at $59/month
• 1% of customers switch (the majority face too high a switching cost)
• You keep pricing at $99/month; margin stays healthy
• Over time, you invest in the product and improve it (you can afford to because margin is healthy)
• The competitor cannot undercut you because the switching cost prevents customers from leaving
• You build a defensible business

Same product. Different moat. Wildly different outcomes.

Diagnostic: do you have a moat?

Here is a simple way to test whether you have a moat:

Test 1: The competitor test. A competitor launches with 80% of your product at 50% of your price. What happens to your churn?

• If churn spikes (>50%), you have no moat. Customers are leaving because the competitor is cheaper.
• If churn stays flat (<10%), you have a moat. Customers are staying because switching is too expensive or your product is too sticky.
• If churn rises moderately (20-30%), you have a weak moat. Some customers are switching.

Test 2: The ecosystem lock-in test. If a customer wanted to switch to a competitor, what would they lose?

• If the answer is “nothing; they can export their data and re-import in 2 hours,” you have no moat.
• If the answer is “all their integrations, their team’s workflows, and 100 hours of configuration,” you have a strong moat.
• If the answer is “some data and some workflows,” you have a weak moat.

Test 3: The expansion test. Are customers expanding their usage over time?

• If yes (NRR > 100%, more seats, more features), they are becoming more locked in. You have a moat.
• If no (flat usage or declining), customers are not getting more locked in. You might not have a moat.

Test 4: The brand premium test. Are customers willing to pay more for your product than a competitor’s similar product?

• If yes, you have some form of moat (brand, product quality, or switching costs).
• If no, you have no moat (assuming the competitor is actually similar).

Rules for building defensible businesses

Rule 1: Do not confuse product excellence with moats.

Product excellence is table stakes. It gets you customers. A moat is what keeps them. Build both, but understand the difference.

Rule 2: Choose a moat aligned to your business model.

Marketplaces need network effects. Enterprise tools need switching costs. Infrastructure needs scale economies. Trying to build a network effect in a single-player product will not work.

Rule 3: Build moats early, but not at the cost of product-market fit.

At $1M ARR, focus on finding product-market fit. Build the best product. At $5-10M ARR, start layering in moat-building. At $100M ARR, the moat should be the business.

Rule 4: Measure your moat strength continuously.

For network effects, track engagement and expansion rate. For switching costs, track churn. For scale economies, track unit cost. Know whether your moat is strengthening or weakening.

Rule 5: Compound moats whenever possible.

One moat is okay. Two moats is better. Three moats is almost impossible to displace. Slack has switching costs and network effects. Stripe has scale economies and switching costs. Notion has switching costs and brand. Stack moats on top of each other.

Rule 6: Protect against moat erosion.

Moats degrade. A competitor will find ways to reduce your switching costs (better APIs, easier migration) or match your scale (lower unit costs). Monitor continuously and invest in moat maintenance.

Rule 7: A moat is not a guarantee.

Ten years ago, Microsoft had a massive moat (Windows, Office, integrations). Apple disrupted it with mobile. Kodak had a massive moat (film patents). Digital photography disrupted it. Your moat can be disrupted by a technology shift or a new competitor with a different model. A moat buys you time and defensibility, but it is not immortality.

Next tier: Pricing power and defensibility

A moat is the foundation of pricing power. If you have high switching costs, you can raise price and customers will stay. If you have network effects, you can charge for premium features and customers will pay. If you have scale economies, you can maintain margin even as you lower prices.

The next chapter explores pricing power as the ultimate test of moat strength: can you raise prices without losing customers? If yes, you have a moat. If no, you do not.