You explain your business idea. Your friends love it. A few people say they would definitely use it. You start thinking about a name, a website, and the perfect launch.
Then you mention a price. The conversation changes.
“Keep me posted.” “Maybe next month.” “I’ll think about it.”
That gap between encouragement and a buying decision is worth investigating before you spend months building. People can like an idea without having a pressing reason to pay for it. Learning the difference is one of the most useful things an aspiring founder can do.
To validate a business idea, look for a specific customer, a problem they already act on, and a realistic next step they are willing to take. Here is how to find those signals without turning every conversation into a sales pitch.
1. Find out what happened before you arrived
“Would you use this?” invites someone to imagine a future in which your product is convenient, affordable, and effortless. A better starting point is a real event from their recent past.
- When did you last run into this problem?
- What did you do to solve it?
- How much time, effort, or money did that take?
- What was frustrating about the solution you used?
- Who decides whether to try or buy an alternative?
Listen for details: a missed deadline, an awkward workaround, a tool someone already pays for. If the person cannot recall the problem happening, your assumption about its urgency may need work. One interview is a clue, not a verdict.
The NSF I-Corps Hub’s guidance on customer interviews recommends starting with a hypothesis and a clear plan. Write down what you need to learn before the conversation, including what would make you change your mind.
2. Choose a customer you can actually picture
“Small businesses” is a market description, but it is too broad for a useful first conversation. A solo designer, a restaurant owner, and a manufacturer can face very different problems and buying decisions.
Consider this hypothetical example: you want to build a productivity app for freelancers. Narrow the first test to freelance designers who manage several client projects and repeatedly lose track of feedback. Now you know whom to interview and which moments to investigate.
You might discover that their real frustration is getting clients to consolidate conflicting comments. That could call for a better review process, a simple service, or a small tool. You do not know yet. A narrower starting point makes that uncertainty easier to investigate.
3. Meet the competitor called “good enough”
Your customer already has a way of getting through the day. It might be a spreadsheet, a group chat, a paid product, an assistant, or simply putting up with the problem.
Ask what makes that approach worth keeping. Familiarity, existing data, team habits, and the effort of switching can matter as much as features. A product can be better in your demo and still feel like more work in someone else’s week.
The U.S. Small Business Administration’s market research guidance highlights demand, available alternatives, pricing, and both direct and indirect competition. Use those questions to understand the choice your customer faces, rather than assuming enthusiasm means there is an open market.
4. Offer one small result you can deliver
Once interviews reveal a recurring problem, describe a modest offer: who it is for, what they receive, when they receive it, and what it costs. Avoid a long menu of features.
For our hypothetical designer example, the first offer might be a paid setup session that organizes one client’s feedback into an agreed review process. Delivering that manually could teach you which steps deserve software later. It would test demand for the service, though—not automatically prove demand for a future app.
Keep the offer honest. Explain what exists today and what does not. If you accept payment, be clear about the scope, delivery date, and refund terms, and offer only something you can fulfill.
5. Notice what people do next
Different responses answer different questions. A compliment tells you the idea sounds appealing. A waitlist signup suggests curiosity. A scheduled trial shows willingness to spend time. A paid pilot tests a specific offer at a specific price. Repeat use or another purchase gives you further evidence.
None of those signals guarantees a sustainable business. A friend may buy to support you. An unusually low price may attract customers you cannot serve profitably. A company may need several approvals before it can purchase. Record the context instead of treating every yes—or every delay—as the same result.
When someone declines, ask what stopped them. The obstacle might be urgency, trust, price, timing, or the wrong buyer. Change one part of the offer at a time so you can learn from the response.
A seven-day exercise to get out of your own head
Use the next week to gather initial evidence. This is a starting exercise, not a deadline for proving your whole business.
- Day 1: Write one customer description, one problem, and the assumption you most need to test.
- Days 2–4: Arrange a handful of conversations with people who match that description. Ask about recent experiences before explaining your solution.
- Day 5: Compare your notes. Which problem repeats? What are people doing about it? What evidence contradicts your original idea?
- Day 6: If a clear pattern emerges, describe a small, deliverable offer and a concrete next step.
- Day 7: Review actual responses and decide what to test next. Continue, narrow the customer group, revise the offer, or pause.
If recruiting people or getting a buying decision takes longer, extend the exercise. A quiet week may reveal a problem with your access to customers, not necessarily a lack of demand.
Before you build, answer this
Finish this sentence with evidence from your conversations: “This customer recently faced this problem, tried this solution, and agreed to this next step.”
If you cannot fill it in yet, you have a useful next task. Find the missing evidence before adding another feature.
The most valuable response to your idea may be an honest objection. It gives you something a compliment cannot: a specific problem to solve next.
