Validate a digital product idea before you build it

Step 02

Look for unprompted pain and workarounds

Notice what people bring up before you pitch an idea. Keep a short evidence log from client conversations, emails, project debriefs, community discussions, or support questions. Capture the date, situation, their exact words, what they tried, and what happened next.

Pay special attention to workarounds: a spreadsheet they keep rebuilding, a long search through old notes, a paid tool they use awkwardly, asking a colleague, or hiring help for a small repeatable task. A workaround shows effort; it does not automatically mean they want a download.

Step 03

Listen for the words people use

Save phrases from actual conversations and look at how people describe the same snag in places they already ask for help: relevant forums, professional groups, search suggestions, reviews of existing tools, and public Q&A threads. Search a few variations of the problem, not only the polished phrase you would put on a sales page.

• What words do they use for the frustrating task or moment?
• Are they asking how to do it, looking for an example, or comparing ways to solve it?
• Do different people mean the same thing by the phrase—or are several problems being bundled together?

Search results and public discussion can reveal vocabulary and possible alternatives, but visibility is not proof of a reachable audience or willingness to pay. Do not treat a search suggestion, post, or review count as a demand forecast.

Step 04

Ask about what happened, not what might happen

Talk with people who match your narrow buyer description. Ask them to walk through a recent, real instance before you show an idea. Keep your explanation until after you have heard their story; otherwise, it is easy to lead them toward the answer you hope to hear.

1. “Tell me about the last time you had to [do the task]. What was going on?”
2. “What did you try first? What else did you try?”
3. “Did you spend money, use a tool, ask someone, or set the task aside?”
4. “What was frustrating or still unresolved after that?”
5. “What did you do next, and how did you decide?”

Avoid “Would you buy this?” or “Do you like my idea?” People are often kind and hypothetical answers cost nothing. Past purchases, time spent, repeated attempts, and the consequences of leaving the problem unsolved give you better context. Listen without trying to sell during the conversation.

Step 05

Test a clear offer before making the product

Turn what you have learned into a one-page description—not a finished download. Say who it is for, which specific problem it addresses, what useful next step it supports, the proposed format, what is included and excluded, and the price you are considering. Add a small sample or rough outline so people can judge the substance rather than a vague promise.

Share it with a few relevant people you have permission to contact, or in a community where this kind of request is welcome. Make one low-cost, non-paid ask: invite them to reply for the outline, point out a missing piece, or opt in to hear if you make it. Track the actual next step and their reason; do not buy ads or build a full funnel just to run this test.

Step 06

Separate attention from purchase evidence

Signals have different weight. Use them to decide what to learn next, not to claim certainty. Write down what each response actually demonstrates.

• Attention: a like, view, click, save, or “great idea” tells you the message got noticed. It does not establish a serious problem or buying intent.
• Problem evidence: an unsolicited, specific account of a recent struggle, repeated workaround, or time/money already spent suggests the problem is real for that person.
• Intent evidence: a relevant person asks for the outline, makes an introduction, shares details so you can tailor the scope, or opts in to a follow-up. This is stronger than praise, but still is not a purchase.
• Purchase evidence: someone actually pays for a clearly described offer. That is direct evidence for that buyer and offer—not a guarantee that a wider audience will buy.

To assess willingness to pay before building, compare the proposed price with what people have already paid or invested to handle the same problem, then notice whether anyone takes a concrete next step toward your offer. A no-payment test can reduce uncertainty, but it cannot establish purchase demand on its own.