Spoke 5 of 7

SaaS Pricing Strategy Validation: How to Set a Price You Can Defend

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.

Why most founder pricing is wrong

Most founder pricing decisions follow this process:

  1. Look at competitor prices.
  2. Average them.
  3. Subtract 20% to “be competitive.”
  4. Pick a round number.

This is not strategy. It’s matching. It leaves money on the table when you’re underpriced and chases buyers away when you’re priced for the wrong segment.

Real pricing validation produces a number with three properties:

  • It maps to a defined buyer’s willingness to pay (you have evidence, not vibes).
  • It clears your unit economics (you make money at this price, not just revenue).
  • You can defend it under pushback (when a prospect says “that seems expensive,” you have a sentence that works).

This guide is the validation discipline that produces that number.

The four numbers

Every pricing decision rests on four numbers. Know all four before you set a price.

  1. 1
    Demand-side

    SOM revenue at price X

    Does the realistic-capture math clear your minimum viable business?

    (SOM buyer count) × (1-5% conversion) × (price X) = year-1 SOM revenue. If this number doesn't cover your minimum business threshold, the price or the SOM is wrong.

  2. 2
    Voice-of-customer

    Willingness-to-pay range from interviews

    What did the buyer spend last time they had this problem?

    20+ Mom Test interviews. Past-spend data beats hypothetical "would you pay" answers. The pattern in their spending bounds your acceptable price band.

  3. 3
    Quantitative

    Van Westendorp band

    Four pricing questions, plotted on a chart, define the band.

    Survey 20-50 buyers with the four classic price-perception questions. The intersection points produce a Lower Bound, Upper Bound, Optimal Price Point, and Indifference Price Point.

  4. 4
    Unit economics

    LTV/CAC at price X

    Does the business actually scale at this price?

    LTV (price × average customer lifetime) divided by CAC (S+M spend / new customers). LTV/CAC > 3 is the venture-scale threshold. Below means raise the price, lower CAC, or accept it as a lifestyle business.

1. SOM revenue at price X

How much revenue does your serviceable obtainable market produce if everyone in it converted at price X?

(SOM buyer count) × (realistic conversion rate, 1-5%) × (price X) = SOM revenue at X

If SOM revenue at your candidate price doesn’t clear your minimum viable business threshold, the price is wrong (or the SOM is). See market research for SOM math.

2. Willingness-to-pay range from interviews

What price range do real buyers describe as acceptable? Get this from 20+ interviews with the Mom Test discipline applied. The question that works: “When you last tried to solve this problem, what did you spend or budget?”

If the typical answer is “$10K/year on a competitor,” you can charge $100-300/month (with a path to $500+). If the typical answer is “nothing, I just deal with it,” you’re not validated. The problem isn’t painful enough.

3. Van Westendorp band

Run the Van Westendorp Price Sensitivity Meter on 20-50 buyers. The four-question survey produces:

  • Lower bound (Point of Marginal Cheapness): below this, buyers doubt quality
  • Upper bound (Point of Marginal Expensiveness): above this, buyers won’t even consider
  • Optimal Price Point (OPP): where curves intersect, the price most buyers find acceptable
  • Indifference Price Point (IPP): where “cheap” and “expensive” curves cross, the price where buyers feel neither over- nor underpaying

The Van Westendorp band is wider and more honest than any single number. Use it as a constraint: your price has to live inside this band.

4. Unit economics at price X

For SaaS, the question is: at price X, is LTV/CAC > 3?

  • LTV (lifetime value) = price × average customer lifetime (in months)
  • CAC (customer acquisition cost) = sales + marketing spend / new customers

If LTV/CAC isn’t 3+ at your candidate price, your business doesn’t scale. Either raise the price, lower CAC (better channels, better conversion), or accept that the business is a lifestyle business, not a scaling one. All three are valid. Knowing which you’re building is the discipline.

Test 3-5 prices, not 1

The most common pricing-test mistake is testing one price. A single-price test tells you whether THAT price works, not whether you’re leaving money on the table or chasing buyers away.

Test a 3-5 price spread, typically following a geometric progression:

TierPriceTest purpose
Anchor low$9/moFloor. Too cheap to take seriously?
Mass$29/moVolume play
Premium$79/moWhere most SaaS lives
Enterprise lite$199/moTest if buyers exist in your space
Enterprise$499/moSanity check

