Amey-Thakur SaaS pricing
Pricing is the exchange rate between the value you create and the revenue you keep, and it is the highest-leverage number in the business: a 10% pricing improvement beats a 10% cost cut in nearly every model. Treat it as a designed product surface, revisited on a schedule.
Method
- Anchor on a value metric. The unit price scales with: seats, usage (requests, GB, messages), or outcomes (bookings, orders). Test: does the customer's cost grow roughly with the value they receive, is it predictable enough to budget, and simple enough to explain in a sentence? A wrong value metric (per-seat for a product where one seat automates a team) caps revenue exactly where value explodes (see product-metrics' north-star logic: the value metric is its commercial twin).
- Design three tiers around customer segments, not feature piles. Entry (self-serve, one clear job), growth (the default: price-anchored where most should land), enterprise (SSO, audit, SLAs, contracts: sold, not clicked: see multi-tenancy's isolation tiers for what enterprise actually buys). Gate by who the customer is becoming (limits, collaboration, controls), not by crippling the core job at entry: a free/entry tier that cannot demonstrate the product's value recruits nobody (see user-activation).
- Blend seats and usage deliberately. Seats are predictable and understood; usage tracks value and monetizes automation; hybrids (seats + usage allowance + overage) are the modern default. Whatever the mix: customers need a dashboard of where they stand and alerts before overage (bill shock is churn with an invoice attached: see churn-analysis).
- Research willingness-to-pay before printing prices. Segment interviews with price-laddering questions, Van Westendorp surveys for range-finding, win/loss data on price objections (see customer-interviews' honesty rules: stated willingness inflates), competitor anchor-mapping (what does the buyer compare you to?). Cost-plus is a floor check only; value-based is the method.
- Test with grandfathering, measure whole-funnel. New prices apply to new customers first (existing customers grandfathered or migrated with generous notice: see feature-sunsetting's trust mechanics); measure conversion x ARPU x retention together, not conversion alone (a price cut that lifts signups of never-activating users lost money: see ab-test-design's guardrails; pricing tests are often cohort-based rather than strict A/B for fairness and legal reasons).
- Raise prices on a cadence, with value framing. Annual review; increases land with the value shipped since ("here is what was added"), notice, and an option path (see roadmap-communication's change-loudly rule). Underpricing compounds silently: the earliest-stage companies' most common pricing error is an order of magnitude of timidity.
Boundaries
- Pricing is constrained by strategy (land-and-expand vs premium positioning), not just optimization; a price war you can win may still be a war you should not enter (see technical-seo's content-vs-tricks ethic: durable beats clever).
- Discounting policy is pricing's shadow system: unmanaged sales discounts rebuild your real price list in salesforce; cap and instrument them (see saas-metrics' ARPU honesty).
- Regulated, marketplace, and open-source-adjacent models carry their own pricing physics; transplant this method's questions, not its defaults.