How to validate a business idea without confusing opinions with evidence

A favourable opinion is not a market signal

Validating a business idea means reducing uncertainty around the questions that shape the project: whether the problem exists, who experiences it most intensely, how they currently solve it, how urgent it is and what would need to happen for them to try or buy a different solution.

The distinction lies in the type of information you collect. An opinion tells you what someone thinks during a conversation. Evidence shows what that person has done, is doing or is prepared to do when the decision has consequences.

Positive reactions are not entirely irrelevant. They may help you determine whether the idea is understandable, whether it creates curiosity or whether the initial proposition sounds reasonable. The mistake is turning that reaction into a conclusion it cannot support: that demand exists, that the problem is a priority or that someone will pay.

A person can like your proposal and never use it. They can recognise the problem without wanting to solve it. They can express interest and return to exactly the same behaviour the following day. Validation must therefore examine not only the reaction to the idea, but also the distance between that reaction and a real decision.

Why positive answers often lead to nothing

The other person is trying to be helpful

When you describe a project enthusiastically, people often assume that you want an assessment. Friends, colleagues and close contacts are particularly likely to encourage you. They do not need to lie to create a misleading signal. They only need to emphasise what sounds interesting and avoid raising objections that might disappoint you.

Politeness makes the conversation easier, but reduces its predictive value. “I like it” may simply mean “I understand what you are trying to do and I do not want to discourage you.”

Giving an opinion has no consequences

Saying you would use a tool does not require you to change suppliers, learn a new process, persuade your team or allocate a budget. It does not force you to give up the alternative you already use. It is a cost-free answer.

Adoption and purchasing decisions always involve costs. Even a free tool requires attention, time, configuration and a change in behaviour. When you ask about hypothetical intent, you remove the constraints that determine what the person will actually do.

The person imagines an ideal version

When you describe a product that does not yet exist, each listener fills in the gaps differently. One imagines a perfectly integrated tool. Another assumes it will be inexpensive. Someone else assumes it will include the exact feature they need.

They may all say they would use it while reacting to different products built in their imagination. Their approval has limited value unless the proposition, use case and conditions of adoption are specific.

Recognising a problem does not make it a priority

The market is full of genuine problems that nobody considers important enough to solve now. A task can be annoying, a process can be slow and an existing tool can be poor without creating any intention to change.

A business needs more than evidence of inconvenience. You need to understand how that inconvenience competes with the customer’s other priorities and what happens if they continue with the current situation.

What to test before treating a hypothesis as validated

Validation does not deliver a single, permanent confirmation of the entire company. It reduces specific uncertainties. Before interpreting a conversation, you should know which hypothesis you are trying to test.

Whether the problem actually occurs

Look for specific situations rather than broad statements. Find out when the problem last occurred, what caused it, who was involved and what happened next. Recent examples provide more useful evidence than an abstract opinion about whether that type of problem exists.

Whether it creates meaningful consequences

A problem becomes more important when it produces a recognisable cost: hours of work, delays, mistakes, lost revenue, risk, recurring frustration or dependence on a process that is difficult to maintain. If the person cannot describe any consequence, the need may be less urgent than it first appeared.

Whether it already changes behaviour

Current solutions reveal how much the problem matters. A complicated spreadsheet, a manual process, an unsatisfactory tool or an employee assigned to handle it all demonstrate existing effort.

The absence of an alternative also provides information. It may mean that nobody has solved the problem well, but it may also mean that the customer has never considered it important enough to address.

Whether the person can influence the decision

The person who experiences the problem is not always the person who purchases the solution. Within a company, users, beneficiaries, buyers and final decision-makers may all be different people. An interview with a user can explain the experience without telling you much about budget, organisational priority or the buying process.

Validation requires you to identify who experiences the problem, who benefits from the change, who can block it and who has the authority to approve it.

Whether there is willingness to take a next step

The evidence becomes stronger when the conversation results in action: sharing information, introducing another stakeholder, accepting a trial, reserving time for a pilot, providing data, negotiating terms or paying.

These actions do not all carry the same weight, but each tells you more than an expression of interest with no follow-up.

What to ask instead of “Would you use my product?”

Useful questions move the conversation away from an imagined future and towards past and present behaviour. They also avoid suggesting what the correct answer should be.

This does not mean turning the interview into an interrogation. The aim is to request examples, explore decisions and understand the circumstances surrounding the problem. When an answer is too general, questions such as “Can you describe a specific example?” or “What did you do next?” can bring the conversation back to useful evidence.

A practical hierarchy of validation signals

Not every signal reduces uncertainty to the same degree. You should interpret each one according to the level of commitment it requires.

Weak signals: attention and approval

• The person says the idea sounds interesting.
• They say they know people who might need it.
• They claim they would probably use it.
• They suggest features without having tried to solve the problem before.
• They respond positively to a post or presentation.

These signals may show that your message is understandable, but they tell you very little about demand.

Intermediate signals: effort and specific intent

