Gavel Gavel
Experts Guides Skills
Cited from real sources 5 min read Updated May 2026

A framework by Madhavan Ramanujam

Madhavan Ramanujam's 20/80 Willingness-to-Pay Axiom

The 20/80 willingness-to-pay axiom, from Madhavan Ramanujam's Monetizing Innovation and Scaling Innovation, is the single most useful pricing rule for software founders: 20 percent of the features you build drive 80 percent of the willingness to pay. The trap is that founders give the 20 percent away for free in the entry tier, then chase their tails building 80 percent of features that drive 20 percent of the willingness to pay. The fix begins with knowing which 20 percent is which, and then pricing the cohort that needs it specifically.

The axiom

20/80

In especially tech companies, 20 percent of what you build drives 80 percent of the willingness to pay. The irony is most founders give that 20 percent away for free.

Madhavan Ramanujam Lenny's Podcast Watch at 54:56

The framework

Founders give away the 20 percent unintentionally

The 20/80 axiom is a pricing diagnostic in disguise. It does not tell you what to charge. It tells you which features deserve to sit in which tier. Most SaaS pricing pages are built feature-by-feature: the team lists everything the product does and stacks it across three tiers in roughly equal weight. The result reads like a parts catalog and prices like one too.

Ramanujam's reframe: a small minority of capabilities drive almost all the willingness to pay. If those capabilities are in your free tier, you have given the most valuable thing away for the lowest price. If they are in your top tier with nothing else compelling around them, the buyer churns up the stack only when forced to. Either way, the pricing page does not capture the value the product creates. He puts the trap directly:

So what founders do is they put this, take this 20%, build it, put it out in the market almost for free, and then they're chasing their tails to build 80% stuff that's only driving 20% willingness to pay. If you have not been thoughtful about that, you've given the farm away unintentionally.

The fix is not to add features. It is to surgically move the high-willingness-to-pay 20 percent into the tier where the buyer who values it most lives. That tier gets repriced upward. The lower tiers get repackaged around the remaining 80 percent. Revenue per customer moves; feature roadmap does not need to.

How to apply it

Find the 20 percent, reprice the cohort

A 30-day sprint, not a quarterly project. The data is already in your CRM and product analytics.

  1. 1

    Survey 30 best-fit customers on the highest-value feature.

    Ask: of the 10 things our product does, which one would you keep if you had to give up the others? The pattern resolves in 30 responses.

  2. 2

    Cross-check the survey with product usage data.

    The features customers say they value should match what they actually open. If they do not, you have stated value and revealed value diverging — pay attention to revealed.

  3. 3

    Map your tier structure today.

    List every feature in every tier. Mark each one: drives WTP (20 percent), supports WTP (60 percent), or doesn't matter (20 percent). The first list is short.

  4. 4

    Move the high-WTP features upward.

    If a key driver is in the free or entry tier, that is the bug. Move it to a tier where the buyer who needs it lives. Expect short-term resistance from existing accounts; price-protect them for 12 months.

  5. 5

    Reprice the new cohort, not existing accounts.

    Apply the new pricing to fresh signups. Measure 30 days of conversion, ACV, and churn. If ACV moves up without conversion collapsing, the price was correctly under-set before.

  6. 6

    Plan the 80 percent roadmap differently.

    Stop building features that drive 20 percent willingness-to-pay just because they sound nice. Direct engineering effort toward extending the high-WTP capabilities for the segments that already pay for them.

  7. 7

    Communicate the value, not the change.

    Customers don't care that you ran a survey. They care that the tier they're on now has the thing they actually need. Lead the email with the value, not the renaming.

It should be the most valuable product and be thoughtful about what are you actually giving out as your early products. I think is key. That's the 20/80 axiom.
Ramanujam on early-product packaging Watch at 55:49

Boundary conditions

When it works, when it fails

Works best when

  • You have at least 30 customers to survey honestly
  • Product analytics expose what is actually used vs what is on the page
  • You can sequence repackaging across cohorts without confusing the market

Fails when

  • Founders treat the axiom as feature-count math instead of value math
  • You repackage everyone, not a fresh cohort — old customers churn on shock
  • The product has a single hero feature and 80 percent vapor; 20/80 still applies but tiering becomes harder

Alex Hormozi would push you to also test the upper anchor — the gasp test — to make sure the high-WTP tier is priced at the ceiling, not the comfortable middle. Patrick Campbell's cohort repricing playbook overlaps cleanly. The 20/80 axiom decides what goes in the tier; the gasp test sets where the tier lands.

