SaaS Pain Point Hunting with Runner H

This is a submission for the Runner H "AI Agent Prompting" Challenge

Introduction

Every builder hits that wall: "What should I build next?"

You scroll Twitter. You stalk indie hackers. You even ask ChatGPT for ideas, but nothing feels real. Nothing feels urgent.

That's the gap I wanted to close.

Instead of pulling ideas out of thin air, I made a system to go where the real problems are: inside user comments on Product Hunt.

Because let's be honest - launch pages lie. Comments don't.

People drop gold when they're frustrated. That's where the pain lives.
And pain = opportunity.

So I built a workflow with Runner H that finds those pain points fast, organises them clearly, and gives you actual SaaS ideas backed by real user frustration.

What I Built

I made a simple but powerful workflow to find real problems people face with new SaaS tools.

I used Runner H to build a step-by-step process that scrapes through Product Hunt comments - but only looks at the top launches of this year.

The goal is simple. To spot pain points, complaints, and problems that show up again and again - and use those to find new SaaS ideas.

Demo

Run link:

Document it generated:

SaaS Pain Points from Product Hunt - Google Docs

docs.google.com

How I Used Runner H

I created a workflow inside Runner H that does this:

1. It opens a Google Doc and names it based on today's date.
2. It searches Product Hunt's top SaaS launches from this year.
3. It is included in each product's comments.
4. It pulls out only critical feedback, comments that discuss what's broken, missing, confusing, or annoying.
5. For each pain point, write down:

• Product Name
• Type of tool
• The actual complaint or quote
• A link to the comment

• Upvotes on that comment (if there are any)

  1. It keeps going until it has 5 real pain points from different products.
  2. At the end, it writes a summary showing:

• Common patterns across comments

• What users are struggling with

• 2-3 solid product ideas you could build from this

All of it goes into a clean Google Doc.
No spreadsheets. No code. No scraping tools.
Just data, sorted by hand, with Runner H as the assistant.

Prompt

You are a SaaS Idea Hunter. Your job is to read through *Product Hunt's top SaaS launches of this year*, and collect *real user pain points* from the comment sections. These pain points must come from critical, constructive feedback, not vague complaints or shallow praise.

You must then *analyse each pain point* and explain why it could become the seed of a good SaaS idea.

*Workflow:*

1. Open a new Google Doc titled:
   `SaaS Pain Points from Product Hunt`

2. Visit Product Hunt and find the *top SaaS products launched this year*. Filter by date. URL: https://www.producthunt.com/leaderboard/yearly/2025

3. For each product, go through all user comments and reviews.

4. Extract only comments that include clear *negative feedback* or *constructive criticism*. Skip low-effort, generic, or praise-only comments.

5. For every useful pain point you find, add it to the Doc as a bullet point in this format:

   - *Product Name:*
   - *Category (if known):*
   - *Pain Point (exact excerpt or a clean summary):*
   - *Link to the original comment:*
   - *Upvotes on the comment (if visible):*
   - *Why this is a solid SaaS idea (your reasoning):*

6. Repeat for at least *5 unique, useful* pain points from different products.

7. After all bullets, write a short *300-word summary* including:

   - Common themes or recurring issues across comments
   - What this says about where SaaS still sucks
   - 2–3 idea directions founders could explore

*Rules:*

- Use *Google Docs only*. No spreadsheets, no tools, no automation.
- Focus on being *data-heavy, insight-rich*.
- Don't overgeneralize. Stay specific.
- Your final output should be so useful that a founder could open it and start building tomorrow.

Use Case & Impact

If you're a builder, solo founder, or just someone with an itch to launch something new, this helps you find ideas that already have demand.

Instead of building something no one needs, you're finding:

• What annoys real users
• What current tools fail to do
• What people are asking for, over and over again

This saves time. It sharpens your focus.
And it gives you a real chance to build something useful, not just another clone.

Imagine finding your next startup idea just by reading through what real people hate about a tool like Notion, Linear, or some new AI tool. This is that - but on autopilot.

Final Thoughts

This isn't magic. It's just smart, focused listening.

Too many founders chase trends. This workflow helps you chase the truth.

What people really need.
What tools actually suck.
What gaps are wide open.

You don't need a billion-dollar vision.
You need one sharp idea that solves one sharp pain.
This workflow gives you 5.

Run it. Read the doc. Sit with the pain.
And then? Build the fix.
You'll be 10 steps ahead of everyone still guessing.

Let's stop building noise. Let's build what matters.

Thanks for reading.
Made with ❤️ by @arjuncodess for the DEV.to Runner H "AI Agent Prompting" Challenge.