SaaS pricing should connect perceived value, the target customer and cost to serve. Choose a billing metric, understandable boundaries and a price level to test rather than treating pricing as one number.
Select a meaningful unit
Per-seat pricing is understandable when value grows with the number of people equipped. Usage pricing can follow processing volume but requires reliable metering and predictable bills. A flat subscription simplifies buying while potentially exposing the provider to expensive heavy usage.
Understand procurement
Ask prospects about alternatives, budget ownership and approvals. Do not rely only on “what would you pay?” Existing purchasing behaviour may reveal a more important constraint than the stated amount.
Package recognisable needs
Differentiate plans through meaningful requirements such as collaboration, volume or governance. Avoid arbitrary restrictions that prevent first value. Explain overages, upgrades, downgrades and cancellation before purchase.
Test without confusing customers
Define the segment, offer and question under examination. Observe objections and post-purchase behaviour as well as conversion. Acceptance by a few customers does not establish that the model sustainably funds the service.
Should we copy a competitor?
Competitor offers provide context, not the answer. Their costs, customer mix and objectives may be unknown. Use comparison to develop questions and a coherent offer rather than assuming their pricing is correct for your product.
Start with the value unit
Per-seat pricing is familiar, but can discourage inviting colleagues when collaboration creates value. Per-organisation pricing can simplify adoption while exposing the supplier to widely different workloads. Usage pricing may follow variable costs more closely, but requires a unit buyers can understand and predict.
For a fictional reporting tool, compare seats, completed reports and processed volume. Ask customers what they can estimate before using it. A technically measurable but unpredictable unit can make budgeting uncomfortable. Also decide whether failed work and retries consume a paid allowance; this affects perceived fairness.
Test the complete offer
Describe a small account, a typical account and intensive usage. Calculate charges using proposed prices and compare the corresponding service effort. Label these as planning scenarios rather than market benchmarks.
Discuss a concrete package with inclusions, limits, assistance and upgrade rules. Reactions to an isolated number reveal less than decisions about a complete offer. Preserve rejection reasons to distinguish price resistance from insufficient value or unavailable budget. Do not interpret every objection as evidence that the product should simply be cheaper.
From this guide to your project
Strategy ↗
An idea becomes an opportunity when it solves a real problem for people willing to change how they work.
Tell us about your ideaExamples are educational and do not describe client results. Content prepared with AI assistance; see our editorial policy. Our method ↗