Written by Simon, founder who shipped 4 products nobody wanted.

The Pre-Launch Validation Playbook: How to Test Your Startup Idea Before Building

Ninety percent of startups fail. You already know that stat. What most people gloss over is why they fail, and CB Insights data consistently points to the same culprit: building something nobody wants. Not a bad team, not poor timing, not lack of funding. Just founders who skipped startup idea validation and started writing code before they confirmed a real problem existed. If you want a different outcome, you need a different process.

This playbook gives you a concrete 30-to-90-day roadmap to test your idea before spending a dollar on development. Validate your idea before you commit months of your life to something that might never find a market. The founders who do this work upfront are not more cautious, they are faster. They cut months of wasted iteration because they know what they are building and who they are building it for before the first line of code gets written.

Part 1: The Foundation of Startup Idea Validation

The Lean Startup methodology, popularized by Eric Ries, gives you the core operating principle: Build-Measure-Learn. But there is a step most founders miss. Before you build even a minimal product, you need to validate whether the problem is real, urgent and worth solving. The loop does not start with building. It starts with a hypothesis.

The Jobs-to-be-Done framework adds another layer. Clayton Christensen's insight is that customers do not buy products, they hire them to get a specific job done. When you focus on the job, you stop obsessing over features and start asking what outcome the customer actually needs. That shift in framing changes everything about how you design your interviews, your landing page and your MVP scope.

Before you run a single test, rank your assumptions by risk. There are three categories worth separating out: market risk (does this problem affect enough people who will pay), product risk (can you build a solution that works) and execution risk (can your team actually deliver it). Most early-stage founders obsess over execution risk when market risk is the killer. Test market risk first. Always.

Part 2: The Pre-Validation Phase (Days 1 to 30)

Set aside 60 minutes this week and do the following exercise. Start by writing down your startup backstory and your personal biases. Why do you think this is a problem? Where did the idea come from? Naming your biases does not eliminate them, but it makes you a more honest interviewer. Then map your nine core assumptions across three categories: who the customer is, what problem they have and why your solution is better than what exists today. Take 20 minutes for the mapping, 10 minutes to rank them by risk and the remaining time to draft your first problem hypothesis in one sentence.

Customer discovery interviews are the next stage and the most important thing you will do in weeks two and three. You are targeting 15 to 20 conversations with people who fit your target customer profile. Cold outreach on LinkedIn works well for B2B. Subreddits, Facebook groups and Slack communities work for consumer-facing ideas. Do not interview friends. They will lie to protect your feelings, and that is useless to you.

Use the 5PM Framework during your interviews: Positioning (who exactly is this person), Problem (what are their real frustrations), Primary use case (how they currently solve the problem), Monetization (what they already pay for in this space) and Market size (how widespread this frustration is in their world). Structure your questions to be open-ended and past-tense focused. Ask "tell me about the last time you struggled with X" rather than "would you use a tool that solves X." The first surfaces real behavior. The second invites fantasy. According to Todd Jackson's validation framework on Lenny's Newsletter, anything short of "I want this!" is effectively a no. Train yourself to hear hesitation as rejection.

After 15 to 20 interviews, look for clusters. Which problems came up without prompting? What language did multiple people use independently? Where did you hear genuine frustration versus mild inconvenience? Update your hypothesis based on what you heard, not what you hoped to hear.

Part 3: The Testing Phase (Days 30 to 60)

A landing page is the most cost-effective validation tool available to you. It tests whether your problem-solution framing resonates with strangers who have no obligation to be polite. Your page needs three things: a headline that names the specific problem, a brief explanation of how you solve it and a call-to-action that requires some commitment (a waitlist signup, an email submission or ideally a pre-order).

For traffic, use targeted channels rather than broad ones. LinkedIn outreach works for B2B. Reddit and niche forums work when you engage authentically before dropping a link. Direct email outreach to your interview subjects works because they already know the problem is real. Drive 300 to 500 visitors before you draw any conclusions. Conversion benchmarks vary, but for cold B2B traffic a 3 to 5 percent signup rate is a meaningful signal. Below 1 percent means your messaging is not connecting, not necessarily that the market does not exist.

One anonymous B2B SaaS founder ran this exact process with an idea for project management tooling aimed at small agencies. After 18 customer interviews, the real finding was not what they expected. Agencies did not need better internal workflow automation. They needed better client-facing portals that reduced communication delays. The founder shifted focus entirely before building anything. The revised landing page pulled a 3.2 percent conversion rate from 4,700 visitors, and a pre-order pilot brought in eight customers at $500 per month each via Stripe. That is $4,000 in monthly recurring revenue committed before a single feature was built. The entire validation cost was time and a $49 Carrd subscription.

