SaaS Pricing Strategy & Optimization

The four primary SaaS pricing models: Per Seat (User-Based): customers pay based on the number of users accessing the product. Revenue scales predictably with the customer's organization size. Risk: customers minimize seat count by sharing logins or using nominal accounts, undermonetizing actual organizational usage. Best for: horizontal collaboration and workflow products where individual user value is measurable. Usage-Based (Consumption): customers pay based on their consumption of a specific metric — API calls, data processed, emails sent, workflow executions. Revenue scales with customer value delivered (high alignment). Creates expansion revenue automatically as usage grows. Risk: revenue predictability is harder for both the company (ARR is partially variable) and the customer (budgeting is difficult). Best for: infrastructure, data, and metered services where usage is the most natural value metric. Feature-Tiered Flat-Rate: customers choose a plan based on feature access (Basic, Professional, Enterprise) with a fixed monthly fee. Simple to understand and budget. Risk: poor value capture — high-usage customers may pay the same as low-usage customers on the same plan. Best for: products with clear feature differentiation across customer segments that don't fit a seat or usage model. Hybrid (most common at scale): combining seat-based pricing for the core product with usage-based billing for consumption-intensive features — capturing both the organizational breadth value (seat count) and the activity depth value (usage volume).

Willingness-to-pay (WTP) research is the empirical foundation for pricing decisions — guiding whether to raise prices, how to structure tiers, and what features can command premium pricing. Research methods: Van Westendorp Price Sensitivity Meter: a four-question survey asking customers: at what price would [product] be so cheap you question its quality? At what price would it be good value? At what price would it be getting expensive but acceptable? At what price would it be too expensive? The intersection of responses defines the "acceptable price range." Gabor-Granger technique: presenting respondents with sequential prices (starting randomly in the middle of the range) and asking whether they would buy at that price — estimating the demand curve and revenue-maximizing price. Conjoint analysis: presenting respondents with feature-and-price configurations and asking which they prefer — decomposes the value attributed to individual features and the price premium each feature can command. Behavioral pricing signals: analyze the current plan distribution (what percentage of customers are on each plan?) and the conversion rate from each free or trial plan to each paid plan — these behavioral signals reveal current market acceptance of price points without requiring surveys. Product Ops partners with Revenue Ops to run WTP research annually and after significant product capability expansions.

Price increases for existing customers are operationally and relationship-sensitive — the execution approach determines whether the increase is net-positive or net-negative for NRR and retention. Execution principles: Advance notice: provide existing customers with a minimum of 90 days advance notice of price changes (120 days is preferred for enterprise accounts). Early notice demonstrates respect for the customer's budget planning process and gives them time to seek approval for the increased spend before the invoice arrives as a surprise. Grandfathering window: offer existing customers the ability to lock in their current price for an extended period (12–24 months) if they commit to a longer contract term. This converts an uncomfortable price increase into an expansion conversation — "your price is changing in 90 days, but if you renew for 2 years today, you can lock in the current rate." The grandfathering window generates renewal revenue before the standard renewal date. Value communications: the price increase announcement must be accompanied by a clear articulation of value delivered — the features added, performance improvements made, and support investments completed in the period since the last pricing. A price increase justified by demonstrated value delivery has dramatically higher acceptance rates than one delivered without context. CSM personalization: for enterprise accounts, the price increase communication should come from the CSM in a personal conversation — not a mass email from billing. The CSM conversation is an opportunity to address the specifics of the account's value realization and renewal context.