How to Validate an Info Product Idea Before You Build It

Ninety-one modules recorded, a slick sales page built, and eleven sales in the first month — that’s the graveyard most abandoned courses share. The idea felt right, the creator was genuinely knowledgeable, and the market simply wasn’t there in the size or willingness-to-pay the creator assumed. Validation isn’t a formality before building an info product; it’s the entire difference between building something people were already trying to pay for and building something you hoped they’d want.

Validation means testing willingness to pay, not just interest

The single biggest mistake in info product validation is confusing engagement with purchase intent. A poll that gets 300 votes, a waitlist that collects 500 emails, a LinkedIn post that gets 200 comments saying “I need this” — none of these predict revenue. People say yes to free things and hypotheticals constantly; the muscle that matters is whether they’ll hand over a credit card before the thing even exists.

The gold-standard validation signal is a pre-sale: asking for money for a product that isn’t built yet, with a clear delivery date. If you can get 20-30 people to pay $150-400 for a course that doesn’t exist yet based on a page describing the outcome and a rough curriculum, you have validated demand. If you can only get people to say they’d be “interested,” you’ve validated nothing except that your topic sounds appealing in the abstract.

The four-week validation sprint

Rather than validating indefinitely (a trap that lets you avoid ever actually launching), run a bounded four-week sprint with a clear decision at the end.

Week 1 — Define the specific transformation. Not “a course on productivity” but “a system that gets freelance designers from chasing invoices to getting paid within 7 days, every time.” Vague topics don’t validate because nobody can evaluate whether they need something undefined. Write the outcome in one sentence a stranger could repeat back to you.

Week 2 — Build a one-page offer and drive 500-1,000 targeted visitors to it. This is a landing page with the promise, the curriculum outline, a price, and a “join the waitlist for early access at 40% off” CTA — not a full checkout yet. Traffic can come from a small ad spend ($200-500), posting in relevant communities, or emailing an existing list if you have one. You’re measuring visitor-to-waitlist conversion rate; above 8-10% for cold traffic is a strong signal, below 3% suggests the offer isn’t resonating even before price enters the picture.

Week 3 — Convert waitlist to pre-sale. Email everyone who joined the waitlist with a real payment link, a real price, and a real delivery date (typically 4-6 weeks out). This is the step most people skip because it’s uncomfortable — asking for money feels riskier than collecting interest. But it’s the only step that actually tells you anything. A waitlist-to-purchase conversion rate above 8-10% among genuinely interested people is healthy; below 3% means people liked the idea in theory but not enough to fund it.

Week 4 — Make the go/no-go call using a real threshold, decided in advance. Before you start the sprint, write down the number that means “build it” — say, 25 pre-sales at $200 — and the number that means “this needs a different angle or audience.” Deciding the threshold after seeing results lets you rationalize any outcome; deciding it first keeps you honest.

Why talking to your audience beats surveying them

Surveys are the validation equivalent of asking someone if they’d like to be healthier — everyone says yes, and the answer tells you nothing actionable. What works instead is structured 15-20 minute conversations with 8-12 people who match your target buyer, where you’re not pitching anything, you’re mining for the specific words they use to describe their problem.

Ask about the last time they tried to solve this problem themselves — what did they try, why didn’t it work, what did they spend (time or money) on it. Ask what they searched for on Google when the problem was worst. The phrases that come up unprompted in these conversations are gold: they become your sales page headlines, because they’re the language your buyer already uses, not the language you’d default to as the expert who’s forgotten what it’s like to not know this.

A pattern worth watching for: if 6 of 10 conversations mention the exact same failed solution (“I bought a template but it didn’t fit my situation” or “I hired someone and they didn’t understand my industry”), you’ve found your positioning wedge — you’re not competing against no-solution, you’re competing against a specific inadequate solution people already tried and rejected.

Pricing signals you get for free during validation

