How to Validate a Side Project Before You Build It
Most side projects fail before they launch. Not because the code was bad, but because nobody wanted the thing in the first place. If you have spent a weekend building something only to get zero sign-ups, you already know this pain.
Validation is the step that separates projects that earn from projects that sit in a GitHub repo gathering dust. Here is a practical process you can run in under two weeks.
Start With a Specific Problem, Not a Feature Idea
Developers tend to start with a solution. "I want to build a tool that does X." That instinct gets you into trouble fast.
Start with a problem instead. A good problem statement names a specific person, a specific frustration, and a measurable cost. "Freelance designers spend two hours each week chasing late invoice payments" is a problem. "Invoicing is annoying" is not.
Write yours in that format. If you cannot, you do not understand the problem well enough yet.
Find 10 People Who Have This Problem Right Now
Before you write code, talk to people. Ten is enough to see a pattern.
Where to find them:
- Reddit communities in your target niche (search "I hate" or "why is it so hard to" in relevant subreddits)
- Twitter/X searches for complaints about the exact workflow you want to fix
- Facebook Groups for your target profession
- Slack communities for indie developers or solopreneurs
Send a short message. Do not pitch a product. Ask about their workflow. "Hey, I'm researching how freelancers handle invoice follow-ups - do you have 15 minutes to talk?" works fine.
In the conversation, ask what they currently use to solve the problem, how much time or money it costs them, and what they have already tried. You are listening for the same frustrations repeated across multiple people. Three people saying the exact same thing is a real signal.
Check Whether People Are Already Paying for a Solution
Existing competition is good news. It means the market exists. A space with no products usually means no demand, not an untapped opportunity.
Search for existing tools or products solving the same problem. Look at their pricing pages. Check their reviews on Product Hunt, Capterra, or the App Store. Negative reviews are a map of what people still want that they are not getting.
If a competitor charges $29/month and has 500+ reviews complaining about a missing feature, that gap is your starting point.
Build a Fake Door Before a Real Product
A "fake door" test is a landing page that describes a product and has a call to action - usually an email sign-up or a payment button - without the product existing yet.
Set it up with a tool like Carrd, Webflow, or even a plain HTML page. Write one clear headline that names the problem and the outcome. Add three bullet points of what the product does. Put up a button that says "Get Early Access" or "Join the Waitlist."
Drive traffic to it. Post in the communities you found earlier. Run a $20 Facebook or Reddit ad. Share it with the people you interviewed.
Measure two numbers: the percentage of visitors who click the CTA, and the percentage who give you their email or pay. An email conversion rate above 20% from cold traffic is a strong signal. Getting even one payment from a stranger - before the product exists - is proof.
Set a Time Limit on the Validation Phase
Validation should take 10 to 14 days. If you are still "gathering data" after three weeks, you are procrastinating.
Set a clear go/no-go rule before you start. Something like: "If I get 50 email sign-ups or 3 pre-orders in 14 days, I build it." If you do not hit that number, you either pivot the positioning, try a different audience, or move on to a different idea.
The number is not magic. What matters is that you decide in advance so you are not rationalizing after the fact.
Price Before You Build
Most people plan to "figure out pricing later." That is a mistake. Pricing shapes what you build.
If your target is $500/month from this project, work backwards. At $9/month that is 56 customers. At $49/month that is 11. Those are very different products requiring very different amounts of support, marketing, and features.
Pick a price before you build anything. Include it on your landing page. It filters out non-buyers early and tells you whether your market can actually support your revenue goal.
Use a Structured Checklist
The process above works, but it is easy to skip steps when you are excited about an idea. A structured checklist keeps you honest. It forces you to answer questions like: Is there evidence of existing spend? Have you talked to real potential buyers? Do you have a go/no-go threshold set?
If you want a ready-made resource that bundles these validation questions with pricing models and real case studies from creators hitting $500+/month, the [Side Project Revenue Playbook](https://stackd