How To Validate Your Startup Idea Quickly?

You Have A Startup Idea? Perfect. Here's What To Do Immediately After.

How many days would it take you to go from “I have an idea” to “I talked to 5 potential users”? 1 month? 1 week? 1 day?

In my opinion, it should be a matter of hours!

Over the last 2 years, I have worked on 8 ideas. 5 were pivots and versions of my old startup, and 3 came after I closed the business, all three in just the last 2 months.

Across all 8, I have been trying to perfect one thing: how fast I can go from an idea to actually talking to potential users.

The first one took 3 months to go from an idea in my head to an actual conversation with a user, because I wanted to walk in with something finished. I never once stopped to ask whether they wanted my solution, or whether they even had the problem I assumed they had.

The one I am building right now already has 17 people testing it from day 1. Every one of them is giving me feedback, on the name, the design language, the features, and a few have already started referring their friends and family.

And that, in my opinion, is the right way to build.

So how do I pull that off? It is not magic. It just takes a little strategy and a little courage.

Today, I want to share my strategy.

---

The Prompts

Everything in this process runs in a Claude or ChatGPT chat on any model.

The only part that takes some time and a little courage is getting real people to answer a survey. Real people who are ideally strangers.

Because responses trickle in over days the priority from day one is getting the survey out as fast as possible.

But before you start with the first prompt, write your hypothesis down on paper. I want you to write what you think the problem is, what you think people are doing about it today, and what you think the potential solutions could be.

Do it before you do anything else. Because everything that follows is created to prove or disprove your opinions.

Once you have that, copy these into your AI chat in order.

Prompt 1: Refining Your Thoughts

You are my validation partner for the next five days. We're going to stay in this one chat the whole time, so keep everything we produce here in mind as we go.

I have an early startup idea and I need to pressure-test it before I build anything.

