How to validate a SaaS idea before you write a line of code
Validate a SaaS idea before building by collecting three pieces of evidence in order: proof the problem is already being paid for (competitors with pricing pages and complaints), proof a specific buyer will describe the problem back to you unprompted (5–10 conversations), and proof of willingness to pay (a deposit, a signed pilot, or a pre-order — not a "yes, I'd use that"). If any of the three fails, no amount of code fixes it. The whole sequence takes 10–14 days and no engineering.
The workflow
Rewrite your one-line pitch into this shape: "[specific role] currently solves [problem] by [expensive workaround] and it costs them [time or money]." If you cannot fill in the workaround, you have not found a problem — you have found a feature. Nobody buys software to solve a problem they are not already spending something on. The workaround is your real competitor, and it is usually a spreadsheet, an intern, or nothing.
An empty market is bad news nine times out of ten. Search the problem phrase, not your product category, and look for paid tools, agencies, and Notion templates charging money. Then read the one- and two-star reviews: those are the sentences your landing page should be written in. Ten minutes in G2 review filters routinely beats a week of brainstorming, because complaints are unmet demand with a receipt attached.
Competitor research— worked example for this page- Input
- Software that reconciles Stripe payouts against invoices for bookkeepers
- What comes back
- 7 existing tools found, $29–$249/mo. Two are bookkeeper-specific; five are general accounting add-ons. Recurring complaint across 40+ reviews: multi-currency payouts break the reconciliation and support takes 3+ days. That complaint, not the category, is the wedge.
What this step looks like when it is done properly — the free Idea Validator covers the same ground as part of its research.
Ask about the last time the problem happened, what they did, and what it cost. Never describe your solution first — the moment you pitch, you stop learning. You are listening for one thing: do they describe the problem in the same words you do, without prompting? Five people is enough to spot the pattern; ten is enough to be sure. If three of five have to be reminded that the problem exists, it is not urgent enough to buy.
Put a real number in front of a real buyer: "This will be $79 a month — would you be a design partner at $39 for the first year if I have it in six weeks?" A yes with a calendar invite is data. A yes with "send me the link when it's live" is politeness. Ask three to five people. The number of committed yeses out of five is the single strongest predictor of whether a bootstrapped SaaS reaches its first $1k MRR.
- Input
- $79/mo single plan for a Stripe-to-invoice reconciliation tool aimed at solo bookkeepers
- What comes back
- Single-plan pricing gives buyers nothing to compare against, so the price becomes the whole conversation. Add a $39 tier capped at 200 transactions and let $79 be the obvious choice. Bookkeepers bill $60–$120/hr — anchor the page on hours saved, not features.
Run it yourself — free, no signup:
0/ 100 — BrokenThis page is costing you money from people who already decided to buy. Rebuild it around the unchecked rows before you spend another dollar on traffic.
Fix in this order- 1.A real price is on the page
- 2.Three or fewer plans
- 3.The price scales on a value metric
Weighted by what each one costs you. Do the top item, ship, then measure — fixing all three at once tells you nothing about which worked.
Before code, do it manually for one paying customer. Reconcile the payouts yourself in a spreadsheet, email them the result, charge them. This is the fastest way to learn where the real work is, and it converts your first customer at full price with zero engineering. Founders who skip it typically build three features nobody needed and miss the one the customer would have paid double for.
Write the number now, while you are still objective: "If I do not have 3 paying customers by [date], I stop." Sunk cost is not a character flaw, it is a default setting, and the only reliable defence is a threshold written before you are emotionally invested. Put it somewhere you will see it — the same doc as the idea, not a note you will never reopen.
- Input
- 8 weeks in, 2 design partners, 0 paid, weekly usage from 1 of 2
- What comes back
- CONTINUE, with a hard line. One engaged partner out of two at week 8 is a normal start, but unpaid usage is the most over-read signal there is. Convert one partner to paid within 3 weeks or the second data point never arrives.
Run it yourself — free, no signup:
1.Has anyone paid you actual money for this?
2.When you stop pushing for a week, what happens?
3.Of the people who tried it, how many still use it a month later?
4.Do you have one channel that reliably brings strangers?
5.Honestly — do you still want to work on this?
6.In the last month, did you learn something that changed the plan?
Answer all six for a verdict. None of them ask what you've already spent — that's the point.
Questions founders ask about this
- Is a waitlist enough to validate a SaaS idea?
- No. Waitlist signups measure interest in a headline, and typically 2–5% of them convert when the product ships. A deposit, a pre-order, or a signed pilot measures purchase intent — that is what "validated" means for a paid product.
- How many customer interviews are enough before building?
- Five to ten, if you stop steering them. You are not gathering statistics; you are checking whether the problem is described back to you unprompted. When the fifth conversation teaches you nothing new, you have your answer either way.
- What if there are already ten competitors?
- That is usually good — it proves budget exists. Competition only kills you when everyone is happy. Read the one-star reviews for a segment that is being served badly, then aim at that segment specifically rather than at the category.
- Should I build an MVP to validate, or validate to decide whether to build?
- Validate first. An MVP costs weeks and answers "can I build it?", which is rarely the risky question. The risky question is "will a specific person pay for this?", and a landing page plus five conversations answers it in days.
- How long should validating a SaaS idea take?
- Ten to fourteen days of real effort. Longer than that and you are usually avoiding the conversation where someone tells you no.
Next, founders usually do this
- How to validate a B2B SaaS idea when you don't know anyone in the industry6 steps
- How to price a micro-SaaS when you have no customers to learn from6 steps
- How to write kill criteria before you fall in love with the idea6 steps
- How to name a startup and check the domain without losing a week6 steps
The tools used above have their own pages — Pricing Page Grader and Kill-or-Continue Quiz — and the SOP SOP: Research and set your first price runs the same ground in more depth. Also worth reading: the Nine Lives Doctrine, and real verdicts from ideas kitty has run this workflow on.
kitty.build runs this entire workflow for you
Every step above — the research, the competitor read, the numbers, the honest verdict — is what nine specialist AI boards do automatically when you feed her an idea. She will tell you to kill it if it deserves killing. First idea is free.
Feed her an idea — freeNo card · Failed tasks are free · Your repo, your domain, your revenue