SaaS Management · Pricing models

When SaaS is no longer priced only by user.
Seats, credits, and consumption—clearly explained.

With traditional SaaS, one question was often enough: How many user licences do we need? Consumption-based SaaS adds new units such as credits, API calls, actions, or tokens. This changes cost control, forecasting, and renewals.

Updated: 27 August 2026Reading time: about 8 minutesClearly explained

In short

The licence remains. Consumption is added.

Many SaaS products now combine fixed subscriptions with variable consumption charges. Comparing only purchased and active seats is no longer enough.

01Seat-based SaaS will not simply disappear.
02Consumption and hybrid models are being added to it.
03More usage does not automatically mean more business value.
04Contract, consumption, cost, and outcome must be assessed together.

From seats to consumption

One product.
Several possible bills.

Consumption-based means that all or part of the bill depends on how much a product is actually used. In practice, several pricing models often exist side by side.

Four simple models

How SaaS can be priced today

The difference is not only the price. Each model needs different data, controls, and optimisation decisions.

PER USER

Seat-based

The organisation pays for a defined number of users or accounts. The bill often stays the same even when some seats are barely used.

Example: 100 user licences per year

BY CONSUMPTION

Consumption-based

Cost depends on a measured unit—for example API calls, processed data volume, transactions, or tokens.

Example: cost per 1,000 API calls

INCLUDED ALLOWANCE

Package with a limit

A base fee includes a fixed allowance. Extra charges or restrictions begin only when the limit is exceeded.

Example: 50,000 credits included per month

COMBINED

Hybrid model

Seats, a platform fee, included credits, and extra consumption can apply at the same time. Each component needs its own control.

Example: user licence plus AI consumption

Important:

‘Pay for what you use’ sounds automatically fair. It can reduce waste from unused seats, but it can also create new risks through uncontrolled or hard-to-predict consumption.

Simple practical example

100 seats are no longer the full cost picture

An organisation buys a fictional SaaS product with AI capabilities. The contract includes user licences and a monthly credit allowance.

100paid seats

50kcredits included

1combined bill

If the credits are used before the end of the month, the contract may trigger extra cost, restrictions, or another purchase.

SEATS ONLY

The analysis stays incomplete

How many licences were purchased?
How many are assigned?
How many users signed in?
Unused seats are reclaimed.

SEATS + CONSUMPTION

The complete cost picture

Who uses which capability?
Which teams or agents consume credits?
What does a task or outcome cost?
Are allowance, budget, and guardrails sufficient?

The new guiding question:

Not only ‘How many licences do we have?’ but also ‘What is being consumed, what drives the cost, and what value does that consumption create?’

Why AI accelerates the shift

Software increasingly works without a direct user click

With AI, APIs, automation, and agents, consumption does not always grow in line with employee numbers. One agent can use several models, data sources, and actions in a single task.

Tokens

Text is divided into small units. Input and output can be priced differently.

AGENTS

Credits or actions

Answers, data retrieval, tools, and multi-step actions can consume different amounts.

APIS

API calls

Every technical call can be counted—even when no person clicks directly.

DATA

Data volume

Stored, transferred, or processed data can determine the bill.

PROCESS

Transactions

Messages, documents, searches, or process steps can become the billing unit.

RESULT

Outcomes

Some providers charge for completed actions or resolved cases. This requires a particularly clear definition.

Concrete example:

Microsoft uses Copilot Credits for certain AI scenarios. The number of credits depends on the capability used. Other providers may charge by tokens or API calls. The unit must therefore be checked for each product.

Consumption is not the same as value

Higher usage can be good—but it does not have to be

More consumption may show adoption and growth. It can also be caused by retries, unsuitable models, poor processes, misconfiguration, or unnecessary automation.

USAGE

What was consumed?

Measure seats, credits, tokens, API calls, or other units over a relevant period.

Create visibility

COST

What did it cost?

Consider base fee, commitment, allowance, overage, and discounts together.

Understand total cost

QUALITY

Was the result usable?

Errors, retries, and rework can raise consumption without improving the process.

Measure quality too

OUTCOME

What value was created?

Where possible, connect cost and usage to a measurable improvement or business outcome.

Scale, optimise, or stop

Shared responsibility

Consumption-based SaaS connects several teams

No single team has all the necessary information. Good decisions emerge when commercial, technical, and business views are brought together.

SAAS MANAGEMENT

The full picture

Bring contract, plan, users, consumption, owner, and renewal into one portfolio view.

FINOPS

Forecast & control

Make consumption trends, budgets, variances, unit costs, and optimisation opportunities visible.

PROCUREMENT

Contract & price

Negotiate commitments, tiers, overage, expiry, price changes, and exit conditions.

IT & ENGINEERING

Technical consumption

Explain which architecture, automation, models, or integrations drive consumption.

BUSINESS OWNER

Need & outcome

Assess whether usage fits the intended scenario and produces a relevant outcome.

FINANCE

Budget & allocation

Support cost centres, accruals, showback or chargeback, and financial predictability.

Before purchase and renewal

Ten questions for consumption-based SaaS contracts

The answers do not need to be perfect on day one. But they should be addressed deliberately before commitment, scaling, or renewal.

01
Understand the consumption unit
What exactly is counted: seats, credits, tokens, actions, data, or outcomes?
02
Document the metering logic
When does a unit begin and end, and can one task create several units?
03
Check the included allowance
What allowance is included, and is it per user, team, environment, or tenant?
04
Clarify expiry and rollover
Do unused credits expire at month-end, or can they roll over?
05
Assess overage
What does overage cost, and is it charged automatically, blocked, or approved first?
06
Require transparency
Are timely dashboards, exports, or APIs available for consumption and cost?
07
Set guardrails
Can budgets, limits, alerts, approvals, and spending caps be configured?
08
Build a forecast
Which usage is normal, seasonal, or planned because of growth and new scenarios?
09
Calculate unit cost
What does an active user, a task, or—where measurable—an achieved outcome cost?
10
Prepare the decision
Should the model be scaled, optimised, renegotiated, limited, or retired?

LizenzFrau takeaway

Consumption-based SaaS does not replace licence management.

It expands the job: alongside rights, seats, and contracts, organisations must manage consumption, forecasts, guardrails, quality, and business value.

Primary and official sources

Verified and clearly explained.

Sources checked on 27 August 2026. Prices, units, and product rules can change. A specific decision must always use the current contract and vendor terms.

Editorial note: The example with 100 seats and 50,000 credits is deliberately fictional and is used only to explain a hybrid pricing model.