3
6 Comments

Don't ask AI for your SaaS idea. I learned this the hard way.

I see new founders do this constantly. I did it myself.

Open ChatGPT or Claude. Ask "what's a good SaaS idea I should build?" Get a list. Pick one. Start building.

Three weeks later — five funded competitors already solving the exact problem.

Here's the thing nobody says out loud:

AI gives you ideas that have already been written about hundreds of times. On Indie Hackers. On Twitter. On Reddit. Which means other people are already building them by the time AI suggests them to you.

The idea must come from your own life.

The best ideas come from a moment where you think "why is this so hard, there should be a tool for this." That moment is specific to you. Your workflow, your frustration, your situation. That specificity is your only real advantage as a solo founder with no funding and no audience.

When I stopped asking AI for ideas and started paying attention to my own frustrations — I noticed I kept losing things in my own Notion workspace. Files I couldn't find without re-reading entire pages. That became my idea. Not because AI validated it. Because I felt it myself.

Where AI actually belongs in this process:

Finding the idea → your job, not AI's
Researching competitors → AI helps
Writing landing page copy → AI helps
Building the MVP → AI helps
Writing validation posts → AI helps

The idea must be yours. Everything after — AI can help you execute faster than any solo founder could five years ago.

One question I ask before starting any idea now:

"Did I feel this frustration myself — or did someone else tell me it was a problem?"

If you felt it → worth building.
If you read about it → research first, build never.

Has anyone else made this mistake? What was the idea AI suggested that turned out to already exist?

on June 18, 2026
  1. 1

    AI is great once the founder already understands the pain point, but it is risky when people use it to pick the idea for them.

    For SaaS MVPs, I think the better flow is: notice a real problem, validate the workflow manually, then use AI to speed up research, prototyping, copy, and development. AI can make building faster, but it still cannot replace the founder’s job of understanding the user.

  2. 1

    One thing I've noticed is that "I experienced the problem myself" can answer a different question than founders think it does.

    It can be a very strong reason to start.

    Whether it's a strong reason to continue is sometimes much less obvious.

    1. 1

      that's a real distinction — feeling the problem gets you started, but it doesn't tell you if enough other people feel it sharply enough to pay.
      i think that's exactly where i am right now. i felt the Notion frustration. but "i felt it" and "people will pay to solve it" are two different validations and i've only confirmed the first one.
      what's the question you think is sitting underneath that most founders miss?

      1. 1

        That's exactly where I'd stop myself from answering publicly.

        The interesting part isn't the question.

        It's the conclusions people draw from their answer to it.

        Happy to continue by email if useful.

        1. 1

          makes sense — some things don't translate well to a comment thread.
          khushirajpurohit2021@gmail.com

          1. 1

            Just sent you a note.