Here's my raw idea:
[DESCRIBE YOUR IDEA IN 3–5 SENTENCES: the problem you think exists, who has it, and what you're thinking of building]

And here's what I already wrote down by hand, before any data:
[YOUR OWN FIRST DRAFT: what you think the problem is, what you think people do about it today, what you think the solution could be. Paste it rough. If you skipped this, go write it now.]

Your job: interview me to turn this into a clear one-page validation brief.

Rules:
- Ask me ONE question at a time. Wait for my answer before the next one. Don't dump a list.
- Keep going until you can fill every section below. Push on anything vague: if I say "small businesses," ask which ones.
- Don't be a cheerleader. If something sounds like a guess, call it a guess.
- Where my handwritten draft and my answers disagree, point it out.

Interview me until you can confidently fill in:
- The core problem (one sentence, in the user's words, not mine)
- Who exactly has it (specific: role, situation, not "everyone")
- How painful it is today and what they do instead (workaround / competitor / "nothing")
- My core hypothesis (the belief that, if wrong, kills the idea)
- My proposed solution (one sentence)

When you have enough, stop asking and output a document titled VALIDATION BRIEF with:
- Problem statement
- Target user (specific)
- Current alternatives
- My hypotheses (rewrite mine clearly)
- 3–5 additional hypotheses I haven't named but that this idea secretly depends on, the hidden assumptions that could sink it
- Riskiest assumption (the single thing most likely to be false, we test this first)
- Where this user already hangs out online (specific subreddits, communities, Slacks, forums, hashtags), I'll use this to find people
- Kill / Pivot / Continue criteria: what survey + research result would make you tell me to kill this, pivot it, or keep going? Give me concrete thresholds now, before I see any data.

Call it the VALIDATION BRIEF and refer back to it by that name for the rest of this chat. Do not quietly revise it later; if something we learn contradicts it, say so out loud.

Start by asking me your first question.

Prompt 2: Fast Landscape Scan

Using the VALIDATION BRIEF above, do a fast landscape scan with web search. 15 minutes of work, not a deep report. The deep one comes later.

I only need three things, in plain language, no jargon:
1. Is this problem already perfectly solved? List the top 3–5 things people use today (products, tools, hacks, spreadsheets) and one line on where each falls short.
2. Are there signs people actually want it fixed, complaints, workarounds, high-engagement threads? Give me 2–3 real examples with links.
3. Based on what you found, what 2–3 things should my survey probe that I might not think to ask?

Keep it under one screen. Bullets. End with Green / Yellow / Red light to keep going, and one sentence why.

If anything here contradicts the brief, say so plainly instead of smoothing it over.

Prompt 3: Build The Survey

Now build me a short validation survey I can drop straight into Tally or Google Forms. Use the VALIDATION BRIEF and the landscape scan above, especially the riskiest assumption and anything the scan told us to probe.

Non-negotiable rules:
- 5 questions. Aim for exactly five; 7 is the absolute ceiling and you need a reason to go past five. Every extra question costs responses.
- Default shape: 4 multiple-choice or scale questions, and at most ONE open-ended question that lets the person talk in their own words.
- Test my riskiest assumptions first, not my solution.
- Ask what people do and pay today, not what they would do. ("How do you handle X today?" not "Would you use a tool that…?")
- Neutral wording. Don't lead the witness, don't suggest the answer inside the question, don't sell my idea anywhere in the survey.
- Ask for name and email at the end, after every real question.

Give me, ready to paste:
1. Survey title (plain, not salesy)
2. Short description (2 sentences, what it's about + how long it takes, e.g. "Takes 90 seconds")
3. The 5 questions, each with type (multiple choice / scale / open text) and answer options
4. The final optional email question, worded well
5. One line under each question naming which hypothesis it tests, and what a good vs bad answer looks like, so I can read the first few responses live and know whether a question is pulling its weight

I would say ask for a name and an email last, after every real question. In my surveys this single change cut drop-off by 15 to 20 percent. Because identity requests up front make a form feel like a lead capture instead of a two-minute favor.

Another thing to remember is that you want to ask people what they do and pay for today, not what they would do if your solution existed. Because behavior is a far better predictor than what someone says they would do.

My own sweet spot is five questions with three multiple-choice and two open-ended, descriptive questions. And I always build my surveys in Tally with the Pro version. It is so worth the money. It shows partial submissions, so you still get signal from someone who drops off halfway. And I also get to observe how the first few people answer, so I can cut, rewrite, or drop a question mid-survey.

Prompt 3b: Optional Mid-survey Feedback

Here are the first responses that came in:
[PASTE THE FIRST 3–5 RESPONSES, partial ones included]

Against the hypotheses each question was meant to test: which questions are actually pulling their weight, and which are giving me mush? For anything weak, tell me whether to cut it or rewrite it, and give me the rewrite. Keep the count at five.

If people are dropping at a particular question, say which one and why you think so.

Prompt 4: The Deep Research

While I collect survey responses, do the deep market research. Use full research mode and web search, dig properly. But the report must be written for someone who knows nothing about this industry.

Work from the VALIDATION BRIEF above, and test every hypothesis in it, mine and the ones you added. Don't re-litigate the landscape scan, go deeper than it.

Research rules:
- Do the heavy research, then translate it. Zero jargon. If you must use a term, define it in five words.
- Assume I know nothing about this market. Explain like you're telling a smart friend at a coffee shop.
- Every section starts with ⚡ TL;DR, do this: 1–3 concrete action items, not a summary.
- For each hypothesis: what the evidence suggests + confidence (High / Medium / Low) + one line why.

Structure the report exactly like this:
1. Is the problem real? (evidence people actually struggle with this)
2. Who has it, and how many (rough size in plain numbers, "roughly X million people / Y thousand businesses," not TAM/SAM jargon)
3. What they use today (the real competition, including "a spreadsheet" and "they just live with it")
4. Why now (what changed, why it hasn't been solved)
5. Reasons this could flop (be honest, the red flags)
6. Hypothesis scorecard (table: hypothesis → evidence → confidence)

End with a VALIDATION CHECKLIST + SCORE:
- 8–10 yes/no checks (e.g. "Is the problem frequent?", "Do people already pay to solve it?", "Is there a wedge competitors miss?")
- A score out of 10
- A one-line verdict: Strong signal / Mixed / Weak, and what would have to be true to move up a tier.

This score is a prediction, not the verdict. We'll compare it to what real people say at the end of the week.

Prompt 5: The Final Analysis

Survey responses are in. Give me the final validation call, using the VALIDATION BRIEF, the landscape scan, and the deep research report from earlier in this chat.

Raw survey responses (CSV):
[PASTE CSV, include partial submissions if your form captures them, and mark them as partial]

Do this:
1. For each question, tell me what the responses actually say, in plain language. Flag anything surprising. Note how many people left an email at the end and treat that percentage as a demand signal.
2. Go back to the Kill / Pivot / Continue criteria you set in the brief, before either of us had seen any data. Did the data hit them? Quote the thresholds back to me and be strict. Don't let me talk myself into it, and don't move the bar because the result is close.
3. Score each hypothesis: Supported / Mixed / Not supported (survey + research combined).
4. Cross-check: where do the survey and the research agree, and where do they contradict? Contradictions are where the real insight is. Also compare the research score you predicted earlier against what real people actually said, and tell me what the gap means.
5. Final VALIDATION SCORE out of 10 and one verdict:
   - BUILD: validated enough to make an MVP
   - PROBE: promising but one key thing is unproven; name the single next test
   - PARK: the evidence isn't there; tell me why, kindly but clearly

If BUILD or PROBE: the one riskiest thing still standing, and the fastest way to test it in the next five days.

This is also where you should think of a kill criteria because the best way to test multiple ideas is to think of it as an experiment. You hold the problem tightly and the solution loosely, and you stay open to whatever the feedback says, because an experiment can be proven or disproven, and neither outcome reflects on you. It just tells you whether this particular problem or this particular solution is the right one.

---

Why It’s Built This Way

I have used this exact structure eight times now, and each time, the fear of showing someone my unfinished idea got a little smaller.

I am still afraid of the judgment. But following a system means that by day five, I am not guessing anymore, and that is worth more than showing up with something polished.

I perfected this because it took me far too long to go from having an idea to actually talking to the people it was for.

If you run it on your own idea this week, reply and tell me which word you landed on. I want to know what got built, what got probed, and what finally got parked.

Durva