Value metrics, pricing models, packaging, and the expansion mechanics behind durable revenue growth.
8 domains · 27 rules.
MODEL · PRICE · PACKAGE · GROW
Monetization is the system by which product value is captured as revenue — not a pricing page, not a Stripe integration, not a decision made at launch and revisited only when sales complains. First-launch prices reflect cost guesses and competitive anxiety, not customer value. Pricing set at launch reflects your first ten customers, not your product-market fit.
The value metric is the axis your pricing scales on. Get it right and alignment is automatic: as customers get more value, they pay more, without negotiation. Get it wrong and you create perverse incentives — customers minimize the billing unit to reduce costs, hiding real engagement and making expansion nearly impossible. The value metric is the single most consequential pricing decision in SaaS.
Flat rate, per-seat, usage-based, and feature-tiered pricing create different incentives for customers and different revenue dynamics for your company. The mistake is picking a model because it is industry-standard or easy to implement, without asking whether it aligns with how customers derive and grow value. Every pricing model is a structural bet on how your customers evolve over time.
One price, all features, all customers. This maximizes simplicity and minimizes friction but caps revenue: your highest-value customer pays the same as your lowest. Flat rate works when the product has a narrow use case and no natural expansion dimension. It fails when customers vary meaningfully in scale, team size, or usage intensity.
Every added seat should create proportional value. Slack, Figma, and GitHub fit this model because the product is fundamentally about teams working together. Per-seat pricing fails when one power user serves a large group, when customers share accounts to reduce their bill, or when usage-per-seat is wildly uneven across the team.
Consumption pricing is correct when value scales directly with usage. It requires strong cost modeling (margin at every usage tier), investment in a free tier or trial to reduce adoption friction, and billing dashboards so customers don't face surprise invoices. Without these, usage-based pricing produces high churn from sticker shock and unpredictable annual ARR.
A platform fee provides revenue predictability and signals product commitment. A usage or seat component captures expansion naturally as customers grow. Most mature SaaS companies land on a hybrid model — base subscription for the core product, usage tiers for consumption-driven features. Starting with a pure model and migrating to hybrid is harder than designing for it from the start.
A pricing page with three tiers and a "Most Popular" badge is not packaging — it is a layout. Packaging is the decision about which features belong in which tier, how the tiers force self-segmentation, and where the natural upgrade trigger lives. The failure mode is feature-stuffing the top tier to justify the price while making the bottom tier so limited it converts nobody. Good packaging creates a natural upgrade moment — one your customer initiates, not one you have to sell.
Free is not a marketing tactic — it is a conversion mechanism. Freemium and free trials serve different purposes and attract different buyer behaviors. Conflating them produces a product that is simultaneously too generous to convert and too limited to grow. The question is never "should we have a free tier?" — it is "what behavior are we trying to drive, and does this design accomplish it?" Free is a product decision, not a pricing decision.
Gross Revenue Retention measures what you keep. Net Revenue Retention measures what you keep plus what you grow. The difference compounds exponentially: at 95% NRR, your existing base shrinks every year and you must run to stand still; at 120% NRR, each cohort doubles in revenue over time without acquiring a single new customer. Expansion revenue is not a sales motion — it is a product design decision.
At 85% GRR, you lose 15% of your revenue base every year from churn and downgrades. New customer acquisition must outpace this erosion just to show growth. Improving GRR by 5 points is usually worth more than increasing new ARR by 20%. Churn investigation — by cohort, by segment, by product usage — comes before any expansion motion.
At 115% NRR, each cohort grows in revenue each year without a single new sale. Expansion motions that live in the product — usage limit nudges, team invitation flows that trigger plan upgrades, in-product dashboards that make seat utilization visible — outperform CSM-driven expansion at scale. The best NRR improvements come from making the expansion moment obvious and frictionless in the product itself, not from adding a renewal call cadence.
Seat expansion happens as teams grow — design onboarding to drive team activation, not just individual activation. Usage expansion happens as customers go deeper — usage limits and upgrade nudges at the point of friction drive this. Cross-sell is a separate product motion requiring a second product with independent value. Treating all three as a single "expansion" motion means investing in none of them effectively.
Raising prices is one of the highest-leverage actions in SaaS — and one of the most avoided. A 10% price increase on your existing customer base is often more impactful than adding 20 new customers. The avoidance is rational: teams have rarely done it and fear churn. In practice, well-executed price increases with appropriate notice produce churn under 5%. The price increase you are afraid to have is usually the one that would have been fine.
Pricing ownership is almost always ambiguous in SaaS companies. Product says it's a business decision. Finance says it's a product decision. Sales says both are wrong. The result is a pricing page nobody reviews, prices that haven't changed in three years, and no process for incorporating market signal. NRR is the scorecard for your monetization model. Everything else is a leading indicator.
Conversion rate, ACV, payback period, and expansion rate are inputs. Net Revenue Retention is the output. A product with 115% NRR and mediocre acquisition metrics is a stronger business than one with 40% conversion and 85% NRR. Optimize the retention and expansion engine first. Acquisition pours water into a bucket — NRR determines how big the bucket gets.
Pricing orphaned across product, sales, and finance gets reviewed only in crisis — when a competitor undercuts or deal flow degrades. Name one owner (Head of Product, VP Revenue, or a dedicated monetization PM), schedule a quarterly review, and instrument the metrics that feed it: willingness-to-pay research, deal velocity by plan, and expansion rate by cohort. Without a review cadence, pricing only changes reactively.
Pricing is testable. New-customer pricing cohorts, landing page copy, tier structure, trial length — all of these can be measured with a control and treatment. Teams that run pricing experiments monthly improve NRR faster than teams that change pricing once a year after a board deck. Treat the pricing page as a product surface with instrumented metrics and a testing cadence.
"I'm losing deals because of price" is a data point, not a decision. It may mean pricing is too high; it may mean the team is selling to the wrong segment; it may mean value communication is weak. Systematically collect loss analysis — who lost, at what price point, to whom, at what deal size — and let the data drive pricing decisions. The loudest voice in the room is not the most representative voice in the market.
Price what you build. Build what you price. They are the same decision.
The value metric is the single most consequential choice in SaaS pricing.
Free is a conversion mechanism — not a marketing tactic.
NRR above 100% means your existing customers fund growth.
The price increase you are afraid to have is usually the one that would have been fine.