
Slack charges teams only for members who are active, and credits the account when someone goes quiet for more than 28 days, under its fair billing policy. Basecamp goes the other way, with one flat price for unlimited users. Both are deliberate pricing choices, and both shape how each product grows.
SaaS pricing models are the structures a subscription software company uses to charge customers, such as per user, per tier or per unit of usage. The model decides who pays more as they get more value, and it shapes the billing system engineers have to build and maintain.
This guide compares seven SaaS pricing models with real examples and shows how to choose a value metric. The last sections cover the billing work and the SaaS metrics to track after launch.
What is SaaS pricing? The answer is a set of rules that turns product use into recurring revenue, covering what you charge for and how prices step up. Among SaaS pricing models, the one you pick matters because it is hard to change later. Customers resist new pricing, and billing code built for one model rarely fits another.
A good model lets small customers start cheaply. Revenue then grows with value. Buyers should still be able to predict the bill before it arrives.
Pricing also drives engineering work. Seat plans need user counts that sync with billing every day, and usage plans need accurate records of every billable event. Settle the model before building the billing layer, and the SaaS development cost stays predictable.
The seven main SaaS pricing models are listed in the table below, from flat-rate to credit-based. Each charges for a different unit and suits a different buyer. Products often combine two. A per-seat charge inside each tier is common.
| Model | How it charges | Real example | Best fit |
| Flat-rate | One price for everything | Basecamp Pro Unlimited at $199 a month billed annually | Simple tools, small teams |
| Per-seat | Price per user | Slack, billing only active members | Collaboration tools |
| Tiered | Plans with rising features | Pro and Enterprise plans | Broad markets |
| Usage-based | Price per unit used | Stripe Billing at 0.7% of billing volume | APIs and infrastructure |
| Freemium | Free plan with limits, paid upgrades | Zoom Basic, capped at 40 minutes per meeting | High-volume, viral products |
| Hybrid | Base fee plus usage overage | Platform fee plus charges above an included quota | Products with variable load |
| Credit-based | Prepaid credits used up over time | Credit burndown plans for AI features | AI and compute-heavy products |
The examples come from each company’s public pricing pages, including Basecamp’s plans and Zoom’s pricing. Prices change, so check the current page before quoting any of them.
Each of the SaaS pricing models trades simplicity against how well revenue tracks value. Flat-rate is easiest to sell but leaves money on the table with large customers. Pay-per-use tracks value closely. Bills get harder to predict, though. Tiers sit between the two for many B2B products.
| Model | Pros | Cons |
| Flat-rate | Easy to sell and bill | Large customers pay the same as small ones |
| Per-seat | Revenue grows with team size | Customers share logins to save money |
| Tiered | Clear upgrade path | Hard to pick the right features per tier |
| Usage-based | Price tracks value | Bills vary month to month |
| Freemium | Fast adoption | Most free users never pay |
| Hybrid | Predictable base plus upside | More complex billing logic |
| Credit-based | Cash upfront, flexible use | Credits need clear expiry rules |
Tiered pricing SaaS products often anchor on the middle plan. Put the most popular features there and keep the top tier for buyers who need SSO, audit logs and SOC 2 reports.
Picking a pricing model before you build billing?
WebOsmotic maps your pricing options to the billing work each one needs, so you choose a model your product can actually support.
Choose a model by picking the value metric first: the unit that grows as customers get more value, such as users, transactions or records. Then match it to your buyer. Small teams want predictable flat or tiered prices. Developers and enterprises accept usage pricing when it maps to their own costs.
Test each candidate value metric against four questions:
A project tool that charges per seat can discourage teams from inviting colleagues. Slack’s active-member rule is one answer to that problem. Charging per project or per workspace is another.
Price levels need evidence. Interview 10 to 20 target buyers about what they pay today and what the problem costs them. Set the first price, then review it after 90 days of real sales data.
Implement tiered and usage-based billing by modeling products and prices in a billing platform, metering usage events in your app, and syncing plan limits with feature access. Buy the billing engine and build only the metering and entitlement logic specific to your product, since invoicing and payment retries are solved problems that rarely repay custom code.
Stripe’s pricing model docs describe the main options that SaaS pricing models map onto. Other billing platforms use similar building blocks. Under its tiered option, the unit cost can change by total volume or step up gradually as usage grows, which Stripe calls graduated pricing. Usage plans can run as fixed fee and overage, pay as you go, or credit burndown.
The engineering work splits into three parts:
Keep pricing data out of the codebase. Limits and prices belong in configuration, so marketing can test a new tier without a release. For data rules such as GDPR, keep usage records separate from personal data where you can.
The SaaS metrics that show whether pricing works are monthly recurring revenue, net revenue retention, churn, average revenue per account and expansion revenue. Track them by plan. A model that works shows customers moving up tiers, and revenue from existing accounts growing faster than churn takes it away.
| Metric | What it tells you about pricing |
| Monthly recurring revenue (MRR) | Overall scale and growth |
| Net revenue retention (NRR) | Whether existing customers pay more over time |
| Gross churn | Whether some customers find the price too high for the value |
| Average revenue per account (ARPA) | Movement upmarket or downmarket |
| Expansion revenue | Whether upgrades and add-ons are working |
Some public SaaS companies report net revenue retention in their SEC filings, which shows how much weight investors put on it. Above 100% means existing customers grow spending faster than others leave.
Review these SaaS metrics every month for the first 12 months after a pricing change, since SaaS pricing models take time to settle. Six months of data shows whether a new model holds. For a team that builds the billing layer with the product, our SaaS product development services cover entitlements and payments together.
Need usage-based or tiered billing built into your product?
Our SaaS engineers build entitlements and billing sync, so a pricing change becomes a configuration edit with no new release.
Plans with three tiers are a very common setup for B2B SaaS, often with a per-seat charge inside each tier. Among tiered pricing SaaS plans, the middle one is usually positioned as the default choice for most buyers.
That depends on what grows with value. Pay-per-use suits APIs and infrastructure, where usage maps to the customer’s own costs. Per-seat suits collaboration tools. Hybrid plans, with a base fee plus usage above a quota, combine both and reduce bill shock.
Review pricing every 6 to 12 months, but change it only with evidence from sales data and customer interviews. Give existing customers notice, often 30 to 90 days, and consider keeping them on their current price for a period.
Offer a free plan when the product spreads through users inviting others and costs little to serve. Set clear limits, such as Zoom’s 40-minute cap on free meetings. A free trial of 14 to 30 days suits products that need setup before users see value.
In product terms, tiers are plans with different features. In billing systems, volume pricing sets one unit price based on total quantity, while graduated pricing charges each band at its own rate. Stripe supports both as tiered price options.