Most founders start with a solution. They have an idea, they see a gap, they feel the spark. So they open a code editor. They pick a stack. They register a domain. Three months later they have a product and zero users.
The problem is not the idea. The problem is the order. You cannot validate a solution until you validate the problem. Building first is expensive procrastination. It feels like progress because you are producing something. But you are producing answers to a question no one asked.
Validation is cheap. Building is expensive. Do the cheap thing first.
You do not need a landing page, a waitlist, or a prototype. You need conversations, observations, and one simple test. Here is the plan.
Start with the problem, not the persona. "Freelance designers" is a persona. "Freelance designers who lose 4 hours a week chasing late invoices" is a pain. The pain is what people pay to make go away. The persona is just a label.
Write down the exact problem your idea solves. Make it specific enough that someone could say "yes, that happens to me every Tuesday." If your problem statement is vague, your solution will be too.
Talk to five people who have the problem. Not friends. Not your mom. People who would actually buy what you are thinking of building. Find them on Reddit, LinkedIn, Twitter, or in niche Slack groups. Send a short, direct message: "I am researching how people handle X. Would you trade 15 minutes for my notes?"
In each conversation, ask three questions and say almost nothing else:
- "Tell me about the last time this happened." You want a story, not an opinion. Stories have details. Opinions are free and usually wrong.
- "What did you try to fix it?" If they have not spent money or time trying to solve this, the problem is not painful enough. People endure minor inconveniences. They only pay for major ones.
- "What would your ideal solution look like?" Do not pitch your idea. Let them describe their dream fix. If it matches what you were planning to build, you have alignment. If it does not, you have a cheaper lesson than building the wrong thing.
After five conversations, patterns emerge. The same words come up. The same workaround gets mentioned. That pattern is your validation signal. If every conversation is different, you have not found a focused problem yet. Keep talking.
Before you build, prove people will act. The smoke test is a promise, not a product. Create a one-page description of what you plan to build. Include the problem, the solution, and a clear call to action. That action might be an email signup, a pre-order, or a booking for a demo.
Share it where your target users already gather. Do not post it to your personal Twitter unless your followers match your market. Go to the communities where the problem lives. Post once, answer questions, and track what happens.
- 10+ signups in 48 hours means there is real interest. The problem is alive.
- 2 or 3 signups means your messaging is off or the problem is weaker than you thought. Rewrite the page and try again.
- Zero signups means you are solving a problem no one feels urgently. Pivot the problem, not the solution.
The smoke test costs nothing but a few hours. It tells you more than a month of building in isolation.
If you want stronger signal, add a fake door. This is a button or link that promises a feature you have not built yet. "Click here to generate your report." When someone clicks, show a message: "This feature is coming soon. Leave your email and we will notify you when it is live."
Track the click-through rate. If 20% or more of visitors click the fake door, you have strong demand for that specific feature. If 2% click, the feature is not the draw you thought it was. The fake door is a lie, but it is an honest lie. It tells you the truth about demand before you invest in the build.
A founder I know spent 6 months building a tool for podcasters to auto-generate show notes. He had a beautiful landing page, a slick demo video, and 200 email signups. On launch day, 3 people used it. Two of them were his co-founders.
His mistake: he validated interest, not behavior. Email signups are cheap. Using the product is expensive. A signup means "this sounds neat." Usage means "this solves my problem." He confused the two.
The fix: run a concierge test. Do the work manually for one customer before you automate it. For his podcast tool, that meant writing show notes by hand for three episodes and charging for it. If people paid for the manual version, the automated version had a market. If they did not, he saved 6 months.
Do the unscalable thing first. It is the fastest way to learn if the scalable thing is worth building.
- Send five direct messages to people who have the problem you want to solve. Ask for 15 minutes. No pitch. Just listen.
- Write a one-page smoke test describing your idea and add one clear call to action. Share it in one community where your users already are.
- Pick one feature and run a fake door test. Add a button to your landing page or a simple post. Count clicks, not compliments.
Validation is not a phase. It is a habit. The founders who win are the ones who stay curious about the problem longer than they are excited about the solution. Bring your validation results to the 52Waypoint community. The feedback you get there will save you months.
Most founders start with a solution. They have an idea, they see a gap, they feel the spark. So they open a code editor. They pick a stack. They register a domain. Three months later they have a product and zero users.
The problem is not the idea. The problem is the order. You cannot validate a solution until you validate the problem. Building first is expensive procrastination. It feels like progress because you are producing something. But you are producing answers to a question no one asked.
Validation is cheap. Building is expensive. Do the cheap thing first.
You do not need a landing page, a waitlist, or a prototype. You need conversations, observations, and one simple test. Here is the plan.
Start with the problem, not the persona. "Freelance designers" is a persona. "Freelance designers who lose 4 hours a week chasing late invoices" is a pain. The pain is what people pay to make go away. The persona is just a label.
Write down the exact problem your idea solves. Make it specific enough that someone could say "yes, that happens to me every Tuesday." If your problem statement is vague, your solution will be too.
Talk to five people who have the problem. Not friends. Not your mom. People who would actually buy what you are thinking of building. Find them on Reddit, LinkedIn, Twitter, or in niche Slack groups. Send a short, direct message: "I am researching how people handle X. Would you trade 15 minutes for my notes?"
In each conversation, ask three questions and say almost nothing else:
- "Tell me about the last time this happened." You want a story, not an opinion. Stories have details. Opinions are free and usually wrong.
- "What did you try to fix it?" If they have not spent money or time trying to solve this, the problem is not painful enough. People endure minor inconveniences. They only pay for major ones.
- "What would your ideal solution look like?" Do not pitch your idea. Let them describe their dream fix. If it matches what you were planning to build, you have alignment. If it does not, you have a cheaper lesson than building the wrong thing.
After five conversations, patterns emerge. The same words come up. The same workaround gets mentioned. That pattern is your validation signal. If every conversation is different, you have not found a focused problem yet. Keep talking.
Before you build, prove people will act. The smoke test is a promise, not a product. Create a one-page description of what you plan to build. Include the problem, the solution, and a clear call to action. That action might be an email signup, a pre-order, or a booking for a demo.
Share it where your target users already gather. Do not post it to your personal Twitter unless your followers match your market. Go to the communities where the problem lives. Post once, answer questions, and track what happens.
- 10+ signups in 48 hours means there is real interest. The problem is alive.
- 2 or 3 signups means your messaging is off or the problem is weaker than you thought. Rewrite the page and try again.
- Zero signups means you are solving a problem no one feels urgently. Pivot the problem, not the solution.
The smoke test costs nothing but a few hours. It tells you more than a month of building in isolation.
If you want stronger signal, add a fake door. This is a button or link that promises a feature you have not built yet. "Click here to generate your report." When someone clicks, show a message: "This feature is coming soon. Leave your email and we will notify you when it is live."
Track the click-through rate. If 20% or more of visitors click the fake door, you have strong demand for that specific feature. If 2% click, the feature is not the draw you thought it was. The fake door is a lie, but it is an honest lie. It tells you the truth about demand before you invest in the build.
A founder I know spent 6 months building a tool for podcasters to auto-generate show notes. He had a beautiful landing page, a slick demo video, and 200 email signups. On launch day, 3 people used it. Two of them were his co-founders.
His mistake: he validated interest, not behavior. Email signups are cheap. Using the product is expensive. A signup means "this sounds neat." Usage means "this solves my problem." He confused the two.
The fix: run a concierge test. Do the work manually for one customer before you automate it. For his podcast tool, that meant writing show notes by hand for three episodes and charging for it. If people paid for the manual version, the automated version had a market. If they did not, he saved 6 months.
Do the unscalable thing first. It is the fastest way to learn if the scalable thing is worth building.
- Send five direct messages to people who have the problem you want to solve. Ask for 15 minutes. No pitch. Just listen.
- Write a one-page smoke test describing your idea and add one clear call to action. Share it in one community where your users already are.
- Pick one feature and run a fake door test. Add a button to your landing page or a simple post. Count clicks, not compliments.
Validation is not a phase. It is a habit. The founders who win are the ones who stay curious about the problem longer than they are excited about the solution. Bring your validation results to the 52Waypoint community. The feedback you get there will save you months.