How SaaS Founders Actually Validate Demand in 2026

By Tomáš Cina, CEO at Discury · AI-assisted research, human-edited

Editor's Take — Tomáš Cina, CEO at Discury

What strikes me reading these threads is how often founders mistake the vanity of a waitlist for the reality of market pull. I have watched this pattern repeat in the 3720+ quotes we've extracted across 53 analyses at Discury — a founder spends months polishing a landing page to harvest emails, only to find that those same signups vanish the moment the "launch" email hits. The signal founders are looking for isn't in an email list; it is in the willingness of a user to stop their current workflow to test your solution.

The second trap is the "Product Hunt" dopamine cycle. We see so the cited founders treat a launch day as the finish line, when it is actually just the starting gun for the real work of customer acquisition. The 97.4% failure rate reported in one r/SaaS thread on launch post-mortems isn't because the code was bad; it's because the founders built in isolation and hoped the market would magically appear on launch day.

If I were starting a B2B motion today, I would ignore the waitlist entirely. I would spend those weeks finding 10 people who are currently suffering from the problem I want to solve and ask them to let me fix it manually. If they won't give me 15 minutes of their time to talk through their current process, they certainly won't pay for a SaaS subscription later. the founders in this sample invert this, and the community threads we monitor amplify that inversion because "launch day" is more shareable than "difficult customer discovery."

The 97.4% Failure Rate of Build-First SaaS

The conventional wisdom of "launching big" on platforms like Product Hunt often masks a lack of underlying demand. One r/SaaS thread on launch post-mortems analyzed 500 launches and found that 487 of them—a staggering 97.4%—failed to reach $1,000 MRR. These zombie products share a common lifecycle: months of isolated coding followed by a single day of artificial traffic, leading to a "now what?" realization.

"487/500 (97.4%) make less than $1,000 MRR. 456/500 (91.2%) have <100 active users. 423/500 (84.6%) haven't updated since launch month." — u/Responsible-Ad431, r/SaaS thread

The survivors in that dataset did not rely on launch day hype. Instead, they secured paying customers before writing code. This confirms that SaaS demand is not generated by a platform launch; it is captured by solving a specific, existing pain point that users are already paying to alleviate. One founder in a recent r/SaaS thread detailed spending an entire year building a one-click n8n solution, only to launch to 3 users who vanished immediately. This reinforces that the "build" phase is often a distraction from the actual work of identifying a specific ICP (Ideal Customer Profile) who is currently suffering enough to pay for a solution.

Why 5 to 10 Users Is the Real Validation Metric

Founders often obsess over getting "enough" signups, but the quality of the interaction matters more than the volume. One Hacker News discussion on SaaS video tools suggests that 5 to 10 active users is the true magic number for early validation. These users are not just signups; they are people who have integrated the tool into their daily work and are providing feedback that drives the product forward.

"5 to 10 is reportedly the magic number." — u/bobosha, Hacker News discussion

This threshold forces founders to move away from vanity metrics. If you cannot get 5 people to use your tool, you don't have a marketing problem—you have a product-market fit problem. The goal is to reach that small group of users who feel the pain so acutely that they are willing to work through the bugs of a version 1.0 platform. A critical observation from this dataset is that when a product is truly needed, users will tolerate missing features. Certainly Health, for instance, identified that 38% of Americans delay medical care due to bill uncertainty, creating a massive, urgent demand that allowed them to build a marketplace around price transparency as noted in their Launch HN discussion. The founders didn't need a polished UI; they needed to guarantee the patient responsibility, a high-value outcome that users prioritized over UX perfection.

The Landing Page Trap and Early SaaS Demand

The temptation to spend weeks perfecting hero copy and CTA buttons is a common form of "productive procrastination." One founder in a recent r/SaaS thread described spending three weeks on a landing page, only to have the first visitor leave in eleven seconds. The lesson here is that a landing page's only job is to answer "is this for me?" within five seconds.

"I spent three weeks on my landing page before I had a single user. I convinced myself this was important work because it felt productive." — u/AdCrazy2912, r/SaaS thread

When demand is missing, founders often blame the marketing channel, but the issue is usually a lack of clear positioning. If you cannot explain the value within seconds, no amount of traffic—whether from Product Hunt or paid ads—will save the product. This "landing page trap" often stems from a lack of deep customer discovery. In another r/Entrepreneur thread regarding SOP tools, the founder admitted that spending 6 months building without talking to 50 potential customers first was their biggest mistake. By failing to understand the specific language their customers used to describe their pain, they built features that nobody asked for. The consequence is a product that looks "impressive" but lacks the core utility that drives retention, leading to the high churn rates often seen in early-stage B2B SaaS.

How to Measure SaaS Demand Beyond Waitlists

Waitlists are often mistaken for validation, but they are frequently just a collection of curious observers. A founder in a small business thread learned this the hard way after demoing to 50+ companies, only to have zero of them try the app at launch. The disconnect occurs because "I'd definitely pay for that" in a demo is often just social politeness.

"Before we launched officially our app, we did demo to more than 50+ companies and 27 of them were enthusiastic... But the day of the launch... guess how many of them tried the app? ZERO." — u/Fantastic-Proof-3220, r/SaaS thread

True validation requires a "high-friction" action: installing the script, testing the workflow, or signing a contract. A waitlist number is a vanity metric that does not correlate with actual usage. If your waitlist is large but nobody is willing to jump on a call to discuss their workflow, your waitlist is not a sign of demand. In one B2B SaaS case study shared in a startup thread, the founder faced 30% monthly churn because users never reached the "Aha!" moment due to poor onboarding. This highlights that demand isn't just about the initial signup; it's about whether the user can actually use the product to get the result they were promised. If the onboarding is too complex, the demand evaporates instantly, regardless of how many people signed up on the landing page.

Audit Your SaaS Demand in One Week

If you are struggling to find traction, stop building and start auditing your current demand signals. The following steps will help you distinguish between curiosity and intent.

Day 1–3: The Workflow Audit

Stop asking "would you buy this?" and start asking "can you show me how you do this today?"

1. Find 10 potential users in your niche (e.g., via LinkedIn or niche forums).
2. Schedule a 15-minute screen-share call.
3. Ask the user to perform the task your SaaS is meant to solve using their current tools.
4. Note every manual workaround they use. If they don't have a workaround, they don't have a pain point.

Day 4–7: The Manual Pilot

If you have a working product, stop trying to automate the onboarding.

1. Reach out to the 10 people you interviewed.
2. Offer to set up their account manually and walk them through it.
3. If they refuse to spend 10 minutes setting it up with you, they will not use your product.
4. If they agree, observe them using the tool. If they struggle, do not fix the UI—fix the core value proposition.

Data Sources for SaaS Demand Generation

This analysis draws on 11 r/SaaS and Hacker News threads (the ones cited inline above). Threads were surfaced via Discury's cross-subreddit monitoring. This analysis was compiled with Discury, which aggregates discussion threads across SaaS-adjacent subreddits.

discury.io