A simple, founder-friendly framework for validating demand before you spend a dollar on development — including the exact 15-minute interview script.
Validation is the cheapest insurance you can buy. It costs you a few weeks and a hundred coffees, and in exchange it tells you whether the next twelve months of your life are going to be a business or a hobby. The founders who skip it almost always wish they hadn't. The founders who do it badly almost always think they did it well.
This is a practical framework for doing it properly — without buying a research agency, without a CRM, without a Typeform that nobody fills out.
What validation actually is
Validation is not asking people whether they would use your product. Everyone says yes to that question and almost no one means it. Validation is finding evidence that a specific problem is painful enough that specific people are already trying to solve it badly.
Notice what changes when you frame it that way. You're not pitching. You're not testing your idea. You're looking for the existing pain — the workaround, the spreadsheet, the duct-tape solution. If you can find ten people doing the painful thing today, you have a market. If you can't, you have a hunch.
The 15-minute interview
The single highest-leverage thing you can do this week is talk to ten potential users for fifteen minutes each. Here is the script I give clients. It works.
The five questions
- Tell me about the last time you had to [do the painful thing]. Walk me through it.
- What did you use? What worked? What didn't?
- How often does this come up?
- What have you tried to make it better?
- If a perfect solution existed, what would you stop doing?
Notice what's missing. You are not describing your product. You are not asking whether they'd use it. You are not pitching. You are asking about the present tense — what they already do, what they already hate, what they already pay for.
Pitching at the validation stage is the most common mistake founders make. The moment you describe your solution, your interviewee starts being polite. Polite data is poison.
How to find ten people
Most founders get stuck here. The fix is to make the bar very, very low.
- Your existing network. Post on LinkedIn or in a relevant Slack: "I'm researching [problem]. Looking for 10 people who deal with it. 15 minutes. No pitch." You will get more responses than you expect.
- Communities your user already lives in. Reddit, Discord, Indie Hackers, niche Facebook groups. Lurk first. Contribute. Then ask.
- Cold outreach. 50 LinkedIn messages produces 5–10 calls. Be specific about who you want. Be specific about what you'll do (and won't do) on the call.
If you can't get ten people to give you fifteen minutes, that is itself a validation result. It probably means the problem isn't as universal or as painful as you think — or you don't yet know who the user actually is. Both are useful to learn before you spend $60,000 finding out.
What counts as a signal
Three patterns to listen for. They matter much more than what people say about your idea.
1. The workaround
If multiple users describe a workaround they currently use — a spreadsheet, a hacky Zapier, a manual process they do every Tuesday — you have a real problem. Workarounds are the strongest signal you can find. They mean someone already pays a cost to solve this.
2. The emotional charge
Listen for sighs, eye-rolls, half-laughs. People are emotional about real problems and indifferent about imagined ones. If the interview is flat, the problem is theoretical.
3. The willingness to pay (today)
"Would you pay for this?" is a useless question. "What do you currently pay to solve this?" is a very useful question. If they already pay something — even a workaround tool, a contractor, a service — you have a budget line you can move into.
If you finish ten interviews and find workarounds, emotional charge, and existing budget, you have validated demand. If you don't find at least two of the three, you are about to build a solution looking for a problem.
What validation is not
- It is not a landing page with an email capture. That tests interest, not demand. Email signups are vanity signals.
- It is not asking your friends. Their job is to support you. They will support you into a bad business.
- It is not waiting for permission. Nobody is going to confirm your idea is right. You are looking for evidence, not confirmation.
- It is not a one-time exercise. The user research that validates the idea is the same research that shapes the MVP. Plan for ongoing conversations, not a single round.
From validation to scope
Validation feeds directly into the Founder Vision Brief and the PRD. The user's words become user stories. The workarounds become the as-is journey. The emotional charge becomes the value proposition. The existing budget becomes the monetization model.
Founders who do real validation produce dramatically better PRDs because their requirements are anchored in specific human behavior instead of abstract user types. Engineers can feel the difference within the first sprint.
Every hour of validation saves a week of engineering. Compounding starts immediately.
What to do this week
- Pick ten people in your network who plausibly have the problem.
- Send the message above today.
- Run the five-question script.
- Take notes during, not after. Quote them verbatim.
- At the end of the ten calls, look for workarounds, emotional charge, and existing spend.
If you'd like a structured place to take those notes and turn them into a Founder Vision Brief, that's exactly what a Clarity Session produces in one focused hour.