Why Test Your Concept?
You have an idea. Maybe a good idea. But is it an idea that someone actually wants and is willing to pay for?
Most startups fail because they build something nobody wants. They spend 6-12 months and €10,000+ developing a product, only to discover the market doesn’t exist. The most common mistake is building first, then showing customers. By then you’ve already invested enormous time and money.
The goal of concept testing is simple: learn quickly and cheaply. Test your idea BEFORE you build everything. Invest weeks instead of months. Spend €100 instead of €10,000. Get real feedback from real customers through what they actually DO, not what they say. Do they pay? Do they sign up? Do they use it?
The Testing Cycle
Every startup follows the same process. Start with your concept, your idea. Make it real by building something testable, not perfect. Test with real people, not friends and family. Measure interest through actions, not words. Learn from the feedback and iterate. Then repeat this cycle.
You’ll go through this 3-10 times before finding what’s right. This is completely normal. Each iteration gets you closer to what customers actually want. Version 1 is rarely right. Version 3-5 is usually where product-market fit happens.
Test with Real People
Once you’ve built something testable, test with real customers. Not friends who’ll lie to protect your feelings. Not Facebook surveys where people say one thing but do another. Find people who have the problem you’re solving, who are actively looking for a solution, and who have budget to pay. Look in online communities, at events, through direct contact, or in your existing network.
You need 5-8 people for initial feedback. After 5 interviews you’ll see patterns forming. For beta testing you need 10-30 people to get reliable data.
The most important thing is to see what people DO, not what they say. For digital products, let them use your prototype and say nothing while they test. Just observe where they get stuck and what confuses them. For hardware, give them the product and watch how they interact with it. Do they understand how it works without you explaining? People often say something is easy but their actions show confusion.
Ask the right questions. Don’t ask if they think it’s a good idea because they’ll say yes. Don’t ask if they would buy it because they’ll say yes but never actually buy. Instead ask them to tell you about the last time they had this problem. Ask how they solve it today and what their current solution costs in time and money. Ask what they would do if this existed tomorrow. These questions reveal real behavior, not polite responses.
Measure concrete things. For landing pages, track how many visitors sign up with their email. For prototypes, track if people can complete the main task without help. For actual products, track if people use it daily and come back after a week. The strongest signal is always payment. If people won’t pay even a small amount, they’re not serious about wanting your product.
What Shows Real Interest?
Learn to tell the difference between polite interest and real commitment. When someone says “this is a cool idea” but does nothing, that’s not interest. When they say “sounds interesting” without asking concrete questions, that means nothing. When they say “I might buy it” or “let me know when it’s ready”, they’re being polite, not committed.
Real interest looks different. The strongest signal is people paying money for a deposit, pre-order, or early access. If they won’t pay, they’re not serious. Real interest shows up in concrete questions like “when can I get this” and “how much does it cost”. It shows when people want it NOW and ask how to get beta access or be first in line. For digital products, real interest means daily usage and coming back week after week. For services, it means booking immediately and paying full price without demanding discounts.
Remember that quality matters more than quantity. Ten people who really want your product and will pay for it are worth more than a hundred people who say maybe.
Learn and Iterate
After testing, look at all the feedback you got. Some feedback is critical and must be fixed immediately like bugs that prevent people from using the product or parts that break. Some feedback is important but not urgent like features that would make the product better but aren’t necessary for it to work. Some feedback is just nice ideas that would be cool but don’t really matter. And some feedback is noise from one person when everyone else disagrees, or extreme use cases that almost nobody will ever need.
Look for patterns in what people tell you. If three or more people say the same thing, pay attention. If the same problem comes up multiple times, that’s something you need to fix. Strong reactions whether positive or negative usually mean something important. But one person’s opinion when nobody else mentions it might just be an outlier.
Prioritize what to work on next. Fix things that have high impact and are easy to change right away. Plan carefully for things that have high impact but are difficult or expensive to change. Do small improvements when you have time. Skip things that don’t matter much and would take a lot of effort.
For digital products, each testing cycle takes about 1-2 weeks and you’ll typically need 3-10 iterations before you find product-market fit. For hardware, each cycle takes 4-6 weeks because production takes time, and you’ll need 2-5 iterations because each prototype costs money. For services, cycles are 1-2 weeks and you’ll need 3-7 iterations to get it right.
Know when to make small adjustments versus big changes. Iterate when people like your concept but want small improvements, when your product works but could be better, and when you get concrete actionable feedback. Make bigger pivots when nobody is willing to pay, when people don’t understand what your product does, or when less than 10% of people show interest even after several rounds of improvements. Small iterations are things like changing your pricing or adding a filter feature. Big pivots are things like changing from selling to consumers to selling to businesses, or completely changing what problem you’re solving.
What’s Next
In the following sections you’ll learn exactly how to make your idea real for testing. For digital products and services, we’ll cover landing pages, clickable prototypes, no-code MVPs, and concierge MVPs. For hardware products, we’ll cover low fidelity prototypes, 3D prints, and working prototypes. Then you’ll learn how to plan your specific tests with the right timeline, budget, and success criteria. Finally you’ll prepare to present your testing plan in the workshop and get feedback from others.
The startups that succeed are the ones that test fast, learn quickly, and iterate based on real customer feedback. Not the ones with the best initial idea, but the ones who find product-market fit through systematic testing. Let’s start testing your idea.