Imagine you are considering a subscription service for healthy meals.

You interview 20 potential customers.
Sixteen say: “That sounds interesting.”
Should you now invest in the platform, kitchen capacity and a large marketing launch?

Not necessarily.
“Interesting” may establish that the Concept sounds attractive. It does not establish that people will subscribe, pay the required price, continue using the service or generate enough Margin for the Business Model to work.

Strategyzer recommends beginning business experiments with explicit Hypotheses and using collected Evidence to decide whether to persevere, pivot or kill an idea, while evaluating Desirability, Feasibility and Viability rather than relying on team opinion alone.

Do not only ask “Is this a good idea?” Ask “Which Critical Assumptions have actually passed?”
Most Business Ideas begin as a collection of Assumptions: customers have an important problem, they see enough value in the proposed solution, they are willing to pay at an acceptable price, and the business can deliver the solution with workable Economics.

Validation is therefore not about accumulating Positive Feedback until the founder feels proven right. It is about reducing Uncertainty before increasing Commitment. Business.gov.uk recommends testing Customer Needs, Market Conditions, Competition, Route to Market and Willingness to Pay, and advises entrepreneurs to go beyond Friends and Family when gathering feedback by speaking with people who represent potential customers.

A useful sequence is: Critical Assumption → Experiment → Evidence → Decision Rule → Go / Revise / Stop

Before deciding Go or Stop, identify what must be true

A Business Idea rarely depends on one assumption.
The healthy-meal subscription may depend on assumptions such as:

• Target customers repeatedly struggle to find healthy meals
• The problem is important enough to pay to solve
• A monthly price of 2,500 baht is acceptable
• Customers prefer a Subscription rather than occasional purchases
• Delivery can be operated while maintaining sufficient Margin
• Customers continue beyond the first month

If one of these is a Critical Assumption and it fails, the Business Model may fail even if people like the Concept.

Strategyzer recommends identifying assumptions that are critical to the idea and prioritizing those with high impact but weak existing Evidence.
The first question is therefore not: “Is this a good idea?”
It is: “What needs to be true for this idea to work?”

Go when Critical Assumptions have enough Evidence for the next level of commitment

Go should not automatically mean: “Build everything.”
Go can mean:
Go to Prototype
Go to Pilot
Go to Paid Test
Go to One Location
Go to Limited Launch
Go to Scale

The key is matching Evidence Strength to Commitment Size.
Customer Interviews may justify building a Prototype.
They should not normally be the only Evidence supporting investment in 20 locations.

Strategyzer distinguishes experiments by the Strength of Evidence they create and emphasizes that Evidence based on Actual Customer Behavior, such as usage or purchase, is generally stronger for behavioral questions than opinions or hypothetical responses.
A Go decision becomes stronger when:

• The Critical Need is supported among Target Customers
• Customer Behavior supports the Value Proposition
• Willingness to Pay has evidence beyond stated enthusiasm
• The solution can be delivered reliably
• Unit Economics show a credible path to Viability
• No untested Critical Risk could undermine the entire model

Revise when the Problem still matters but part of the Solution or Business Model does not work

A weak test result does not always mean Stop.
Suppose customers clearly experience the healthy-meal problem and enjoy the Product during a trial, but refuse to commit to a monthly Subscription.
The Evidence may not mean: “There is no demand for healthy food.”
It may mean: “The current Subscription Model does not fit.”

Possible revisions include:
Price
Package Size
Payment Model
Target Segment
Channel
Value Proposition
Product Feature
Delivery Frequency
Positioning

Revise is appropriate when the Core Problem or parts of the Business Model remain supported, while another important assumption has failed and can reasonably be redesigned.
A useful revision should be able to answer: Which Evidence caused us to change what?
and: What new Hypothesis are we testing?

Stop when a Critical Assumption fails and further revision no longer has a reasonable case

Stopping can be difficult because founders have already invested time, money and personal commitment.
But Stop does not mean: “The founder was wrong about everything.”
It means: “Based on the current Evidence, further investment under these assumptions is not justified.”

Possible Stop Signals include:

• arget Customers do not experience the expected problem strongly enough
• The Need exists, but customers will not pay near the level required
• Usage occurs only when the service is free and disappears when payment begins
• Customer Acquisition Cost remains too high relative to likely Margin
• The solution is technically possible but too expensive to deliver
• Several reasonable revisions have failed to resolve the same Critical Assumption

Strategyzer recommends assessing progress through Evidence related to Desirability, Feasibility and Viability and using that Evidence to determine whether an idea deserves further investment, a pivot or termination of the current direction.

Stopping is therefore part of Evidence-based Decision Making, not a failure of Research.

Do not use Positive Feedback as the main Decision Threshold

