Conduct Market Research Validation

The most expensive mistake in early-stage business is building something nobody wants — and the second most expensive is convincing yourself the demand is there because you want it to be. Market research validation is the discipline that stands between an idea and a commitment of money and time. Done well, it tells you whether a real, reachable, willing-to-pay market exists before you spend a year finding out the hard way.

This prompt produces a structured validation plan: it identifies what assumptions your idea depends on, designs concrete ways to test each one, and defines what evidence would count as a genuine pass or fail. The goal is not to confirm your idea — it is to give your idea a fair, rigorous chance to be proven wrong before it is expensive to be wrong.

What It Does

Breaks a business idea into its core, testable assumptions about the market, the customer, and willingness to pay.
Designs a concrete, sequenced validation plan with specific research methods for each assumption.
Defines explicit pass/fail evidence thresholds so the results lead to a clear go, pivot, or stop decision.

The Prompt

#CONTEXT:
I have a business or product idea that I am considering investing time and money into. Before I commit, I need to validate whether a real market exists — meaning a specific group of people who have the problem, are reachable, and would pay for a solution. Your job is to help me design a rigorous, low-cost validation plan that tests the riskiest assumptions first, so I can make an evidence-based decision to proceed, pivot, or stop. Do not validate the idea for me — help me build the process that will validate or invalidate it honestly.

#ROLE:
You are an experienced market research strategist and startup advisor who has guided dozens of founders through pre-launch validation. You are skeptical by default, you distinguish sharply between vanity signals and real demand evidence, and you know that the goal of validation is to fail bad ideas cheaply.

#RESPONSE GUIDELINES:
1. Begin by restating the idea and extracting the core assumptions it depends on — about the problem, the target customer, the market size, the willingness to pay, and the channel to reach customers.
2. Rank these assumptions by risk: which, if false, would kill the idea? Test the riskiest first.
3. For each key assumption, design a specific, low-cost research method (interviews, surveys, landing-page tests, pre-sales, competitor analysis, search-demand analysis).
4. Define what result would count as evidence the assumption is true versus false — be concrete about thresholds.
5. Sequence the plan into phases, with a clear decision point after each phase.
6. Warn me explicitly about the most common ways founders fool themselves during validation.

#VALIDATION QUALITY CRITERIA:
1. Riskiest-first: The plan tests the assumptions most likely to be false before the comfortable ones.
2. Behavior over opinion: Methods should favor what people do (sign up, pre-pay, click) over what they say they would do.
3. Falsifiability: Every test must have a defined outcome that would prove the assumption wrong.
4. Low-cost: Methods should be achievable on a small budget and short timeline before major investment.
5. Decision-linked: Each phase ends with a clear go/pivot/stop criterion, not just "more data."

#INFORMATION ABOUT ME:
- The business or product idea: [DESCRIBE_YOUR_IDEA]
- Who I believe the target customer is: [TARGET_CUSTOMER]
- The problem I believe it solves: [PROBLEM_STATEMENT]
- My budget and timeline for validation: [VALIDATION_BUDGET_AND_TIMELINE]
- What I have already learned or assumed about this market: [EXISTING_KNOWLEDGE]

#RESPONSE FORMAT:

Idea Summary & Core Assumptions:
[Restated idea]
1. [Assumption — labeled with what it claims]
2. [Assumption]
3. [Assumption]

Risk Ranking:
- Highest risk: [Assumption + why it would kill the idea if false]
- Medium risk: [Assumption]
- Lower risk: [Assumption]

Validation Plan by Phase:
Phase 1 — [Name]:
- Assumption tested: [Which]
- Method: [Specific research method]
- Pass evidence: [Concrete threshold]
- Fail evidence: [Concrete threshold]
- Decision point: [Go / pivot / stop criteria]

Phase 2 — [Name]:
[Same structure]

Phase 3 — [Name]:
[Same structure]

Self-Deception Warnings:
- [Common trap and how to avoid it]
- [Common trap and how to avoid it]

How to Use

Describe your idea honestly and specifically — including who you think will buy it and why. Vague inputs produce a vague plan.
Be realistic about your validation budget and timeline so the methods proposed are ones you can actually execute.
Copy the completed prompt into your preferred AI tool.
Review the pass/fail thresholds critically — if any feel too easy to satisfy, push back and ask for stricter evidence criteria before you start.

Example Input

## Information about me

- The business or product idea: A subscription service that delivers pre-portioned baking kits for parents to bake with young children on weekends
- Who I believe the target customer is: Parents of children aged 4–9 in dual-income households who want screen-free weekend activities
- The problem I believe it solves: Parents want quality activities with their kids but lack time to plan and shop for them
- My budget and timeline for validation: €500 and 6 weeks before deciding whether to build
- What I have already learned or assumed about this market: Competitor meal-kit services exist; I assume parents will pay €25/box; I have not spoken to any potential customers yet

Tips

Test the riskiest assumption first. It is tempting to start with research that is comfortable. Start instead with the assumption that, if false, makes everything else irrelevant.
Favor behavior over words. A landing page that collects pre-orders or deposits tells you far more than a survey asking "would you buy this?" Build behavioral tests into the plan wherever possible.
Write your pass/fail thresholds before you collect data. Deciding what counts as success after seeing the results is how founders rationalize weak evidence into a green light.
Talk to people who will say no. Interview skeptics and non-buyers, not just enthusiasts. Their objections are the most useful data you will get.
Follow up with a pricing-validation prompt. Once demand is confirmed, run a dedicated prompt to test what customers will actually pay — demand and price are separate questions.