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

The Pre-Launch Validation Playbook: How Founders Test Ideas Without Burning Cash

Ninety percent of startups fail. You've heard that stat so many times it's lost its sting. But here's the part that should actually scare you: most of those failures were predictable. The founders built something nobody wanted, and they could have known that before writing a single line of code. Startup idea validation isn't a nice-to-have step you squeeze in before the real work. It is the real work, at least for the first four weeks.

I've shipped four products that went nowhere. Each time, I convinced myself I was validating while actually just building. There's a difference, and it's expensive to learn. This playbook is the process I wish I'd followed from day one. It's a 2-4 week framework you can run on a shoestring budget, and it will tell you whether your idea deserves your time before you commit months of your life to it. Validate your idea before you build it. That's the entire thesis.

Part 1: Define Your Validation Goals Before Anything Else

The first thing most founders skip is writing down their assumptions. Not their vision, not their roadmap, their assumptions. The things they believe to be true but haven't proven yet. Every startup is a bundle of assumptions, and the ones you don't examine are the ones that kill you.

Think in three layers. Market assumptions cover whether the problem exists at scale and whether people are actively looking for a solution. Customer assumptions cover who specifically has the problem, how badly it hurts and whether they have budget to fix it. Product assumptions cover whether your particular approach actually solves it better than existing alternatives. Most founders obsess over the product layer and completely ignore the market and customer layers. That's backwards.

Once you've listed your assumptions, rank them by lethality. Ask yourself: if this assumption is wrong, does the whole business collapse? Those are your riskiest assumptions, and they're what you test first. Not the fun stuff. Not the feature design. The things that could kill you fastest.

Define your success metrics before you start testing, not after. This sounds obvious but almost nobody does it. If you decide what counts as validation after you see the results, you'll rationalize your way into false confidence every time. Set a bar: at least 15 percent of people who see my landing page click the call-to-action, or at least 5 people out of 20 interviewed say they'd switch from their current solution immediately.

Part 2: Customer Discovery, Done Lean

You need 15 to 20 real conversations with people who match your target customer profile. Not your friends. Not your co-founder's network of supportive colleagues. People who actually have the problem you think you're solving.

Source them from LinkedIn, industry Slack communities, relevant subreddits and niche forums. A cold outreach message that works is short, specific and leads with their problem, not your solution. Something like: "I'm researching how recruiters handle candidate no-shows. Would you do a 20-minute call? I'll send a $20 gift card for your time." That's it. No deck, no pitch, no excitement about your idea.

In the interviews, use the Jobs-to-be-Done framework. You're not asking people what features they want. You're understanding the context in which a problem arises, what they're currently doing about it and what that costs them in time, money or frustration. Ask about the last time they dealt with this problem. Ask how they handle it today. Ask what they've already tried. Listen for frequency and intensity. A problem someone deals with daily and hates is worth solving. A problem they encounter twice a year and shrug about is not.

The biggest mistake in customer discovery is confirmation bias. You will unconsciously steer conversations toward answers that validate your idea. Guard against this by writing your interview questions before you start, sticking to them and actively seeking disconfirming evidence. Ask people why they wouldn't switch. Ask what would have to be true for them to keep using their current solution. Their hesitation tells you more than their enthusiasm.

Once you've mapped the competitive landscape, be honest about what you find. Identify five to ten direct and adjacent competitors. Look for where they underserve customers, not where they're weak on features you planned to build anyway. Read more about competitive analysis frameworks if you want to go deeper on this step.

Part 3: Low-Cost Validation Experiments That Actually Work

By week two, you should be running your first real test. A single landing page with a clear value proposition is still one of the most reliable validation tools available. Build it with Carrd or a basic HTML template. Write one headline that describes the outcome your customer gets, not the features of your product. Add a call-to-action: "Join the waitlist" or "Get early access" or, better yet, "Reserve your spot for $X."

Spend $100 to $200 on LinkedIn ads or Google ads to drive targeted traffic. For a B2B idea, LinkedIn's targeting is worth the higher cost-per-click. A ten to fifteen percent conversion rate on a cold traffic landing page is a meaningful signal. Under five percent means your value proposition isn't landing, and you should rewrite before spending more on traffic.

