SaaS Pricing Models Compared

Pricing model and packaging are different jobs, and confusing them costs companies a year. The model is the shape of the meter: what you count and how the bill behaves as a customer grows. Packaging is which features sit in which tier.

Get the model wrong and no amount of packaging work saves you, because you will be counting the wrong thing forever. So here are nine models, what each does to your revenue, and the three inputs that should decide which one you pick.

The nine models at a glance

Each model changes five things: how revenue behaves month to month, how accurately you can forecast, how high net revenue retention can go, how you compensate sales, and how complicated billing gets.

Model	Forecast accuracy	NRR ceiling	Billing complexity	Fits
Flat rate	Very high	Low, price rises only	Trivial	Single persona tools under $100/mo
Per seat	High	Medium, tracks headcount	Low	Collaboration products, sales led B2B
Per active user	Medium	Medium high	Medium	Products with sporadic usage, large rosters
Tiered packaging	High	Medium, needs tier jumps	Low	Broad market with clear segments
Usage or consumption	Low	Very high	High	Infrastructure, APIs, observable units
Credit based	Medium	Very high	High	Multi product usage, AI workloads
Hybrid commit plus overage	High	High	High	Most companies above $25K ACV
Outcome based	Low	Very high	Very high	Measurable, undisputed outcomes
Freemium plus paid	Medium	Depends on paid model	Low	Large TAM, low marginal cost, viral loop

A note on the forecast accuracy column, because it is the one finance cares about most. Pure usage in year one commonly swings quarterly revenue by 10 to 20 percent against plan, in both directions. That is survivable at Series B and career limiting at scale, which is why almost every large consumption business ends up with commitments layered on top.

Flat rate, per seat and per active user

Flat rate is one price, everything included. Basecamp made it famous. It is genuinely good for a narrow product with one persona and low price sensitivity, and it is a trap for anything that gets adopted at different scales, because a ten person customer and a thousand person customer pay the same.

Per seat is still the default in B2B, and it deserves defending. It is legible to a buyer, easy to forecast, easy to comp a rep on, and it grows with headcount. Zoom scaled to billions on it. Figma still prices by editor seat, which tracks value well because the value is created by a person doing work in the file.

Where per seat breaks is where software replaces the person rather than equipping them. If an AI agent closes support tickets, charging per support seat means your revenue falls as your product succeeds. Intercom’s move to charging per resolution is the clearest public example of a company refusing to price against its own value. That is the real argument, and it is narrower than “seats are dead”. A deeper comparison sits in seat based vs usage based pricing.

Per active user is the middle path: you have a roster of 5,000 potential users and you bill on the 900 who did something this month. It sells well into organisations with long tails of occasional users. The cost is forecast noise and a monthly conversation about what counts as active.

Tiered packaging, usage and credits

Tiered packaging is the most common structure in SaaS and the least interesting economically, because it is really a wrapper. Atlassian runs tiers across Jira and Confluence, and the tiers do the segmentation work while seats do the metering work. Tiers are good at capturing willingness to pay across segments. They are bad at expansion, because growth requires a tier jump, and tier jumps are discrete, negotiated and easy to delay.

Usage pricing charges for what gets consumed. Twilio per message. Datadog per host and per ingested gigabyte. AWS for everything. It aligns price to value beautifully when the unit is observable, and it produces the highest expansion rates in SaaS.

The two failure modes are worth stating plainly. Bill shock churn happens when a customer’s usage spikes and the invoice arrives without warning, and it kills accounts that were otherwise healthy. Procurement resistance happens because an unbounded bill cannot be approved by a finance team that budgets annually. Both are solvable with caps, alerts and commitments, and both are ignored by teams excited about consumption growth.

Credit based pricing is usage pricing with a comprehension layer. Snowflake sells credits that convert to compute. The customer buys a predictable number of credits, and the vendor gets to change the underlying conversion without renegotiating price. It also lets one currency span multiple products, which is why it keeps appearing in AI pricing. The tradeoff is opacity: customers cannot easily compare your credit to a competitor’s, and some of them resent that.

Hybrid commit plus overage, outcome based, freemium

Hybrid commit plus overage is where most companies above 25 thousand ACV should land, and it is my recommendation for the majority of readers. The customer commits to an annual dollar amount, receives an allowance at a discounted unit rate, and pays a higher rate above it.

Finance gets committed revenue to forecast. Sales gets a number to comp against. The customer gets a discount for commitment and a bill they can budget. Expansion happens through overage without waiting for renewal, which is the single biggest revenue advantage over pure seats. Snowflake, Twilio and Datadog all run variants of this.

Outcome based pricing charges for a result: a qualified meeting, a resolved ticket, a recovered payment. It aligns incentives perfectly and it is operationally brutal. Both parties must be able to measure the outcome, neither must be able to dispute it plausibly, and your gross margin must absorb the cases where you deliver effort but no outcome. I would only recommend it where you already control the measurement surface end to end.

Freemium is not really a pricing model, it is an acquisition model attached to one. The question is always what the paid model underneath is. Free works when marginal cost per free user is near zero, the TAM is large, and free users generate distribution. It fails when free users cost real money to serve, which is the position most AI products are now in.

A decision tree you can actually run

Three inputs decide it: ACV band, gross margin, and whether usage is observable to the buyer before purchase.

That last step is where most repricing projects should stop and restart. Run it early. The usage based pricing simulator and the value metric pricing calculator will do the arithmetic against your own customer base, which beats arguing about it in a spreadsheet built during the meeting.

Named implementations to study

Copying a model without understanding the business underneath it is how teams end up with credits nobody wants.

Stripe is the outlier worth noting. Percentage of transaction volume is outcome pricing in disguise, and it works because the outcome is undeniable and automatically measured. Very few products get that luxury.

If you want the decision frameworks behind these choices rather than the models themselves, SaaS pricing frameworks compared covers Van Westendorp, conjoint and the rest, and value based vs cost plus pricing handles the philosophical layer above the mechanics.

What each model costs you internally

Every model has an operational bill nobody puts in the business case.

Usage and credit models need metering infrastructure that is accurate to the cent and auditable, plus a billing system that can handle mid cycle proration. Budget two to four months of engineering, or buy it. The pricing and billing tools roundup covers what is available.

Hybrid commit models need a sales team that can negotiate a commitment level, which is a harder conversation than selling 40 seats. Expect three to six months of ramp and some lost deals while reps learn it.

Outcome models need a dispute process. Build it before launch, staff it, and accept that roughly one in twenty invoices will be contested in year one.

And per seat, the simplest of all, quietly costs you expansion revenue every year that your customers’ value grows faster than their headcount. That is the tradeoff most teams never price.

What to do next

Write down your current value metric in one sentence. If you cannot, that is the finding. Then run last year’s usage data through two alternative models and look at what happens to your top ten and bottom ten accounts.

Do not reprice on a hunch, and do not reprice more than once every eighteen months. Customers forgive a price rise. They do not forgive three structural changes in two years, because each one forces their finance team to redo work. Start at the pricing strategy overview if you need the wider context, and build the announcement from a pricing page spec rather than a design mock.