How to Validate a SaaS Idea Before You Write Code

You have a great SaaS idea. Now you have one job: prove someone will pay for it before you write any code. This is how you validate a SaaS idea without building the wrong thing.

Most technical founders do the opposite. We love building. We retreat to the comfort of the keyboard and spin up a database, configure a server, and start hammering out features. Six months later, we emerge with a beautiful, functional product that nobody wants. I've done it. It feels terrible.

This guide is the antidote. It's a step-by-step process to get real, concrete validation from the market. The kind of validation that comes in the form of time, commitment, and money. Not just compliments.

Where Do I Find My First 20 People to Talk To?

Validation starts with conversations. Not with your mom, not with your friends, and not with other founders. You need to talk to people who are living the problem you think you can solve. Your goal is to find 20 of them.

Why 20? It's enough to see patterns. After 20 conversations, you'll know if the pain is real or imaginary. You'll hear the same words, the same frustrations, again and again. Or you'll hear nothing but confusion, which is also a signal.

Here’s where to find them:

1. Your Warm Network (Tier 2): Think of former colleagues, old clients, or people you know professionally who fit your ideal customer profile (ICP). Not your best friends who will tell you what you want to hear. People who will be honest. Send them a personal note. You’re not selling, you’re learning.

2. LinkedIn: This is the best place for B2B SaaS validation. If you can afford it, Sales Navigator is worth its weight in gold for a month. You can filter people by job title, company size, industry, location, and keywords. Let's say your idea is for construction project managers. You can find 500 of them in 10 minutes. Then, you connect with a simple, honest message. No spam.

3. Niche Communities: Find where your people hang out online. This could be a subreddit, a Slack community, a Discord server, or a private forum. The key is to not be a marketer. Join the community. Add value for a week. Answer questions. Be a good citizen. Then, and only then, can you post something like, "Hey, I'm exploring solutions for [problem]. I'm not selling anything, just trying to understand the space better. Would anyone who deals with [problem] be open to a 15-minute chat?"

Here’s the email or LinkedIn message template I use. It works.

Subject: Quick question about [their area of expertise]

Hi [Name],

I came across your profile on LinkedIn and saw you're a [Job Title] at [Company].

I'm doing some research on how [job title]s handle [the problem area]. I'm not selling anything, just trying to learn from experts like you.

Would you be open to a 15-minute call in the next week or two to share your experience? I'm especially curious about how you currently manage [specific task].

Best,

[Your Name]

It’s short, respectful of their time, and frames them as the expert. People like being seen as experts. When you do your outreach, you're not trying to sell a product. You're trying to learn about their problems.

What Do I Ask in a Validation Interview?

This is where most founders get it wrong. They pitch their idea. This is the fastest way to get useless feedback.

Your idea is a hypothesis. You don't test a hypothesis by asking people if they like it. You test a hypothesis by gathering data about the problem it's meant to solve. The best validation interviews feel more like therapy sessions for your customer than a sales pitch.

You want to learn about their life. Their workflows. Their frustrations. You want specifics.

The golden rule comes from Rob Fitzpatrick's book, The Mom Test. You're not allowed to talk about your idea. At least not at first. You ask questions about their life and work that are so good, you could ask your mom and she couldn't lie to you.

Bad questions (hypothetical and leading):

• "Do you think it's a good idea if...?"
• "Would you use a product that did X?"
• "How much would you pay for a solution like this?"

These questions invite compliments and speculation, not facts. You'll get a lot of "Oh yeah, that's a great idea! I would totally use that." This is a false positive. It's worthless.

Good questions (about specific, past behavior):

• "Tell me about the last time you dealt with [problem]."
• "What was the hardest part of that?"
• "What are you using now to solve this?" (Could be a competitor, a spreadsheet, or just human labor).
• "And how much does that solution cost you? In money, or in time?"
• "Have you ever searched for a better solution? What did you find?"

These questions force them to tell you stories about what they've actually done, not what they might do. If they say the problem is a huge pain, but they've never tried to solve it or are using a free Google Sheet, the pain might not be big enough to pay for. Past behavior is the only predictor of future behavior.

Listen more than you talk. Aim for a 90/10 split. Take detailed notes. When you hear a moment of frustration in their voice, dig in. Ask "Why was that frustrating?" five times. Get to the root cause.

Why Surveys Are a Waste of Your Time

I have a strong opinion here. For the purpose of early-stage SaaS idea validation, surveys are almost completely useless. They are a dangerous tool that gives you the illusion of data and the comfort of a colorful chart.

