Skip to main content
Menu

⚠️ Risk Warning: Trading forex, CFDs, and cryptocurrencies involves substantial risk of loss and may not be suitable for all investors. This platform provides educational content only and does not constitute financial advice.

Ξ Level 2 · Beginner Research & Due Diligence Project Fundamentals

Competitive Landscape

Crypto competition includes direct protocols, centralised services, traditional financial products and even the option for users to do nothing. A useful co

Progress 0%

Reading progress — saved on this device

RESEARCH & DUE DILIGENCE · PROJECT FUNDAMENTALS
Risk-first note. Projects often define a market so narrowly that they appear unique. If a user can solve the same problem with a bank, exchange, SaaS product or different blockchain, those alternatives belong in the competitive set.

Learning objectives

  • Define competitors by user job rather than project category.
  • Compare products on cost, liquidity, trust, UX, distribution and switching costs.
  • Distinguish sustainable advantage from temporary token subsidies.

What it is

Direct competitors use a similar architecture and target the same user. Indirect competitors may use a completely different technology while still satisfying the same need. Both matter for market share and pricing power.

Crypto markets can exhibit network effects through liquidity, integrations, collateral acceptance, developer tooling and community distribution. But network effects should be demonstrated with switching costs or compounding utility, not assumed from size alone.

Forkability is an important constraint. Open-source code can make product features easy to copy, so defensibility may reside in liquidity, brand, governance credibility, data, distribution or regulatory access rather than software code.

How to analyse it

Build a feature matrix only after defining the user decision. Traders may prioritise depth, spread and reliability; developers may value tooling and composability; institutions may prioritise legal structure, custody and reporting.

Compare unit economics. A protocol that charges lower fees because it is distributing token subsidies may not have a sustainable cost advantage. Remove incentives where possible and compare underlying gross margins or take rates.

Assess distribution. Wallet integrations, exchange listings, developer mindshare and institutional partnerships can be harder to reproduce than technical features. Distribution can explain why a technically inferior product retains users.

Monitor strategic response. Competitors can cut fees, launch incentives, copy features or integrate new chains. A static market-share snapshot is less useful than understanding how quickly advantages can be neutralised.

Research framework

CheckWhy it mattersWhat to verify
User jobDefines true competitive setList direct and non-crypto alternatives.
EconomicsTests sustainable pricingCompare fees, subsidies, margins and capital efficiency.
Switching costsTests defensibilityMeasure liquidity fragmentation, integrations, custody and workflow lock-in.
DistributionTests reachCompare wallets, exchanges, developers, institutions and community channels.

Evidence hierarchy and limitations

Market-share data should use comparable denominators. TVL share, DEX volume share and developer share measure different things. A project can lead in capital deposited while lagging in revenue or active users.

Beware self-reported partnership lists. Verify whether an integration is live, economically used and material. A logo on a website can represent anything from a deep commercial relationship to a one-time technical connection.

Worked example and thought exercise

Protocol A has 45% of sector TVL but pays 8% annual token incentives. Protocol B has 25% of TVL, pays no incentives and generates twice the fees per dollar of liquidity. A simple TVL ranking would miss the difference in economic quality.

If users can move between protocols in minutes with minimal cost, feature differentiation may be fragile unless liquidity or distribution creates a stronger moat.

Thought exercise: Which competitive advantage would be hardest to copy in an open-source protocol: code, liquidity, distribution, governance reputation or regulation?

Common mistakes and practical workflow

  • Defining competitors only as projects using the same blockchain architecture.
  • Treating TVL leadership as automatic pricing power.
  • Ignoring subsidy-adjusted economics.
  • Counting announced partnerships without verifying usage.

Practical workflow

  1. Define the user job and alternative solutions.
  2. Create a comparable metric set for cost, liquidity, UX and trust.
  3. Adjust market share for subsidies and concentration.
  4. Identify switching costs and real distribution advantages.
  5. Model how competitors could respond to the project’s strongest feature.

Knowledge checkpoint

  1. Why are indirect competitors important?
  2. What makes open-source code a weak moat by itself?
  3. How can subsidies distort market share?
  4. Why should partnerships be verified for actual usage?

FAQs

❓ Is the largest protocol always the strongest competitor?

No. Size can be subsidised or concentrated and may not translate into durable economics.

❓ What is a moat in crypto?

A durable advantage such as liquidity, distribution, integrations, brand, data, governance credibility or regulatory access.

❓ Should centralised exchanges count as DeFi competitors?

Yes when they solve the same user job, such as trading, lending or custody.

❓ How often should the landscape be updated?

Frequently enough to capture material fee changes, launches, incentives, integrations and regulatory shifts.

Summary

Competitive research should start from the user’s available alternatives. Sustainable advantage comes from economics, liquidity, switching costs, distribution and trust—not simply from unique terminology or temporary token incentives.

BUILD YOUR OWN PATH

Want this in a personalised order?

Take the crypto assessment and get a custom path of 10 modules matched to what you already know. Free, no card required.

Build my path →