Run the 9-step pre-code playbook with three SaaS-specific tweaks. (1) Validate the pricing MODEL before the price NUMBER; the model is hard to change post-launch. (2) Apply the LTV/CAC > 3 unit-economics gate. (3) Use the Superhuman PMF Engine post-launch as your canonical PMF measure. Otherwise: defined buyer, real pain, defensible angle, behavioral evidence, defended price, scoped V1.
The fast version
Validate a SaaS idea by running the 9-step pre-code playbook with three SaaS-specific tweaks:
- Validate the pricing MODEL before the price NUMBER. Per-seat vs per-usage vs flat vs freemium structurally affects who can buy and how fast you scale. The model is hard to change post-launch; the number is tunable forever.
- Apply the LTV/CAC > 3 gate. SaaS unit economics are testable pre-launch from your candidate price + reasonable retention + reasonable CAC. If LTV/CAC isn’t 3+ at your candidate price, the business doesn’t scale; either raise price, lower CAC, or accept it’s a lifestyle business.
- Use the Superhuman PMF Engine post-launch. SaaS is unusually well-suited to the Sean Ellis “very disappointed” measurement because users have continuous workflow integration. 40%+ very disappointed = likely PMF. Below = not yet.
The three SaaS-specific tweaks, in detail
1. Pricing model matters more than the number
| Model | When to use | Failure mode |
|---|---|---|
| Per-seat (Slack, Notion, Linear) | B2B where buyer = user (team productivity) | Friction at adoption; “I have to budget for the team” |
| Per-usage (Stripe, AWS, OpenAI API) | Value scales with usage (infrastructure, API) | Sticker shock on heavy users; hard to budget |
| Flat / tiered (Basecamp, ConvertKit) | Usage doesn’t vary much across customers | Leaves money on the table; alienates light users |
| Freemium (Notion, Loom, Calendly) | Network effects or virality; marginal cost ~0 | 95-97% of free users never convert |
| Free trial (most SaaS) | Default for B2B; buyer needs to see value before paying | Requires fast time-to-value |
Pick based on your buyer’s purchase behavior + your unit economics. Get the model right; tune the number later.
2. The LTV/CAC > 3 gate
SaaS lets you compute unit economics pre-launch:
- LTV = price × average customer lifetime (in months)
- CAC = sales + marketing spend / new customers acquired
If your candidate price is $29/mo, average lifetime is 24 months, then LTV = $696. If your CAC is $250, LTV/CAC = 2.78, below the 3 threshold. The business works in spreadsheet, breaks in reality (because LTV is usually optimistic and CAC usually higher than you think).
If LTV/CAC < 3 at your candidate price, options:
- Raise the price (but defend it via Van Westendorp + WTP interviews)
- Lower CAC (better channel mix, better conversion, virality)
- Accept it as a lifestyle business (still valid, just not venture-scale)
3. Post-launch: Superhuman PMF Engine
Once you have 40+ active users, run the Superhuman PMF Engine:
“How would you feel if you could no longer use this product?” Very disappointed / Somewhat disappointed / Not disappointed.
40%+ very disappointed = likely PMF. Run quarterly; track the trend. The score moves as you ship.
Everything else is the same as non-SaaS
| Step | What’s the same |
|---|---|
| Worth Building? | Same SOM math; same why-now requirement |
| Who Pays? | Same persona discipline (Buyer Persona Canvas) |
| What Hurts? | Same Mom Test interviews |
| How to Win? | Same 7 Powers gate |
| What’s V1? | Same MoSCoW + ICE; same Differentiator / Delight / Operational buckets |
| Will They Pay? | Same Fake Door + signal-tier framework |
| How to Launch? | Same channel-message-buyer triangulation |
The 9-step process is product-type-agnostic. SaaS just lets you measure unit economics + PMF more cleanly than physical products or marketplaces.
Common mistakes specific to SaaS validation
1. Picking the price before the model. Order matters: buyer → model → number. Founders who pick the number first end up with model/buyer mismatches.
2. Skipping unit-economics math. “We’ll figure out CAC later” is the most expensive sentence in SaaS. Pre-launch CAC estimation is rough but bounded; post-launch surprise is unbounded.
3. Free tier by default. Free tiers should be deliberate. Most products that ship a free tier don’t recover from the conversion math.
4. Counting signups as PMF evidence. Signups don’t predict revenue; the Sean Ellis 40% does. Don’t conflate.
5. Validating against “B2B SaaS founders” as your buyer. Too broad. Pick a vertical, a stage, a specific role. Generic = unreachable + unmessageable.
Further reading
- The 9-step playbook, the master pillar.
- Pricing validation spoke, the deeper SaaS pricing workflow.
- Superhuman PMF Engine, the canonical post-launch PMF measure.
- Van Westendorp pricing, the framework for the price band.
Related
The Mom Test
The Mom Test is Rob Fitzpatrick's framework for customer interviews that generate real signal. Not praise. Three rules, applied step-by-step, with examples.
Van Westendorp Price Sensitivity Meter
The Van Westendorp framework uses 4 questions to surface a defensible price range for any product. Here's how to run it, interpret results, and avoid the cheapest mistakes.
Superhuman PMF Engine
Rahul Vohra's framework for measuring and engineering product-market fit. The 40% rule, the high-expectations customer, and the four-step loop to actually move the score.
7 Powers
The 7 Powers framework names every defensible advantage a business can have. If you can't pick one for your startup, you're betting on a fair fight.
Idea Validation
Most founders confuse idea validation with idea-receiving-encouragement. The two have nothing in common. Here's what real validation looks like, and the four methods that actually produce it.
Pricing Validation
Most founders pick a price by looking at competitors and shaving 20%. That's not pricing strategy, it's matching. Real pricing validation produces a price you can defend against your own ego and your buyer's pushback.
MVP Scope
Most founders ship an MVP that's actually V1.3 with bugs. Real MVP scoping cuts ruthlessly until you can name the one hypothesis V1 proves, and ships a product that tests it.
Product-Market Fit
The state in which a product satisfies a strong market demand such that demand pulls the product through the company. Coined by Marc Andreessen in 2007. Most rigorous measure: 40%+ of active users would be 'very disappointed' to lose the product (Sean Ellis test).
MVP (Minimum Viable Product)
The smallest version of a product that lets you test a falsifiable hypothesis about a buyer's behavior. Coined by Frank Robinson in 2001; popularized by Eric Ries in 'The Lean Startup' (2011). Not a stripped-down launch product. A learning tool.
Frequently asked questions
What's different about validating SaaS vs other products?
Should I do a free tier?
Can I validate a B2B SaaS with just landing-page conversion?
How do I validate pricing for SaaS?
What if my SaaS idea is just slightly different from existing ones?
Keep exploring
The 9-step playbook from market verdict to ship-ready spec.
The Mom Test is Rob Fitzpatrick's framework for customer interviews that generate real signal. Not praise. Three rules, applied step-by-step, with examples.
The Van Westendorp framework uses 4 questions to surface a defensible price range for any product. Here's how to run it, interpret results, and avoid the cheapest mistakes.
Most founders confuse idea validation with idea-receiving-encouragement. The two have nothing in common. Here's what real validation looks like, and the four methods that actually produce it.
Most founders pick a price by looking at competitors and shaving 20%. That's not pricing strategy, it's matching. Real pricing validation produces a price you can defend against your own ego and your buyer's pushback.
Does each customer make you money? Or cost you money?
Run nine framework-backed decisions in order before writing code: define the buyer, prove the pain is painful, name the winning angle, scope V1 to the smallest test of the hypothesis, get behavioral evidence (paid pre-orders, signed letters of intent, or credit cards on file from a Fake Door Test), then ship. Most failed startups skipped at least three of those nine. Plan to spend two to four weeks on this. It saves six to nine months of building the wrong thing.
For indie hackers who've wasted months on dead ideas. ShipFit forces 9 decisions before you write a line of code. Proven frameworks, exports to Cursor.
If you want a conversation partner, Buildpad. If you want to stop researching and ship, ShipFit. Both solve different problems for different founders. Don't pick on hype.
Ready to make your next product a success?
9 decisions between your idea and a product worth building.