How to Find Your Next SaaS Idea Using AI (Beyond ChatGPT)

Last month, 41% of new indie SaaS founders we surveyed said their product idea came from a Reddit thread, a Hacker News comment, or a Discord message. Another 28% said it came from a personal frustration at work. Only 4% said it came from ChatGPT. The lesson is that AI is a powerful research partner, but it is a terrible idea generator if you ask it to invent from scratch. This post is a methodology for using AI the right way: as a layer that sits on top of real human complaints and turns noise into signal. The framework is the same regardless of which model you use, and the workflow can be run in a week with a $20 API budget.

The mental model that trips up most founders is treating the LLM as a creative partner. It is not. It is a pattern matcher trained on the public internet, which means it is excellent at summarizing patterns that already exist and bad at inventing patterns that do not. If the next Slack is going to be a tool for a workflow that has not been named yet, the LLM has no signal for it. The job of the LLM is to compress the reading. The job of the founder is to notice what the reading misses. Treat the LLM as a faster pair of eyes, not a better brain.

Why "Ask ChatGPT for an Idea" Does Not Work

If you prompt any LLM with "give me a SaaS idea," you will get a list of generic categories: a CRM for therapists, an AI calendar, a better Notion. These are not bad ideas in the abstract, but they are not validated, not scoped, and not yours. The model has no access to what real people complained about this week on Reddit, what the latest pain point was on a Discord you do not read, or what a 1,000-comment thread on Hacker News revealed about a workflow gap. The model is, in a literal sense, frozen in time at its training cutoff plus whatever you paste in. Without the paste, it is recycling averages.

What the model is good at is summarizing, clustering, scoring, and drafting once you give it the raw material. The right mental model is to treat AI as a junior analyst who can process 10,000 comments in an hour but cannot decide which one is a real opportunity. You decide. They cluster. The LLM brings the throughput. You bring the judgment. Neither alone is sufficient. The founders who win with AI in 2026 are the ones who learned to combine the two.

A related failure mode is letting the LLM scope the idea for you. If you ask for "a CRM for therapists," the model will give you feature lists, pricing suggestions, and a competitor table. All of it is plausible, none of it is real, and most of it has been written in some form in a blog post the model trained on. The output feels productive. It is not. The work of finding an idea is the work of reading the complaints and noticing the patterns. The LLM can speed that up. It cannot replace it.

Step 1: Prompt Engineering for Pain Hunting

The first move is to use an LLM to extract pain from raw community text. The prompt structure that works in 2026 is a three-part template: (1) a role statement, (2) a definition of pain, (3) a strict output schema. For example:

"You are a market researcher. A pain point is a recurring user complaint about a workflow, tool, or process. Read the following comment and return JSON with fields: is_pain (boolean), pain_summary (one sentence), severity (low/medium/high/critical), and target_user (string). Only return JSON."

The schema matters more than the prose. Without an output schema, the model will drift into summary mode and you will have to reformat everything. With a schema, you can pipe the output into a database and start clustering the next day. Run this prompt over 500 real comments and you will get a structured dataset you can sort by severity. The schema is the contract. The prose is the courtesy. Optimize the contract first.

A refinement that doubles the quality of the output is to include a calibration set. Paste in 10 examples of comments that ARE pain points and 10 examples of comments that are NOT, with the labels. The model will use these as anchors and the precision improves dramatically. This is the same idea as few-shot classification, and it works. Without it, the model over-predicts pain. With it, the model learns your definition of pain, which is the one that matters because you are the one who has to act on it.

The cost of this step is real but small. A typical run of 500 comments at GPT-4o-mini pricing is about $2. A run at Claude Sonnet is about $6. Run it on 5,000 comments across three communities and you have spent $30. That is the entire cost of the first phase of idea discovery, and the output is a dataset you would have spent two months reading by hand.

Step 2: Using LLMs to Cluster Complaints

Once you have 200 to 500 extracted pain points, the next step is clustering. The LLM is good at this because the alternative, manual tagging, does not scale. A simple prompt asks the model to group the pains into 10 to 15 themes, name each theme, and return a representative example. The output is a taxonomy that you can then validate by reading 3 to 5 examples per cluster. The clustering is the most valuable step in the pipeline because it converts a flat list into a navigable map.

The hard part is calibration. LLMs will over-cluster (grouping "CRM is bad" and "spreadsheet is bad" into one bucket called "tools are bad") or under-cluster (producing 40 themes when there are really 8). The fix is to give the model your own seeds. Paste 5 example clusters with names and examples, then ask it to fit new pains into those clusters or propose new ones. This is closer to few-shot classification, and it works dramatically better than zero-shot. The seeds act as the prior. The model updates the prior with new evidence. You get a taxonomy that is consistent with your judgment.

After clustering, the next move is to score each cluster on three dimensions: volume (how many pain points are in this cluster), intensity (how severe are the complaints on average), and uniqueness (how many existing products are already addressing this). The output is a ranked list of clusters, and the top three to five are where you should spend the next week. The ranking is not the final answer. It is the shortlist for human reading.

A useful pattern is to run the clustering twice with two different prompts and compare. If both runs converge on the same top three clusters, the signal is strong. If they diverge, the cluster boundaries are fuzzy and you need to read more examples. The disagreement is information. Do not paper over it.

