Validate a SaaS idea by proving three things before any code exists: a specific group of people has the problem, they already spend time or money working around it, and some of them will commit to paying you. Interviews, a landing page, a small ad test and pre-sales can answer all three in a few weeks for very little money.
What does "validated" actually mean?
An idea is validated when strangers commit something real, such as money, time or a signed letter of intent, not when friends say it sounds great. Compliments are free. Commitments cost the other person something, and that is what makes them a signal.
Write down, before you start, what evidence would convince you. For example:
- "Ten target customers describe this problem without prompting."
- "At least five of them currently pay for a workaround or spend several hours a week on it."
- "Three or more agree to pay a deposit or sign up for a paid pilot."
Setting the bar in advance stops you from moving the goalposts once you are emotionally invested. The exact numbers are yours to choose; what matters is that they are written down first.
Who exactly has the problem?
Narrow the customer down until you could list twenty real people or companies who fit. "Small businesses" is not a customer. "Independent physiotherapy clinics with two to five practitioners that still take bookings by phone" is.
A tight definition makes every later step easier. You know where to find people to interview, which words to use on your landing page and which audience to target with ads. If you can't name where these people gather, online or offline, that is useful information too.
How do you run customer interviews that tell you the truth?
Ask about past behaviour, not future intentions. People are poor at predicting what they would buy and quite good at describing what they did last week.
Aim for 15–20 conversations with people who match your definition. Useful questions include:
- "Tell me about the last time this problem came up. What happened?"
- "How do you handle it today? Which tools, spreadsheets or people are involved?"
- "What does that cost you, in money or hours?"
- "What have you tried that didn't work?"
- "If this problem disappeared tomorrow, what would change for you?"
Avoid pitching your solution until the end, if at all. The strongest signal is someone who has already tried to solve the problem and is still unhappy. If nobody has tried anything, the pain may not be sharp enough to pay for.
Keep notes in a simple table so patterns become visible across interviews rather than relying on memory.
How do you test demand with a landing page?
Build a one-page site that describes the outcome, shows a price, and asks for a real action. Then send relevant traffic to it and measure what people do.
A good validation page includes:
- A headline about the problem solved, in the customer's own words from your interviews.
- Three or four concrete benefits, not a feature list.
- A visible price or starting price, so sign-ups mean something.
- One clear call to action: "Join the paid pilot", "Reserve founding-member pricing" or "Book a 15-minute demo".
Our guide to the anatomy of a landing page that sells covers layout and copy in more detail. A landing page like this is a small project that doesn't require building the product itself.
Should you run ads to validate an idea?
A small, tightly targeted ad test is a fast way to see whether strangers care, but read the results carefully. Ads tell you whether a message attracts interest from a defined audience; they don't prove people will pay.
Our own campaign data, from service businesses rather than SaaS, shows how much the setup matters. Across nine featured Meta ad accounts, click-to-message campaigns that open a WhatsApp or Instagram chat were usually the cheapest way to start a conversation, while lead forms produced more leads to qualify. Results also vary enormously by audience and offer: a clothing brand averaged ₹5.43 per conversation, while an interiors account got just two conversations at ₹423 each. A poor result can mean the wrong audience or message, not just a bad idea.
For SaaS validation, that suggests a few rules:
- Test two or three different problem statements, not one.
- Send traffic to the landing page or straight into a conversation where you can ask follow-up questions.
- Set a fixed, modest budget and timeframe before you start.
- Judge success by conversations and sign-ups with a price shown, not by clicks.
How do you get people to pay before the product exists?
Ask for a deposit, a paid pilot or a signed letter of intent; whatever the format, the request should make people decide. This is the step most founders skip because it feels awkward, and it is the most valuable.
Options, from strongest to weakest signal:
| Method | What the customer commits | Time to run | Strength of signal |
|---|---|---|---|
| Paid pilot or pre-sale | Money upfront, often discounted | 2–6 weeks | Very strong |
| Refundable deposit | Money, with an exit option | 1–4 weeks | Strong |
| Signed letter of intent | Written intent to buy at a stated price | 2–4 weeks | Moderate to strong |
| Concierge service | Uses a manual version you deliver by hand | 2–8 weeks | Strong, plus deep learning |
| Waitlist with price shown | Email address only | 1–3 weeks | Moderate |
| Interviews alone | Time and opinions | 2–4 weeks | Weak on its own |
The concierge approach deserves special mention. You deliver the outcome manually, using spreadsheets, forms and email, while charging a real fee. If customers won't pay for a hand-delivered version that solves their problem, software alone is unlikely to change their mind. If they will, you learn exactly which steps are worth automating first.
Pricing deserves early thought here, because the price you test shapes who signs up. Our explainer on SaaS pricing models can help you choose what to put on the page.
How do you decide whether to build, pivot or stop?
Compare what you learned against the bar you set at the start, and be honest. There are usually three outcomes:
- Build. People described the problem unprompted, already spend money on it, and several committed to pay. Move to a tightly scoped MVP.
- Pivot. The problem is real but your audience, price or angle is off. Adjust one variable and test again.
- Stop. Few people recognise the problem, or nobody will commit. Stopping now costs weeks; stopping after a build costs months and a large budget.
If the answer is build, keep version one deliberately small. Our guide to building an MVP without wasting money explains how to scope it, and typical MVP builds run roughly $15k–50k and 8–16 weeks, depending on scope. What comes after validation, from scoping to launch, is mapped out in our complete SaaS build guide.
Frequently asked questions
How long should SaaS idea validation take?
Most founders can run interviews, a landing page and a small ad test in three to six weeks. Pre-sales and concierge pilots may take a little longer. If validation drags on for months without commitments, that is itself a signal.
How many customer interviews do I need?
There is no magic number, but 15–20 conversations with people who closely match your target customer usually reveal clear patterns. Stop when you keep hearing the same answers. If every interview sounds different, your customer definition is probably too broad.
Is a waitlist enough to validate a SaaS idea?
Usually not on its own. Email sign-ups are cheap to give and easy to forget. A waitlist with a visible price is better, and turning a share of that list into deposits or paid pilots is the real test.
What if someone steals my idea while I validate it?
This worry stops far more founders than actual idea theft does. Execution, customer relationships and speed matter much more than the idea itself. You can share the problem and outcome openly without revealing implementation details.
Can I validate a SaaS idea with a no-code prototype?
Yes. Clickable prototypes and no-code tools are useful for showing the workflow and testing whether people understand it. Just remember that enthusiasm for a prototype is still weaker evidence than payment.
From validated idea to first build
Once real customers have committed, the next step is a scoped plan that turns your interview notes and pilot feedback into a lean first version. Browse recent GRWW projects to see the kind of web products we ship. When you are ready, share your validation notes with us for a fixed-price MVP quote.