Yes. Every guide is free to read, with no account and no credit card. If we ever charge for something, it will be a product — never the library.

How long does validating an idea take?

Most founders get to a defensible verdict in two to four weeks: a dozen interviews, three tested assumptions, and one scored decision.

What if the verdict says pivot?

Then you saved months. The pivot guide walks you through which part to keep — usually the customer, rarely the feature.

Do I need a technical co-founder to use this?

No. Everything here happens before code: conversations, evidence, and one honest score.

The complete guide. It's one long read that links out to jobs & journeys, the evidence engine, personas and the launch kit.

Building A Moat: How to Create Defensible Competitive Advantage

A startup without a moat is fragile. Competitors can copy it. Bigger companies with more resources can enter the space and outspend you.

A startup with a moat is defensible. The bigger they get, the harder they are to compete against.

Understanding moats is how you go from "temporary advantage" to "durable competitive advantage."

This guide covers the 7 types of moats and how to build yours.

What Is A Moat?

A moat (borrowed from Warren Buffett) is something that protects your business and makes it hard for competitors to steal your customers.

Without a moat: Customers switch to a competitor if they're 10% cheaper or 10% better.

With a moat: Even if a competitor is 20% cheaper or better, customers don't switch because switching costs are too high or leaving means losing value they've built.

The 7 Types of Moats

1. Network Effects

How it works: The product gets more valuable as more people use it.

Example: Twitter. The more people join Twitter, the more valuable it is. If a competitor launches with better UX but no users, Twitter still wins because the network is valuable.

How to build:

Build a platform where value increases with users to the network
Example ideas: Marketplace, community, communication platform

Strength: Very strong. Network effects are hard to overcome.

Build time: Long (needs critical mass)

2. Switching Costs

How it works: Once customers have invested time/money/data into your product, switching is expensive.

Example: Salesforce. Companies spend 6 months configuring Salesforce, training teams, integrating with other systems. Switching to a competitor means doing that all over again.

How to build:

Deep integrations with other tools customers use
Complex data that's hard to export and migrate
Workflows built around your product
Training and team adoption

Strength: Very strong. Once built, it's durable.

Build time: Medium (6-12 months of customer use)

3. Brand

How it works: Customers prefer your brand even if competitors are equal.

Example: Nike vs. generic sports shoes. Nike's brand makes people pay more for essentially the same shoe.

How to build:

Consistent messaging and values over years
Earn trust through excellent product
Build cultural resonance
Thought leadership

Strength: Medium to strong. Depends on how deeply it's embedded.

Build time: Very long (2+ years)

4. Data & AI

How it works: You have more data or better ML models than competitors, making your product better.

Example: Spotify's recommendation engine. The more people use Spotify, the more data they get. Their recommendations get better. Competitors can't easily replicate this.

How to build:

Collect unique data only your users generate
Build ML models that improve with more data
Make the data/models defensible (not shareable)

Strength: Strong. Gets stronger over time.

Build time: Long (usually 18+ months)

5. Cost Advantage

How it works: You can operate more cheaply than competitors, so you can undercut them.

Example: Amazon. Through scale and infrastructure efficiency, Amazon can operate at lower margins than competitors. This is hard to overcome.

How to build:

Operate more efficiently than competitors
Leverage unique resources (cheaper suppliers, better tech infrastructure)
Scale to have unit economics competitors can't match

Strength: Strong but requires scale.

Build time: Long (2+ years to build efficiency advantage)

6. Switching Friction (Complexity)

How it works: Your product is so complex/customized that replacing it would require huge effort.

Example: Enterprise security software. Once integrated into a company's systems, replacing it would require IT team oversight, risk assessment, compliance validation. Too much friction to switch.

How to build:

Build deeper integration with enterprise workflows
Support complex use cases competitors ignore
Create business processes around your product

Strength: Very strong in enterprise context.

Build time: Medium (6-12 months)

7. Scale

How it works: Your infrastructure or platform is so large that competing would require massive upfront investment.

Example: AWS. The infrastructure, availability zones, services, and integrations around AWS are so massive that building a competitor would require $billions and years.

How to build:

Build platform/infrastructure that benefits from scale
Lock in customers with interoperability
Expand feature surface area faster than competitors can

Strength: Very strong at scale.

Build time: Very long (3+ years)

Moat Playbook: Build Your Moat

At Product-Market Fit (0-18 months):

Focus on switching costs and brand

Make onboarding so good customers don't want to leave
Start building thought leadership and brand
Make integrations sticky

At Growth Stage (18-36 months):

Layer on data/AI and network effects

Collect data that makes your product better
Build features that benefit from more users
Create network effects if possible

At Scale (3+ years):

Leverage scale, cost advantage, complexity

Use scale to build features competitors can't match
Leverage accumulated data
Integrate so deeply that switching is economically irrational

Moat Anti-Patterns

Anti-pattern 1: "Features are our moat" Reality: Features can be copied in weeks. Features are not a moat.

Anti-pattern 2: "We'll have a moat when we're big" Reality: Scale alone isn't a moat. You need a mechanism (network effects, switching costs, data, etc.). Scale just amplifies it.

Anti-pattern 3: "We're building a moat by being first" Reality: Being first is temporary unless you build one of the 7 moats. Latch onto one of the moat mechanisms.

Moat Analysis Template

For your startup, answer:

What is our moat? (Which of the 7?)
How strong is it today? (Weak / Medium / Strong)
What makes it defensible? (Why can't competitors easily copy it?)
What needs to happen for it to get stronger? (What milestones?)
What threatens it? (What could make it weaker?)

Real Example: Slack's Moat

Early stage (2014): Brand (best-designed chat tool), switching costs (integrations)

Growth stage (2015-2017): Network effects (more Slack workspaces = more value), switching costs (entire company workflows around Slack), data (Slack knows everything about your communications)

Today: Multi-layered moat (brand + switching costs + network effects + data)

This is why Microsoft Teams hasn't taken over despite being included free with Microsoft. The moat is too strong.

Connection to Competitive Analysis

Your moat is what you've identified in competitive analysis → as defensible differentiation.

Once you've found your moat, you obsess over building it.

Build your moat deliberately.

Most startups stumble into moats. Better ones build them intentionally.

Pick one of the 7. Build ruthlessly. Protect it jealously.

Use Edmired to identify and build your defensible competitive moat as you grow. Join the beta.