The startup graveyard is full of beautifully-coded products that solved imaginary problems. Pixel-perfect UIs, clean architecture, 95% test coverage. And zero customers.

The founders behind those products were not lazy. They were not stupid. They were builders who confused building with progress. They assumed that if they could make the thing work, people would want it. That assumption killed them.

Validation is the process of killing that assumption before it kills your company. Before you write a single line of code, you need evidence that strangers will pay money to solve the problem you're targeting. Not your friends. Not your co-founder's mom. Strangers with credit cards.

This guide walks you through exactly how to do that, what it costs, and how long it should take.

What does "validation" actually mean for a startup?

Validation is not a survey. It is not asking ten friends if they think your idea is good. It is not a Twitter poll. It is not a pitch deck that investors said "looks interesting."

Validation means finding evidence that strangers will pay money to solve a specific problem. That's it. Everything else is noise dressed up as progress.

The bar for validation: Can you get 3-5 people to pre-pay, sign a letter of intent, or commit meaningful time before you build anything?

Notice the word "meaningful." Someone saying "yeah, I'd probably use that" over coffee is not meaningful. Someone giving you their credit card number, signing an LOI, or spending an hour walking you through their current broken workflow — that is meaningful. The difference is skin in the game.

Here's why this matters: building a product takes 3-6 months minimum. If you skip validation, you're betting half a year of your life on the assumption that your problem is real, your solution is right, and people will pay for it. Three separate bets, stacked on top of each other, with no evidence for any of them.

Validation lets you test all three before you invest the time. It's not a guarantee. But it's the difference between educated risk and roulette.

How do you test demand without building anything?

You don't need a product to test demand. You need an offer. There are four proven ways to do this, and none of them require writing code.

The landing page test

Put up a single page that describes the problem you solve and the outcome your product delivers. Not features. Outcomes. "Stop losing 5 hours a week to manual invoice reconciliation" beats "AI-powered invoice matching with REST API."

Add an email signup form or a "Join the waitlist" button. Run $50 worth of Google Ads or Reddit Ads targeting people who search for the problem. Measure how many people land on the page versus how many sign up.

A 5-10% signup rate from cold ad traffic means there is real interest. Below 3% means either the problem is not painful enough or your positioning is off. Above 15% means you're onto something worth building fast.

This entire test costs under $80 and takes 3 days to set up.

The waitlist approach

Similar to the landing page test, but with a twist: instead of just collecting emails, tell people their position in line and give them a way to move up by sharing. Tools like Viral Loops or a simple referral script can turn your waitlist into a growth channel.

The metric that matters: organic shares. If people share your waitlist without being asked, you have struck a nerve. If nobody shares even when you offer to move them up, the problem is not urgent enough for people to stake their reputation on recommending you.

The concierge MVP

Deliver the value of your product manually to 5 people. If you're building an automated report tool, create the first 5 reports by hand. If you're building a matching marketplace, make the first 5 matches yourself via email. If you're building a data pipeline tool, clean the first 5 datasets in a spreadsheet.

This is the most underrated validation method because it gives you two things at once: proof of demand and deep insight into the problem. When you deliver the value by hand, you see exactly what customers struggle with, where they get confused, and what they actually care about versus what you assumed they would care about.

Charge for this. Even a small amount. $50, $100, whatever feels reasonable for the manual work. The point is not to make money. The point is to test whether people will actually pull out their wallet. Charging is the ultimate filter.

The pre-sell

Charge for access to the product before it exists. This is more aggressive than a waitlist and far more informative.

Specific ways to do it:

If 10-20 people pre-pay for something that doesn't exist yet, you have about as strong a validation signal as you can get without an actual product. If nobody pre-pays, you just saved yourself months of building the wrong thing.

Where do you find people who already have this problem?

The biggest validation mistake is testing demand in a vacuum. You post your landing page on your personal Twitter (200 followers, mostly friends), get 6 signups, and declare the idea validated. That's not validation. That's your friends being polite.

You need to find strangers who are already experiencing the problem. They exist. They are talking about it right now. You just need to know where to look.

Reddit

Search Reddit for your problem keywords combined with emotional language: "[problem] + frustrated," "[problem] + hate," "[problem] + looking for," "[problem] + alternative to." These queries surface real people describing real pain in their own words.

The subreddits r/SaaS, r/startups, r/smallbusiness, r/Entrepreneur, and niche industry subs are goldmines. Don't pitch. Read. Understand how they describe the problem. The language they use becomes your landing page copy.

Twitter/X

Search for complaints about existing solutions. "[Competitor] sucks," "looking for alternative to [tool]," "anyone know a good [category]?" These are people in active buying mode, broadcasting their intent publicly.

G2 and Capterra reviews