Don’t ship all 5. The point of the test is to find the elasticity curve so you can pick 1-3 final tiers with confidence.

A common pattern in the data: conversion drops off a cliff between $29 and $79, suggesting your buyer pool segments at $50/month. You then launch a $29 tier (mass) and a $79 tier (premium) and skip the $9 tier (too cheap, attracts wrong customers) and the $199+ tiers (no buyer pool yet).

Pricing model matters more than price

Before obsessing over the number, validate the model.

Per-seat (Slack, Notion, Linear)

  • Pros: scales naturally with customer; predictable
  • Cons: friction at adoption. “I have to budget for the whole team”
  • When to use: B2B where the buyer = the user (team productivity tools)

Per-usage (Stripe, AWS, OpenAI API)

  • Pros: aligns price with value delivered; no waste
  • Cons: hard to budget; sticker shock on heavy users
  • When to use: when value scales with usage (infrastructure, API)

Flat / tiered (Basecamp, ConvertKit, Webflow)

  • Pros: predictable billing; easy to understand
  • Cons: leaves money on the table for power users; alienates light users
  • When to use: when usage doesn’t vary much across customers

Freemium (Notion, Loom, Calendly)

  • Pros: massive top-of-funnel, viral potential
  • Cons: 95-97% of free users never convert; requires PLG mechanics
  • When to use: network effects or virality; marginal cost near zero

Free trial (most SaaS)

  • Pros: high conversion (10-30%); buyer sees value before paying
  • Cons: requires fast time-to-value; trial expiration nudge mechanics
  • When to use: default for most B2B SaaS

Pick the model based on your buyer’s purchase behavior and your unit economics. Get the model right; tune the number later.

The willingness-to-pay interview script

Five questions, in this order, with at least 15 target buyers:

  1. “When you last tried to solve [problem], what did you do?”
  2. “How much did it cost. In money, time, or attention?”
  3. “If I told you there was a tool that did X for $Y/month, what would your first reaction be?”
  4. “What would have to be true for you to pay $Y/month for this?”
  5. “How would you justify this expense to [boss / partner / yourself]?”

The signal isn’t the price number they give. It’s question 5. The justification model. If they can articulate the justification cleanly, they’re a real buyer at that price. If they can’t (“I dunno, it just seems like a lot”), they’re not.

Run 15-20 of these. Patterns emerge. The patterns name your price.

Common mistakes

1. Picking a price by averaging competitors. That’s matching, not strategy. Competitor pricing is one input among many.

2. Setting price once and never revisiting. Pricing is an ongoing decision, not a launch one. Annual review minimum.

3. Testing one price point. You learn nothing about elasticity. Test a spread.

4. Asking “how much would you pay?” Predicts nothing. Replace with past-spend and justification questions.

5. Skipping unit economics. A price that doesn’t clear LTV/CAC > 3 is a price you can’t scale at. Doesn’t matter how validated the willingness-to-pay is.

6. Free tier by default. Free tiers should be a deliberate choice, not a default. Most products that ship a free tier never recover from the conversion math.

What ShipFit does at this stage

ShipFit Stage 6, How to Charge? Pricing Position chart placing your candidate price against competitors across Value, Premium, Budget, and Overpriced zones, with the recommended Optimal Price Point.

Stage 6 of the 9-step playbook is How to Charge?. Pricing validation. The output is your Pricing Position: where your candidate price sits in the competitive landscape, scored against four zones.

ZoneWhat it means
Value ZoneYou’re priced below most competitors but above the cheap end. Easy entry, room to raise.
Premium ZoneAbove competitors. Defensible only if you have a clear differentiator the buyer recognizes.
Budget ZoneCheapest in the market. Signals “not serious” to enterprise buyers. Volume play only.
Overpriced ZoneAbove the Premium Zone with no matching differentiator. Buyers won’t even consider you.

The output is a Pricing Position chart placing your candidate price against the Value / Premium / Budget / Overpriced zones, plus an Optimal Price Point recommendation drawn from the Van Westendorp curves.

The full Stage 6 output:

  1. Van Westendorp questions phrased for your buyer + product, with the four-curve diagram and the OPP / IPP / PMC / PME labels.
  2. A pricing position chart placing your candidate price against the competitor pack.
  3. A pricing model recommendation (per-seat, per-usage, tiered, freemium, etc.) keyed to your buyer profile.
  4. Tiering guidance with the “what a prospect will say” framing — the objection you should be ready to answer at the price you’ve chosen.

