Write the assumption you are actually testing

Use one sentence: ‘I believe this buyer will pay for this product because it helps them achieve this result or avoid this problem.’ If the sentence names everyone, several outcomes, or a complicated bundle, narrow it before testing.

Separate the assumptions: the problem exists, the buyer cares now, your promise is credible, the format is usable, the price is acceptable, and you can reach the buyer. One positive signal does not prove all six.

Build an evidence ladder

Move from low-cost learning to higher-confidence behavior. Do not treat every signal as equal.

  • Problem language: repeated searches, questions, reviews, complaints, and workarounds.
  • Buyer conversations: specific examples of when the problem occurred and what it cost.
  • Offer response: qualified people request details, join a relevant waitlist, or book a fit conversation.
  • Payment behavior: a preorder, deposit, paid pilot, or completed purchase.
  • Use and completion: customers access the product, use it, and reach the intended useful outcome.

Ask questions that do not invite compliments

Ask about past behavior: ‘When did this last happen?’ ‘What did you try?’ ‘What made the current option frustrating?’ ‘What happens if it remains unsolved?’ ‘Have you paid for help?’ Avoid explaining your idea for most of the conversation.

The buyer’s real examples, priorities, words, and existing spending are more useful than a polite answer to ‘Would you buy this?’

Test the minimum credible offer

Describe the buyer, problem, result, contents, delivery, price, and next step on one page. The product can begin as a small paid pilot, preorder, live workshop, or manually delivered version when the terms are transparent.

Do not call a test ‘validated’ merely because traffic arrived. Decide the threshold in advance: for example, a defined number of qualified conversations, deposits, purchases, or completed uses from a stated audience size.

Decide: build, revise, or stop

Build when the problem, buyer, promise, and paid response are coherent. Revise when buyers care about the problem but reject the framing, format, price, or timing. Stop or park the idea when evidence remains weak after a fair, qualified test.

Stopping an unsupported idea is not failure. It protects the time and money needed for a stronger one.