How to validate a startup idea with your first customers

Choose one person and one problem

Try writing down who you want to help and the task they struggle with. Be specific enough that you could find that person this week. A small clinic trying to follow up with patients is easier to learn from than a broad category like healthcare.

Write down what you believe is happening and what you need to check. Perhaps staff spend an hour each evening making reminder calls. Perhaps patients forget appointments. Those are different problems. Finding out which one matters changes what you build.

Ask about the last time it happened

Ask someone to walk you through the last time they did the task. What started it? Which tools did they use? Where did they get stuck? If they are comfortable showing you, watch them do it. Give them time to explain before offering a solution.

Questions about a real event tend to give you more to work with than asking whether someone likes your idea. Listen for what they already do to get around the problem, what it costs them and who else is involved.

Keep a few notes after each conversation. Record what the person said separately from what you think it means. If their experience surprises you, leave room for that in your next conversation.

Test the smallest useful thing

Choose a test that helps you learn one thing. You could help someone complete the task by hand, show a simple prototype or try a small pilot. Tell them honestly what works and what you are still doing manually.

Agree on what you will watch for. Did they finish the task? Did it save time? Did they come back? A test is easier to understand when you decide what would count as useful before you run it.

For a product that needs equipment or safety checks, choose a test that fits those constraints. You can learn about a workflow or buying decision while the technical work continues. Give people a clear account of what they are agreeing to try.

Look at what people do next

A kind comment feels good, and it is okay to appreciate it. Then look for the next action. Someone uses the product again, brings a colleague into the conversation or agrees to a pilot. Ask what made them take that step.

If they stop using it, ask about that too. They may have found it confusing, needed a different feature or had a problem that mattered more. You are trying to understand enough to make the next decision with care.

Bring what you learned back to the work

At The Founding Company, we want founders to have people they can show this work to. Bring the conversation notes, the rough demo and the question you are unsure about. Another founder may spot something you missed or help you plan a better test.

Assembly brings founders and co-founders together in Hyderabad for 70 days. If you have an MVP, prototype, pilot or concrete problem evidence and want a place to keep working, read how Assembly works. Our application gives you space to explain what you have tried so far.

If you are still figuring out your stage, you can contact the team with a simple question. We would rather you understand the program before deciding to apply.