Validation means looking for evidence that a specific customer will take a meaningful action, not collecting compliments about an idea. The cheapest useful test usually happens before building the full product.
1. Define the specific customer
Describe one customer group narrowly enough that you can find and interview real examples. Include the situation or problem that triggers the need; “small businesses” is too broad if different businesses buy for completely different reasons.
2. Interview real prospects
Ask prospects how they handle the problem today, what it costs them and what they have already tried. Avoid pitching the solution during the interview, because polite agreement is much weaker evidence than concrete behaviour, budgets and existing workarounds.
3. Test a simple offer
Present the smallest credible offer that tests the riskiest assumption, such as a paid pilot, booked consultation, pre-order or manual service. State the price or commitment clearly enough that the response reflects real intent rather than curiosity.
4. Measure willingness to act
Track meaningful commitments such as deposits, booked calls, qualified signups, repeat requests or completed pilots. Compliments and social likes can support research, but they should not be treated as proof that customers will pay or change behaviour.
Test the riskiest assumption first
Define the customer and the problem in narrow terms, speak to real prospects about how they solve it today, and create a small offer that asks for commitment. Depending on the business, that might be a paid pilot, pre-order, booked consultation or qualified waiting list. Record objections and reasons for inaction rather than explaining the idea until people agree with you.
Validate a service before building a platform
Instead of building a marketplace for local businesses, manually offer the core matching service to a small group. If customers will not use or pay for the manual version, more software is unlikely to solve the demand problem.
Practical example
To validate a service idea, create a narrow offer for one identifiable customer and try to get a real commitment before building a large system. A simple landing page, direct outreach and a short discovery call can reveal whether people understand the problem, value the result and accept the expected price range. Treat compliments as weak evidence; enquiries, deposits, pilots and repeat requests are stronger signals.
Validate demand before building the full business
Validation means collecting evidence that a specific customer will take a meaningful action for a specific problem. Start with conversations, existing alternatives and the cost of the problem, then define the smallest offer that can test willingness to pay or commit. Likes and compliments are weak evidence when they require no sacrifice from the potential customer.
Create a simple landing page or direct outreach message that explains the outcome, target customer, price range and next step. Run a small number of sales conversations or pre-orders before investing heavily in software, branding or inventory. Record objections and reasons people decline. Those details often reveal whether the problem, audience, timing or offer is wrong.
- Ask about current behaviour and spending instead of only asking whether someone 'would use' the idea.
- Test one customer segment at a time so conflicting feedback remains interpretable.
- Include delivery cost and your own time when estimating whether early demand could become a viable business.
- Define the evidence that would make you stop or change direction before starting the test.
Use paid commitments, qualified enquiries and repeatable customer pain as stronger signals than traffic. Validation reduces uncertainty; it does not guarantee that a business will succeed.
What to avoid when working on validating a small online business idea
- Building before validating.
- Asking only friends.
- Confusing compliments with demand.
Quick checklist for validating a small online business idea
- Define the specific customer.
- Interview real prospects.
- Test a simple offer.
- Measure willingness to act.
Validate demand before building the full business
Validation means collecting evidence that a specific customer will take a meaningful action for a specific problem. Start with conversations, existing alternatives and the cost of the problem, then define the smallest offer that can test willingness to pay or commit. Likes and compliments are weak evidence when they require no sacrifice from the potential customer.
Create a simple landing page or direct outreach message that explains the outcome, target customer, price range and next step. Run a small number of sales conversations or pre-orders before investing heavily in software, branding or inventory. Record objections and reasons people decline. Those details often reveal whether the problem, audience, timing or offer is wrong.
- Ask about current behaviour and spending instead of only asking whether someone 'would use' the idea.
- Test one customer segment at a time so conflicting feedback remains interpretable.
- Include delivery cost and your own time when estimating whether early demand could become a viable business.
- Define the evidence that would make you stop or change direction before starting the test.
Use paid commitments, qualified enquiries and repeatable customer pain as stronger signals than traffic. Validation reduces uncertainty; it does not guarantee that a business will succeed.
Frequently asked questions
How many customer interviews are enough?
There is no magic number. Continue until you see repeated patterns and can test a specific offer rather than collecting general opinions.
Does a large social following prove demand?
No. Attention is useful, but payment, signups with real intent or repeated use are stronger signals.
When should I build an MVP?
After you understand the riskiest customer assumption well enough to build the smallest version that tests it.
Keep Learning
Continue with these related guides:
