2
4 Comments

I spent 20 hours on competitor research. Here's how I cut it to 2.

Every time I had a new startup idea, I'd waste a full week before writing a single line of code.

50 browser tabs. G2 reviews. Capterra rabbit holes. A giant Excel feature matrix that took forever to build and told me almost nothing useful.

After doing this painful process 4+ times, I finally mapped out exactly where the time was going and where most of it was being wasted.

The 3 places founders waste the most time in competitor research:

  1. Looking at the wrong things.
    Most people read competitor landing pages and feature lists. That's nearly useless. The real signal is in 1-star reviews on G2, Capterra, and Reddit that's where paying users tell you exactly what's broken. I started going there first, and my research quality jumped immediately.

  2. Building a feature matrix instead of a gap map.
    A feature matrix shows you what exists. A gap map shows you what's missing. They're completely different documents. When I switched from "who has what feature" to "what are users consistently complaining about that nobody fixes" I started finding actual opportunities instead of just copying competitors.

  3. Doing research sequentially instead of in parallel.
    Most people research one competitor fully, then move to the next. The faster way: scan all competitors for the same single signal (e.g., pricing) across all of them first, then move to the next signal. It cuts context-switching time massively.

Implementing just these three changes took my typical competitor research from 20+ hours down to about 2 hours per idea.
(Full disclosure: I eventually automated most of this into a tool 'Bunzee' because even 2 hours per idea adds up fast when you're testing multiple ideas. But the manual process above works on its own.)

What's the biggest time sink in your validation process right now? I'm curious whether the bottleneck is the same for everyone or if I'm just particularly slow at this.

on May 13, 2026
  1. 1

    The time savings are definitely important, but I think there's another problem beyond reducing the research time.

    Even if you can get competitor research down from 20 hours to 2 hours, you still have the problem of deciding what information actually matters.

    For me, the useful part is connecting the information together — pricing changes + new features + positioning + customer feedback — and looking for patterns rather than treating each data point separately.

    Otherwise you just end up with a much faster spreadsheet.

    1. 1

      Exactly. Ultimately, finding that middle ground is the direction I think our team should move in.

  2. 1

    This was a very compelling read. Thank you for the valuable perspective.

    1. 1

      Thanks for the reply! I also really appreciate you taking an interest in my post.

Trending on Indie Hackers
I built a launch coach after my own product launch got 11 upvotes and 3 signups User Avatar 34 comments Solo → Pre-Seed: The Tool Stack Decision That Will Either Save or Sink Your First 18 Months User Avatar 26 comments Most directories forget you exist after you list. We're trying something different. User Avatar 23 comments Built TermsGuard to explain contracts in plain English — looking for feedback User Avatar 19 comments Show IH: Apollodorus Video - browser-based video editor that runs locally User Avatar 12 comments Show IH:GSL Runtime: Moving Beyond .vrp Input User Avatar 9 comments