How to Validate a Business Idea Before You Build It

Table of contents

Open Table of contents

• Why most validation efforts fail
• Step 1: Confirm the problem actually exists at scale
• Step 2: Audit competitors — proof that money already exists
• Step 3: Build the smallest possible smoke test
• Step 4: Get a commitment before you build
• Step 5: Set a pass/fail threshold before you start
• Common validation mistakes
• What signals mean “go”
• The validation stack
• The operator’s bottom line

Why most validation efforts fail

The obvious failure mode is no validation at all — build first, ask questions later. But the subtler trap is validation theater: running surveys, talking to friends, collecting vague “great idea!” responses, and calling that signal.

Surveys lie. People are polite. Asked “would you pay $50 for this?” in a hypothetical context, the answer is almost always yes. The only signal that matters is commitment: someone actually giving you money, time, or a written letter of intent.

Everything else is noise reduction, not validation.

Step 1: Confirm the problem actually exists at scale

Before you validate your solution, validate that the problem is real and searched-for.

Search demand is the fastest proxy. Type your problem into Google. Look at the autocomplete suggestions, the “People also ask” section, and the top-ranking pages. If there are no results, no one is searching — and a business that solves a problem no one looks for will spend all its energy on education instead of conversion.

Use a keyword tool like Semrush to check actual monthly search volume. A problem with 1,000–10,000 monthly searches in your target market is viable. A problem with 20 searches per month is a niche product with a distribution problem.

Forum evidence is a qualitative layer on top. Search Reddit, Quora, niche Facebook groups, and Discord communities for your problem. Are people actively complaining about it? Asking for solutions? Workarounds? Real frustration is gold — it means the pain is strong enough to motivate people to seek help publicly.

If you can’t find 20 forum threads from real people describing the problem, be skeptical.

Step 2: Audit competitors — proof that money already exists

A common founder instinct: “there’s no competition, so I’ll own the market.”

This is almost always wrong. No competition usually means no market. Competition is proof that customers exist and will pay.

Search Google for your solution category. Who’s ranking? What do their landing pages promise? What do they charge? Read their testimonials and reviews — especially the negative ones. Negative reviews are a product roadmap: they show you exactly what the market wants but isn’t getting.

If you find 3–5 established competitors with real products and real customers, that’s a healthy sign. If you find zero, dig harder before concluding the market doesn’t exist — or treat it as a red flag.

Key questions to answer:

1. Who are the top 3–5 players?
2. What do they charge?
3. What are reviewers criticizing?
4. Is there a positioning gap I can own?

Step 3: Build the smallest possible smoke test

Once you know the problem exists and money is in the market, build the minimum artifact needed to test whether your version gets traction.

This is not a full product. It’s a signal-capture mechanism.

Option A: Landing page with email capture. A one-page site describing the problem and solution, with a “Join the waitlist” or “Get early access” CTA. The conversion rate tells you whether your positioning resonates. Tools like Webflow, Carrd, or even a Notion public page work fine — don’t over-engineer it.

Option B: Pre-sale. An actual checkout flow with real money. This is the highest-quality signal. If someone hands you cash for something that doesn’t exist yet, they believe in the solution. Even a refundable deposit works.

Option C: Concierge MVP. Do the thing manually before automating it. Consulting instead of a SaaS. A custom spreadsheet instead of a software tool. A manually curated newsletter instead of an AI-generated one. You serve a handful of customers with brute force, learn exactly what they value, then build the product around that.

Step 4: Get a commitment before you build

This is the gate that separates real validation from wishful thinking.

Define what “commitment” means for your idea before you run the smoke test:

• SaaS / software: A pre-sale at a discounted price, or a signed letter of intent
• Content / media: Email subscribers who clicked to join (not just followers)
• Services / consulting: A paid discovery call or a signed proposal
• Physical product: A deposit or a Kickstarter/pre-order

If you can’t get at least one person to commit — even at a discount, even with a money-back guarantee — the idea isn’t ready. That’s not failure; that’s the system working. It saved you months of build time.

Step 5: Set a pass/fail threshold before you start

The trap is this: you run your smoke test, get lukewarm results, and talk yourself into proceeding anyway. “The landing page copy wasn’t great.” “I didn’t promote it enough.” “It just needs more time.”

Stop. Before you run the test, write down the threshold:

“If I get 50 waitlist signups in 14 days with $0 in paid ads, I build. If I don’t hit 50, I don’t build — I either pivot the positioning or kill the idea.”

Write it down. Tell a friend. Make it public if you can. Then honor it.

The number is arbitrary; what matters is that you decide in advance and don’t move the goalposts when the data comes in cold.

Common validation mistakes

1. Asking people if they’d buy it. They almost always say yes to be polite. The only question that counts is: “Will you buy it now?”
2. Validating with friends and family. They’re rooting for you. They’re not your customer.
3. Solving your own problem without checking if others have it. Your problem might be unique to you. Check the forums.
4. Calling survey responses validation. A survey can generate ideas. It can’t validate demand. Only money or genuine commitment can.
5. Waiting for perfect information. Validation is about getting enough signal to take the next step, not eliminating uncertainty entirely.

What signals mean “go”

You’re looking for a combination of:

1. Search volume above 1,000 monthly searches for the core problem keyword
2. Competitor activity — 3+ real players charging real money
3. At least 20 forum or community threads showing active frustration with the problem
4. A smoke test conversion rate above 5% on targeted traffic
5. At least one person commits — pays, signs, or deposits — without you having to beg

Hit all five and you have a viable direction. Hit two or three and you have a signal worth refining. Hit zero and you need a fundamentally different idea or audience.

The validation stack

The tools I use and recommend for this process:

• Search demand: Semrush — keyword volume, competitor analysis, and content gaps in one place
• Forum research: Reddit, Quora, niche Facebook Groups, Discord communities
• Landing page: Carrd (free, fast) or Webflow for more design control
• Email capture / waitlist: Kit (ConvertKit) to start building the list as you validate
• Payments: Stripe — link directly to a checkout before you build product
• Analytics: Google Analytics on your smoke test page to track real behavior

The operator’s bottom line

The most expensive thing you can build is a product nobody wants. Validation isn’t about eliminating risk — it’s about failing fast on paper instead of failing slow in production. Run the smoke test, get a commitment, set the threshold before you start, and honor the result. If the signal is there, you’ll know. If it isn’t, you’ll know that too.

---

Related: How to Build a Profitable Business · Growth Marketing Strategies Guide · How to Become an Entrepreneur