Validation is the part of the startup process that most founders rush. They have an idea, they are excited, they want to build. The urgency to get moving feels productive. But spending six months and $60,000 building a product that nobody actually wants is not moving fast. It is moving in the wrong direction very efficiently.
The good news: you can validate most SaaS ideas in four to six weeks without writing any code, without hiring a developer, and without spending more than a few hundred dollars.
What you are actually trying to validate
Before you start, be clear about what you are testing. Validation is not "do people think my idea is interesting?" People will tell you your idea is interesting because they want to be polite. That is not validation.
Real validation answers three questions:
- Do enough people have this specific problem?
- Are they actively looking for a solution right now?
- Will they pay for it?
Specifically for SaaS, you also need to know: is the problem sticky enough that people will pay monthly? A one-time problem needs a one-time purchase. A recurring, ongoing problem can support a subscription.
Step 1: Define the exact problem and the exact person
Write one sentence: "I am building [product] for [specific person] who has [specific problem]."
Be as specific as possible. Not "for small businesses" but "for freelance graphic designers who invoice more than 10 clients per month." Not "who struggle with admin" but "who spend more than 3 hours per week chasing overdue invoices."
The narrower you are at this stage, the better your validation conversations will be. You can always broaden later. You cannot retroactively validate a broad assumption.
Step 2: Find 20 people who fit your description
Go find twenty people who match your target customer profile. Not friends and family. Not people who will give you polite feedback. Actual people who have the problem you think you are solving.
Where to find them:
- LinkedIn searches for specific job titles
- Industry-specific Facebook groups or Reddit communities
- Slack communities for your target profession
- Attendees of industry conferences (check conference websites for speakers and sponsors)
- Your own professional network, filtered strictly by fit
You need twenty because some will not respond, some conversations will teach you that you have the wrong person profile, and some will tell you things that contradict each other. Twenty gives you enough signal to see patterns.
Step 3: Run problem interviews, not solution interviews
This is the most important technique in validation and the most commonly misused.
A problem interview asks about the person's current situation. It does not pitch your solution. You are gathering information, not selling.
Questions that work:
- "Walk me through how you currently handle [problem area]"
- "What does your current process look like?"
- "What is the most frustrating part of this?"
- "Have you tried anything to fix it?"
- "What did you use? Why did you stop?"
- "If this problem disappeared tomorrow, what would that be worth to you?"
Questions to avoid:
- "Would you use a tool that did X?" (people say yes to hypotheticals)
- "Do you think there is a market for this?" (you are asking them to be analysts, not customers)
Run 20 conversations. Record them with permission. Transcribe the key quotes. The patterns in what people say are your validation data.
Step 4: Build a landing page in a day
After your interviews, you have a clear picture of the problem and the language your customers use to describe it. Use their exact language to build a landing page.
Tools that make this fast: Carrd, Webflow, or even a simple Notion page with a form. The page needs:
- A headline that names the problem in the customer's words
- Three to five bullet points that describe what the product does
- A call to action: "Join the waitlist" or "Get early access"
Do not describe features. Describe the outcome. "Stop losing track of which invoices are overdue" is more compelling than "invoice tracking dashboard."
You are not lying to anyone. You are describing a product you intend to build. Be transparent: "We are building this. Sign up for early access and you will be first to know."
Step 5: Drive traffic to the page and measure
Now spend money to drive traffic. Not organic search, which takes months. Paid ads.
For B2B SaaS, LinkedIn ads targeting specific job titles or industries are expensive but highly targeted. For consumer SaaS, Facebook and Instagram ads are cheaper per click.
Spend $200-$500 and measure your click-through rate and conversion rate (percentage of visitors who sign up).
Benchmarks to interpret your results:
- Click-through rate below 0.5%: the ad copy or targeting is off
- Landing page conversion below 5%: the messaging does not resonate or the offer is unclear
- Landing page conversion above 10%: strong signal
If you get 20+ email sign-ups from your first $300 of spend, that is meaningful. It is not proof that people will pay, but it is proof that the problem resonates enough to capture attention.
Step 6: Ask early sign-ups for money
This is the step most founders skip. They build the waitlist but never test whether people will pay.
Email your sign-ups with a specific offer: "We are about to start building. If you sign up for the founding member plan at $X/month before we launch, we will lock in that price forever."
Watch what happens. Not whether people reply positively. Whether they actually pay. A credit card charge is the only validation signal that matters.
You can take payment via Stripe in 30 minutes without building any product. Set up a payment page, send the link, see who clicks.
Five to ten paying customers before you write a line of code is sufficient validation to proceed with confidence. Zero paying customers after two weeks of pitching the founding plan is a signal that something fundamental needs to change.
What to do if validation fails
If the idea does not validate, you have learned something valuable before spending your real budget. The question is: what do you change?
Go back to your interview transcripts. Where did people push back? What alternative did they mention? What was the problem they wished was solved instead?
Validation failure is not idea failure. It is usually a targeting failure, a messaging failure, or a pricing failure. The underlying idea often has merit. The specific framing does not.
Iterate once or twice before abandoning the idea entirely. Some of the most successful SaaS products looked nothing like their original concept after the first round of validation.
Ready to build?
Once you have paying customers or committed pilot users, you are ready to build. Use our MVP cost calculator to scope the first version and understand the realistic budget.
Then book a call with our team. We work with early-stage founders regularly and can help you build the smallest version of your product that delivers real value, without gold-plating features that do not matter yet.
The whole point of validation is to make the build phase cheaper and faster. Once you know exactly what to build and who it is for, a focused custom development team can deliver an MVP in eight to twelve weeks.