Pre-orders deserve special attention as a validation signal. A signed-up email list tells you someone is curious. A payment tells you someone has a problem worth solving. Use Stripe, Gumroad or Kickstarter to collect payment commitments. Be transparent about the product status. Most people respond well to honesty when the problem is real enough for them.

Part 4: Market Sizing and Viability (Days 60 to 90)

Once you have problem validation and early conversion signals, size the market using both top-down and bottom-up approaches. Top-down means starting from industry reports (Gartner, IDC, CB Insights) and working down to your serviceable slice. Bottom-up means estimating how many customers you could realistically reach and what each one might pay. Both numbers should tell a similar story. If they are wildly different, your assumptions are off somewhere.

For competitive analysis, map at least 15 direct and indirect competitors. Pay close attention to negative reviews on G2, Capterra or app stores. Customer complaints about existing tools are a map of unmet needs. If you find an oversaturated market with a dominant player who owns 60 percent or more of mindshare, that is not automatically a dead end, but you need a very specific angle on why someone would switch.

Customer acquisition cost projections are where most optimistic founders get humbled. Pick your two or three likely acquisition channels and estimate realistic CPCs, conversion rates and close rates for each. If your unit economics require a CAC below $50 but your channel math suggests $300, you have a viability problem that no amount of product polish will fix. Face it now, not after you have raised a seed round.

Part 5: Common Pitfalls That Kill Validation

Confirmation bias is the single biggest threat to honest validation. You will unconsciously phrase questions to confirm your hypothesis. You will remember the positive signals and minimize the skeptical ones. The mitigation is structural: use a fixed interview guide, record every call with permission and have someone else review your notes for patterns you might have missed.

Vanity metrics are the second trap. Two thousand landing page visitors sounds exciting until you realize 1,950 bounced in under ten seconds and you have a 0.4 percent conversion rate. Focus on the denominator, not just the numerator. Signups without intent are noise. Money or a strong verbal commitment to pay is signal.

Insufficient sample size causes the third common failure. Founders draw hard conclusions from four or five interviews when the real pattern only emerges after fifteen or more. One passionate potential customer is not a market. Three is a coincidence. Fifteen with consistent themes is a direction worth betting on.

Part 6: The Metrics That Tell You What to Do Next

Here are the thresholds that matter in startup idea validation. If 70 percent or more of your interviewees acknowledge the problem as urgent without being prompted, your problem hypothesis is solid. If 50 percent or more indicate they would use your solution, your solution framing is working. If 20 percent or more commit to a paid pilot, you have demand worth building for. A landing page conversion rate below 1 percent means your messaging needs a full rethink. Between 1 and 3 percent means you are close but the framing needs work. Above 3 percent on cold traffic means proceed to MVP.

If your problem validation comes in below 60 percent, do not push through. Rethink your customer segment or your problem definition. If willingness to pay is below 15 percent, either the price point is wrong or the demand is softer than you thought. Either way, building now is a mistake.

Your 90-Day Roadmap

Weeks one through three are for foundation and discovery. Map assumptions, rank by risk and complete 15 to 20 customer interviews. Weeks four through six are for testing. Launch a landing page, drive targeted traffic and collect signal through conversion rates and follow-up interviews. Weeks seven through nine are for viability. Size the market, analyze competitors and run a pre-order pilot if your conversion rate warrants it. Weeks ten through twelve are for decision. Either you have evidence to build, a reason to pivot or an honest case for killing the idea. All three are good outcomes. The bad outcome is spending six months building and discovering the same thing then.

Tools worth knowing: Calendly and Typeform for recruiting interviews, Notion or Airtable for centralizing feedback, Carrd or Webflow for landing pages, Mixpanel or Amplitude for conversion tracking and Stripe for payment validation. None of these require significant spend. The Presta validation framework also covers a useful set of templates for assumption mapping and lean canvas documentation if you want a head start.

The founder who validates fastest wins. Not because speed is inherently virtuous, but because every week you spend building on unvalidated assumptions is a week you cannot get back. Pick your riskiest assumption right now. Design one experiment to test it this week. Get started on your validation plan today, before the momentum of the idea carries you into six months of building something nobody asked for. Read more on how other founders have run this process and what they learned along the way.