How to validate a product idea with customers before you build
How to validate a product idea with customers: find people who already complained, ask about the last time it hit, then ask them to pay before you build.
The short answer to how to validate a product idea: find people who already have the problem, ask them what happened the last time it hit, then ask them to commit money or real effort to your fix before you build it. Opinions about a future product cost nothing to give. A workaround someone describes step by step, or a paid pilot, costs them something, and that’s the evidence you want.
Product idea validation is collecting evidence, before you build, that real customers have the problem and will pay for a fix. With customers it runs in three stages. Recruit people who have written about the problem in public, interview them about past behavior rather than your pitch, and run a commitment test with a kill line: the result, written down in advance, that ends the idea. The desk checks that come first (complaints, paid demand, search volume and competitors for each function) are covered in how to validate a business idea.
It’s written for indie developers and micro SaaS builders planning an app, a marketplace add-on or a browser extension. It covers interviews and product-level tests, not large surveys, ad campaigns or the MVP build, and it says where our data stops: anywhere outside software. Whether your evidence justifies quitting a job or raising money is covered in startup idea validation.
Key takeaways
- Recruit from public complaint threads, since those people already said they have the problem.
- Ask about the last time the problem happened, never whether they would buy a product.
- A workaround someone repeats every week is stronger evidence than a compliment about your idea.
- Write each kill line before the test, as a count out of a fixed number of people.
- A concierge version, done by hand for 3 to 5 customers, tests the product before any code exists.
Find customers who already wrote about the problem
Finding people who have the problem is the hard part, so start where they already complained. Every day we read app marketplace reviews, vendor forums, Reddit threads and one-star Chrome extension reviews, drop praise, off-topic chatter and support noise, and group posts about the same frustration into one pain card. As of November 2026 there are 7,775 cards across 78 marketplaces, and every quote links to its original post, so each one has an author you can reach. Our evidence method puts the real posts behind every generated idea “so your first move is talking to people who already have the problem.”
Two public cards and one public sample idea, as of November 2026:
| Problem | Posts | Distinct people | Score | What people do today |
|---|---|---|---|---|
| Jira admins manually compile reports from delivery data for management | 26 | 24 | .69 | Turn Jira data into slides, PDFs or Confluence pages by hand before management meetings |
| Small business owners oversell when Square and Shopify inventory sync fails | 5 | 4 | .66 | Update stock between Square and Shopify by hand, almost every day |
| Shopify merchants can’t tell real traffic from bot spam (sample generated idea) | 16 | 15 | 0.97 | Write IP exclusion rules by hand, or ignore the data |
Score is the demand score shown on each card (the sample idea calls it pain score), from 0 to 1, weighing reach, recency, engagement and willingness to pay.
Read the quotes before you write to anyone. On the Jira card, one person wrote that before a management or steering meeting “someone still ends up manually turning all of that into a different format: summarising what changed, explaining risks, adding commentary, preparing slides/PDFs, and sometimes publishing another update in Confluence.” (source) That one post gives you the job, the trigger and the workaround. The interview only has to find out what it costs.
Almost every post there is from a different person (26 posts, 24 people).
How to validate a product idea in customer interviews
Ask about past behavior, never about your product. Our sample generated idea tells the founder to ask merchants what they actually did about bot traffic, then adds: “Do not pitch a solution; only ask about past behavior.” People are generous about a future product and precise about last Tuesday.
Questions that keep the conversation on facts:
- When did this last happen? Walk me through it.
- What did you do next, and how long did it take?
- What have you tried already, and why did you stop using it?
- Have you paid for anything to fix it, such as an app, a freelancer or extra staff hours?
- What happens if you leave it as it is?
Listen for a workaround described in steps, money or tools already spent, and threats to switch. A seller on the Square and Shopify card gave the workaround and its frequency in one line: “They don’t talk to each other, so I’m the one manually updating inventory between them almost every day.” (source) Only 4 people stand behind that card, so it’s a list of people to call, not proof. The call asks how long the daily update takes and what an oversold order costs.
Write the pass line as a count before the first call. The sample generated idea plans 10 calls with performance marketing leads and this kill line: “Fewer than 3 of the 10 describe a concrete financial consequence (wasted ad spend they can quantify) and fewer than 2 have paid for any traffic-quality or bot-related tool in the past.” A fixed count stops you from reading a polite “sounds useful” as a pass.
Product idea validation methods that ask for a commitment
Interviews can’t show that anyone will pay you. For that the customer has to give something up. Three product idea validation methods from our public reports, with the line each one was set to clear:
| Method | What the customer commits | Example | Pass or kill line set in advance |
|---|---|---|---|
| Concierge version | Data, time, and acting on your output | Manual bot-traffic reports for 3 brands, then ask for $99 a month | Kill if zero of 3 apply the rules within one week, or zero commit to pay |
| Paid pilot from a mockup | Money | Ask 20 multi-warehouse merchants to commit to a pilot at $29 a month (sample validation report) | Kill if fewer than 2 commit |
| Free manual audit for a call | 15 minutes | Message 20 people who posted about bot traffic in the last month | Pass if 5 audits are done in 7 days and 3 merchants ask for a follow-up report |
Pick by what you still lack. A free audit gets you conversations, the concierge version tests the product when you can do the job by hand, and a paid pilot from a mockup tests the price when you can’t.
The concierge version is the method most builders skip: you do by hand what the software would do. In the sample idea, the first step to ship is a founder who “personally onboards 5 DTC brands”, finds bot sessions in a spreadsheet and emails each brand a report. Watch what customers do with the output. A report nobody acts on is a no, even when they reply with thanks.
Price the commitment against money that already moves. The sample idea anchors its test price on Fiverr bot-protection work with a median price of $435.52, then says the price “is a hypothesis anchored on a different product category and is entirely unproven for this specific solution.”
Validating a product idea one feature at a time
Customers rarely want every part of a product equally. Split the idea into separate functions and, in each interview, ask which one they would pay for first. Our idea validation tool does the desk half: it checks each function against complaints, paid work, search volume and competitors, and in the sample validation report only one of four functions had direct evidence. The evidence levels are explained in our guide to idea validation, and what software can and can’t check for you is in AI tools for validating product ideas.
Most of our generated ideas come out as an add-on for the marketplace the pains live on, and the Monday.com card is that shape: 130 posts from 109 people who can’t build conditional automations. One of them wrote on the Monday.com community forum that the every-time-period trigger “lacks many basic functions” (source). If the platform ships the feature itself, an add-on that does only that loses its reason to exist, so ask interviewees what else breaks around the missing feature.
How companies validate bold new product ideas with limited data
We can’t show you any company’s internal process. We can show how the sample generated idea handles thin evidence. It stands on 15 people and paid demand for a neighbouring job: merchants pay freelancers to block bots, and the idea only reports on them.
Its 7-day plan runs riskiest and cheapest first:
- Search the Shopify App Store and Google for existing tools. Kill if 2 or more apps have a dedicated bot-detection or traffic-quality feature and active reviews from the past 6 months.
- Ask in r/shopify_growth and r/shopify what people did about it. Kill if fewer than 5 commenters describe a specific action in the past 3 months.
- Run 10 calls, then the concierge version for 3 brands.
With limited data, run the test that can end the idea fastest first and leave anything that needs code for last.
Google Trends, food products and retail: where our data stops
How do I validate a product idea using Google Trends?
You can’t validate one with Trends alone: a rising line says nothing about whether anyone pays. We don’t use it. Our search signal is Google Keyword Planner monthly volume and advertiser competition for short, task-shaped phrases. Use Trends to spot a seasonal or fading topic before you spend a week on interviews.
Food products and retail
Steps to validate new food product ideas follow the same order as this guide: find people who complain about what they buy now, ask what they did last time, and ask for a pre-order before you produce at scale. We have no numbers for any of it, because our complaint corpus covers software only. The same goes for how retailers validate new product ideas before full-scale development: we don’t see inside retailers’ processes, so we won’t describe them. Store software problems are in our data (the Square and Shopify card is one); the products on the shelf aren’t.
FAQ
How do you validate a product idea without building it?
Do the job by hand. A concierge version, a mockup with a paid pilot or a free manual audit all test whether customers act and pay, and none of them needs code.
Is a survey enough to validate product ideas?
Rarely. A survey asks about the future, and people answer it generously. Use one to find people who have the problem, then interview them about what they did last time.
What if nobody has complained about my idea in public?
Then the idea is unobserved, which isn’t the same as disproven. Interviews become your first evidence instead of your second.
Start validating a product idea this week
That is how to validate a product idea with customers: recruit people who already wrote about the problem, ask about the last time it happened, and run one commitment test with a kill line. Pick one public card tonight and message five of the people quoted on it. If you already have an idea, paste it into idea validation first to see which functions have evidence. It’s a Pro feature at $15 a month with 5 validations a day (plans).
Other ways people search for this
Some searches arrive as product+idea+validation, with the plus signs left over from a URL. The three stages above answer it.
Short forms such as validate product idea, how to validate product idea, how to validate product ideas, how to validate your product idea and how to validate your product ideas get the same answer. So does validating product ideas, one idea at a time.
People also type validate new product idea with customers or best ways to validate product idea with customers; the interview section answers both. A search for how companies validate bold new product ideas with little data is answered in the limited data section.