| Business question | What it affects | Practical check |
|---|---|---|
| Choosing the pricing basis | A pricing strategy is the structural framework that determines how a customer pays for access to a software product. | It is distinct from the acquisition model—how a user starts using the product—and the billing mechanics—how the payment is technically processed. |
| Matching strategy to product type | For internal business systems, CRMs and staff portals, value is usually tied to the number of people using the system or the volume of records being managed. | Per-seat or tiered pricing generally fits well here. |
| Cost-plus versus value-based pricing | Cost-plus pricing—calculating server costs and adding a margin—is rarely effective for SaaS. | The marginal cost of serving one additional user is typically so low that basing prices on it leaves significant revenue on the table. |
| Hybrid models in practice | Many SaaS products eventually adopt a hybrid model to balance predictability with fairness. | As an illustrative example, a document-management portal might charge a flat monthly fee for a base allowance—such as up to five user accounts and 1,000 stored documents—with an additional per-seat charge and a per-document. |
A pricing strategy is the structural framework that determines how a customer pays for access to a software product. It is distinct from the acquisition model—how a user starts using the product—and the billing mechanics—how the payment is technically processed. The strategy defines what the customer is actually buying and how that value is measured.
Most SaaS pricing structures fall into a few broad categories, though mature products frequently combine them:
- Flat-rate pricing: A single price for full access to the product. This is simple to communicate but limits revenue growth as the customer’s usage or team size expands.
- Tiered pricing: Multiple packages—typically three—offering increasing capacity, features, or support levels. This accommodates different customer sizes and willingness to pay without requiring a custom quote for every deal.
- Per-seat pricing: The cost scales with the number of user accounts. This is common for collaborative tools and internal systems, though it can inadvertently penalise organisations that want broad adoption across their workforce.
- Usage-based (metered) pricing: The customer pays based on volume, such as API calls, gigabytes of storage, or documents processed. This aligns the supplier’s revenue directly with the value delivered, but it makes monthly revenue less predictable.
- Feature-gated pricing: Access to specific modules or capabilities is locked behind different tiers. This suits products where distinct user types need entirely different toolsets, such as an admin panel versus a basic read-only portal.
Choosing between these is not a purely theoretical exercise. The structure dictates how the product is built, what metrics the business needs to track, and how the sales team negotiates contracts.
The right pricing strategy depends on how the target customer measures the value of the product. A founder or operations manager buying a system cares about the return it generates, and the pricing model should mirror that return as closely as possible.
Matching strategy to product type
For internal business systems, CRMs and staff portals, value is usually tied to the number of people using the system or the volume of records being managed. Per-seat or tiered pricing generally fits well here. The buyer can easily map the software cost to their headcount or departmental budget.
For API services, data-processing tools or integration platforms, the customer values output volume. A company sending ten thousand data requests per month should not pay the same as one sending a hundred. Usage-based pricing is usually the most logical fit, as it scales automatically with the customer’s own business growth.
Cost-plus versus value-based pricing
Cost-plus pricing—calculating server costs and adding a margin—is rarely effective for SaaS. The marginal cost of serving one additional user is typically so low that basing prices on it leaves significant revenue on the table. Value-based pricing, where the charge is set relative to the financial impact or time saved for the customer, is the standard approach. This requires a genuine understanding of the customer’s operational problem rather than a spreadsheet of hosting costs.
Hybrid models in practice
Many SaaS products eventually adopt a hybrid model to balance predictability with fairness. As an illustrative example, a document-management portal might charge a flat monthly fee for a base allowance—such as up to five user accounts and 1,000 stored documents—with an additional per-seat charge and a per-document overage fee beyond that threshold. This gives the customer a predictable baseline while ensuring the supplier is compensated for heavy usage.
Starting too cheap
Founders frequently underprice at launch to win early customers. While this can accelerate initial adoption, it establishes a low baseline that is commercially difficult to correct. Raising prices for new customers is straightforward, but increasing fees for existing users often triggers resistance and churn. It is generally easier to launch at a sustainable price and offer time-limited discounts than to start low and negotiate upwards.
Overcomplicating the pricing page
Offering six or seven tiers with complex add-ons creates decision paralysis. If a prospective buyer cannot understand the pricing within a few seconds, they are likely to abandon the page and contact a competitor. Three clearly differentiated tiers remain the most common structure because they provide a baseline option, a popular middle ground, and an aspirational premium tier.
Ignoring the cost of delivery
Even though the marginal cost of a SaaS product is low, high-usage customers on flat-rate plans can strain infrastructure and support resources. If a small number of users consume a disproportionate share of server capacity or require constant technical support, the pricing strategy must account for this, either through usage caps, overage charges, or explicit premium support tiers.
Misaligning price with buyer authority
In a B2B context, the person using the tool daily is often not the person approving the budget. An operations manager might evaluate the features, but a finance director will scrutinise the cost per employee. The pricing structure and the surrounding copy need to justify the outlay to both audiences, translating technical features into business outcomes like reduced admin time or fewer errors.
Key checks before committing to a strategy
- Technical feasibility: Can the chosen subscription billing provider support this pricing model natively, or will it require custom workarounds that add ongoing maintenance burden?
- Clarity: Can a prospective customer understand the pricing without speaking to a sales representative?
- Forecasting: Does the structure allow your finance team to predict revenue reliably, or does extreme usage variability make cashflow planning difficult?
- Upgrade path: Is there a clear, logical route for a customer to move to a higher tier as their business grows, without needing to renegotiate their entire contract?