A practical guide

How to validate a startup idea before building

Start by testing whether a specific group of people experiences the problem, how they handle it today and what they are willing to do to improve it. An AI score, a vote or a compliment is a starting signal, not proof of demand.

1. Write down the problem and your assumptions

Describe who has the problem, when it happens and what they do today. Then separate what you know from what you are guessing. Pick one assumption that would change your decision if it turned out to be wrong.

2. Talk to people who experience it

Ask about a recent situation instead of pitching your solution. Try questions such as: “When did this last happen?”, “What did you do?” and “What was difficult about that?” Listen for existing workarounds and for evidence that contradicts your idea.

3. Choose a small experiment

Depending on your question, you might demonstrate a prototype, offer a manual service or invite a suitable person to try a workflow. Say clearly what exists today. Define the action you hope to observe and what you will do if the result is different.

4. Compare signals honestly

Interest, a completed test, returning to use a product and paying for it are different signals. Each answers a different question. Record what happened, who participated and what remains unknown; do not turn a positive reaction into a claim that the market is proven.

Example: test a shift-swapping idea

A public TinIdeas profile proposes a way for healthcare workers to coordinate shift swaps. This is an idea published on TinIdeas, the site hosting this guide. Its description is a starting hypothesis, not evidence that the product exists, that the problem is widespread or that the proposed solution improves staffing.

One assumption to test is whether arranging a swap is difficult enough for staff or managers to change their current process. Ask a few people who actually arrange or approve swaps to describe a recent example: what happened, who needed to approve it, and where, if anywhere, did it get stuck? Avoid asking them to share identifiable patient or colleague information.

Before building software, agree on a small test with willing participants, such as walking through a mock request. Record whether they can explain the next step and which approvals or existing tools the process depends on. A clear conversation is useful learning, but it does not establish that people will adopt or pay for a product.

Share what you are learning

A clear profile can help others understand the problem, the proposed solution and the contribution you are looking for. TinIdeas lets you describe an idea and a specific request; responses can help you find people to talk to or work with. They do not replace research with the people affected by the problem.

Create an idea profile Browse ideas

If an idea is approved, the original submission can be publicly accessible. Do not submit confidential information. Privacy details.

Ready to ask for help? Read how to find collaborators for an idea.

Preparing a conversation? Use these customer discovery interview questions.

Want to discuss an early concept? See how to share an idea before building and choose a specific feedback question.

Need to explain your idea first? Use the app idea description template.