← All posts

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

L
LaunchHQ Team
·April 2, 2026·8 min read

The default startup failure mode isn't running out of money. It's building something nobody wants.

You spend six months building, launch with confidence, and discover the market doesn't care. This happens not because founders are bad — it happens because building felt like validation. The act of making the thing convinced them the thing was worth making.

Validation means finding out whether your riskiest assumption is true before you act on it. It sounds obvious. It almost never happens.

Start with your riskiest assumption

Every startup idea is a stack of assumptions. Some are almost certainly true. Others would sink the whole thing if they were wrong.

The job is to identify which assumption is riskiest — most uncertain and most load-bearing — and test that one first.

For most early-stage ideas, the riskiest assumption is: do people actually want this? Not "do people say they want it" — but will they change their behavior to get it?

Other common riskiest assumptions:

  • "People will pay for this" (not just use it if it's free)
  • "This specific group of people has this specific problem" (not just people, generally)
  • "We can acquire customers for less than they're worth" (unit economics)

Write your assumption in one sentence: "I believe [specific group] will [specific behavior change] to solve [specific problem]."

If you can't write it in one sentence, the idea isn't specific enough yet. Work on that first.

The one-sentence pitch test

Before you build anything — even a landing page — run this test.

Write a one-sentence pitch: "It's [product category] for [specific audience] who want [specific outcome]."

Then message 10 people who fit the target audience. Not friends. Not people who will be nice to you. Find actual strangers or loose acquaintances who match your customer profile on LinkedIn, Twitter, or in communities.

Send something like: "Hey, I'm exploring a problem — [describe it]. Is this something you've run into? Would a 10-minute call to talk about it be worth your time?"

If you get 5 of 10 to respond with genuine interest, you're onto something. If you get 0 responses or everyone says "not really my problem," reconsider before going further.

This is uncomfortable. Do it anyway. The discomfort is the point — it forces you to engage with the market, not your own assumptions.

Set up a waitlist page to measure real interest

There's a huge gap between people saying "I'd use that" and people taking action. A waitlist page sits in the middle.

When someone signs up for a waitlist, they're doing something real. They're handing over their email — something with personal value — based on a promise you haven't delivered. That's a genuine signal.

Write a specific headline. Something that makes a specific person think "yes, that's exactly my problem." If you can make someone feel seen in one sentence, you're ahead of 90% of landing pages.

Keep the description short and problem-first. What's the problem, and what's the outcome? Save the feature list for when you have features.

Use a tool that gets you live in minutes. LaunchHQ and Carrd both work. Don't spend more than a few hours on this. Getting the page live today is more valuable than getting it perfect next week.

Set a launch expectation. "Launching Q3 2026" or "Beta access this summer." This gives people a reason to sign up now rather than bookmarking and forgetting.

The target: 30–50 genuine signups from people who aren't your friends or family. That's a meaningful signal. If you can't reach 30 in 3–4 weeks of active promotion, that's information — the problem might not be painful enough, or the messaging isn't connecting.

Where to share your waitlist

This is where most founders underinvest. They post once on Twitter, share with their network, and wait. Result: 12 signups, all from people who know them personally and want to be supportive.

Communities where your target customer actually is:

  • For B2C products: find the specific subreddits for the problem you're solving — not r/startups, but r/[your-niche]
  • For B2B products: LinkedIn groups and industry Slack communities in your vertical
  • Indie Hackers if you're building tools for founders or developers

When posting in communities, lead with the problem, not the product. "I'm solving X problem in Y industry. Looking for 10 people who've experienced this to give feedback" gets real responses. A raw link to your waitlist page does not.

Direct outreach to 50 ideal customers. Find people who match your target customer profile and message them personally. Ask about the problem, not your solution. This feels slow and doesn't scale — do it anyway. The conversations are irreplaceable.

Your own network — but track it separately. Post on your personal social media, tell friends. But note which signups come from this vs. organic channels. You want to know how many strangers found you, because those are the signups that prove real demand.

How to interpret your results

You ran the waitlist for 3–4 weeks. Here's how to read what happened:

30–50+ signups from strangers: Strong signal. The problem resonates and your messaging is working. Start building while continuing to talk to early signups.

10–30 signups: Weak signal. The problem might be real but either the messaging isn't connecting or you haven't promoted enough. Talk to everyone who signed up and find out what made them do it.

Under 10 signups after real promotion: Pause before building. Either the problem isn't painful enough to motivate action, you're talking to the wrong audience, or the promise isn't compelling. This is valuable — you've saved yourself months of building the wrong thing.

Page conversion rate below 10%: Traffic is reaching the page but not signing up. The issue is the copy, not the audience. Test a different headline — make it more specific.

Page conversion rate above 30%: Something is working. Push more traffic and track which channel it's coming from so you can double down.

Talk to your first signups

An email address is the start of validation, not the end. The real insight comes from conversations.

Email your first 20 signups personally — not a newsletter, an actual email from you to them:

"Hey [name], thanks for signing up. I'm the founder. Quick question — what made you sign up today? And what problem are you hoping we solve for you?"

Aim to get on a 20-minute video call with at least 5 of them. Listen more than you talk. Don't pitch. Ask about their current situation, how they handle the problem today, what they've tried, and what they'd need to actually change their behavior.

You're looking for two things: whether they have the problem in the way you think they have it, and whether they would pay to solve it.

If 3 of 5 people describe the exact problem you're solving in their own words — without you prompting it — you have a real problem worth solving. If they describe a slightly different problem or solve it in a way you hadn't considered, you've learned something more valuable than months of building would have taught you.

When to move on

Give your idea a genuine 3–4 week shot. If after real effort you can't get 20 signups from strangers, or you can't find anyone who describes the problem you're solving in the way you're describing it — move on. Not defeated, but informed.

The goal isn't to find ideas that "could work." It's to find ideas where the evidence is so compelling it would be strange not to build. The bar for continuing should be high.


The startup graveyard is full of products that were well-built but poorly validated. The hardest part of validation isn't the tactics — it's accepting that a "no" signal is information, not failure. The earlier you get that signal, the less it costs you. That's the whole point.

Ready to build your waitlist?

Get your page live in minutes. Free plan, no credit card required.

Get started for free

Next →

Best Waitlist Page Builders in 2026 (Honest Comparison)