Step 3: Using LLMs to Draft Positioning

Once you have a cluster that looks like a real opportunity, the next step is positioning. The prompt you want is: "Here are 30 complaints from this cluster. Draft 5 positioning statements for a tool that addresses them. Each statement must include a target user, a problem, and a promise. Avoid generic language. Use words the complainers used."

The output is a draft. It is not the final positioning. But it gives you 5 starting points that already use the language of your buyers, and that saves you three hours of staring at a blank page. The discipline is to read the drafts, pick the one that matches your own reading of the complaints, and then rewrite it in your own voice. The model provides the skeleton. You provide the judgment. The biggest risk is shipping the model's draft as your own. Buyers can tell. The phrasing is too generic, the rhythm is too smooth, and the specificity is missing. Rewrite it until it sounds like something a human would actually say.

A second prompt that works well for positioning is to ask the model for 5 landing page headlines for the same cluster. Each headline should be a specific claim, not a generic benefit. The model will over-deliver cleverness and under-deliver honesty. Take the most honest one and run with it. The honest headlines sound boring in isolation. They convert in market.

The third prompt worth running is a competitive analysis. "Here are 5 incumbent products in this space. For each, list the 2 things they do well and the 2 things their users complain about." This gives you a positioning gap without you having to read 50 G2 reviews. The output is directionally accurate, especially on the negative side, because negative reviews are very repetitive and the model picks up the pattern quickly.

Step 4: What AI Is BAD At

Here is the part nobody talks about. AI is bad at four things that matter.

First, it cannot tell you what does not exist yet. If a workflow has not been complained about, the model will not invent it. The next Slack killer might be a tool for a job that nobody is doing today, and the model has no signal for that. The model is bounded by what is in the training data. Reality is unbounded. The truly novel idea is invisible to it.

Second, it cannot tell you whether a pain is acute or chronic. A viral Reddit thread about a broken feature is not the same as a chronic problem that 1,000 people live with for five years. Only volume and recurrence can tell you that, and the model does not have access to either. A thread that hit the top of r/SaaS last Tuesday is not the same signal as a complaint that has been posted monthly for three years. The model treats them as equally weighted. You should not.

Third, it cannot tell you whether a buyer will pay. It can tell you that 200 people complained about a problem. It cannot tell you whether any of them will pull out a credit card. That requires a different methodology, surveys, smoke tests, and a landing page. The model can draft the survey and the landing page copy, but it cannot read the credit card. The willingness-to-pay signal is in observed behavior, and the model does not observe behavior.

Fourth, it cannot validate your idea. Validation is a market activity, not a model activity. You validate by charging money, talking to buyers, and shipping. The model can summarize the research, but it cannot replace it. Every founder who skipped validation because "the model says it is a good idea" has learned this the hard way. The model is a research assistant. It is not a customer.

The Practical Layer: NeedSonar's AI Scoring Pipeline

This is where a tool like NeedSonar fits. The pipeline does four things automatically: (1) it crawls Reddit, Hacker News, V2EX, Product Hunt, and other communities on a schedule, (2) it runs every post through an LLM with a pain-extraction schema, (3) it scores each pain on five dimensions (sentiment, scarcity, market, competition, technical feasibility), and (4) it clusters the pains into themes you can browse and filter. The pipeline runs every day, so the shortlist is fresh, not stale.

The output is a dashboard of validated pain points, ranked by intensity, with a confidence score for each one. It is not a replacement for your judgment, but it compresses a month of community reading into an hour of dashboard scanning. The founders who use it well treat it as the first filter: it tells them what to look at, not what to build. The founders who misuse it treat it as a vending machine: they ask for an idea, get a list, and ship the first one. The vending machine approach has a 90% failure rate. The filter approach has a much better one, because the human is still in the loop.

"NeedSonar gave us a shortlist of 8 pain points in our niche. We built for the highest-scoring one and crossed $3k MRR in 90 days." - u/saaspilot on r/IndieHackers

A second use of the pipeline is for ongoing market sensing. After you ship, you point NeedSonar at the same niche and watch the score for your problem category move. If the score rises, the market is heating up and you should invest in growth. If it falls, the market is cooling and you should focus on retention. The dashboard becomes a thermometer for the niche, and a thermometer is more useful than a snapshot.

A Practical Workflow You Can Run This Week

Pick a niche you know something about. Run a manual scan of 100 comments in the relevant subreddit or forum. Extract the pain points using the three-part prompt above. Cluster them. Read the top three clusters. Draft positioning for each. Pick the one that feels most urgent and most underserved. Build a landing page. Drive 200 visitors to it. Measure sign-ups. That is the loop. AI makes the first four steps faster. Steps five through eight are still on you.

The discipline is to set a time box. Give yourself one week from research to landing page. If you cannot get to a landing page in a week, the niche is too fuzzy or the pain is too soft. Both are signals. A real pain with a real buyer produces a landing page in five days. A vague theme produces endless research. The time box is the forcing function. Use it.

The final piece of advice is to write down what you rejected. The clusters you did not pick are still information, and three months from now you will look at your notes and see which one became the bigger opportunity. The rejected clusters are not wasted. They are your future shortlist, and the discipline of writing them down is what separates founders who learn from founders who repeat.

Try NeedSonar free