How to Validate a Digital Product Idea Before You Build

What validation can—and can’t—tell you

Validation means gathering evidence before investing more effort. You’re testing assumptions about the buyer, their problem, your proposed solution and how you’ll reach them.

No small test guarantees future sales. Someone saying they like your idea is different from trying a prototype, asking about delivery or paying for a clear offer. Treat each signal according to what it actually shows.

1. Find evidence of the problem

Read discussions where your intended buyer asks for help. Check reviews of related products, questions in relevant groups and search results for the task. Look for recent, repeated examples rather than one enthusiastic post.

Keep a simple research note with the problem, the person describing it, the date, their current workaround and a link to the source. Use exact wording in your private notes when helpful, but don’t republish someone’s private details or present their words as your testimonial.

Existing products can show that people buy in a category. They don’t prove that your version will sell. Look for a specific gap: unclear instructions, a missing use case or a format that is awkward for your buyer.

2. Have five useful buyer conversations

Invite a few people who fit the intended audience. Explain that you’re learning about the task, keep it brief and give them an easy way to decline. Follow community rules when asking in a group.

Five conversations are a manageable starting point. They aren’t a representative survey. Ask about recent behavior before showing your solution:

• When did you last deal with this problem?
• What did you do to solve it?
• What took the most time or felt confusing?
• Have you used or paid for anything to help?
• What still didn’t work for you?

A question like “Would you buy my amazing planner?” introduces the answer you want. “Walk me through the last time you planned meals” gives you a more useful story.

3. Show a small example

Make a sample page, outline or rough template that demonstrates the core task. It should be enough to react to, without becoming a week-long design project.

Ask the person to explain what they think it does. Then ask which part they would use, which part is missing and what they would use instead. If possible, let them try one task with it.

Be careful with praise. “It looks lovely” tells you about the presentation. “I would use this grocery section, but I need a place for lunches” tells you about the product.

4. Test an honest, specific offer

Describe who the product is for, what they receive, the price you’re testing and the current stage of the product. Include a real preview. If you’re collecting interest rather than selling, say so clearly.

A request to see the finished version can be a useful interest signal. A purchase of a usable product is stronger evidence of willingness to pay for that offer. Neither guarantees a repeatable channel or a large market.

If you offer a preorder, clearly state that it’s a preorder, the delivery date and the applicable purchase and refund terms. Only make commitments you can meet. A simple interest test can be enough when you aren’t ready to accept payments.

Record where visitors came from and what they did next. A test shown only to friends may say less about demand from people who don’t know you.

5. Decide what the evidence supports

Review the pattern across your research, conversations and offer test. Don’t pick a convenient number of likes as a universal pass mark.

• Proceed with a small draft: suitable people describe the same problem, understand the offer and take a meaningful next step.
• Revise and test again: the problem is real, but the format, wording, included features or price causes specific objections.
• Pause this idea: you can’t find the problem, can’t reach the buyer or repeatedly hear that current alternatives already work well.

“No response” is ambiguous. The wrong audience, weak distribution, confusing copy or low demand can all produce it. Change one assumption and run another small test when you have a concrete reason.

A one-page validation note

Keep the decision simple enough to revisit:

1. Buyer and task: who are you helping, and what are they trying to do?
2. Evidence: what real examples did you find?
3. Conversations: what repeated across the people you spoke to?
4. Offer: what did you show, to whom, and at what price or level of commitment?
5. Response: what did people actually do?
6. Next decision: build small, revise one thing or pause.

Write down doubts as well as positive signals. A useful test reduces uncertainty; it doesn’t need to produce the answer you originally hoped for.

What to do after the first test

If the evidence supports proceeding, build only the core version and ask a suitable buyer to try it. Use the seven-step digital product guide to move from that decision to a draft and offer.

If you need a more specific idea, revisit our beginner product examples and narrow the person or task. “A planner for everyone” is harder to test than a checklist for one situation.

Keep checking demand as the product changes. Validation is part of making a useful product, not a badge you earn once and never revisit.