How to Validate a Startup Idea Before Writing a Line of Code

The most expensive mistake in early-stage startups is building something nobody wants. Validation is the discipline of finding out whether people want your thing before you spend six months building it. Here is a practical sequence that works.

1. Articulate the problem, not the solution

Most founders fall in love with their solution. The first step is to write one sentence describing the problem your target customer has — without mentioning your product. If you cannot do this clearly, you do not understand the problem well enough yet.

A useful test: could you post this problem sentence in a relevant Hacker News thread or Reddit community and have people immediately say "yes, I have this exact problem"? If it lands flat, the problem may be too niche or too abstract.

2. Check if the market already has a signal

Before talking to anyone, do desk research. Search Hacker News for your problem area. Look for Ask HN threads, Show HN posts, and comments that reference the pain you are targeting. If nobody has discussed it in 15 years of HN archives, ask yourself why. Either the problem is too niche to have reached HN, or it does not really exist.

Tools like IdeaCheck automate this search — they run semantic similarity over 28,000+ HN discussions and surface the most relevant ones in seconds. Use it as a quick pre-filter before committing time to interviews.

3. Talk to 10 potential customers before writing any code

Ten conversations is enough to spot patterns. The goal is not to pitch — it is to listen. Ask about the last time they experienced the problem. Ask what they did about it. Ask what it cost them (time, money, stress). If they already have a workaround, that is a positive signal: the problem is real enough that they built something.

Red flags in customer interviews: polite interest without any evidence of the problem in their actual workflow; "I would definitely use that" without any indication they currently do something to solve the problem; difficulty explaining who the buyer is.

4. Run a smoke test

A smoke test is a landing page that describes your product and asks for an email signup or a pre-order. You spend zero time on the product itself. You drive traffic via Google Ads, Reddit, or a relevant community, and measure conversion rate.

A 2–5% conversion on cold traffic is a reasonable signal. A 0.1% conversion means either the copy is wrong or the market is not there. Smoke tests are not perfect — email signups are cheap commitments — but they are much cheaper than building.

5. Map the competitive landscape honestly

If there are competitors, that is good — it confirms the market exists. The question is whether you have a credible reason to believe you can win a segment of it. "We will do it better" is not a strategy. "We will win the [specific segment] because [structural advantage]" is.

If there are no competitors, be suspicious. Either you have found a genuine gap, or the market tried and failed — and the failure post-mortems are sitting in HN threads waiting to be read.

The sequence

1. Write the problem sentence.
2. Run a community signal check (HN search or IdeaCheck).
3. Do 10 customer interviews.
4. Run a smoke test with a landing page.
5. Map competitors and define your wedge.
6. Only then, write code.

This sequence takes two to four weeks. It will save you six months of building the wrong thing.