These statements sound encouraging:
“That is interesting.”
“I would probably try it.”
“I like this Concept.”
“The price does not sound expensive.”
But they are Stated Responses. They are not Actual Behavior.

If the question is: “Do customers experience this Problem?”
Interviews may be useful.
‍
If the question is: “Do customers understand the Concept?”
A Prototype Test may be appropriate.
‍
If the question is: “Will customers give us their details to access this offer?”
A Waitlist or Landing Page can provide additional Evidence.
‍
If the question is: “Will they actually pay?”
A Pre-order, Paid Pilot or Transaction Test is closer to the Behavior being evaluated.
‍
Business.gov.uk recommends examining both what Potential Customers think and what they would be willing to pay when validating an idea.
Therefore:
Liking ≠ Willingness to Pay
Intent ≠ Purchase
Signup ≠ Retention
Trial ≠ Repeat Purchase
Each stage requires Evidence that matches the assumption being tested.

Set the Decision Rule before the Experiment, not after seeing the result

Suppose a Landing Page generates 35 Signups from 1,000 Visitors.
Without a predefined rule, the team can argue:
“Thirty-five people is promising.”
“Conversion is only 3.5%.”
“With better Targeting it would be higher.”
“Let's just run it for another month.”

Discussion is useful, but when Success Criteria move after the result appears, it becomes difficult to separate learning from confirmation bias.
Before testing, write down:
Hypothesis
Metric
Threshold
Test Period
Target Audience
Action if Pass
Action if Fail
Example:

Hypothesis: Target Customers show sufficient Willingness to Pay for a Monthly Package.
Evidence: Paid Pre-orders.
Go: Reach the minimum level required to justify a Pilot with no Critical Customer Barrier.
Revise: Interest is strong but Price is the dominant barrier.
Stop: Paid Demand remains below the minimum level after reasonable adjustments to Value Proposition and Targeting.
The Threshold should come from your Economics and Decision Need—not from copying another company's benchmark.

Use four questions before putting more money behind an idea

SMEs do not need an overly complex scoring model to begin.
Start with four questions.

1. Desirability - Do customers genuinely want it?
   Is there an important Problem or Need?
   Does Customer Behavior support what customers say?
2. Willingness to Pay - What will customers exchange for the solution?
   Will they actually pay?
   Is the price close to what the Business Model requires?
3. Feasibility - Can the business deliver it?
   Can Technology, Operations, Supply, People and Channels support the proposition?
4. Viability- Can the Economics work?
   After Price, Margin, Acquisition, Delivery, Service and Retention are considered, is there a credible path to a sustainable Business Model?

Strategyzer uses Desirability, Feasibility and Viability as core dimensions for evaluating Evidence around new Business Models, with experimentation used to determine which assumptions remain weak.

A practical Go / Revise / Stop Framework for Business Ideas

1. Define the Business Idea
   Who is the customer, what is the Problem, what is the Solution and how does the business make money?
2. List Critical Assumptions
   What must be true for the model to work?
3. Rank by Risk
   Which assumptions have high impact but little Evidence?
4. Design the Smallest Useful Test
   Choose an Experiment that reduces meaningful Uncertainty without building the entire business.
5. Set the Decision Rule
   Define the Metric, Threshold and Action before testing.
6. Collect Evidence
   Separate Opinion, Stated Intent and Actual Behavior.
7. Decide
   Go → Evidence supports the next level of commitment.
   Revise → The Core Opportunity remains, but an assumption needs to change.
   Stop → A Critical Assumption fails and the expected value of further testing no longer justifies the resources required.
8. Test the Next Unknown

Even after a Go decision, larger commitments introduce new assumptions that still need validation.
This changes the purpose of Validation from: “How can we prove our idea is good?”
to: “What Evidence would justify investing more, changing direction or stopping?”

The takeaway: Go does not mean the idea is proven, and Stop does not mean the work was wasted

Every Business Idea begins under Uncertainty.
The purpose of Validation is not to achieve 100% certainty before starting.
It is to reduce Risk before increasing Commitment.

A practical rule is:
Go when the Evidence is strong enough for the next investment.
Revise when the opportunity remains attractive but an important assumption has failed.
Stop when a Critical Assumption has failed and further Evidence is unlikely to change the Business Case enough to justify the cost.
Business.gov.uk recommends testing Customers, Markets, Competition, Routes to Market and Willingness to Pay before committing fully to an idea, while business

experimentation frameworks emphasize explicit Hypotheses and Evidence as a way to progressively reduce risk.
Before the next investment round, the more useful question for an SME is therefore not simply: “Do we still believe in this idea?”
It is: “Which Critical Assumptions have passed, which have not, and is the Evidence strong enough for the next amount of money we are about to commit?”