How to validate a SaaS idea — step-by-step framework

Why SaaS validation needs its own framework

Generic idea validation misses the signals that specifically kill SaaS businesses: category saturation against well-funded incumbents, defensibility that survives a feature-copying competitor, churn assumptions that quietly erode a seemingly-healthy MRR chart, and pricing that doesn't match what comparable tools already charge.

Step 1 — Check category saturation

Count direct competitors honestly. Markets with 5–15 established players can still support a focused, differentiated entrant. Markets with 50+ players — generic project management, generic CRM — require an extremely specific wedge to have any realistic shot, regardless of how good your execution is.

Step 2 — Confirm defensibility beyond features

Ask specifically: what stops a well-funded competitor from shipping this exact feature set within six months? Feature-level differentiation alone rarely survives that timeframe. Real moats in SaaS: proprietary data that compounds with usage, deep workflow integration that's costly to rip out, or regulatory complexity that takes competitors a year or more to navigate.

Step 3 — Benchmark pricing against comparables

Find 3–5 tools your buyer would consider comparable and note their published pricing. Pricing significantly below the category average is a red flag, not a competitive advantage — it usually signals you're underselling the value or haven't validated what buyers actually pay for this category.

Step 4 — Model churn honestly

SMB SaaS commonly sees 3–7% monthly churn; enterprise SaaS is typically under 1%. Model your business against category-typical churn, not an optimistic best case — churn assumptions that are too rosy make an unviable business look viable on paper until the actual numbers arrive.

Step 5 — Test with a landing page before building

Before writing product code, build a landing page describing the specific outcome your SaaS delivers, with a waitlist or pre-order mechanism. This tests both demand (do people sign up?) and pricing sensitivity (do they proceed at your stated price point?) at a fraction of the cost of building the actual product.

Step 6 — Get 3 design partners committed

Before building the full product, secure three early customers explicitly committed to using a rough first version and giving structured feedback. This validates that real buyers — not just landing-page signups — will change their workflow to adopt your tool.

Score the result

Once you've worked through these steps, run your specific idea through the SaaS-specific validator to see a Ship, Fix, or Skip verdict with reasoning tuned to the signals that matter most for SaaS specifically — defensibility, competition density, and monetisation realism.