Three ways to make a better product decision
Generate a new idea, validate one you already have, or research the market yourself. The tools are separate, but all three use the same inspectable evidence.
Seven minutes of the real interface, no slides
Everything below is described in text on this page. If you would rather see it, the full tour walks the same path on real data: complaints, paid work, search demand, and the brief they add up to.
Three shorter runs, one job each — pick the one closest to what you are doing.
Start from where you are
You need an idea
Choose a platform, add 1–10 related pains or opportunities to its idea draft, and generate one product direction grounded in that exact set.
Generate an idea →You already have an idea
Describe the user, problem and workaround. See direct support, adjacent evidence and the parts that remain unproven.
Validate my idea →You want to explore
Browse marketplace pains, the Chrome market, paid work and competitor gaps at your own pace.
Start researching →Four checks behind the tools
Group independent complaints that describe the same underlying problem for the same kind of user. One loud thread is an anecdote; repeated frustration is a pattern.
Find recurring Fiverr tasks that solve the same job. Gig count, sellers, buyer reviews, starting prices and package tiers show whether a paid market already exists.
Check Google search volume and advertiser competition around short, task-shaped queries. Search volume shows interest; advertiser competition adds a commercial-intent signal.
Use the evidence to generate an idea, validate your own, or make a manual research decision. Supporting pains, paid-task clusters and search signals stay inspectable.
No single signal proves a business. Agreement between independent signals is what makes an opportunity worth investigating.
We start from real conversations, not surveys
Every day we read public discussions where people vent about the software they use — Reddit threads, community forums like the Shopify and Atlassian communities, and one-star Chrome extension reviews. These are people describing a problem in their own words, unprompted.
We keep only the genuine complaints. Off-topic chatter, praise, and support noise are filtered out. Then we group posts that describe the same underlying frustration into a single pain — so one pain card stands for many voices, not one loud thread.
A complaint is a lead. Payment and search make it a market signal.
Pain evidence tells us what is broken, but not whether the problem is valuable enough to buy a solution. The workflow adds two independent forms of intent before treating a pain as a serious product opportunity.
Are people already hiring someone for this job?
VettedGaps crawls Fiverr’s lowest-level categories and groups gigs by the concrete task they perform. Each cluster keeps its member-gig links and aggregates starting prices, package tiers, unique sellers and buyer reviews. Reviews are a conservative lower bound of paid demand — not a claim that they equal every completed order.
Explore paid demand →Do buyers actively search for the task?
Short phrases extracted from each pain are checked with Google Keyword Planner data. VettedGaps currently stores average monthly searches and advertiser competition. The API also exposes the 20th–80th percentile top-of-page bid range: a useful willingness-to-compete signal, but not the actual CPC any advertiser is guaranteed to pay.
Do independent signals point to the same job?
The strongest opportunities repeat across all three layers: users describe the pain in their own words, buyers pay specialists to handle it, and people search for a solution. Missing evidence stays visible instead of being filled in by the model.
A single number for “how much demand is behind this”
Once a pain is grouped, we give it a demand score — one number from 0 to 1 that answers a simple question: how much real want sits behind this problem? Higher means louder and more urgent.
The score weighs four plain things: how many people are affected (reach), how recently they’re still complaining (recency), how strongly they react — upvotes, replies, follow-ups (engagement), and whether they say they’d pay to fix it (willingness to pay).
A high bar like this means many people, complaining recently and loudly, several saying they’d pay. A short bar means a quiet, isolated grumble.
Full definitions of every number, label and badge — in the scoring glossary →
Validated demand still needs a competitive opening
Even a pain with paid and search demand may be a poor product opportunity if existing tools already solve it well. We check the competitive landscape and mark each pain with an opportunity signal:
Every pain links back to the people who said it
We never invent a pain. Each card carries the real quotes it was built from, with a link straight to the original post or review. Open any card and you can read the exact words, on the exact thread, and judge for yourself.
One focused idea draft becomes one grounded idea
Start by choosing the platform where you want to build. As you browse and spot pains that rhyme — the same underlying problem and the same kind of user — use Use in idea to put them in that platform’s idea draft. Keep the draft focused: a product that fixes three related failures in one workflow is coherent; a grab-bag of unrelated complaints is not.
Inside the idea draft, Generate idea reads those materials together and writes one idea grounded in them: the thesis, the beachhead persona, the wedge to start with, the competitor gap, a monetization angle, and a build brief — plus the real posts behind it, so your first move is talking to people who already have the problem. Every idea is saved under My ideas.
Most ideas come out as an add-on for the marketplace the pains live on. When the pains point elsewhere, the same brief can describe a standalone workflow tool or a direct competitor — the report always names which shape it chose and why.
Already have an idea of your own? Validate it instead. VettedGaps compares it with the corpus and marks every retrieved card as directly supporting your idea, merely adjacent, or unrelated — and when nothing directly supports it, it says so instead of dressing up weak evidence.
Free research covers Shopify, Atlassian and the basic Chrome catalog. Generating ideas and validating your own are Pro features — 5 idea generations and 5 validations per day.
PRO · 5 + 5 / day