Here’s why they don’t work.

First, surveys are entirely hypothetical. Every question is a variation of "Would you...?" or "How much would you...?" As we just discussed, people are terrible at predicting their own future behavior. They answer with the best version of themselves in mind. They tell you they'd pay $100/month for a product that saves them time because they want to be the kind of person who values their time. But when the invoice arrives, their behavior changes.

Second, the data is incredibly shallow. You get a multiple-choice answer or a one-sentence text response. You have no idea what the person was thinking. You can't see them roll their eyes. You can't hear the sigh of frustration. You can't ask, "Can you tell me more about that?" The real insights are buried in the context, and surveys strip all context away.

Third, they create massive false positives. It's easy to get 200 people to fill out a 2-minute survey. You’ll feel great when 85% of them say your idea is "Very interesting." You'll build a product based on this 'validation' and then wonder why none of those 200 people will actually pull out their credit card. They didn't lie to you. They just answered a hypothetical question hypothetically.

Don't waste a week crafting the perfect survey. Spend that week having five real conversations. One 30-minute conversation is worth more than 1,000 survey responses when you're trying to validate a SaaS idea.

How Do I Know If I Have a 'Validated' Idea?

Validation isn’t a simple yes or no. It's a spectrum. You need to know what a strong signal looks like versus a weak one. I think of it in four tiers.

Tier 1: Compliments. This is the weakest signal. It's fool's gold. When you pitch your idea and someone says, "That's a cool idea!" or "I like it!" that means nothing. They are just being nice. Compliments are poison. If you get one, your next question should be, "Thanks. But what parts don't you like? What's the biggest flaw in what I've described?"