The sources

Where Ramanujam discusses this

54:56
Timestamp

Lenny's Podcast — Pricing your AI product

The 20/80 axiom stated

20 percent of what you build drives 80 percent of the willingness to pay. But the irony is most founders give that 20 percent away for free.
55:21
Timestamp

Lenny's Podcast — Pricing your AI product

The trap most founders fall into

They take this 20 percent, build it, put it out in the market almost for free, and then they're chasing their tails to build 80 percent stuff that's only driving 20 percent willingness to pay.
55:49
Timestamp

Lenny's Podcast — Pricing your AI product

The fix begins with packaging

It should be the most valuable product and be thoughtful about what are you actually giving out as your early products.

Useful? Pass it to a founder still feature-stacking on three tiers.

Want the full playbook?

Get 98 product management frameworks.

31 frameworks 12 rules 47 heuristics & principles 49 operators

From Chandra Janakiraman, Stewart Butterfield, Ami Vora, and 46 more. Drop one .md into Claude, Cursor, or ChatGPT. Your AI cites practitioners, not guesses.

See the pack

Instant .md download · One-time purchase · No subscription

Related frameworks

Pricing

Van Westendorp Pricing

Rahul Vohra

How Superhuman priced at $30/mo using the Van Westendorp price sensitivity meter: four questions, real buyers.

Pricing

Gasp Pricing

Alex Hormozi

If the buyer doesn't gasp at the price, you didn't go high enough. Anchor, then walk down.

Retention

Churn Is a Delivery Problem

Alex Hormozi

People don't churn because the product is wrong. They churn because they never got the result. Fix onboarding, expectations, and demonstrated value.

Positioning

The Right Amount of Weird

Rory Sutherland

Familiar enough to be understood, strange enough to be interesting. Distinctiveness beats optimized logic at winning attention.

Apply this in a guide

Pricing guide

Van Westendorp pricing

The Van Westendorp Price Sensitivity Meter is four questions put to real buyers. Here's how to run it on your SaaS, how to read the chart, and where operators disagree on trusting the result.

Pricing guide

Pricing framework

A pricing framework is the sequence operators use to set a price on purpose: value metric, willingness to pay, anchor, package, ICP. Here's each step, cited, and where the experts disagree on freemium.

AI advisors guide

AI business advisor

An AI business advisor should cite named operators, show where they disagree, and remember your context, not hand you the generic average. Here's what to demand from one, and why generic ChatGPT falls short.

Pricing guide

SaaS pricing models

Flat, tiered, per-seat, usage-based, or freemium? The right SaaS pricing model follows from your value metric. Here's when each fits, cited to operators, and where they disagree on freemium vs free trial.

Pricing guide

SaaS pricing strategy

A SaaS pricing strategy sequences the moves over time: pick a value metric, price to willingness to pay, expand revenue, reprice on cohorts. Cited to operators.

Pricing guide

B2B SaaS pricing models

The B2B cut on pricing models: per-seat vs usage vs tiered vs hybrid, how to choose a value metric that expands the account, and why freemium misfires in B2B.

Pricing guide

Usage-based pricing

Usage-based pricing works when the metered unit is your value metric. The case for it, the real risk of bills buyers can't predict, and the hybrid that fixes it.

AI advisor guide

AI co-founder

An AI co-founder should bring cited operator frameworks to your hardest calls, remember your context, and show where experts disagree, not hand you the generic average of the internet.

AI advisor guide

ChatGPT for startups

ChatGPT is useful at a startup for drafts, code, and research, but weak on the decisions that move the company: pricing, positioning, and product-market fit. Here's the cited operator answer to use instead.

AI advisor guide

Why ChatGPT is generic

ChatGPT gives generic startup advice for four structural reasons: the averaged internet, no retrievable citations, built-in agreeableness, and no memory of your context. Here's what a cited answer looks like instead.

Pricing guide

Sanity-check my pricing

Before you commit a price, run five checks: value metric set, priced to willingness-to-pay not cost, anchored high enough to gasp, the high-WTP 20% protected, and the ICP that renews.

AI advisor guide

Expert frameworks for founders

One canonical operator framework per founder decision: positioning to Dunford, pricing to Ramanujam, PMF to Sean Ellis, first customers to Hormozi. The cited map, applied to your situation.

AI advisor guide

AI advisor for startups

Pre-PMF startup advice is the opposite of scaling advice, so an AI advisor must know your stage: Sean Ellis and Paul Graham before fit, Hormozi and Ramanujam after. The cited, stage-aware map.