Filter competitor reviews by 1-2 stars. Read every one. These people paid for a solution, used it, were disappointed, and took the time to write about it. That level of frustration is a validation signal in itself. Their complaints tell you exactly what to build differently.

Job postings

Search job boards for postings that describe the problem you solve. "We need someone to manually reconcile invoices" means there's a company paying $60K-$80K per year for a human to do what your product could automate. That's your total addressable budget per customer.

Job postings that say "experience with [competitor] required" tell you which companies are using the tools you want to replace.

Competitor analysis

Understanding what already exists in your space is not optional. If there are zero competitors, that's usually a red flag, not an opportunity. It means either nobody wants this or someone tried and failed. PostBuild's competitor finder maps the landscape for you: who the players are, how they position, where the gaps exist.

What are the strongest validation signals?

Not all validation signals are created equal. Here's how to rank them, from strongest to weakest:

Tier 1: Money

Tier 2: Time

Tier 3: Words

Money beats time. Time beats words. If all you have is words, you don't have validation. You have encouragement. Those are not the same thing.

The hierarchy exists because each level requires increasing levels of commitment. Anyone can say "great idea." Fewer people will spend an hour on a call. Even fewer will hand over money. Each step up the ladder reduces the chance you are being polite-d to death.

What are common false positives that trick founders?

False positives are validation signals that feel real but aren't. They are the most dangerous part of the validation process because they give you confidence to build something nobody actually wants.

Friends and family saying "that's a great idea." They love you. They want you to succeed. They would tell you a restaurant that serves gravel on toast is a great idea if you were excited about it. Their opinion is worthless for validation. Not because they are bad people. Because their incentives are wrong.

Lots of social media engagement on your announcement. Likes, retweets, and "this is amazing" replies are social currency, not purchase intent. People engage with announcements because it feels good to be supportive. The same people who liked your tweet will not remember your product exists in 72 hours.

Investors saying "interesting" or "keep us posted." This is investor-speak for "no." If an investor is genuinely interested, they ask follow-up questions, introduce you to potential customers, or write a check. "Interesting" means they are being polite while they wait for you to leave the room.

Survey respondents saying they'd pay $50/month. Survey data on willingness to pay is almost always wildly inflated. In one well-known study, 80% of survey respondents said they would pay for a product. When the product launched, 3% actually did. Hypothetical money is not real money. The only reliable way to test willingness to pay is to actually ask for payment.

Being able to build it. Technical feasibility is not market validation. "I can build this" is about your capabilities. "People will pay for this" is about their needs. The two overlap less often than engineers think. The world is full of technically impressive products that solved problems nobody had.

How long should validation take?

Two to four weeks. Maximum. If you cannot find signal in a month, one of two things is true: the problem is not urgent enough to sustain a business, or you are looking in the wrong place.

Here is why a time constraint matters: validation without a deadline becomes research. Research feels productive. You read articles, you analyze competitors, you build spreadsheets of market data. But you never actually talk to a customer or ask for money. The deadline forces you to take action.

The $100 validation budget

You do not need thousands of dollars to validate an idea. Here is the breakdown:

With 300 clicks at a 5% conversion rate, you have 15 email signups. Reach out to all 15 personally. Ask if they would pay for what you described. Offer the concierge version. You will have your answer within a week.

Don't build during validation

This is the hardest discipline for technical founders. You get excited. You start sketching the database schema. You think "I'll just build a quick prototype while I wait for the ad data." No. Stop.

Building during validation defeats the purpose. The entire point is to test whether the idea is worth building before you invest time in code. If you build while you validate, you have already committed emotionally and financially. You will interpret ambiguous signals as positive because you need them to be positive. You have skin in the game in the wrong direction.

Keep the code editor closed for four weeks. If validation succeeds, you will build faster and with more confidence because you actually understand the customer. If it fails, you just saved yourself months.

The validation stack — what to use

You don't need ten tools. You need five, and most of them are free.

That's the stack. Landing page, traffic, payment, tracking, and competitive intelligence. Total cost: under $100. Total setup time: one weekend.

The founders who succeed are not the ones with the best ideas. They are the ones who kill bad ideas fast and double down on the ones that show signal. Validation is how you tell the difference.

Here is your action plan for this week: pick one validation method from this guide. The landing page test is the easiest starting point. Buy the domain today, build the page tomorrow, run $50 in ads by Wednesday, and have your first data by Friday. By next week you will know more about your market than most founders learn in three months of building.

If nobody signs up, that's not failure. That is the most valuable data you could have gotten. It means the idea — or the angle — needs to change. Adjust the positioning, change the target audience, or try a different problem entirely. Then test again.

The only real failure is building for six months and then discovering what a $50 ad test would have told you on day three.