Scrolls
6 min read
On this page

Competitive Analysis

Know your competitors, but do not copy them. The purpose of competitive analysis is not to build a feature comparison matrix and check every box. It is to understand the strategic landscape — why competitors make the choices they make, where they are strong, where they are vulnerable, and where you can build a position they cannot easily replicate.

Why Most Competitive Analysis Is Useless

The typical competitive analysis is a spreadsheet with competitors across the top and features down the side, filled with checkmarks. This is the least useful form of analysis because it tells you nothing about strategy. It answers "what do they have?" but not "why do they have it?" or "where are they going?"

Feature comparison (low value):
                   Us    Comp A    Comp B
  Feature X        Y       Y        N
  Feature Y        N       Y        Y
  Feature Z        Y       N        Y
  Price          $49     $99      $29

  Conclusion: "We need to build Feature Y."
  Problem: This tells you nothing about whether Feature Y matters
           to your target customers or whether building it is
           strategically sound.

A feature comparison treats all features as equally important and assumes that more checkmarks equals a better product. In practice, the product with fewer features often wins because it does the important things better.

Strategic Competitive Analysis

Instead of comparing features, analyze competitor strategy. Understand their choices, not their feature list.

Understanding Competitor Strategy

For each major competitor, answer:

Strategic questions:
  1. Who is their core customer? (Not who they say — who actually pays them)
  2. What is their business model? (How do they make money)
  3. What are they optimizing for? (Growth? Margin? Market share?)
  4. What have they said no to? (What complaints do their users have?)
  5. Where are they investing? (Job postings, acquisitions, blog posts)
  6. What is their distribution advantage? (Sales team? Community? Brand?)
  7. What would be hard for them to change? (Architecture, business model, culture)

This analysis reveals strategic intent, not just current features. A competitor hiring 50 machine learning engineers is telling you something about their future even before they ship anything.

Direct vs Indirect Competition

Direct competitors solve the same problem the same way. Indirect competitors solve the same problem differently. Both matter, but indirect competitors are more often underestimated.

For a project management tool:
  Direct competitors:   Asana, Monday, Jira, Linear
  Indirect competitors: Spreadsheets, email threads, Slack channels,
                        sticky notes on a whiteboard, no tool at all

For a cloud monitoring platform:
  Direct competitors:   Datadog, New Relic, Grafana Cloud
  Indirect competitors: Custom dashboards, checking logs manually,
                        waiting for users to report problems

Indirect competition is especially important for new categories. If you are creating something that did not exist before, your real competitor is the status quo — whatever hacky workaround people are using today. Your marketing needs to convince people the problem is worth solving with a dedicated tool, not just that your tool is better than the other tool.

Competitor Segmentation

Not all competitors compete with you for the same customers. Map competitors to the segments they serve.

Segment mapping:
  Enterprise (1000+ employees):
    Competitors: Salesforce, ServiceNow, Oracle
    Their advantage: Integration, compliance, existing relationships
    Our disadvantage: We lack enterprise sales, SSO, audit trails

  Mid-market (100-1000 employees):
    Competitors: HubSpot, Zendesk
    Their advantage: Brand recognition, sales teams
    Our disadvantage: We lack case studies at this scale

  Small teams (under 100):
    Competitors: Linear, Notion, Basecamp
    Their advantage: Simplicity, community
    Our advantage: We do X better than any of them

This mapping helps you understand where you can win today and which segments to approach later. Trying to compete across all segments simultaneously is a recipe for losing everywhere.

Moats & Defensibility

A moat is what prevents competitors from easily replicating your position. Features are not a moat — they can be copied. Moats are structural advantages that compound over time.

Types of Moats

Network effects. The product becomes more valuable as more people use it. This is the strongest moat in software.

Network effect examples:
  Slack:      More colleagues on Slack = more useful for everyone
  GitHub:     More developers = more open source = more reason to use GitHub
  Figma:      More designers = more shared components = better design systems
  LinkedIn:   More professionals = better recruiting = more professionals

Switching costs. The cost (time, money, pain) of moving to a competitor.

Switching cost examples:
  Salesforce:  Years of customization, training, integrations
  AWS:         Code depends on AWS-specific services
  Stripe:      Payment data migration, API integration changes
  Jira:        Workflows, custom fields, years of history

Data advantages. You have data that competitors do not, and that data makes your product better.

Data advantage examples:
  Google Search:  Decades of search queries improve ranking algorithms
  Waze:           Real-time traffic data from users makes routing better
  Stripe:         Transaction data improves fraud detection
  Grammarly:      Writing corrections data improves suggestions

Brand & trust. In some markets, being the known, trusted option is a significant advantage.

Brand advantage examples:
  AWS:           "Nobody gets fired for choosing AWS"
  Datadog:       Default choice for cloud monitoring
  Stripe:        Default choice for payments
  Twilio:        Default choice for communications APIs

Economies of scale. Being bigger makes you cheaper or better, creating a flywheel.

Scale advantage examples:
  AWS:           More customers = more investment in infrastructure = lower prices
  Vercel:        More deploys = better edge network = faster sites = more deploys

Building Defensibility

Moats are built, not declared. You cannot decide to have network effects — you have to build a product where network effects emerge naturally. The strategic question is: which moat can you build given your product and market?

