- Validation is about proving willingness to pay, not just collecting compliments.
- Customer interviews reveal problems; landing page tests measure real interest.
- Pre-sales are the strongest signal: money changes hands before code is written.
- A go/no-go checklist prevents you from building a product nobody wants.
- Skip validation only if you enjoy burning 4-8 weeks and your savings.
You've got a SaaS idea that keeps you up at night. You've sketched the architecture, picked Next.js and PostgreSQL, and even started mapping out Stripe webhooks. But before you sink 4 to 8 weeks and thousands of dollars into an MVP, you need to answer one question: will anyone pay for this? Too many founders skip this step, build for months, and launch to crickets. The fix is a structured validation process that tests demand before you write a line of production code. Devs & Logics is a US-focused software development agency that builds SaaS MVPs, web platforms, mobile apps, AI-powered products, and cloud setups for startups and enterprises. We've seen what happens when validation is skipped, and we've seen the difference it makes when it's done right. For a deeper look at the build phase, check out our step-by-step guide to building a SaaS MVP.
Why Validate a SaaS Idea Before Writing Code
Validating a SaaS idea before coding prevents you from spending 4 to 8 weeks and thousands of dollars building something nobody wants. It forces you to confront the only question that matters: will people pay for this?
Building an MVP is expensive. Even a lean build with Next.js, TypeScript, and a managed Postgres like Supabase can run into tens of thousands of dollars if you hire an agency. And that's before you factor in the opportunity cost of your time. Validation is your insurance policy. It won't eliminate risk, but it will stop you from building a product that solves a problem nobody has or that people aren't willing to pay to solve.
Think about the last SaaS tool you paid for. You probably didn't buy it because the landing page was pretty. You bought it because it solved a painful, recurring problem. Validation is about finding that pain and confirming that others feel it too. If you can't find 10 people who are visibly frustrated by the problem you're solving, you don't have a business yet. You have a hobby.
For a detailed breakdown of what an MVP actually costs, including realistic ranges for design, development, and infrastructure, see our SaaS MVP development cost guide. It will help you understand the financial stakes of skipping validation.
Customer Interviews: How to Ask Questions That Reveal Real Demand
Customer interviews reveal real demand when you ask about past behavior and current workarounds, not hypotheticals. The goal is to find painful, frequent problems that people already pay to solve.
Most founders botch interviews by asking leading questions like "Would you use a tool that does X?" People are polite; they'll say yes to be nice, then never open their wallet. Instead, ask about what they do today. For example: "Walk me through how you handle invoicing right now." or "What's the most frustrating part of that process?" If they've built a spreadsheet with 15 tabs and a macro, that's a signal. If they say it's fine, move on.
You want to hear about workarounds, hacks, and money already being spent. If someone is paying a virtual assistant $500 a month to manually reconcile Stripe payouts, you've found a pain point. If they've cobbled together Zapier, Airtable, and a prayer, that's a buying signal. Your job is to listen for the emotion: frustration, anger, resignation. Those are the problems worth solving.
How many interviews? Aim for 15 to 20 conversations with people who fit your ideal customer profile. If you hear the same pain point from at least 10 of them, and they're actively spending time or money to solve it, you're onto something. If you hear crickets, pivot or kill the idea. Don't fall in love with your solution; fall in love with the problem.
Record the interviews (with permission) and tag recurring themes. This qualitative data will inform your landing page copy and your MVP scope. It's the raw material for everything that follows.
Landing Page Smoke Tests: Measuring Interest Before You Build
A landing page smoke test measures interest by driving traffic to a page that describes your solution and tracking sign-ups or clicks. It's a cheap way to validate messaging and gauge demand before writing a line of code.
Here's the playbook: build a simple landing page with Next.js and deploy it to Vercel in a day. Use a template or a no-code tool like Carrd if you want to move even faster. The page should clearly state the problem, your solution, and a call to action (CTA). The CTA could be "Join the waitlist" or "Get early access." Then drive traffic to it using Google Ads, LinkedIn ads, or organic posts in communities where your buyers hang out.
What you're measuring is conversion rate. A typical conversion rate for a B2B SaaS waitlist page is 2% to 5% of visitors. If you're getting 10% or higher, that's a strong signal. If you're getting less than 1%, your messaging or your value proposition is off. But be careful: a high conversion rate from a broad audience doesn't mean much. You need to target the right people. A 20% conversion rate from a bunch of students when you're selling to enterprise CFOs is noise.
Use UTM parameters to track which channels drive the best conversions. Install analytics like Plausible or PostHog to see where people drop off. Maybe they bounce at the pricing section, or maybe they don't understand the headline. Iterate on the copy and run the test again. This is your chance to refine your pitch before you build the product.
One caveat: a landing page test only measures interest, not willingness to pay. Someone might give you their email to stay informed, but that doesn't mean they'll pull out a credit card. That's why the next step is crucial.
Pre-Sales and Letters of Intent: The Strongest Validation Signal
Pre-sales and letters of intent are the strongest validation because they require a commitment of money or resources. If someone won't pay a deposit or sign a non-binding LOI, your idea likely isn't painful enough.
Pre-sales can take many forms. You could offer a discounted early-bird price for the first 10 customers, with the promise of delivery in 8 weeks. Or you could ask for a refundable deposit. The key is that money changes hands. Even a $50 deposit is a signal that someone is willing to pay. If you can get 5 to 10 pre-sales before you build, you've validated demand and funded part of your development.
Letters of intent (LOIs) are common in B2B. They're non-binding documents that state a company's intent to purchase once the product is available. They're not as strong as cash, but they're a signal that a real business with a budget is interested. Use LOIs when you're selling to enterprises that can't cut a check for an unbuilt product.
We worked with a healthtech startup that used pre-sales to validate their idea before we built their MVP. They got 12 clinics to sign LOIs and 5 to pay a deposit. That gave them the confidence (and the cash flow) to move forward. You can read the full story in our healthtech MVP case study.
If you can't get anyone to pre-pay, that's a red flag. It might mean your price is too high, your target customer isn't feeling enough pain, or your solution isn't compelling. Better to learn that now than after you've burned 6 weeks of development.
Validation Methods Compared: Cost, Speed, and Signal Strength
Different validation methods vary in cost, speed, and signal strength. Interviews are cheap and fast but qualitative; pre-sales are slower but provide quantitative proof.
| Method | Typical Cost | Time to Results | Signal Strength | Best For |
|---|---|---|---|---|
| Customer Interviews | Low (your time) | 1-2 weeks | Qualitative (problem discovery) | Understanding pain points and workarounds |
| Landing Page Smoke Test | Low to Medium (ads, tools) | 1-2 weeks | Quantitative (interest) | Testing messaging and initial demand |
| Pre-Sales / Deposits | Low (sales effort) | 2-4 weeks | Strong (willingness to pay) | Confirming real demand and funding development |
| Letters of Intent | Low (sales effort) | 2-6 weeks | Medium (intent, non-binding) | B2B validation with enterprise buyers |
| Prototype / Concierge MVP | Medium (design/dev time) | 2-4 weeks | Medium (usability and value) | Testing solution fit before full build |
Use a combination. Start with interviews to find the pain, then run a landing page test to gauge interest, then push for pre-sales to confirm willingness to pay. Each step builds on the previous one and reduces your risk.
Your Go/No-Go Checklist: Deciding Whether to Build the MVP
Use a go/no-go checklist to objectively decide whether to proceed with the MVP. If you don't hit at least three of these signals, don't build yet.
Here's the checklist we use with founders:
- Problem validation: At least 10 out of 20 interviewees describe the problem as painful and frequent.
- Workaround evidence: Interviewees are spending money or significant time on makeshift solutions.
- Landing page conversion: Your smoke test converts at 5% or higher from a targeted audience.
- Pre-sales: You have at least 3 paying customers or 5 signed LOIs.
- Clear buyer: You know exactly who holds the budget and what triggers a purchase.
- MVP scope: You can define a minimal feature set that delivers core value in 4 to 8 weeks.
If you hit three or more, you have enough signal to build. If you hit fewer, go back and refine your hypothesis. Maybe you need to niche down, adjust your pricing, or change your target customer. Building without these signals is a gamble. For a structured framework to plan your build once you're ready, grab our free MVP launch playbook.
The Honest Tradeoff: Validation Can't Eliminate Risk
Validation can't eliminate risk. Even with strong signals, you might build and find the market shifts. But skipping validation guarantees you'll learn the hard way.
We've seen founders do everything right: 20 interviews, a landing page that converted at 8%, and 10 pre-sales. They built the MVP, launched, and then a competitor with deeper pockets entered the market and undercut them. That's business. Validation reduces the odds of failure, but it doesn't make them zero. The goal is to avoid the obvious mistakes: building something nobody wants, solving a problem that isn't painful, or targeting a market that won't pay.
Another limitation: validation takes time. You might spend 4 to 6 weeks on interviews, landing pages, and pre-sales before you write any code. That feels slow, especially if you're eager to build. But it's a lot faster than spending 8 weeks building and then 6 months trying to sell something nobody wants. The tradeoff is worth it.
Finally, validation is not a one-time event. Markets change, customer needs evolve, and what worked six months ago might not work today. Build a feedback loop into your product from day one. Instrument your app with analytics, talk to users regularly, and be willing to pivot. Validation is a habit, not a phase.
Frequently Asked Questions
How many customer interviews do I need to validate a SaaS idea?
Aim for 15 to 20 interviews with people who fit your ideal customer profile. The goal is to hear the same pain points repeated until you can predict what the next person will say. If you hear a consistent problem from at least 10 people, and they're actively spending time or money on workarounds, you have a strong signal. Fewer than 10, and you might be chasing noise.
What's a good conversion rate for a landing page smoke test?
A 2% to 5% conversion rate is typical for a B2B SaaS waitlist page. Anything above 5% from a targeted audience is a strong signal. But context matters: a 10% conversion rate from a broad, untargeted audience might be meaningless if those people aren't your buyers. Focus on quality over quantity.
Can I validate a SaaS idea without a landing page?
Yes, you can validate through customer interviews and pre-sales alone. But a landing page is a cheap, fast way to test messaging and measure interest at scale. It also gives you a place to send interviewees to gauge their real interest. If you're allergic to marketing, at least do the interviews and pre-sales.
How long does validation take before I can start building?
Plan for 4 to 6 weeks. That includes 1 to 2 weeks of interviews, 1 to 2 weeks for a landing page test, and 2 to 4 weeks for pre-sales. You can run some of these in parallel. If you're in a hurry, you can compress it to 3 weeks, but you'll have less confidence in the signal.
Final Takeaways
Validation is the difference between building a product people want and building a monument to your assumptions. Start with customer interviews to find a painful problem, run a landing page test to gauge interest, and push for pre-sales to confirm willingness to pay. Use the go/no-go checklist to make an objective decision. And remember: validation reduces risk, but it doesn't eliminate it. The only way to guarantee failure is to skip it entirely.
If you've validated your idea and you're ready to build, Devs & Logics can help. Our SaaS MVP development services are designed to get you from validated concept to working product in 4 to 8 weeks, with a focus on clean architecture, scalable infrastructure, and a codebase you can grow. We'll help you scope the MVP, choose the right stack, and ship something real.