How to Find Product Ideas and Pain Points on Redditcustomer research nobody was asked to give

Ask “would you pay for a tool that does X?” and you get a number, wrong in a direction you cannot see, because you supplied both the X and the frame. Read what people volunteer instead and the surprise arrives intact: the part that actually hurts is the third step, not the one you named. The corollary is uncomfortable — if every thread you find is about the feature you already planned, you have found your own search terms rather than a pain point.

People describing a problem to a vendor round it off; they know they are being sold to. People describing it to peers name the tool, the day of the week, the number of rows, the colleague who breaks it. “Reporting is painful” is not actionable. “I export three CSVs every Monday, glue them together with VLOOKUP, and the client's ops guy still emails asking why the totals moved” is a product spec, a headline and an objection-handling paragraph in one sentence.

A survey response is one person's word in a spreadsheet you own. A thread is a durable artefact with a timestamp, a score and a row of replies saying “same” or “no, you're doing it wrong” — the claim and its peer review together, years after it was written. 83% of the B2B decision-makers SurveyMonkey surveyed with Reddit said they complete their research via peer communities and self-directed search before ever engaging a sales team. The instinct that keeps them away from your sales team keeps them candid in front of each other.

One row is decisive. When somebody describes what they built to survive a problem — the spreadsheet with the colour-coded tab, the cron job, the Zapier chain held together by a Google Form — they tell you three things at once. The problem is worth real effort. Nothing off the shelf fits, or they would have bought it. And they have already sketched the solution's shape.

That is why the DIY spreadsheet is the classic pre-product signal: a spreadsheet is what a market builds when it has a job and no software. Five people who independently built the same one is a product; one is a hobbyist.

These are not buying signals, and treating them as such wastes both lists. A buyer intent phrase — “any tool for”, “X vs Y”, “alternative to X”, “moving away from X” — means the writer accepts that a category exists and is asking which product to give money to. The phrases here mean the opposite: a problem, no vocabulary, no shortlist, often no belief that software for it exists.

The difference is what you do next. Pre-purchase language is a reply opportunity today, with a window measured in hours; pre-product language is research, and its writer may not buy anything for a year. Track both, read them in separate sittings, and never judge a pain-point keyword by the customers it produced this week. Our guide to buyer intent keywords is the other half of the pair.

One thread is an anecdote. The test is not whether you can find more by searching harder — you always can — but whether the same description turns up in threads you did not go looking for, in communities that have nothing to do with each other. Different words is the part that matters: if everybody phrases it identically you may be watching one blog post's vocabulary echo around a niche.

Complaints are free; workarounds are not. Look for evidence that the problem already costs money or hours — a VA doing it by hand, a $9 tool that half-solves it, a script somebody maintains. A thread whose top comment is “yeah, we just hired someone for that” beats fifty threads of pure grievance. The inverse reads just as well: if nobody has ever done anything about it, that is usually a problem people have decided to live with, and the hardest thing to sell is a solution to something nobody has tried to solve.

Ask of every candidate what the consequence is. Somebody loses a client, misses a deadline, gets shouted at in a meeting, works a Sunday. If the honest answer is “it is mildly annoying”, you have found a feature rather than a product — which is the line between the two commonest false positives here.

• Discount price complaints about a competitor. They are about perceived value, and they arrive in waves after a pricing change.
• Discount the single vivid thread, and anything that spikes for a week. Prose quality is not signal strength, and an outage, a bad release and a viral post all produce the same shape.
• Discount complaints from people who are not your buyer. A hobbyist's frustration and a team lead's are the same sentence with different budgets behind them.

The original complaint tells you what one person wanted. The replies tell you how many wanted it and what they do instead. Half the time the top reply explains a workaround, which lands you back on the strongest signal on this page; the other half says “that's what Z is for”, which is your competitive set assembled for free by a stranger. Resist replying to sell in these threads — you are the one participant with an obvious stake, and every reader knows it. A tool named in a complaint thread is also a keyword, and our guide to tracking competitors on Reddit covers following those names continuously.

Suppose three threads across three months say, in different words: “I export three CSVs every Monday and glue them together”, “our reporting process is a spreadsheet somebody has to babysit”, “I lose the first two hours of every week rebuilding the same report”. Nobody said reporting automation, unified analytics or single source of truth — roughly what your category page says.

What they said was Monday, spreadsheet, rebuild, every week, by hand. So the headline is “Stop rebuilding the same report every Monday”, and the subhead is a workaround sentence quoted almost intact, because a visitor who has written that sentence themselves recognises it in half a second.

• Keep the concrete nouns. Spreadsheet, Monday, CSV, inbox, VLOOKUP. Abstraction is what everybody else's page is made of.
• Keep their verb. If they wrote glue, babysit, chase or rebuild, do not upgrade it to streamline.
• Drop your category name from the headline — it belongs further down, where somebody who has recognised themselves looks for what to call this.

Take the sentence you are about to put on the page and search it, as a literal string, in the communities you researched. Nothing back means nobody talks like that and you have written marketing language; threads back means you have written something your buyer has already typed. It works in reverse too, and that is where the keyword list comes from: every phrase returning real threads is worth watching from now on.

One archaeology session produces a document that starts going stale the day you finish it. The version that compounds is a small weekly loop: thirty minutes in one sitting, reading only what is new; every quote worth keeping filed with its link and its date; every phrase that recurs added to the list of things you watch.

Then the step that does the work: once a month, re-read the whole file rather than the month's additions. The pattern only exists in aggregate, and a running file read end to end is the only place it is visible. Automating the collecting is not laziness — the recurrence test only means anything if the sample was not chosen by you.

The phrases go in as keywords, one at a time, each with its own settings, and two mechanics matter more here than anywhere else in this set. The first is match mode: Broad Match, the default, requires every word in the keyword to appear somewhere in the text in any order, so “is there a tool that” asks for five of the commonest words in English and behaves like the bare word “tool”. Nearly everything here is built from small words, which makes Phrase Match — a literal re-check done locally — the right default for this list.

The second is scope: a per-keyword subreddit list narrows Reddit results after a site-wide search, which is what makes a phrase as broad as “am I the only one” readable at all. Run unscoped for a week to find where these threads live, then narrow.

An AI Filter is a plain-English instruction attached to one keyword, checked against every mention that matched it. Here it is close to essential, because “describes a problem they have not solved” is a judgement no keyword can hold: “only keep posts where the writer describes a manual workaround they built themselves” is a usable filter and an impossible keyword.

The setting to leave off is Lead Detection. It scores each mention against your brand description, asking whether this person is a plausible customer to reply to now — so a research-stage complaint from somebody a year from buying typically scores low and is usually rejected before you see it. Correct for lead generation, precisely wrong for research.

Worth saying plainly, because it is the one place the product's defaults point away from this guide's reader. Whenever an AI Filter or Lead Detection runs, each mention also gets one intent tag at no extra cost — buy intent, product question, competitor complaint, pain point, testimonial or promotional. The Leads view collects exactly two of them, buy intent and product question, because it exists for the queue you open when you want somebody to answer today.

Pain point and competitor complaint are not in it. That is not a gap to work around; it is the same distinction this page has drawn since the language table. What you want is the full mentions feed with the intent filter set to pain point — a different queue, read at a different pace.

ParseStream surfaces and tags the threads. It does not summarise your pain points, cluster them into themes or tell you what to build, and there is no report at the end of the month. The reading is the work — a tidy machine summary would have thrown away the exact wording, which is the most valuable thing in the thread. On the days you do reply, it drafts a Suggested Reply from your brand context and the thread; you edit it and post it yourself from your own account, because automatic posting is disabled at the server level by design.