Stage 6 is the most-skipped stage in founder workflows. It’s also the highest-leverage one for revenue per customer. Don’t skip it.

The bottom line

Pricing isn’t a number; it’s a decision made up of four numbers (SOM revenue, WTP range, Van Westendorp band, unit economics) and one structural choice (model). Real pricing validation produces a price you can defend, a model that scales, and a unit-economics story that makes the business work. Founders who do this work charge 2-5x what their peers charge for similar products. That gap is mostly discipline, not market positioning.

Related frameworks

Frequently asked questions

What is SaaS pricing validation?
The process of generating evidence. Before you launch. That your target buyer will pay your proposed price for your proposed product. It's the difference between 'this feels like a $29/month product' (a guess) and 'these 20 target buyers told us their pain threshold for this problem is $19-49/month and 4 of them put down a deposit at $29' (validation). Pricing validation typically uses three methods together: Van Westendorp Price Sensitivity Meter, willingness-to-pay interviews, and pre-order/deposit testing.
What is the Van Westendorp Price Sensitivity Meter?
Peter van Westendorp's 1976 method, still the most-evidence-based pricing-research tool ever published. Ask 4 questions of 20-50 buyers: at what price would the product be (1) so cheap you'd doubt the quality, (2) cheap but acceptable, (3) expensive but worth it, (4) too expensive to consider. Plot the answers on a cumulative percentage chart; the intersection points define your acceptable price band. Not perfect, but miles ahead of guessing. Full breakdown on the [Van Westendorp framework page](/frameworks/van-westendorp).
How many price points should I test?
Test 3-5 candidate prices, not 1. A single-price test only tells you whether THAT price works; it doesn't tell you whether you're leaving money on the table or chasing buyers away. A 3-5 price spread (e.g., $19 / $29 / $49 / $99 / $199) lets you see conversion drop-offs and find the elasticity curve. Most founders test one price too low, anchor low, and miss revenue they could have captured.
What's the difference between price and pricing model?
Price is the number ($29/month). Pricing model is the structure (per-seat? per-usage? flat? freemium?). The model matters more than the number for SaaS because it determines who can buy you (a freemium model expands your buyer pool 10x but limits ARPU; a per-seat model scales with the customer but raises adoption friction). Validate the model before you obsess over the number. The model is structural and hard to change post-launch; the number is tunable forever.
Should I offer a free tier?
Yes if your product needs network effects, virality, or PLG-style self-serve adoption. No if your buyer is enterprise IT (free tiers signal 'not serious' to those buyers). Yes if your marginal cost per user is near-zero. No if it isn't (storage-heavy products often can't sustain meaningful free tiers without losing money). The 'free tier yes/no' question is one of the biggest pricing-model decisions and most founders default to 'yes' without doing the math.
How do I do willingness-to-pay interviews without leading questions?
Never ask 'how much would you pay for this?' (predicts nothing). Instead ask: 'When you last tried to solve this problem, what did you spend?' followed by 'What would have to be true for you to pay $X/month for this?' followed by 'At $X, how would you justify this to your boss / partner / yourself?' The buyer's answer reveals their cost-justification model, which is what actually predicts purchase. If they can't articulate the justification, they won't buy at any price.
When should I raise prices?
Three signals: (1) >70% of prospects don't blink at your price during sales conversations (you're underpriced), (2) competitor prices in your space have moved up, (3) you've added meaningful capability since your last pricing review. Most SaaS companies raise prices every 18-24 months in modest increments (10-20%) with new logo customers only. Existing customers grandfathered. Annual review minimum. Pricing isn't a launch decision; it's an ongoing one.
Related on ShipFit

Keep exploring

Framework
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.

Framework
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.

Spoke
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.

Spoke
Validation with AI

Default-prompted AI is a slop machine: agreeable, plausible-sounding, useless for validating an idea. Here's how to use AI for the parts where it actually adds signal, and where to keep it out of the way.

Calculator
CAC / LTV ratio calculator

Does each customer make you money? Or cost you money?

Q&A
How do you validate a business idea?

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 founders
indie hackers

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.

Comparison
Buildpad

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.

Glossary
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.

Ready to make your next product a success?

9 decisions between your idea and a product worth building.

No credit card required.

Try an example: