How to Validate a Digital Product Before You Build It

Test a claim you can disprove

Product validation means checking whether a proposed solution addresses a problem people care enough about to act on. It does not mean finding enough positive comments to feel ready. Start with a specific claim: 'Independent podcast editors need a clearer way to collect client files, and some will pay for an intake system that reduces missing information.' That claim can be investigated.

Write down your assumptions separately. You may be assuming the task happens often, the current workaround is painful, the buyer has permission to purchase, and your file fits the software they use. If any one assumption is wrong, an attractive product can still fail. Test the most uncertain or costly assumption first.

Ask about the last time the problem happened

A useful conversation starts with recent behavior. Ask somebody to describe the last project in which the problem occurred. What information was missing? How did they recover it? What did the delay cost in time or attention? Which tools did they use? Avoid introducing your solution before you understand the task. An interview about real work is more useful than asking whether your idea sounds good.

Keep notes in the person's language, but get permission before recording or publishing their words. Do not collect private client information you do not need. Shopify's market-validation guidance identifies interviews, surveys, and tests as ways to investigate customer needs. The questions below are an original starting point, not a requirement to run a large research project.

• When did this last happen, and what were you trying to finish?
• What did you do instead, and what was frustrating about that workaround?
• Have you tried buying or creating a solution already?
• What would a useful result look like, and what would make a new tool inconvenient?

Build a small, usable prototype

For a template, make one completed example and one blank version. For a calculator, implement the central calculation and explain the inputs. For a course, create one lesson that helps someone complete a defined task. The prototype should show the work, not just describe the future product. A screenshot alone cannot reveal whether the person can use the file.

Invite a small number of relevant users to try it. You might choose five as a manageable first round, but that is a planning choice and not a statistically representative sample. Observe what they complete without your help. Ask which part they would keep using and which part duplicates something they already have. Revise the confusing parts before expanding the product.

Separate interest from purchase evidence

A page view shows exposure. A download shows curiosity. A request for the finished tool shows stronger interest. A completed purchase is evidence of willingness to pay at that particular price and presentation. None of these signals alone tells you the eventual size of the market. Track each step so that enthusiasm does not get mistaken for revenue.

If you test a paid offer, describe exactly what exists and what the buyer will receive. A pre-order needs a clear delivery date, scope, cancellation process, and reliable fulfillment. For a simpler first test, finish a narrow version and sell that version. Do not invent availability, customers, testimonials, or sales numbers to make a test look successful.

Choose the next action from the evidence

Set a decision rule before the test. For example, you might proceed when several relevant users independently describe the same problem and at least one buys the usable version. That is a modest experiment threshold, not proof of a sustainable business. If people understand the problem but dislike the file, change the format. If they do not recognize the problem, reconsider the audience or the idea.

Record what you tested, who saw it, what happened, and what you will change. The goal is to reduce uncertainty one decision at a time. A useful validation log can save you from repeatedly rebuilding around the same untested assumptions. Use the Validation Sprint Kit when you want interview prompts, a decision sheet, and an experiment log in one place.