Module 2: Validate before you build

The 10-conversation test

Before building anything, have ten conversations with people in your target audience. Not surveys — conversations. Ask: "What's your biggest frustration with [topic]? What have you tried? What would solving it be worth to you?" Then shut up and listen. You're hunting for the exact words they use — those words become your sales copy — and for willingness to pay, the only validation that counts.

The killer question, asked last: "If I built [specific product] that [specific outcome], would you buy it for [price]?" Then the real test: "Great — I'm taking founding-member pre-orders this week." Interest is cheap; credit cards are truth. If nobody reaches for a wallet, your idea needs work, not your building skills.

Find these ten people where they gather: relevant subreddits, Facebook groups, Slack communities, your own email list or customers, LinkedIn. Offer nothing, pitch nothing — just ask questions. Ten conversations will teach you more than ten weeks of building in isolation.

Record (with permission) or take verbatim notes — the exact phrases matter more than your summary of them. When three different people describe the same frustration in the same words, you've found your headline. Founders who paraphrase lose the voice-of-customer gold; founders who quote it write sales pages that feel like mind-reading.

The pre-sale landing page

Be honest on the page: "Founding members get early access on [date]" — pre-selling with a clear delivery date is legitimate; selling vaporware with no date is not. Offer founding members a discount and a direct line to you (feedback calls, early input). Early buyers who shape the product become your best testimonials.

No audience yet? Validation gets harder but stays possible: post the concept in three communities with a link, run a tiny ad test ($5/day for a week to a simple page), or partner with someone who has the audience for a revenue share. "No audience" is a distribution problem to solve, not a reason to skip validation.

Reading the signals honestly

Validation signals, ranked: actual pre-orders (strongest) → waitlist signups with stated price (strong) → enthusiastic conversation responses (moderate) → polite encouragement (worthless). "That's a great idea, I'd totally buy that" without a wallet is the most expensive sentence in product development. Discount it to zero.

If signals are weak, iterate the idea before abandoning it: wrong audience? (Try a narrower niche.) Wrong outcome? (The conversations reveal what they actually want.) Wrong price? (Test higher — low prices can signal low value.) Change one variable at a time and retest. Most "failed" ideas are one pivot from working.

When signals are mixed — some enthusiasm, no wallets — the most common fix is narrowing the audience, not changing the product. "Freelancers" is too broad to convert; "freelance bookkeepers drowning in client onboarding" is specific enough to buy. Specificity converts; generality gets polite nods.

Keep a validation journal: one page per idea, with the conversations, the pre-sale numbers, and your honest read. When you revisit ideas months later, the journal prevents rose-tinted memory ("I think people liked that one") from overriding what actually happened. Data beats nostalgia, even at this early stage.