Product Potential Research: Test the Assumptions Before Scale
Product potential research asks whether a defined group has a worthwhile need and would choose a proposed offer under realistic conditions. It connects desirability with the ability to deliver. It cannot guarantee that a concept will become the most profitable product in a market.
The useful output is a decision and its evidence: proceed with a limited test, revise an assumption or stop. A collection of favourable comments is insufficient if the price, alternative and use conditions were never shown.
Describe the problem before the solution
Ask how people currently handle the task, what they dislike and how often the need arises. Include alternatives outside the obvious category, including doing nothing. A complaint can identify an inconvenience without establishing willingness to pay for a solution.
For a hypothetical meal-planning tool, explore how households plan today and what makes the task difficult. Do not begin by asking whether an appealing new application sounds useful. The example illustrates an enquiry, not a finding about household demand.
Choose an audience by relevant need
Define who uses, chooses and pays. Those roles can differ. Demographic descriptions help identify a sample but should not replace purchase circumstances or implementation constraints.
Include people who rejected similar offers as well as interested users. A group of enthusiastic followers may supply development ideas without representing the addressable market. Report recruitment, location and dates whenever findings are used beyond the study team.
Compare a complete proposition
Show what the product does, the expected price and the conditions necessary to use it. State which features exist and which are proposed. An attractive concept with no cost is not equivalent to a product available at a realistic price.
Ask participants to choose among relevant alternatives and explain the decision. Include rejection. Check whether participants can describe the proposed benefit independently without repeating the advertising language. Separate understanding of the concept from preference and willingness to try; otherwise a confused interpretation can look like demand.
Use prototypes for the questions they can answer
A prototype can help investigate a task, interface or product experience. Define what it represents and which limitations are artificial. Do not treat a demonstration as proof of reliable performance under everyday conditions.
Observe completion, errors, assistance and reasons for stopping. Ask what the person expected before explaining the intended design. See product prototype testing for this narrower stage.
Estimate the opportunity with explicit assumptions
Distinguish the population with a possible need from the group the business can reach and serve. State the source, geography and timeframe behind each estimate. Stated purchase intention is not a sales forecast.
Consider support, distribution, cost and repeated use alongside initial appeal. A concept can solve a problem but still require an operating model the team cannot deliver. Technical or regulated claims need appropriate verification separate from consumer preference.
Continue learning after launch
Track completed purchases or adoption, actual use, returns, support and repeat behaviour where relevant. Compare results with the assumptions recorded beforehand. Weak adoption may reflect price, availability or onboarding rather than a lack of need.
Set criteria for continuing, revising or stopping before the trial. See testing a minimum viable product, review market research services and contact INTAGE Vietnam with the product and decision. Keep the evidence and remaining uncertainty visible.