The pre-sale phase doubles as a pricing test if you set it up right. Instead of picking one price, offer three price points during the waitlist conversion email to different segments of your waitlist (this only works cleanly with waitlists over roughly 150 people, otherwise segments get too small to read): a lower anchor, your target price, and a premium tier with added support or a live cohort element. Watch which tier absorbs the most volume, not just which gets the highest per-unit revenue — a $600 tier that converts at 2% might generate less total revenue and, more importantly, less proof of broad demand than a $250 tier converting at 9%.

Resist the urge to price low “to be safe.” Underpricing during validation actively distorts your data, because a $29 course validates almost nothing — it’s an impulse buy, not a considered purchase, so a high conversion rate at $29 tells you people will impulse-click, not that they’re committed to doing the work or that you have pricing power. Validate near the price you actually intend to charge at launch.

A worked example: what the numbers actually look like

Abstract percentages are easy to nod along to and hard to apply, so walk through an actual cohort. Say you’re validating a course on negotiating freelance contracts, targeting freelance consultants earning $80k-150k a year. You spend $350 on targeted ads and get 620 clicks to the landing page. Of those, 54 people join the waitlist — an 8.7% visitor-to-waitlist rate, comfortably in the healthy range. You email the waitlist a week later with a real payment link at $297 and a 5-week delivery date. Six people buy immediately, and after two follow-up emails over the next ten days, four more convert, for 10 total pre-sales — an 18.5% waitlist-to-purchase rate, which is strong.

Total: $2,970 in pre-sale revenue against $350 in ad spend, from a list of 54 people. That’s a clear go signal on conversion rate, but notice the raw number — 10 buyers — is still small in absolute terms. This is where the pre-set threshold matters: if you’d decided in advance that 25 pre-sales was your bar, this result tells you the conversion mechanics work but the top-of-funnel volume doesn’t yet exist at this ad spend. The fix isn’t changing the offer, it’s either increasing spend proportionally (since the funnel math already checks out) or testing a second acquisition channel to see if the same conversion rates hold with a different audience source. Conflating a volume problem with a resonance problem is the single most common misread of validation data — the data above would look identical whether the true addressable audience is 500 people or 50,000, and only scaling the test distinguishes the two.

The most common failure mode: validating the topic instead of the offer

Even people who run a disciplined pre-sale process often validate the wrong thing without realizing it. A pre-sale that converts well can still be masking a fragile assumption if the price, the delivery timeline, or the specific promise tested isn’t what you actually intend to ship. If you pre-sell at an introductory $97 “founding member” price and it converts beautifully, that result doesn’t automatically transfer to the $297 price you plan to charge at public launch — you’ve validated demand for $97, not $297. Similarly, if your landing page promises “a live cohort with weekly office hours” and converts well, but your actual production plan is a self-paced recorded course with no live component, you’ve validated a different product than the one you’re about to build.

The discipline here is boring but important: whatever you write on the validation page — price, format, delivery timeline, level of support — has to match what you intend to actually ship, or you need to re-validate the specific variable you changed. Teams that skip this step frequently discover, only after building the full self-paced version, that a meaningful share of their pre-sale buyers request refunds once they realize the live component they expected isn’t included. That’s not a validation failure, it’s a scope-creep failure introduced after validation was already complete.

Sequencing validation when you’re starting from zero versus already having an audience

The four-week sprint above assumes you have some list, community, or paid traffic option available. If you’re starting completely cold — no email list, no existing audience, no social following with any density in your target niche — the sprint needs a zero’th week bolted on front: two weeks of showing up consistently in the exact places your future buyers already gather (relevant subreddits, industry Slack or Discord communities, niche LinkedIn groups, comment sections of adjacent creators) with genuinely useful, non-promotional contributions. The goal isn’t to build a huge following before validating; it’s to build enough two-way trust with 200-500 relevant people that a validation offer from you gets taken seriously rather than ignored as an unknown stranger’s pitch.