Pre-sales conversations are where the real validation happens. After your discovery interviews, go back to the people who expressed the most pain and ask them directly: "I'm building a solution for exactly this problem. Would you pay $X per month for it? I can take a card today." The moment you ask for money, the conversation changes. People who were enthusiastic in a research context suddenly get vague. That's data. The ones who say yes and actually give you a card are your true signal.

Consider the B2B scheduling software founder: eight years in recruiting, assumed the pain was scheduling complexity. After 18 interviews, the real pain turned out to be candidate ghosting. She reframed her entire concept, ran a $150 ad test in week two with a twelve percent conversion rate, and closed five customers at $200 per month in pre-commitments before writing any code. Total budget: $300. Total time: three weeks. The validation signal that mattered most was customers asking "When can I actually buy this?"

For your prototype, start manual. Build a Zapier workflow, a Google Sheets backend and a Typeform intake form before you write a single line of code. Run ten to fifteen real users through it. Measure time to value: how long does it take them to accomplish what they came to do? Look for churn signals: where do they drop off or get confused? You'll learn more from watching someone struggle with a clunky manual prototype than from a polished no-code app they casually click through.

Part 4: The 30-Day Roadmap in Practice

Week one is assumption mapping and interview prep. Define five to seven core assumptions, source twenty potential interview candidates and write a five-question interview guide. Budget about ten hours.

Week two is your customer discovery sprint. Run fifteen to twenty problem interviews, document patterns and contradictions, and start narrowing your core hypothesis. If your assumption mapping was honest, you'll likely already be seeing cracks in one or two of them. That's good. Budget twelve to fifteen hours.

Week three is rapid testing. Launch your landing page with your ad budget, build a simple manual prototype, run ten prototype user tests and do a thorough competitive analysis. Budget another twelve to fifteen hours.

Week four is your decision point. Compile everything into a simple validation report. Calculate your confidence in market size. Assess willingness to pay based on actual conversations and pre-sales attempts. Make a go or no-go call. If you're pitching investors, this data is also the core of your pre-seed narrative.

Do the unit economics now, not later. Build a simple spreadsheet with your expected customer acquisition cost, average revenue per user and estimated payback period. If the math only works at venture-scale margins you haven't earned yet, that's a red flag to address before you start building. HBS Online's market validation guide outlines a similar assumptions-first process and is worth reading alongside this playbook.

Part 5: The Pitfalls That Kill Validation Sprints

Confirmation bias is the most common failure mode. Talking only to people who already think your idea is great is not validation. It's marketing research theater. Seek out the skeptics. Ask people in your target segment who have tried and abandoned similar tools why they gave up.

Feature creep during validation is the second killer. The moment you start adding "just one more thing" to your prototype or landing page, you've left the validation sprint and started building a product. Lock your scope for the four weeks. Every new idea goes on a list for later.

The wrong customer segment is a subtler trap. Founders often test with whoever is easiest to reach, not whoever matches their target persona. Talking to ten startup founders when your target is mid-market enterprise procurement managers is not useful data. Be intentional about who you sample.

And watch your sample size. Three to five conversations will feel like enough when all three tell you the same thing. They're not enough. Patterns in qualitative research usually emerge around fifteen to twenty interviews. Push through even when it feels repetitive, because the exceptions are where the real insight lives. Get started on the platform and use the built-in validation tracking tools to keep your research organized.

The Tools You Actually Need (Budget: Under $300)

For research: Airtable or Notion for interview notes, Google Forms or Typeform for surveys, Calendly for scheduling. All free or nearly free. For your landing page: Carrd at $19 per year. For ads: $100 to $200 split between LinkedIn and Google. For prototyping: Figma, Zapier and Google Sheets. Total spend under $300, and that's with paid ad testing. You can do the whole discovery and prototype phase for zero dollars if budget is tight.

Digital Wonder Lab's validation framework also covers stress-testing assumptions with real users and prioritizing features by impact, which aligns well with the approach here.

Pick One Assumption and Test It This Week

Startup idea validation is not a box to check. It's a discipline that separates founders who build things people buy from founders who build things people politely ignore. The 2-4 week playbook works because it forces you to put your assumptions in front of real people before you've invested everything in them.

You don't need to run the whole playbook perfectly on your first try. Pick your single riskiest assumption, the one that would kill your business if it's wrong, and design one test for it this week. Talk to five people. Build a landing page. Ask for money. The founders who validate move faster, waste less and make bets with actual evidence behind them. Start there.