SaaS Pricing Strategy · Models, Tiers & Pricing Psychology

Value-based pricing sets prices based on the value the product delivers to the customer — not on the cost of producing it or on competitor prices. It requires understanding what outcome the customer achieves with the product and what that outcome is worth to them financially. A product that saves a customer £50,000 per year in manual work can sustainably charge £10,000–15,000 per year — 20–30% of the value delivered — without pricing itself out of consideration.

Cost-plus pricing (price = cost × markup) is inappropriate for software because the marginal cost of serving an additional customer is near zero — cost-plus would produce pricing too low to support the business. Competitor-based pricing (match or slightly undercut competitors) anchors pricing to market expectations rather than value delivery — which is more appropriate for commodity products than differentiated software.

The per-seat vs usage-based pricing decision is one of the most consequential for SaaS businesses. Per-seat pricing is predictable (both for the vendor and the customer), scales naturally with team growth, and creates an expansion mechanic as customers add users. But it creates an incentive for customers to share accounts and to minimise the number of licensed seats.

Usage-based pricing aligns cost with value — customers who use the product more pay more — and lowers the barrier to entry (customers start small and scale). Twilio, Stripe, and AWS are the canonical usage-based pricing examples: low cost to start, but revenue grows naturally with customer usage. The risk is revenue predictability — a customer who reduces usage significantly reduces revenue without cancelling, which can mask retention problems in traditional logo-churn metrics.

Tier design is the discipline of determining which features go in which pricing tier — and at what price — to maximise both conversion (enough value in the lowest tier to justify purchase) and expansion (enough additional value in higher tiers to justify upgrades).

The most effective tiering principle: put features in tiers based on which customer segments value them most, not based on cost to deliver them or on which features you want to restrict. The tier boundary should be at the point where the next level of customer value becomes material — not arbitrarily at a round number of features.

Three-tier structures (Starter/Professional/Enterprise or equivalent) are dominant in SaaS because they anchor the middle tier's value: with three tiers, most customers choose the middle option (a well-documented effect in behavioural economics). The middle tier should be designed to be the most attractive option for the core target customer — with sufficient features to satisfy most needs, at a price that feels reasonable relative to both the lower and higher tiers.

Several documented psychological effects influence how customers perceive and respond to pricing:

• Anchoring. The first price seen becomes the reference point for evaluating subsequent prices. Presenting the highest-tier price first makes lower tiers feel reasonable by comparison — even if the absolute price of the lower tier is the same.
• Decoy pricing. Adding a deliberately less attractive option (high price for limited features) makes the target tier look better by comparison. The decoy creates a reference point that makes the value of the target tier more apparent.
• Charm pricing. Prices ending in 9 ($99/month vs $100/month) produce higher conversion rates in studies — the left-digit effect means customers process the first digit more heavily than the remainder.
• Price framing. Expressing the same annual price as a monthly equivalent ("only £8/day" vs £240/month) changes perceived expense. Annual plans presented as monthly equivalents consistently show higher conversion than identical prices shown as annual lump sums.

Freemium pricing offers a permanently free tier as an acquisition strategy — using the free product as marketing for the paid product. The freemium decision involves a fundamental trade-off: the free tier must be valuable enough to attract genuine users and demonstrate the product's value (otherwise nobody uses it), but not so complete that users have no reason to upgrade (otherwise no revenue is generated).

The design principle: free tier should solve the core problem for individual users or small teams at basic scale; paid tier should add the collaboration features, scale, or advanced capabilities that businesses need as they grow. Mailchimp's freemium was effective because the free tier was genuinely useful for early-stage businesses but had list size and feature limits that growing businesses needed to exceed. Slack's freemium was effective because it provided full product value for small teams but had message history limitations that larger teams needed to remove.

Offering both monthly and annual billing (with annual at a 15–20% discount vs monthly) creates several advantages: annual customers have significantly lower churn rates (they make one renewal decision per year rather than 12); annual billing improves cash flow (receive the full year's revenue upfront); and annual customers tend to have higher LTV.

The discount level for annual vs monthly should reflect the value of the cash flow advantage and churn reduction — not be set arbitrarily. A 20% annual discount for 12 months' upfront payment is common; lower discounts (10–15%) produce lower annual take rates but higher revenue per annual customer.

Pricing A/B tests — showing different prices to different user segments — are technically more complex than standard product tests because pricing changes affect customer trust and fairness perceptions. The standard approach: test pricing with new prospects (not existing customers); use geographic cohorts to test different price points; or test price presentation (framing, tier structure, feature emphasis) rather than absolute price levels.

The most informative pricing research is often qualitative: customer interviews asking "what would be too expensive?", "what would be too cheap to trust?", and "at what price would this be a compelling deal?" produce the price sensitivity data that informs pricing decisions before committing to a specific price point in production.

• Underpricing out of fear. Most startup founders underprice because they are uncertain about the product's value and fear rejection. Underpricing creates a lower-quality customer base (more price-sensitive, lower LTV), makes the unit economics of customer acquisition harder, and signals lower value to the market.
• Never revisiting price. A price set at launch rarely reflects the product's value 2–3 years later when features have been added, customer outcomes have been documented, and the market position has strengthened. Annual pricing reviews should be standard practice.
• Tier cannibalisation. Designing tier boundaries such that the lower tier meets the needs of customers who should be on the higher tier — reducing upgrade motivation. Each tier should have a natural upgrade point where a specific use case or scale milestone triggers the need for the higher tier.
• Discounting without strategy. Ad-hoc discounting — offering discounts to close deals without a clear policy — trains customers and sales teams that the list price is negotiable, which undermines pricing integrity over time.

Raising prices for existing customers is one of the most uncomfortable but highest-ROI actions a SaaS business can take. Price increases of 10–20% on an existing customer base flow almost entirely to profit — there are no incremental costs. The risk is churn: if too many customers cancel in response to the price increase, the revenue gain is offset by lost MRR.

Best practices for price increases: give advance notice (minimum 30–60 days); explain the value added since the last pricing change; grandfather existing customers at their current rate for a defined period before moving them to new pricing; and segment the increase — customers who use more features or have higher usage are least likely to churn from a price increase, because they derive the most value from the product.

Sources & Further Reading