SaaS validation
SaaS Idea Validator — Test Your SaaS Before You Build
A structured analysis tuned for SaaS — recurring willingness to pay, churn risk, pricing tier fit, ICP narrowness, and the SaaS-specific distribution path. In under 60 seconds, free.
Last updated · September 20, 2026
Quick answer
What is a SaaS idea validator?
A SaaS idea validator is a tool that turns a one-sentence SaaS idea into a structured evaluation across the recurring-revenue dimensions that decide whether the product survives month six. The standard SaaS dimensions are recurring willingness to pay (not just first-payment intent), churn risk (whether buyers renew past the first billing cycle), ICP reachability (whether the buyer is identifiable enough to find), pricing-tier fit (whether the chosen price matches the buyer's budget), distribution channel fit (whether SEO, content, sales, or community actually reaches that ICP), and founder execution. Each dimension is scored 0–100 and combined into an overall score, plus a critical-assumption callout and an MVP blueprint. Yibud's SaaS validator is the Startup MRI rule engine, tuned so the SaaS-specific assumptions — recurring willingness to pay, churn, ICP narrowness — are first-class dimensions rather than afterthoughts. Free, no signup, the same inputs always produce the same report.
Key takeaways
What makes a SaaS validator different
- A SaaS validator scores recurring willingness to pay — not just first-payment intent. A free trial that converts is not the same signal as a customer who renews past month two.
- The SaaS-specific assumption stack is: ICP narrowness, recurring willingness to pay, churn past first renewal, pricing-tier fit, distribution-channel reachability, and founder execution.
- Discounted pricing contaminates the signal. A SaaS validator should score the test at the real recurring price, not the founder-friendly launch price.
- A free trial tests curiosity, not willingness to pay. The cheapest SaaS validation experiment is a 30-day concierge (Notion template, Loom video, no-code MVP, manual service) sold at the business-model price.
- Free SaaS validators that pair scoring with a first-customer plan are most useful to solo SaaS founders — the cost of building a SaaS that does not retain is the six-month runway that disappears while churn silently outpaces acquisition.
How it works
Four steps from SaaS idea to retention signal
The flow below is tuned for SaaS. Step 4 — the recurring pricing-tier test — is the part generic validation advice leaves out.
Step 1
Describe the SaaS idea
Write one sentence about the SaaS product and who pays for it monthly. The clearer the ICP, the sharper the recurring-revenue score.
Step 2
Answer five short questions
Audience, monetization tier (subscription / freemium / enterprise), acquisition channel, technical background, and the SaaS risks you already see. Five minutes total.
Step 3
Get your SaaS-tuned score
Recurring willingness to pay, churn risk, ICP reachability, pricing-tier fit, distribution fit, founder fit, and overall opportunity. Each 0–100, derived from a transparent rule engine.
Step 4
Test the recurring pricing tier
Run a 30-day concierge at the business-model price with five paying customers. The only experiment that produces a real renewal signal — and the part no landing page can fake.
Who it's for
Built for SaaS and micro-SaaS founders
Four SaaS sub-verticals, each with a different recurring-revenue risk to test first.
Micro-SaaS
Solo founders shipping small SaaS
Narrow ICP, low price point, founder-built. The risk: underpricing and ICP sprawl. The validator scores ICP narrowness and pricing-tier fit first.
Vertical SaaS
Industry-specific SaaS
A defined vertical (dentists, lawyers, fitness studios). The risk: shallow distribution into the vertical. The validator scores distribution-channel fit against the named vertical.
B2B SaaS
Self-serve and small-team B2B SaaS
Sold to a single champion inside a small business. The risk: a champion who leaves and takes the seat with them. The validator scores churn risk separately from acquisition.
Consumer SaaS
B2C subscription products
Sold to individual users on a monthly or annual plan. The risk: consumer churn, which is unforgiving compared to B2B. The validator scores consumer-churn risk and the trial-to-paid conversion path.
Why validate
Why validate a SaaS idea before building it
SaaS failures rarely look like failures at launch. They look like quiet launches that flatline at month six, when churn and acquisition cancel each other out.
Reason 1
Surfaces the recurring-revenue cliff
Most pre-build signals test first-payment intent. SaaS lives or dies on whether buyers renew past month two. The validator names retention as a first-class dimension so it gets tested before launch, not after.
Reason 2
Separates ICP narrowness from ICP breadth
Many SaaS founders target 'small businesses' or 'marketers' — segments too broad to acquire against. The validator scores ICP narrowness so the founder sees whether the chosen buyer is reachable at the chosen price.
Reason 3
Forces a real pricing-tier test
Discounted launch prices hide the real willingness-to-pay signal. The validator recommends a 30-day concierge at the business-model price, the experiment that produces a renewal signal you can trust.
When to skip
When this validator is the wrong tool
A SaaS validator is built around one assumption: the product survives on recurring payment. When the product's economics do not fit that shape, the validator's signal becomes misleading. Three cases where this validator is the wrong instrument.
Reason 1
The idea is a marketplace, not SaaS
Two-sided businesses need supply and demand liquidity at the same time. The SaaS validator scores one side and calls the result a SaaS score. Use the marketplace validator instead — the chicken-and-egg assumption is a different problem entirely.
Reason 2
The product is a service with no recurring component
Consulting, agencies, and bespoke work do not fail because of renewal. They fail on capacity — the founder's hours. A SaaS validator will score distribution and ICP and ignore the constraint that actually binds. Score the capacity question separately.
Reason 3
The founder has no realistic distribution channel
The validator scores the channel the founder names. If the founder cannot name one — or the named channel has not been used before — the distribution score is fiction. Do distribution work first, then return to the validator.
Common mistakes
Four mistakes SaaS founders make on the way to a recurring-revenue cliff
These are the failure modes that show up most often in the SaaS validator reports. Each one produces a mid-60s score that feels reassuring and hides a real problem.
Reason 1
Discounting the launch price to "test demand"
Founders launch at $9/month to get traction, then assume $49/month is a future step. The launch price contaminates the willingness-to-pay signal. The first-month revenue at $9/month does not predict the renewal rate at $49/month. Test at the price the founder intends to charge, or the renewal signal will be fiction.
Reason 2
Treating free-trial signups as validation
Free-trial signups test the headline. They do not test payment intent and they do not test renewal. A 1,000-signup free trial that converts at 2% to paid is the same signal as a 20-signup free trial. The free trial cannot tell the founder whether buyers will renew.
Reason 3
Skipping the renewal signal
Founders who pre-sell 50 annual plans often stop measuring at the sale. The real signal is whether the customer is still using the product 90 days in. A churned annual customer is more expensive than a churned monthly customer, because the founder spent onboarding time they cannot recover.
Reason 4
Testing without a real channel
A landing page that gets 200 visitors from the founder's Twitter followers is not a validation metric. The visitors are warm. The validator's distribution score needs traffic from the channel the founder will actually use — not the channel the founder happened to use.
Worked example
A concierge validation that surfaced ICP drift
Hypothetical scenario, anonymized and illustrative only. Names, prices, and dates are fictional.
A first-time founder wants to build a $39/month dashboard for SaaS founders who run paid ads. The validator returns an overall score of 64 with a CAUTION label on the ICP dimension, and recommends a 30-day concierge at $39/month with five paying customers.
Reason 1
The founder recruits five SaaS founders from a paid-ads Slack community. Each agrees to a 30-day concierge at $39/month — a manual weekly report delivered through Notion and email.
Reason 2
By day 14, four of five customers are using the weekly report actively. By day 30, all five renew. The founder has spent $195 in cash and roughly 30 hours of work for one month of evidence.
Reason 3
By day 60, two customers have cancelled. By day 90, only one remains. The 30-day signal looked like recurring demand. The 90-day signal showed the report was useful but not load-bearing — customers went back to their spreadsheet once the novelty wore off.
Reason 4
The validator's ICP-narrowness flag had been correct: "SaaS founders who run paid ads" was too broad a buyer. The founder narrows the ICP to "B2B SaaS founders spending $5,000+/month on paid ads" and re-runs the validator. The second-round score climbs to 70, with the ICP dimension moving out of CAUTION.
Limitations
What this validator cannot tell the founder
A deterministic rule engine cannot answer every question a SaaS validation needs. The three below are the most important limits.
The actual churn rate
The validator names retention as a first-class dimension. It cannot predict whether a specific cohort will churn at 4% or 12% per month. Only a real customer cohort, observed over months, produces that number.
Defensibility or moat
The validator scores the product's fit for the named buyer today. It does not score whether the product will still be the buyer's choice six months from now, when competitors copy it or platforms change pricing.
Timing and market readiness
The validator assumes the named ICP exists and has the named problem today. It cannot tell the founder whether the market is ready for the category, or whether a regulatory shift will close the category tomorrow.
Sources
Where these ideas come from
The SaaS-specific assumptions — recurring willingness to pay, churn risk, ICP narrowness — are drawn from primary sources, not invented for this page.
Y Combinator, RFS: Vertical SaaS (2024)
Y Combinator's published wishlist for vertical SaaS names pricing-tier fit and ICP narrowness as the two make-or-break assumptions. The SaaS validator's audience section and Step 4 logic follow that framing.
a16z, "The SaaS Startup's Guide to Churn" (a16z.com)
The published essay distinguishes voluntary from involuntary churn and primary from secondary churn. The validator's churn dimension is calibrated to that taxonomy.
Paul Graham, "Default Alive or Default Dead?" (paulgraham.com)
The classic framing of the recurring-revenue cliff — the moment a SaaS must outrun churn with new acquisition. The validator's "recurring-revenue cliff" reason names that moment explicitly.
FAQ
Frequently asked questions about SaaS idea validation
Short answers, in the same vocabulary the SaaS pillar uses. The longer playbook lives in the linked article.
- How do I validate a SaaS idea?
- Run a free Startup MRI analysis first — it scores recurring willingness to pay, churn risk, ICP reachability, and pricing-tier fit in under 60 seconds. Then run five problem interviews using the Mom Test script from the Startup Validation hub, and ship a 30-day concierge (Notion template, Loom video, no-code MVP, or manually-operated service) at the business-model price. The concierge is the only experiment that produces a real renewal signal before you write code.
- Can I validate a SaaS idea without building it?
- Yes. The cheapest SaaS validation experiments are a problem interview, a landing-page test, and a 30-day concierge sold at the business-model price. Each takes one to two weeks, costs almost nothing, and produces evidence you can act on. The concierge is the step most SaaS founders skip — and the step most likely to surface the recurring-revenue cliff before you commit six months to a build.
- How do I test SaaS pricing before I build?
- Charge at the real recurring price, not a discounted launch price. A founder-friendly launch price contaminates the willingness-to-pay signal: if you can only get paid customers at a steep discount, the recurring willingness to pay at the business-model price is weaker than the business needs. The cheapest experiment is a 30-day concierge sold at the planned monthly or annual price, with five paying customers.
- What is the difference between a SaaS validator and a startup validator?
- A generic startup validator tests whether anyone will buy. A SaaS validator tests whether buyers will keep paying — recurring willingness to pay, churn past first renewal, and ICP narrowness are first-class dimensions. SaaS lives or dies on retention; a generic validator skips the retention question and treats first-payment intent as the signal.
- How long should SaaS validation take?
- Plan for two to six weeks of structured work. One to two weeks on problem interviews, one to two weeks on a landing-page or smoke test, and one to two weeks on a 30-day concierge sold at the business-model price. The concierge is the SaaS-specific step — and the one most founders skip.
- What is a SaaS MVP?
- A SaaS MVP is the smallest version of the product that lets you test the recurring-revenue assumptions. For most early-stage SaaS, the MVP is not the full product — it is a 30-day concierge (Notion template, Loom video, no-code MVP, or manually-operated service) sold at the business-model price to five paying customers. The concierge produces a renewal signal no landing page can fake.
- What is the cheapest way to test a SaaS idea?
- A problem interview, then a landing-page test, then a 30-day concierge at the business-model price. Total cost is roughly the founder's time plus a domain name and a payment processor. The concierge is the step that produces the recurring-revenue signal — the part no landing page or free trial can produce.
- Can a free trial validate a SaaS idea?
- Partially. A free trial tests curiosity — whether users will sign up and explore. It does not test whether they will pay, and it certainly does not test whether they will renew. The willingness-to-pay signal comes from a real payment at the business-model price; the renewal signal comes from observing that payment through a second billing cycle. Both signals must exist before the SaaS is validated.
SaaS validation summary
Summary
A SaaS idea is not validated by sign-ups alone. Test a narrow ICP, charge the intended recurring price, and look for renewal evidence before building the full product.
Run the SaaS validator on your idea
Five short questions. A SaaS-tuned report in under 60 seconds. The recurring-revenue signal a generic validator skips.