How to Validate a Digital Product Idea Before You Build It

The most expensive mistake in digital products isn’t a bad cover or the wrong price. It’s spending three months of evenings on an ebook, template pack or mini-course that nobody wanted in the first place. When your building time is squeezed in around a job and family, those evenings are the scarcest thing you have.

Validation is how you protect them. It means collecting real evidence that people want a specific product before you finish building it. It won’t guarantee success, but it can save you from building the wrong thing and point you toward a better version of the right one.

What Validation Is and What It Isn’t

Validation is not asking friends whether your idea sounds good. Most people are kind, and kind people say “I’d totally buy that” without ever buying. It’s also not finding a popular topic and assuming popularity means people will pay.

Useful validation answers three questions:

Does a specific group of people have this problem often enough to care?
Are they already spending time or money trying to solve it?
Will some of them pay you, specifically, for this solution in this format?

The strongest evidence is money changing hands. The next strongest is people giving you something that costs them a little, like an email address, a reply or 20 minutes of their time. Likes and compliments are the weakest signals of all.

Step 1: Write the Product Promise in One Sentence

Before any research, write a single sentence that names the buyer, the problem and the result: “A [format] that helps [specific person] [achieve specific result] without [common frustration].”

For example: “A one-page weekly planning template that helps freelance designers track client deadlines without juggling three apps.” This sentence will change as you learn. Writing it down forces you to be specific enough to test.

If you can’t fill in the blanks, the idea isn’t ready to validate yet. Go back and narrow it down.

Step 2: Look for Evidence That the Problem Already Exists

Spend one or two evenings looking at what people already say and buy. You’re looking for repeated pain, not a single loud post.

Search forums, subreddits and Facebook groups where your buyer hangs out. Note the questions that come up again and again and copy the exact phrases people use.
Look at existing products on marketplaces such as Gumroad, Etsy or Payhip. Read the reviews, especially the three-star ones, which often explain what buyers wished was different.
Check search demand with free keyword tools or Google Trends to see whether interest is steady, seasonal or fading.
Look at your own inbox or comments if you already have a small audience. Repeated questions are product ideas in disguise.

Competition is usually a good sign. If other people sell something similar and get reviews, the market exists. Your job is to find a sharper angle: a narrower audience, a better format, clearer instructions or a lower-effort way to get the result.

Step 3: Talk to Five to Ten Potential Buyers

Reading is useful, but conversation is where you learn the details that make a product sell. Find five to ten people who match your buyer and ask for a short call or a few questions by message.

Ask about their past behavior, not their future intentions:

“When did this problem last come up for you?”
“What did you do about it?”
“Have you ever paid for something to help with this? What was it like?”
“What would make a solution worth paying for?”

Leave your product idea until the end. If you lead with it, people tend to react to your enthusiasm rather than describing their reality. When you do describe it, watch for questions like “When can I get it?” or “How much is it?” Those are much stronger than “Sounds great.”

Step 4: Build a Simple Landing Page Before the Product

Now turn what you’ve learned into a page that describes the product as if it already exists, without pretending it does. Include:

A headline built from the buyer’s own words
Who it’s for and who it isn’t for
What’s included (formats, number of pages or lessons, what they’ll be able to do)
A price, or a price range you’re testing
A clear, honest note about availability, such as “Launching in early December. Join the list to get it first.”
A simple call to action: join a waitlist, reply with interest or pre-order

You don’t need a full website for this. A storefront product page, a free landing page from your email tool or a simple page on your blog all work.

Waitlist or Pre-Order?

A waitlist is the low-pressure option: people give you an email address in exchange for early access. It’s a useful signal, but a free sign-up is much easier to give than money.

A pre-order or founding-member sale is the stronger test. A buyer pays now and receives the product on a stated date, often at a lower price in exchange for patience and feedback. If you do this, be specific about what they’ll get and when, keep your promise and offer a full refund if you can’t deliver on time. Treat early buyers’ trust as the most valuable thing you’ll earn from the test.

Step 5: Set Up a Small Test on a Storefront

If you use Gumroad for your test, a few features from its help center are worth knowing (as of October 2026):

Prices can range from free up to $5,000, and adding a “+” to a price, like “$5+”, lets customers pay what they want above that minimum.
With pay-what-you-want turned on and the amount set to $0, a buyer can take the product free, but anyone who chooses to pay must pay at least $0.99.
Gumroad’s fee on sales from its own website is 10% + $0.50 per transaction, plus card processing of 2.9% + $0.30. Sales through its Discover marketplace carry a flat 30% fee instead.
Gumroad doesn’t charge a fee on free products, but free products have a lower file-size limit.
You can add a custom refund policy to each product, and Gumroad shows it on the product page.
One catch for early sellers: Gumroad says you can’t send email updates until you’ve earned $100 after fees and received a payout. If you plan to email pre-order buyers through Gumroad, check that limit first or use your own email tool.

Other platforms such as Payhip, Lemon Squeezy and Etsy have their own fees and rules, so check each official pricing page before you decide. If you compare Gumroad and Payhip, Plrexpert has a fee and tax comparison worth reading.

Step 6: Decide Your Success Line Before You Launch the Test

The easiest way to fool yourself is to decide what “good” looks like after you see the results. Set a simple target before you start, based on how many people you can realistically reach. For example:

“If at least five people pre-order from the 40 I contact directly, I’ll build it.”
“If fewer than 2 out of 100 visitors to the page join the waitlist, I’ll rework the offer before building anything.”

These numbers are examples, not benchmarks. There’s no universal conversion rate that guarantees a product will work, and results vary a lot by audience, price and traffic source. What matters is that you pick a line in advance and respect it.

Then send real people to the page: the folks you interviewed, your email list if you have one and communities where you already contribute and self-promotion is allowed. Give the test a fixed window, such as one or two weeks.

Step 7: Read the Results Honestly

When the window closes, you’ll land in one of three places:

Clear Yes

You hit or beat your success line, and buyers asked specific questions. Build the product, starting with the parts people asked about most. Deliver to your early buyers first and use their feedback to improve the version you sell to everyone else.

Mixed Signals

People joined the waitlist, but few paid, or traffic was too low to tell. Don’t scrap the idea yet. Change one thing at a time: a narrower audience, a clearer headline, a different format or a lower starting price. Then test again.

Clear No

Almost nobody bit, even among people who described the problem. That’s disappointing, but it’s also a win. You learned it in two weeks instead of three months. Refund any pre-orders promptly, thank everyone who took part and take what you learned to the next idea. Often the next idea comes straight from those conversations.

Common Validation Mistakes

Asking “Would you buy this?” and trusting the answer
Testing with people who don’t match your buyer, like friends outside the niche
Hiding the price, so you never learn whether anyone would pay it
Running the test so briefly, or with so little traffic, that the result means nothing
Promising a pre-order delivery date you can’t realistically meet around your day job
Building the full product “while waiting” for results, which defeats the purpose

Do This Today

Write your product promise in one sentence: format, buyer, result and frustration. Then spend 30 minutes in one community where your buyer hangs out and copy five questions or complaints, word for word, that your product could answer. If you can’t find five, that’s your first piece of evidence.