Moat-building questions:
  "Does our product get better as more people use it?"
  "What would a customer lose by switching to a competitor?"
  "Do we accumulate data that improves the product over time?"
  "Is our brand becoming synonymous with the category?"
  "Does our scale give us cost advantages?"

If the honest answer to all of these is "no," you are competing on features alone, and features can always be copied.

How to Monitor Competitors

Sources of Intelligence

Public sources:
  - Product changelog and release notes
  - Blog posts and engineering blog
  - Job postings (reveals investment areas)
  - Press releases and media coverage
  - Conference talks and presentations
  - Pricing page changes
  - G2, Capterra, and review site trends
  - GitHub activity (for open-source competitors)
  - SEC filings (for public companies)
  - Patent filings

Customer sources:
  - Win/loss analysis (why did we win or lose a deal?)
  - Support tickets mentioning competitors
  - Sales call recordings
  - Customer interviews and surveys
  - Community forums and social media

Frequency

Do not make competitive analysis a one-time event. Build it into your rhythm.

Competitive analysis cadence:
  Weekly:    Scan competitor changelogs, news mentions
  Monthly:   Review win/loss data, update competitive positioning
  Quarterly: Deep-dive competitive strategy review
  Annually:  Full competitive landscape assessment, update strategy

Win/Loss Analysis

The most valuable competitive intelligence comes from deals you won and lost. After every significant sales interaction (won or lost), ask:

Win/loss questions:
  "Who else were they evaluating?"
  "What was the deciding factor?"
  "What did the competitor do better?"
  "What almost made them choose the competitor?"
  "What feature or capability was the deal-breaker?"

Over time, patterns emerge. If you consistently lose to Competitor X on pricing, that is a strategic signal. If you consistently win on ease of use, that tells you what to protect.

Responding to Competitors

When to Respond

Not every competitor move requires a response. Most do not.

Respond when:
  - A competitor enters your core segment with a differentiated offering
  - A competitor's move threatens your primary moat
  - Customers are consistently asking for a capability a competitor has
  - A competitor's pricing change affects your win rate

Do not respond when:
  - A competitor ships a feature you were not planning to build
  - A competitor gets press coverage for something irrelevant to your users
  - A competitor copies one of your features (they are following, not leading)
  - A competitor enters a segment you are not targeting

How Not to Respond

The worst response to competition is reactive feature building. If Competitor X launches feature Y and you immediately add it to your roadmap, you are letting your competitor set your strategy. You are following instead of leading.

Bad competitive responses:
  "They have it, so we need it."
  "We need to match their pricing."
  "We need to be in that market too."
  "We need to announce something to counter their press."

Good competitive responses:
  "They shipped X. Does our target customer care? Let us check the data."
  "They cut prices. What does that mean for their business model?
   Can they sustain it?"
  "They entered our market. Where are they weakest?
   How do we strengthen our position?"

Real-World Examples

Figma vs Sketch: Platform Shift

Figma did not try to out-feature Sketch. They made a strategic bet that design tools would move to the browser. While Sketch optimized their Mac app, Figma built a web-based tool with real-time collaboration. By the time Sketch recognized the threat, Figma's network effects (shared files, collaborative editing, design systems) had created a moat that Sketch could not easily cross.

Notion vs Confluence: Simplicity as Strategy

Notion did not build a better Confluence. They built a simpler tool for a different audience. While Confluence served enterprise teams with complex permission structures and integration ecosystems, Notion targeted individuals and small teams who wanted flexibility without administration overhead. The competitive analysis that mattered was not Confluence's feature list — it was understanding that a large market segment was over-served by Confluence's complexity.

Datadog: Moat Through Integration

Datadog built defensibility through breadth of integrations. With hundreds of integrations across cloud providers, databases, and application frameworks, switching away from Datadog means recreating all those monitoring connections. This is a switching cost moat — each integration a customer configures makes them less likely to leave.

Common Pitfalls

  • Feature comparison obsession — spending more time comparing checkboxes than understanding competitor strategy. Features tell you what they built. Strategy tells you why and where they are going.
  • Competitor-driven roadmap — building features because competitors have them rather than because your customers need them. This turns you into a follower.
  • Ignoring indirect competition — the spreadsheet that solves 80% of the problem for free is often a bigger threat than the funded startup.
  • Overestimating moats — "our technology is proprietary" is not a moat if someone can rebuild it in six months. Moats require structural advantages, not just clever code.
  • Analysis paralysis — spending so much time analyzing competitors that you do not ship anything. Analysis should inform strategy, not replace execution.
  • Underestimating incumbents — "they are slow and we are fast" works until the incumbent decides to compete. Microsoft entering your market is a different challenge than a startup entering it.

Key Takeaways

  • Competitive analysis should focus on strategy, not features. Understand why competitors make their choices, where they are investing, and what they have decided not to do.
  • The most dangerous competitors are indirect ones — the status quo, the spreadsheet, the manual workaround. Do not fixate on direct competitors while ignoring the real alternatives your customers consider.
  • Moats are structural advantages that compound over time: network effects, switching costs, data advantages, brand, and scale. Features can always be copied; moats cannot.
  • Monitor competitors systematically through public sources, customer feedback, and win/loss analysis. Do it at a regular cadence, not as a one-time exercise.
  • Do not let competitors set your strategy. Respond when they threaten your core position. Ignore when they are operating in a different segment or solving a different problem.