• The person describes recent experiences in detail.
• They show you the process or tools they currently use.
• They provide data needed to investigate the problem.
• They arrange another conversation involving relevant stakeholders.
• They join a clearly explained waiting list.
• They agree to spend time testing a solution.

These actions involve a cost in time, attention or exposure. The evidence is stronger, although it still does not prove willingness to pay or repeated use.

Strong signals: behaviour and commitment

• The customer accepts a pilot with objectives, owners and dates.
• They provide operational data or introduce the solution into a real process.
• They sign a letter of intent that is meaningful in that market.
• They preorder, pay a deposit or purchase an initial version.
• They continue using the product after the initial curiosity disappears.
• They renew, recommend or expand their use.

Even strong signals validate individual hypotheses rather than the entire company. A payment may support willingness to buy without demonstrating retention. A pilot can confirm value without proving that the sales process is scalable. You must always ask which uncertainty each behaviour actually reduces.

How to avoid contaminating a validation interview

The way you conduct the conversation influences the quality of the answers. If you present the solution first, explain all its benefits and argue why it should work, the person will evaluate your pitch instead of describing their reality.

Begin with context. Ask about previous experiences, decisions, costs and alternatives. Introduce the proposition later, once you understand how the problem appears. This lets you compare what the person said before seeing your idea with how they react afterwards.

You should also resist the urge to defend the proposal against every objection. If someone says they would not change their process, do not have a budget or do not see a fit, your first task is not to persuade them. It is to understand why. A carefully explored objection may be more valuable than several favourable comments.

Finally, separate your notes from your interpretation. Record what happened and what the person did before deciding what it means. This distinction reduces the temptation to turn an ambiguous comment into the confirmation you wanted.

How to interpret what you learn without misleading yourself

A single conversation rarely supports an important business decision. Look for patterns among people who share a comparable context. Combining different segments, company types and roles can create a false impression of agreement.

For each interview, it is useful to record:

• Who the person is and what role they perform.
• When they last experienced the problem.
• How often it occurs.
• Which consequences it creates.
• How they currently solve it.
• What they have tried before.
• Who participates in the decision.
• Which next step they accepted, if any.

Compare behaviours rather than phrases. Five people may describe the problem as important, but if none has ever dedicated resources to solving it, that absence is also part of the evidence. Equally, someone may sound unenthusiastic while demonstrating a serious need through the time and money they already spend.

Turning evidence into a decision

Validation only creates progress when it changes what you do. After a series of interviews or an experiment, you should be able to choose among several options: retain the hypothesis, narrow the segment, redefine the problem, change the proposition, run a more demanding test or stop pursuing that direction.

Before running a test, decide what would count as supporting evidence and what result would force you to reconsider the hypothesis. Defining the criteria afterwards makes it too easy to reinterpret every outcome as a success.

You should also keep track of what remains unknown. You may have confirmed that the problem exists without demonstrating that a budget exists. A landing page may show initial interest without proving intent to use the product. Recognising these limits does not weaken the validation. It prevents you from asking the evidence to support conclusions it cannot provide.

Mistakes that turn validation into a search for approval

• Speaking only to people close to you. They may help you practise the message, but their relationship with you introduces a bias that is difficult to remove.
• Explaining the solution too early. The more persuasive your presentation is, the harder it becomes to distinguish the real problem from the reaction to your story.
• Counting answers instead of assessing their quality. Ten hypothetical yeses may reveal less than one detailed account of a failed attempt to purchase a solution.
• Selecting only favourable comments. Contradictions, lack of urgency and objections are part of the results.
• Treating a waiting list as proof of demand. A sign-up can be useful, but its value depends on the audience, proposition and cost of the action.
• Declaring the entire idea validated. Evidence about the problem, segment, proposition, price, channel and usage normally develops at different times.

How Foundeia uses validation within the process

Foundeia does not approach validation as a general question about whether an idea is good. It treats it as a sequence of hypotheses, tests, evidence and decisions.

The platform can help you identify the assumptions behind an idea, prioritise the ones that create the greatest risk, prepare customer interviews and organise what you learn. It does not, however, turn an opinion into proof or replace the market’s response. Evidence appears when real people describe their behaviour, allow you to observe their processes and accept commitments connected to the proposition.

The objective is not to collect enough praise to justify continuing. It is to build a stronger basis for deciding whether to proceed, change direction or stop investing in a weak hypothesis.

Your idea does not need approval; it needs a better test

Wanting a positive reaction is human. Once you have invested time in an idea, you want reassurance that you are not moving in the wrong direction. A pleasant conversation does not remove that risk.

Validation begins when you stop asking what someone thinks about your idea and start investigating what they do when they encounter the problem. It becomes stronger when you observe costs, alternatives and decisions. It becomes more valuable when interest creates a commitment with consequences.

Someone liking your idea may help you communicate it more effectively. Someone changing their behaviour helps you understand whether an opportunity exists.

You do not need the market to encourage you. You need to design situations in which it can show you, through action, what is worth building.