## TL;DR
A framework lecture on how to think about pricing for B2B SaaS — moving from cost-plus pricing to value-based pricing, with three case studies showing 2-3x price increases without churn.

## Outline

### Section 1: Why most pricing is wrong
Most SaaS founders price by intuition or by undercutting the next-cheapest competitor. Both anchor on cost or competitor; neither anchors on customer value. This caps revenue, signals "cheap" in the buyer's mind, and creates ongoing internal arguments about price changes.

### Section 2: Three pricing models
1. Cost-plus — Add a margin to cost. Easy to defend internally; ignores the buyer entirely.
2. Market-based — Match competitor pricing. Easy to defend; converges everyone to the same number.
3. Value-based — Price as a fraction of the value created for the customer. Hard to defend internally; produces the highest revenue.

### Section 3: How to do value-based pricing
Four-step framework:
- Step 1: Quantify the value (in dollars saved or earned for the customer).
- Step 2: Decide what fraction of that value to capture (10-20% is a healthy range).
- Step 3: Set the price.
- Step 4: Validate via customer conversations, not surveys.

### Section 4: Case studies
Three companies (anonymised) shared with year-over-year pricing graphs and customer-loss/retention metrics post-increase.

### Section 5: Q&A
(Brief — only mentioned a couple of recurring questions.)

## Key concepts (with definitions)
- **Cost-plus pricing**: Setting price by adding a fixed margin to the cost of production.
- **Value-based pricing**: Setting price as a fraction of the dollar value created for the customer, not based on cost or competitor.
- **Anchor**: The first number or comparison a buyer is exposed to, which shapes their sense of what's "expensive" or "cheap".
- **The 10-20% rule**: A heuristic — capture 10-20% of the value you create. Below 10% and you're underpriced; above 30% and customers feel exploited.
- **Price-walk**: Incrementally raising prices while measuring retention and customer-acquisition impact — used as a discovery tool, not just a revenue play.

## Illustrative examples
• A B2B analytics company that raised prices 2.5x by quantifying that they saved customers 14 hours/week of analyst time — illustrates "quantify the value first".
• A workflow tool that increased ACV from $5K to $18K by repricing per-seat → per-outcome (number of successful workflows run) — illustrates "the wrong unit of pricing".
• A company that lost 40% of customers after a price increase — illustrates "price-walking" gone wrong (too large a jump, applied to existing customers).

## Active recall questions
1. If a customer says "your competitor charges half as much", what does value-based pricing say you should do? (Hint: not "match them".)
2. A SaaS tool saves a customer $200K/year in operational cost. What's a reasonable price range for that tool, using the 10-20% rule?
3. Why does the lecturer say cost-plus pricing leads to "ongoing internal arguments about price changes"? Can you reproduce the reasoning?
4. When would market-based pricing actually be the right choice? (The lecture acknowledged at least one case.)
5. What's the difference between "validating price via surveys" and "validating price via customer conversations", and why does the lecturer prefer the latter?

## If you remember only 3 things
1. Most SaaS pricing is anchored on cost or competitor; both leave money on the table compared to anchoring on customer value.
2. The four-step framework: quantify value → decide fraction (10-20%) → set price → validate via conversations.
3. Price-walking lets you discover the ceiling; jump-walking (40%+ increases applied to existing customers) destroys retention.