Creating a digital product can feel productive. You can spend weeks writing, designing, recording, and polishing something before discovering that the intended customer does not want it.
Validation means gathering evidence that a real group of people has the problem, cares enough to solve it, and understands the value of your proposed product.
Start with a person and a problem
Weak product ideas often begin with a format:
- “I want to create an ebook.”
- “I should make a course.”
- “I want to sell a template.”
A stronger starting point is:
Examples:
- A weekly expense tracker for independent delivery drivers
- A client-onboarding checklist for new virtual assistants
- A résumé worksheet for adults returning to work
- A meal-planning template for people cooking for one
- A simple inventory sheet for small online sellers
Look for evidence that the problem already exists
Do not ask only, “Would someone buy this?” Look for observable behavior.
Evidence can include:
- Repeated questions in communities
- Search suggestions and related questions
- Existing products with active reviews
- Complaints about current solutions
- People creating their own awkward workarounds
- Professionals already being paid to solve the problem
Competition is not automatically bad. It can prove that customers recognize the problem. Your job is to understand what is missing, confusing, too expensive, too broad, or poorly suited to your specific audience.
Talk with potential users
Short conversations can reveal language and priorities that online research misses.
Ask questions such as:
- What is the hardest part of this task?
- How are you handling it now?
- What have you already tried?
- What usually causes you to stop?
- What would a useful solution help you complete?
- How often does the problem occur?
- What would make a solution feel too complicated?
Avoid leading questions such as, “Would you buy my amazing planner for $19?” People may be polite without intending to purchase.
Study existing solutions without copying them
Read product descriptions and customer reviews to identify patterns.
Look for:
- Features customers praise
- Missing instructions
- Confusing layouts
- Products designed for the wrong skill level
- Requests for a simpler or more specialized version
- Complaints about price or ongoing subscriptions
Use this information to understand the market—not to copy another creator’s wording, design, or copyrighted material.
Write a one-sentence product promise
Complete this sentence:
For example:
If the sentence remains vague, the product idea probably needs more focus.
Create the smallest useful version
A minimum useful product solves the narrow problem without unnecessary extras.
Instead of creating:
- A 30-module business course
- A 200-page general guide
- A giant template bundle
Test:
- One focused worksheet
- A short step-by-step guide
- A five-template starter pack
- A live pilot workshop
- A simple spreadsheet
The first version should be complete enough to create value but small enough to improve quickly.
Test the message before the finished product
Create a simple description page containing:
- The intended user
- The problem
- The result
- What is included
- The expected price
- A request to join a waitlist or pilot
Share it only with relevant people. Random traffic tells you little about whether the right audience understands the offer.
Use ethical pre-selling carefully
Pre-selling can provide stronger evidence than compliments, but be transparent.
Clearly explain:
- That the product is not finished
- What the buyer will receive
- The expected delivery date
- What happens if the project is canceled
- The refund policy
Do not create fake scarcity, pretend the product already exists, or use money from preorders for unrelated expenses.
Know the difference between weak and strong signals
Weak signals
- Friends saying the idea sounds good
- Social likes from people outside the audience
- People asking for a free copy
- General encouragement
Stronger signals
- Relevant people joining a waitlist
- Potential users agreeing to an interview
- People asking detailed questions about availability
- Pilot users completing the product
- Preorders made with clear terms
- Customers returning or referring others
Price the result—not the number of pages
A five-page checklist that prevents an expensive mistake may be more valuable than a 100-page ebook that remains unread.
Consider:
- The importance of the problem
- How frequently it occurs
- Time or money the product may save
- Prices of credible alternatives
- The support included
- The audience’s ability and willingness to pay
Test pricing rather than assuming the cheapest offer will sell best.
Run a seven-day validation sprint
- Day 1: Define the person, problem, and result.
- Day 2: Collect 20 examples of questions, complaints, or existing solutions.
- Day 3: Interview two or three potential users.
- Day 4: Write the one-sentence promise and product outline.
- Day 5: Create a simple description or waitlist page.
- Day 6: Share it with a relevant audience and collect questions.
- Day 7: Decide whether to build, revise, narrow, or stop.
When to continue
Move forward when you have evidence that:
- The problem is repeated and specific.
- The intended user recognizes the problem immediately.
- Your proposed result is easy to explain.
- People engage beyond polite compliments.
- You can create a useful first version responsibly.
When to revise or stop
Reconsider the idea when:
- People do not understand who it is for.
- The problem occurs too rarely to motivate action.
- Free solutions already solve it well enough.
- The audience likes the idea but will not use it.
- The product requires more support than you can provide.
- You would need misleading claims to make it attractive.
Sources and further reading
The practical guidance in this article is supported by the following government and consumer-education resources:
Educational information only. This article is not legal, tax, financial, investment, employment, or professional business advice.