How to Validate a SaaS Idea Before You Build
Generic startup validation advice misses the parts that make SaaS specifically hard. Churn compounds. CAC scales differently. And “people want this” is not the same as “people will pay monthly for this forever.”
TL;DR
- 01.SaaS has a unique kill vector: people love the product but cancel after month three. Validate retention before you validate acquisition.
- 02.The willingness-to-pay test for SaaS is harder than one-time purchases — monthly payments feel different to buyers.
- 03.LTV/CAC math must close before you build, not after you have traction. Run it at the worst-case churn rate.
- 04.The switching cost question determines whether you have a product or a feature a platform will ship for free.
The verdict
“The SaaS graveyard is full of products people loved in month one and quietly cancelled in month four.”
Why SaaS validation is different
When you validate a one-time purchase, you need to answer one question: will someone pay for this once? SaaS requires a harder answer: will someone pay for this every month, for years, and find enough ongoing value not to cancel?
That is a fundamentally different product requirement. A tool that solves a problem brilliantly once might still fail as a subscription if the problem only needs solving occasionally. A tool that people describe as “really useful” might still churn at 8% monthly — which means you lose half your customer base every eight months.
The validation question for SaaS is not “do people want this?” It is “will people still be paying for this in twelve months?” Those are different questions, and most founders only ask the first one.
Generic startup validation frameworks — landing pages, fake door tests, customer interviews — are useful, but they test initial demand. They do not test retention. You need to pressure-test the retention assumption before you build, not after.
The retention question
Before anything else, answer this: why will a customer still be paying twelve months from now?
The answer must be specific. Not “because the product is valuable” — that is circular. The actual mechanism of retention in SaaS is usually one of three things:
Habit and workflow integration
The product becomes part of how the customer works. Switching creates workflow disruption, not just cost. Notion, Slack, Linear — all of these are retained because switching them out requires reorganizing how a team works.
Compounding data or value
The product becomes more valuable the longer a customer uses it. Their data, history, or trained preferences make the product personalized to them. CRMs and analytics tools have this property.
Ongoing job completion
The product completes a recurring job the customer has to do anyway. Payroll, invoicing, email marketing. The customer does not stay because they love the product — they stay because stopping means the job does not get done.
If your SaaS idea does not clearly fit one of these retention patterns, that is the first thing to investigate — not the market size.
Your idea is next
Your startup idea has a fatal flaw. Four AI examiners find it.
Results in ~60 seconds. No account needed.
Running the LTV/CAC math before you build
Most founders run this math after they have traction. By then it is too late to change the core business model. Run it now, with the worst-case assumptions you can defensibly make.
SaaS unit economics — worst-case inputs
Monthly churn rate
Use 5–10% for B2C SaaS, 2–5% for B2B SMB, 1–2% for B2B enterprise. If you do not know, use 7%.
Average Revenue Per User (ARPU)
The price you actually charge, after any discounts. Not the list price.
LTV = ARPU / monthly churn rate
At 5% churn and $50/month ARPU, LTV = $1,000. At 10% churn, LTV = $500.
Customer Acquisition Cost (CAC)
Total sales and marketing spend divided by new customers acquired. Include your time if you are doing outbound yourself.
LTV/CAC ratio
Below 3× is a difficult business. Below 1× means you lose money on every customer. Most early-stage SaaS is between 1× and 3× — which is the danger zone.
The output of this exercise is not a business plan. It is a constraint. You now know the maximum you can spend acquiring a customer and still build a viable business. That number determines which acquisition channels are available to you — and rules out most of them for most price points.
The switching cost question
Every SaaS idea needs to answer: what is the switching cost for the customer, and is it high enough?
Low switching cost is the silent killer. A customer who can replace you with a competitor in an afternoon, or who can build a passable substitute in a spreadsheet, will leave the moment a cheaper option appears or your price increases. Low switching cost also means platforms can absorb your feature set without you.
If your SaaS idea is primarily a better UI on top of existing infrastructure — a nicer dashboard, a simpler interface — the switching cost is low. Someone will ship a native version of your feature eventually, and customers will move to where it is already integrated.
High switching costs come from data lock-in, workflow integration, team adoption, or the time cost of rebuilding history. Before you build, identify specifically what switching cost your product creates and whether it is sufficient to survive competition.
Testing willingness to pay for a subscription
Monthly payments feel different to buyers than one-time purchases. A customer who would pay $200 once for a report might not pay $20/month for the same output, even though the annual cost is identical. Recurring payment requires them to actively keep choosing you every month.
The cleanest test: find ten people with the problem and tell them the price. Not ask if they would pay — tell them the price and ask them to pay it right now, for the first month, before the product exists. Not a waitlist. Not a letter of intent. Actual payment for month one of a thing that does not exist yet.
Five out of ten paying without much friction is a strong signal. Two out of ten suggests either the wrong audience or the wrong price point. Zero out of ten is data.
For a broader framework on testing whether people will actually pay, see the post on how to find out if people will pay before you build.
The B2B vs B2C difference in SaaS validation
B2B and B2C SaaS fail in different ways and require different validation approaches.
B2B SaaS has longer sales cycles, lower churn, and higher contract values. The validation challenge is proving you can reach buyers — not individual users, but the person with budget authority — and that the sales cycle is short enough to work at your stage. B2B SaaS also needs to clear procurement, security review, and often IT approval. These are not just sales friction; they are part of the product requirements.
B2C SaaS has faster sales cycles, much higher churn, and lower contract values. The validation challenge is proving the retention mechanism works. B2C customers cancel for emotional reasons — boredom, habit disruption, a better-looking competitor — as often as rational ones. The LTV/CAC math is harder to close at consumer price points and consumer acquisition costs.
Most SaaS ideas that “could work for businesses or consumers” end up serving neither well. Pick one and validate the specific dynamics of that model before building anything that tries to serve both.
For more on the specific kill vectors that end startup ideas before launch, see why most startup ideas fail before launch.
Four agents. Four angles. One verdict.
Your SaaS idea has a fatal flaw. Find it before you build.
IdeaRoast runs your idea through four specialist AI agents — market, tech, finance, and timing — each with live web data and an adversarial mandate. The Finance Agent specifically checks your unit economics. $1, no account required.
Find my idea's fatal flaw →