Tier 2: Specific Pain. You're getting warmer. This happens during a good customer interview. The person isn't complimenting your idea (you haven't pitched it yet). They are telling you about their problem. You hear real emotion. "Ugh, you have no idea. Last month, our reporting process took three full days. Jen had to stay late all week just to copy-paste data into our spreadsheet."

This is a great signal. It tells you the pain is real and has measurable consequences (time, morale). But it is not yet validation. It's a strong indicator that you should keep digging.

Tier 3: Commitment. This is where validation starts to get real. At the end of a great conversation, you can gently pivot toward your solution. "I've been exploring a way to automate that reporting process. It's very early, but would you be open to seeing a mock-up next week?" If they say yes and actually schedule a time, that's a micro-commitment. They are willing to give you more of their time. That's a good sign.

Tier 4: Currency. This is the gold standard. Currency isn't just money. It's anything a person risks to get your solution. There are three types:

• Money: The strongest signal of all. Someone pre-pays for your product before it exists. We'll cover this next.
• Time: A signed letter of intent for a pilot program where they commit their team's resources. Or they agree to a weekly 30-minute check-in call for the next two months.
• Reputation: They introduce you to their boss or another key decision-maker. They are putting their own social capital on the line for you. This is a very strong signal, especially in large organizations.

Your goal is to move from compliments to currency. A validated idea has at least 3-5 instances of Tier 4 validation. That’s when you can start to feel confident.

Building Your Fake Front Door: The Landing Page Test

Conversations give you qualitative data. A landing page test gives you quantitative data. It helps you see if the problem you've heard about is compelling enough for a total stranger to take action. This is the simplest way to test your messaging and value proposition at scale.

Don't spend more than a day on this. Don't hire a designer. The goal is speed and data, not perfection.

1. Use a Simple Builder: I love Carrd for this. It costs $19 per year. It's dead simple. Webflow is great too, but has a steeper learning curve. Pick one and move on. Don't get stuck here.

2. Write Clear, Outcome-Oriented Copy: The headline (H1) is 80% of the battle. It must promise an outcome, not describe a feature.

   • Bad H1: "A Collaborative Project Management Platform"
   • Good H1: "Finish Your Team Projects On Time, Every Time"

   The rest of the page should be simple. A sub-headline that explains who it's for. Three bullet points that highlight the pain you solve or the gain you provide. Maybe a short paragraph explaining how it works. That's it.

3. The Call to Action (CTA): The button is your test. What you ask for matters.

   • Weak CTA: "Learn More" (Where do they go? What do they learn?).
   • Okay CTA: "Join the Waitlist" or "Request Early Access". This is a good starting point. You can link this to a simple email form. This is a good way of building a waitlist to gauge interest.
   • Strong CTA: "Pre-order & Save 50%" (More on this in a moment).

4. The Thank You Page Matters: After someone clicks the CTA and fills out the form, don't just say "Thanks!" Use the thank you page to get more qualitative data. Say, "Thanks for your interest! To help us build the right product, could you answer one quick question: What's the biggest challenge you face with [the problem]?" Use a simple form tool like Tally or new-school Typeform for this.

5. Drive Traffic (and Spend a Little Money): Don't just post your page on Twitter and hope for the best. You need to simulate real-world traffic. The best way to do this is with paid ads. Budget $100 to $200. Run ads on the platform where your customers live (LinkedIn for professionals, Reddit for enthusiasts, Facebook for consumers). Target them as precisely as you can. Your goal is to see what percentage of clicks convert into signups. A 5-10% conversion rate is a good signal. Below 2% means your messaging isn't resonating.

The 'Pay Me Now' Test

Asking for money is the most uncomfortable and the most important part of validation. It cuts through all the compliments and hypotheticals. A credit card number is a fact. It's the purest form of validation.

But how do you ask for money when you don't have a product? You sell the outcome, and you make them an offer they can't refuse.

This can be your landing page CTA, or it can be the follow-up for the most interested people from your interviews or waitlist. You need to be transparent.

Here’s a script I’ve used:

"Thanks so much for your feedback so far, it's been incredibly helpful. Based on our conversations, we've decided to build this product. We're planning to launch in about three months.

The public price will be $99/month. However, for the first 10 customers who want to partner with us from the beginning, we're offering lifetime access for a one-time payment of $499. Or the first year for $299. (Pick a price that feels scary to you).

This commitment helps us focus on building the right features for you, and it gives you a huge discount for taking a chance on us. It's fully refundable if we don't launch. Would you be interested in one of those founding customer spots?"

This script does a few things. It creates scarcity (10 spots). It provides a clear, compelling discount. It reduces their risk (fully refundable). And it frames them as a "founding customer" or "design partner," which is more appealing than just being a pre-order number.

To accept payment, use Gumroad or a Stripe Payment Link. It takes less than 30 minutes to set up. Seriously. Don't use "I don't have a payment system" as an excuse. This isn't just about a specific saas pricing strategy; it's about testing any willingness to pay at all.

If they say yes, you have real validation. If they say no, you have an even more valuable opportunity. You get to ask, "Could you tell me what gave you pause?" The objection (price, trust, features, timing) is pure gold. It tells you exactly what you need to fix.

Get five people to pre-pay. Just five. That's a powerful signal that you should start writing code.

What to Do When They Say No

Rejection is the default state in sales and validation. You will hear "no" far more than "yes." Do not let this discourage you. A "no" is not a failure. A "no" is data. Your job is to be a detective and figure out what the "no" is telling you.

When someone doesn't sign up, doesn't commit, or doesn't pre-pay, it's almost always for one of a few reasons. Try to categorize the rejection.

• The Market No: "I just don't have this problem." If you hear this from 15 out of 20 people, you have a market problem. The pain isn't real or widespread. Your solution, no matter how elegant, is a solution in search of a problem. It's a signal to pivot to a different problem entirely.

• The Solution No: "I have the problem, but this wouldn't solve it for me because of X, Y, and Z." This is actually great feedback. They are validating the problem but rejecting your proposed solution. This tells you that you need to rethink your features or your core value-prop. They are giving you the roadmap.

• The Price No: "I want it, but it's too expensive." If you hear this once, it might just be a cheap person. If you hear it ten times, your price is misaligned with the value. You either need to lower the price or, more likely, do a better job of communicating the value and ROI. A good question to ask is, "What would a solution like this need to do for you to feel like $99/month is a great deal?"

• The Trust No: "It seems interesting, but I'll wait until you've launched." This is a trust and urgency problem. They are risk-averse. You haven't built enough credibility or made a compelling enough offer for them to take a leap of faith. This is common. You can sometimes overcome this with money-back guarantees or by focusing on getting a few more innovative early adopters first.

Don't fall in love with your idea. Fall in love with the problem your customers have. When you get a "no," get curious, not defensive. The person giving you the "no" is giving you a gift. Unwrap it carefully.

If you go through this entire process and get nothing but market "no's" and a 0% conversion rate on your landing page, it's okay. You just saved yourself six months or a year of your life building something nobody wanted. That's a massive win. Kill the idea, mourn for a weekend, and start looking for a new problem to solve.

If you do nothing else this week:

1. Find five people on LinkedIn who fit your ideal customer profile.
2. Send them the connection request and email script from this post.
3. Schedule one 15-minute conversation. Just one. Start listening.