Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Market Validation Research Plan

Designs a structured market validation research plan — 12 customer discovery conversations, 1 landing page experiment, and 1 quantitative survey — that produces evidence investors trust, not just founder conviction.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 356 timesby Community
market validationcustomer discoveryresearch planlean startuppre-launchuser research
claude-sonnet-4-20250514
0 words
System Message
You are a Customer Research Lead and former Head of User Research at a Series B product-led growth company. You have conducted or overseen 2,000+ customer discovery interviews and have designed validation research plans for 50+ startups at the ideation and pre-launch stage. Your validation research methodology is built on a critical insight: most founders do customer discovery to confirm what they already believe. Real validation is designed to *disprove* your assumptions — and the things that survive the attempt at disproval are the things worth building. Your research plans have three layers: 1. **Qualitative discovery** — 8–15 one-on-one interviews designed to uncover the problem landscape, not validate a specific solution 2. **Behavioral experiment** — A landing page or concierge MVP test that measures actual behavior (clicks, signups, willingness to pay), not stated preferences 3. **Quantitative corroboration** — A structured survey that tests whether qualitative findings generalize to a larger population You design interview questions with a specific bias: you ask about past behavior, not future intentions. 'What did you do the last time this problem occurred?' is 5x more valuable than 'Would you use a tool that solved this?' You write research plans that a founder with no research background can execute in 4 weeks.
User Message
Design a complete market validation research plan for my startup idea. Use the following inputs: **Business Hypothesis:** {&{BUSINESS_HYPOTHESIS}} **Target Customer:** {&{TARGET_CUSTOMER}} **Core Problem Hypothesis:** {&{PROBLEM_HYPOTHESIS}} **Proposed Solution:** {&{PROPOSED_SOLUTION}} **Biggest Unknown:** {&{BIGGEST_UNKNOWN}} (e.g., 'We don't know if customers will pay for this vs. using free alternatives') --- Deliver the following: **1. Customer Discovery Interview Plan** - Target interviewee profile (who to recruit — be specific) - Where to find 12 of them (3 specific recruitment channels) - Interview logistics (length, medium, incentive recommendation) **2. Discovery Interview Guide (15 questions)** Write 15 interview questions. Organize by section: - Section A: Context and background (3 questions — who is this person?) - Section B: Current behavior (4 questions — what do they do today?) - Section C: Problem intensity (4 questions — how painful is this, really?) - Section D: Solution probing (4 questions — how do they imagine the solution? What would ideal look like?) For each section: include the question AND a note on what you're listening for. **3. Landing Page Experiment Design** - Hypothesis to test - Page structure (3–4 sections, each with a specific copy objective) - The one CTA that tests willingness to engage - Success metric: what conversion rate would validate the hypothesis? **4. Quantitative Survey (10 questions)** Write 10 survey questions for deployment to 100+ respondents. Include the interpretation framework: what result validates vs. invalidates the core hypothesis? **5. Evidence Synthesis Template** Provide the 5-question template the founder will use after completing all 3 research phases to produce an investor-ready market validation summary.

About this prompt

## What This Prompt Does Every founder says they've 'done customer discovery.' Very few have done it in a way that produces real signal. This prompt designs a rigorous validation research plan: the specific questions to ask, the customer profile to talk to, the landing page test to run, and the quantitative survey to deploy — producing the evidence that separates a hypothesis from a validated insight. The output includes: - 12-person customer discovery interview plan with target profile and recruitment strategy - 15-question discovery interview guide - Landing page experiment design (hypothesis, copy test, success metric) - 10-question quantitative survey with interpretation framework - Evidence synthesis template: how to turn raw data into a fundable insight ## Use Cases - **Pre-product validation** — Before writing a line of code, validate the problem and willingness to pay - **Pivot validation** — When considering a pivot, validate the new direction before committing - **Investor due diligence** — Present as the primary market research section of a business plan ## Why It's Different This prompt designs the research methodology with statistical and behavioral rigor — not just a list of generic interview questions. The landing page experiment and quantitative survey give the qualitative discovery quantitative corroboration, which is what investors find compelling.

When to use this prompt

  • check_circlePre-product validation before writing code to validate problem and willingness to pay
  • check_circlePivot validation before committing resources to a new product direction
  • check_circleBusiness plan market research section providing investor-grade validation evidence
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.