The Fastest Way to Validate a Business Idea Before You Build It

My first digital product took three weeks to build. I wrote the guide, created the templates, designed a product mockup, wrote a product description, and set up the product page.

It made four sales in its first two months. All four were from people I personally knew.

The product wasn't bad. The topic just didn't have real demand — at least not the kind of demand that converts into sales from strangers. I hadn't validated anything before I built it. I just assumed people would want what I'd made.

I don't make that mistake anymore. Here's the exact process I use to validate business ideas before spending a single hour on the product itself.

Why Most Validation Advice Fails

Most validation advice tells you to "ask your audience if they'd buy this." That sounds logical, but it's deeply flawed.

People lie when they say they'd buy something. Not intentionally — they're just telling you what they think you want to hear, or what they believe they'd do in an ideal version of themselves. The gap between "I would buy that" and "I actually spent money on that" is enormous.

The only real validation is evidence that people are already trying to solve this problem — either by searching for it, buying similar things, or visibly struggling with it in public.

The Three Validation Signals I Look For

Signal 1: Search Volume

I use free tools — Google's autocomplete, Ubersuggest's free tier, or just the "People also ask" section in Google results — to see if people are actively searching for solutions to the problem my product would solve.

If I type the problem into Google and get back a list of autocomplete suggestions, dozens of related questions, and multiple results pages — demand exists. If I type the problem and Google gives me a half-empty results page and no autocomplete, I reconsider.

I'm not looking for massive volume. Even a few thousand monthly searches is enough for a niche digital product to gain traction through consistent SEO content.

Signal 2: Existing Purchases

The fastest way to confirm people pay for solutions in this space is to find existing products and look for reviews.

I search Etsy, Gumroad, and MadeThis for products related to my topic. If I find products with actual buyer reviews — not just products for sale — that's strong validation. Someone created something similar, people bought it, and people cared enough to leave feedback.

Reviews are the most honest market research available. They tell you exactly what buyers wanted, what they got, and what was missing. That information is gold when you're building something new.

Signal 3: Community Pain

I spend 20–30 minutes reading through relevant subreddits, Facebook groups, or Discord communities around the topic. I'm looking for posts where people describe frustration, ask for recommendations, or explain a problem they haven't been able to solve.

The ideal signal is a question that appears frequently. If I see the same question in three different posts across two different communities, that question is a product.

I take notes on exact language — the specific words people use to describe their problem. That language goes directly into my product title, description, and marketing copy later.

The 48-Hour Validation Test

When all three signals are pointing in the right direction, I sometimes do a quick 48-hour test before building.

I post in a relevant community — honestly, without being salesy — something like: "I'm thinking about creating [specific product] for [specific audience]. Does anyone here struggle with [specific problem]? Would something like this be useful to you?"

I look at two things: How many responses do I get? And are the responses specific enough to suggest genuine frustration (not just polite encouragement)?

If I get 10+ real responses where people describe their specific problem in detail, I proceed. If I get 2 polite thumbs-up responses, I reconsider.

The Pre-Sell Option

If you want the highest possible confidence before building, pre-sell the product before it exists.

Describe what you're building, name a price, and tell people they can buy now and receive it when it's complete. Put a simple landing page up — just a title, a brief description, and a "reserve your copy" button.

Pre-sales are the only true validation signal. If someone hands you money for something that doesn't exist yet, they really want it. Even five pre-sales completely changes the psychological math of building the product — you now have real customers waiting.

I use MadeThis.com to set this kind of thing up quickly. A basic product page can be live in an hour, and you can list the product at a pre-launch price with a note that delivery is coming.

What to Do When Validation Fails

Sometimes you go through this process and the signals aren't there. Maybe search volume is too low, maybe there are no existing products, maybe community posts get no engagement.

This is good news. You've just saved weeks of wasted work.

The response is to adjust, not to push forward hoping demand will appear. Either: (a) niche down further — a smaller, more specific problem might have stronger demand, (b) broaden slightly — maybe the specific framing you chose is wrong but an adjacent version has clear demand, or (c) pivot to a different topic entirely.

I've killed ideas that I thought were great because validation didn't support them. I've built products I wasn't initially excited about because validation was unmistakable. The product that sold the most in my first year was one I was lukewarm about — but the research was undeniable.

Follow the data, not your gut. Your gut is wrong about what the market wants surprisingly often.