Most SaaS products fail not because they were built badly, but because they were built for problems nobody cared enough about to pay for. Idea validation — done before you write a line of code — is the highest-ROI activity in the early stages of a SaaS.
Here's how to validate a SaaS idea in 2–4 weeks without building anything.
The one question that matters
Before anything else, answer this: Is this a problem people are already paying to solve?
If yes, there's budget. If no, you're selling against the status quo (doing nothing), which is infinitely harder. Look for existing solutions — even terrible ones. A market with bad competitors is a good sign. A market with no competitors is a warning.
Week 1: Find 20 people with the problem
Describe the problem (not your solution) and find 20 people who have it. Places to look:
- Reddit: Search r/entrepreneur, r/SaaS, and niche subreddits for posts complaining about the problem. DM the authors. People who publicly complained are already motivated.
- X (Twitter): Search the problem keywords. Reply to relevant tweets.
- LinkedIn: Search job titles of your target customer. Cold message 50 of them with a 3-sentence note asking if the problem resonates.
- Slack communities and Discord servers in your niche.
- Your existing network. Most founders underuse this. Who do you already know in the target industry?
Your goal is 10 conversations. Not surveys — conversations. 20 minutes each, voice or video preferred.
What to ask in discovery calls
Don't pitch. Don't describe your solution. Ask about their experience:
- “Walk me through the last time you dealt with [problem].”
- “What do you currently do to solve it?”
- “How much time does that take?”
- “What does it cost you, roughly?”
- “What have you tried that didn't work?”
If they've tried multiple solutions, paid for at least one, and the problem keeps coming back — that's a real problem. If they say “yeah it's annoying but we just deal with it” — that's a pain, not a problem worth building a product around.
Week 2: Qualify with a landing page
Build a landing page that describes the problem and the outcome your product delivers. Don't show screenshots or a product. Just the promise.
Add a CTA: “Join the waitlist” or “Get early access.” Drive traffic with a single Reddit post, a tweet, or a LinkedIn post. If 50+ people sign up with zero paid traffic, you've found something. Under 10? The messaging isn't landing, or the problem isn't urgent enough.
You can build this landing page in a weekend with Next.js and a Resend form. The whole point is speed — you're not building a company yet, you're running an experiment.
Week 3: Pre-sell before building
The strongest validation signal is money. Not a list of “I'd pay for that” promises — actual money.
Go back to your best discovery call contacts and offer them a founder's deal: early access at a discount in exchange for feedback and a commitment to pay. Use Stripe to create a payment link (Stripe Dashboard → Payment Links) and send them the URL.
If someone pays before the product exists, you have validation. 5–10 pre-sales at any price point means you should build it. Zero pre-sales after direct outreach means you either have the wrong problem, the wrong audience, or the wrong price — not usually a reason to abandon the idea, but a signal to dig deeper.
The signals that matter
Green flags:
- They've paid for a competing solution
- They describe the problem without prompting
- They ask when you'll be ready
- They offer to introduce you to others with the same problem
- They sign up for your waitlist without you having to ask
Red flags:
- “That sounds interesting, keep me posted”
- They need to check with their boss before committing to anything
- The problem only occurs once a year
- The existing solution is “good enough”
- Your landing page converts at under 1%
When to start building
Start building when you have at least one of:
- 3+ pre-sales (real money collected)
- 10+ discovery calls where everyone describes the same pain unprompted
- 100+ waitlist signups from organic traffic
If you have none of these after 4 weeks of genuine effort, either the problem isn't painful enough or your target customer isn't reachable through the channels you tried. Consider pivoting the audience before the idea.
Build fast once validated
Once you have validation, speed matters. Every week you spend on setup is a week not spent on the product. Use a boilerplate that has auth, payments, email, and database already wired — so your first week of building goes toward the actual features your discovery calls asked for.
GetLaunchpad is built for this moment: the transition from “validated idea” to “first paying customers.” Clone the repo, add your API keys, and you have a production-ready foundation in a day instead of a month.