Startup idea validation is not asking friends whether an idea is good. It is collecting evidence that a reachable group of people has a painful problem, already tries to solve it, and would give up money, time, or workflow control for a better answer.
Founders need this discipline even more than funded teams. Every unvalidated build cycle costs nights, weekends, motivation, and opportunity. A runway is too short to spend three months building something nobody wants.
The 5-step validation checklist
1. Define the exact buyer
"Small businesses" is not a buyer. "Solo SaaS founders with a working prototype and no repeatable acquisition channel" is closer. A validated idea starts with a buyer you can find, describe, and interview without paying for ads.
The test: Can you list 10 specific people who fit this profile right now? Can you email them today? If the answer is no, your buyer definition is too broad or too disconnected from your existing network, which means you lack founder-market fit.
2. Name the painful situation
People buy in situations, not categories. Instead of "a productivity app," write the moment: "I have 200 saved startup resources, but I still do not know what to do this morning." The situation must be acute enough that the buyer is actively looking for a way out.
The test: When you describe the situation to the buyer, do they nod aggressively? Do they interrupt you to share their own version of the story? If they just politely agree, the pain is not high enough to drive a purchase.
3. Find the current workaround
If there is no workaround, there may be no urgency. Workarounds include spreadsheets, consultants, Notion docs, Slack threads, manual exports, saved bookmarks, or a person doing repetitive coordination by hand.
The test: Ask the buyer to show you their current setup. Do not ask what they use; ask them to open their laptop and walk you through the steps they take when the problem occurs. The messier the workaround, the better the opportunity.
4. Check frequency
A problem that appears once a year can still matter, but it is harder to build a habit around. Early products are easier when the problem repeats weekly or daily. High frequency builds workflow depth and makes the product sticky.
The test: How often did this happen in the last 30 days? If the answer is "zero," the problem is either seasonal, rare, or not actually a priority for this buyer.
5. Look for payment or commitment
Payment is the strongest signal, but it is not the only one. Useful commitment can also be a booked pilot, a calendar slot, a data import, a signed letter of intent, or a promise to switch when a specific feature exists.
The test: Ask for something that costs the buyer time, money, or social capital. "Would you pay $50 for this right now?" or "Can you introduce me to your boss to pitch this?" If they hesitate, the idea is not validated, regardless of what they said earlier in the conversation.
Questions to ask in validation interviews
The best interviews focus on the past, not the future. When you ask people what they would do, they lie to be polite. When you ask what they did, they tell the truth. (For more on this, see our Mom Test translation guide).
- When did this last happen?
- What did you do instead?
- How much time or money did it cost?
- What happens if you do nothing?
- Who else is involved in the decision?
- What have you already tried?
- If this existed today, what would stop you from using it?
The 14-day validation protocol
Do not spend months validating. The goal is a fast "yes" or a fast "no." Here is a two-week sequence:
- Days 1-3: Define the buyer, the situation, and the hypothesis. Write the interview script.
- Days 4-7: Reach out to 20 potential buyers. Book 5-8 interviews.
- Days 8-11: Conduct the interviews. Focus on past behavior and current workarounds.
- Days 12-14: Review the data. Do you have 3 out of 5 people confirming the same painful situation and workaround? If yes, build. If no, pivot or kill the idea.
Signals that the idea is still too vague
Watch for compliments without specifics. "This sounds interesting" is weak. "Can I send you three examples from my workflow?" is stronger. "I tried to solve this last week and failed" is stronger still.
Another warning sign: every interview points to a different buyer, different problem, and different urgency level. That usually means the idea is a theme, not yet a product. You need to narrow the focus until the interviews start sounding identical.
Anti-patterns: What bad validation looks like
Founders often run "validation" exercises that produce false positives. Avoid these:
- The landing page smoke test with no traffic. A landing page only validates an idea if you can get the target buyer to look at it. If you have no distribution, a 0% conversion rate means nothing.
- Surveying your friends. Friends will tell you the idea is great. Their feedback is worse than useless; it is misleading.
- Pitching the solution too early. If you spend the first 20 minutes of a 30-minute interview explaining your product, you are selling, not validating. You learn nothing about their actual problem.
What to build after validation
Build the smallest version that resolves the painful situation. Not the full platform. Not the eventual vision. The first product should create one obvious before-and-after moment.
Then, figure out how to price it and put it in front of the people you interviewed. Their reaction to the price tag is the final step of validation.
MoatKit teaches validation as a daily operating loop: clarify the stage, choose one decision, apply one tool, and save what changed. You can see the product structure in the curriculum tour.