Skipping this step and going straight to cold ad spend against a brand-new, zero-trust identity is possible but meaningfully harder — expect conversion rates at every stage of the funnel to run 40-60% lower than the benchmarks above until you’ve built some initial credibility signal, whether that’s a modest personal following, a few public testimonials from informal beta conversations, or visible proof of expertise like a portfolio of past client results. If you already have an audience of any real size in an adjacent topic, you can compress the sprint to two weeks by skipping straight to the waitlist and pre-sale emails, since the trust-building step is already done.

Reading rejection signals correctly

Not all “no” signals mean the idea is dead — some mean the idea is right but something else is wrong, and conflating those two leads people to abandon good ideas or stubbornly push bad ones.

• High traffic, low waitlist opt-in: the topic doesn’t resonate with this specific audience, or the promise on the page is unclear. Try rewriting the headline before concluding the topic is bad.
• Good waitlist opt-in, low pre-sale conversion: people are curious but not convinced enough to pay, often because the outcome feels uncertain or the price feels disconnected from the promised result. Try adding more specific proof (a case study, a sample lesson) before dropping price.
• Good pre-sale conversion, but from a tiny total audience: you validated demand within a niche too small to build a sustainable business on. This is a real finding — it usually means widening the audience definition slightly, not abandoning the core idea.
• Silence across every channel: genuinely low demand, or you’re reaching the wrong audience entirely. This is the one pattern that should make you seriously reconsider the topic, not just the execution.

What to do with pre-sale money before the course exists

Collecting money for something unbuilt creates an obligation, and handling it well protects your reputation for the next launch. Set the delivery date conservatively — promise 6 weeks even if you think you can do it in 4, because production always takes longer than expected once you’re actually building lesson-by-lesson instead of outlining. Communicate proactively during the build: a short weekly update email to pre-sale buyers (“here’s what module 3 covers, here’s a sneak peek”) keeps trust high and, as a side benefit, gives you a live testing ground — buyers who reply with questions are showing you exactly where the curriculum needs more detail.

If your validation numbers come back weak, refund pre-sale buyers immediately and transparently rather than building a mediocre version just to avoid the awkwardness of refunding. A prompt, gracious refund preserves your relationship with that audience for the next idea; a rushed, underwhelming product you built purely to avoid refunding poisons it.

Turning validated demand into a launch plan

Once you’ve cleared your go/no-go threshold, the pre-sale buyers become your first cohort and your most valuable source of real-time feedback — their questions, confusions, and completion rates through the first version of the course tell you exactly what to fix before the public launch. Treat this first cohort’s experience as more valuable than the revenue it generated; a founder cohort that finishes the course and refers three friends validates the business model in a way that a bigger, colder second launch never will if you skip building genuine outcomes for the people who believed in you first.

The discipline of validating before building doesn’t just save you from wasted production time — it forces the clarity of thought that makes the eventual product good. Creators who validate properly consistently report that the process of writing the one-sentence promise and running real sales conversations sharpened their curriculum more than months of solo outlining ever did.

Measuring whether validation actually worked, after launch

The final check on whether your validation process was sound doesn’t come during the sprint — it comes 60-90 days after public launch, when you can compare what validation predicted against what actually happened. Track three numbers: public launch conversion rate against the pre-sale conversion rate (they should be in the same range; a public conversion rate less than half the pre-sale rate suggests your validation audience wasn’t representative of your broader market), completion rate of the pre-sale cohort (a low completion rate here, even with strong sales, flags a curriculum or format problem that will eventually show up as refund requests and bad word-of-mouth at scale), and unprompted referrals from the pre-sale cohort (genuine validation of both the offer and the delivery, since people don’t refer friends to something they merely tolerated).

If those three numbers hold up, the validation process did its job twice over — it protected you from building something nobody wanted, and it produced a founding cohort whose behavior tells you the model will scale. If they diverge significantly, treat that gap as data for the next product rather than a one-off anomaly: it usually means the original validation sample was drawn from a warmer, more bought-in group (an existing list, a personal network) than the cold audience you’re now trying to reach at scale, and the next validation round should test acquisition channels closer to how you actually intend to grow.