SaaS Idea Validation Checklist

CB Insights tracked 431 VC-backed startups that raised $17.5 billion combined. 43% failed because they built something the market didn’t want. This checklist is designed to close that gap.

Before You Build Anything: Market Signal Evaluation

The most common validation mistake is skipping this step entirely. You have an idea. You are excited about it. You want to start building. But the first question is not “how do I build this?” It is “does anyone want this?”

Market signal evaluation takes a few hours and can save you months of building something nobody searches for, asks about, or would pay for.

Search volume check. Go to Google Keyword Planner, Ahrefs, or any keyword tool and search for the problem your product solves. Not your product name. The problem. If you are building a dispatch tool for plumbers, search “plumber scheduling software” and “plumbing dispatch software” and “field service management plumbing.” You want to see that people are actively searching for a solution. If the search volume for every relevant keyword is zero, that does not mean the problem does not exist, but it means discovery through SEO will be difficult and your go-to-market strategy needs to account for that.

Reddit and forum activity. Search Reddit for the problem. Look for posts where people describe the pain you are solving. Read the comments. Are people recommending existing solutions? Are they saying they wish something existed? Are they describing workarounds that are clunky and frustrating? Active discussion about the problem is a strong signal. If nobody is talking about it anywhere, you need to question whether the pain is real or whether you imagined it.

Competitor pricing. If competitors exist and charge money, that is a good sign. It means the market has been validated by someone else spending their own money to build and sell a solution. Check what they charge. If the lowest competitor charges $200/month, your $20/month alternative has a clear pricing angle. If competitors are all free, monetization will be your challenge, not market existence.

Competitor reviews. Read the 2-star and 3-star reviews of existing competitors on G2, Capterra, and the app stores. The 1-star reviews are often rage venting. The 2-3 star reviews are from people who need the product but are frustrated with specific shortcomings. Those shortcomings are your opportunity. If the same complaints appear across multiple competitors, you have found a validated gap.

Willingness to pay. This is the hardest signal to evaluate without talking to potential customers, but there are proxies. Are people paying for competing products? Are they paying for adjacent products? If your target audience already spends money on software in the same category, adding your product to their budget is a smaller leap than convincing someone to start paying for something they currently do manually.

Landing Page Setup Checklist

Your landing page is a hypothesis test. The hypothesis: if I describe this product clearly, a meaningful percentage of visitors will give me their email address. The landing page is the test environment.

Domain. Register a domain that matches the product name. A .com is ideal but .app, .dev, .io, and other TLDs are fine for validation. The domain itself does not need to be the final brand. It needs to be real enough that visitors take it seriously. A subdomain of your personal site signals “side project.” A dedicated domain signals “real product.”

Above-the-fold section. The first screen visitors see needs three things: a headline that states what the product does, a subheadline that states who it is for, and an email capture form. Do not start with your company story. Do not start with “welcome to.” State the value proposition in plain language.

The headline should pass the “5-second test.” If someone reads only the headline and then leaves, do they know what the product does? “Dispatch software for plumbing contractors” passes. “Reimagining field service management” fails.

Problem section. After the fold, describe the problem you solve. Use the language your target audience uses. If plumbers call it a “dispatch board,” use “dispatch board.” If they call it a “schedule,” use “schedule.” Do not use your own terminology. Mirror the language from the Reddit posts and forum threads you found in the market signal evaluation.

Solution section. Now describe what your product does about the problem. Be specific. “Drag-and-drop scheduling” is more persuasive than “intuitive interface.” “See every truck on a map” is more persuasive than “real-time fleet visibility.” Concrete beats abstract.

Pricing section (fake-door). Show pricing tiers even though the product does not exist yet. This is a fake-door test. When someone clicks “Start Free Trial” or “Choose This Plan,” you capture the click event and redirect them to the email capture or waitlist. The click data tells you which price point attracts the most interest and whether people are willing to pay at all. More on this below.

Social proof section. If you have it, use it. If you do not, skip it entirely. Do not fabricate testimonials, user counts, or logos. An empty social proof section is better than a dishonest one. Early visitors will find out, and the trust damage is permanent. Instead, you can describe the team’s background, the research behind the product, or the problem in more depth.

Footer. Include a real company name, a working email address, and links to a privacy policy and terms of service. These signal legitimacy. A landing page with no footer feels like a scam.