SaaS Management · Foundations

What is SaaS Management—
and why is a licence list not enough?

SaaS Management connects applications, contracts, access, actual use, cost, risk, and business value. Only this combined view shows which solutions are needed, what can be optimised, and which decision makes sense before the next renewal.

Updated: 13 August 2026Reading time: about 12 minutesSaaS Management explained clearly

In short

A SaaS licence is assigned. But does it create value?

SaaS Management turns an often decentralised application portfolio into repeatable decisions about demand, use, access, contracts, cost, and the future of each application.

01A contract or licence list is only one part of the SaaS portfolio.
02Assignment, login, and value-creating use are not the same.
03Renewals must be prepared months before the extension date.
04Optimisation does not automatically mean cutting—it means choosing the right action.

From subscription to portfolio

SaaS is quick to buy.
Accountability still follows.

Business teams can acquire applications directly, by corporate card, through a reseller, or via a cloud marketplace. Cost, access, and data flows can therefore grow faster than traditional inventory processes. SaaS Management creates a shared operating framework without blocking useful innovation.

Definition & context

SaaS Management governs more than subscriptions

NIST defines SaaS as using provider-hosted applications running on cloud infrastructure. The organisation does not operate the underlying servers, but it remains accountable for selection, contract, identities, data, use, cost, and exit.

NOT JUST INVENTORY

More than an application list

A name and vendor do not reveal who owns the service, which data it processes, who can access it, or which dependencies exist.

NOT JUST LICENCES

More than unused seats

An assigned licence may be unused, oversized, or essential for a critical task. Activity needs context.

NOT JUST PROCUREMENT

More than a renewal process

Negotiations improve when usage, demand, alternatives, risk, and forecast are known early.

NOT JUST BLOCKING

More than stopping shadow IT

Unknown apps should be discovered and assessed. The goal is a conscious decision: approve, replace, limit, or retire.

The essential connection

01Contract
02Licence or plan
03Assignment
04Actual use
05Cost
06Business value

SaaS Management, SAM, and FinOps:

SaaS Management is not an isolated replacement for SAM, licence management, procurement, security, or FinOps. It connects their perspectives for SaaS in one decision process.

Pricing & procurement

Not every SaaS product can be optimised like a seat

The FinOps Foundation distinguishes licence-based, consumption-based, and hybrid SaaS models. Buying channels and contract mechanisms add further variation.

PER USER

Seat- or account-based

Cost is linked to a user, role, device, or edition—often with minimum quantities and fixed terms.

Do quantity, assignment, and edition fit?

CONSUMPTION

Usage-based

Storage, transactions, API calls, data volume, or other units determine the bill.

Which usage drives cost and value?

PLATFORM

Plan or package model

A base plan combines features, limits, and support; add-ons or overages are charged separately.

Do we use the features and limits we fund?

HYBRID

Combined models

Seats, platform fees, credits, and consumption can apply together and require separate controls.

How do the pricing components interact?

90%

of State of FinOps 2026 respondents already manage SaaS or plan to do so in the coming year. This describes the survey population, not automatically every organisation worldwide.

The SaaS lifecycle

Seven decision points from initial demand to a controlled exit

A renewal is not where management begins. Every stage needs data, an accountable role, and a clear outcome.

01
Discover
Combine contracts, spend, single sign-on, browser and network data, expenses, and information from business teams.
Which SaaS applications actually exist?
02
Assess & approve
Review business need, existing alternatives, architecture, privacy, security, integration, vendor, and exit capability.
Should this application enter the portfolio?
03
Procure
Document plan, quantity, pricing metric, term, notice period, data terms, and negotiation options.
What do we buy—and with how much flexibility?
04
Provision
Name owners, grant role-based access, use SSO and provisioning, and integrate the app into catalogue and support processes.
Who receives which access, and why?
05
Use & enable
Monitor activity, feature adoption, service quality, and business outcomes, and support users where needed.
Is the solution being used effectively?
06
Optimise & renew
Assess reclamation, downgrade, plan changes, consolidation, quantity, forecast, and negotiation together.
What should be renewed, changed, or stopped?
07
Retire
Remove access, export or delete data, disconnect integrations, end cost, and retain evidence.
Has the app been closed functionally, technically, and commercially?

The data foundation

Six data worlds create one meaningful SaaS view

SaaS data is often split across vendor portals, contracts, identity systems, finance, and business teams. A single source rarely contains the whole truth.

APP

Application & portfolio

Product, vendor, category, capabilities, criticality, business owner, and technical owner.

CONTRACT

Commercial terms

Order, term, renewal, notice period, price tiers, commitment, and buying channel.

RIGHT

Plan & entitlement

Edition, licence metric, quantity, add-ons, usage rights, limits, and regional terms.

IDENTITY

Account & access

User, role, department, status, SSO, provisioning, privileged access, and service accounts.

USAGE

Activity & adoption

Last login, active days, features used, consumed units, and the relevant measurement window.

VALUE

Cost & outcome

Cost centre, forecast, cost per active user or outcome, quality measures, and business KPIs.

Assigned does not mean used:

A login alone does not prove value. Equally, no recent login does not automatically mean a licence can be removed. Measurement windows, role, seasonality, integrations, service accounts, minimum quantities, and contract terms matter.

Practical case · 500 licences

180 inactive accounts are a signal—not a saving yet

An organisation is preparing the renewal of a central SaaS application. The provider reports 500 assigned licences and 320 active users in the selected period.

500assigned licences

320active users

180to validate first

The difference of 180 is not an automatically cancellable quantity. It is the starting point for a defensible analysis.

WITHOUT SAAS MANAGEMENT

One number drives the decision

All 500 licences are renewed unchanged because time is short.
Or 180 licences are cut without checking roles and demand.
Minimums, editions, seasonality, and planned hiring remain invisible.
The next variance appears only at the following renewal.

WITH SAAS MANAGEMENT

Usage becomes an actionable decision

Accounts are reconciled with HR, IAM, contract, and owner data.
Inactive users are classified by leaver status, wrong assignment, seasonality, adoption, and special roles.
Reclaim, downgrade, enablement, quantity change, and contract options are assessed separately.
The forecast includes growth, planned projects, and a defined buffer.

The outcome is more than a new licence count.

It is a traceable renewal decision: which accounts to remove, which editions to change, which users to enable, and which quantities to negotiate under which terms.

Accountability

SaaS Management is a team effort—but every app needs an owner

Decentralised use requires shared guardrails and clear decision rights. A central function can coordinate, but it cannot make every business decision alone.

BUSINESS

Business owner

Owns demand, target users, adoption, outcomes, and the business decision about future use or replacement.

IT · SAM

SaaS / Asset Management

Maintains the portfolio, data model, controls, usage transparency, and cross-functional lifecycle.

PROCUREMENT

Procurement & Vendor Management

Manages sourcing, terms, negotiation, notice periods, vendor relationships, and commercial risk.

FINANCE · FINOPS

Finance & FinOps

Connects cost, allocation, forecast, budgets, optimisation impact, and business value.

SECURITY · DATA

Security & Privacy

Assesses identities, data, configuration, compliance, third-party risk, and exit requirements.

HR · IAM

HR & Identity

Provides joiner-mover-leaver signals and enables timely assignment, change, and removal of access.

Meaningful measures

Do not measure the number of apps—measure control and value

A single utilisation rate is not enough. Useful measures connect portfolio coverage, usage, cost, renewal readiness, risk, and outcomes.

VISIBILITY

Portfolio coverage

Share of relevant SaaS apps with a documented owner, contract, renewal, cost, and risk class.

USAGE

Active utilisation

Active users or consumed units in an appropriate period, segmented by plan, role, and target group.

EFFICIENCY

Reclaim & downgrade potential

Validated—not merely calculated—opportunities for removal, downgrade, or reassignment.

RENEWAL

Decision readiness

Share of major renewals with demand, usage, forecast, alternatives, and negotiation position prepared on time.

PORTFOLIO

Capability overlap

Applications with similar purposes, parallel contracts, and realistically consolidatable volume.

VALUE

Cost per active user or outcome

Connect cost to real use and, where possible, a measurable business outcome.

Beware of vanity metrics:

Fewer apps or a higher login rate is not automatically better. Critical capability, user experience, resilience, risk, innovation, and realised value belong in the assessment.

Practical starting point

Turn distributed subscriptions into a manageable SaaS portfolio

Do not begin with completeness at any cost. A clear scope, reliable owners, and a working renewal cadence create value faster.

01
Start with the most important applications
Prioritise the 20 highest-cost, most critical, or highest-risk SaaS products and make the scope explicit.
02
Define a minimum data model
Capture app, owner, contract, renewal, plan, quantity, cost, user source, usage signal, and risk class.
03
Embed owners and a renewal calendar
Name business, technical, and commercial accountability plus preparation lead times for each relevant app.
04
Connect identity, usage, and cost
Gradually combine SSO, provisioning, vendor telemetry, HR signals, and finance data, including clear data-quality indicators.
05
Establish a decision cadence
Review usage and anomalies monthly; prepare major renewals 120 to 180 days early with demand, forecast, and alternatives.

LizenzFrau takeaway

SaaS Management does not mean fewer tools at any price.

It means making a conscious, evidence-based decision for every relevant application—using demand, usage, access, contract, cost, risk, and business value.

Primary and official sources

Verified with NIST, FinOps Foundation, and Microsoft sources.

This article reflects information available on 13 August 2026. Frameworks and product capabilities evolve; controls must be adapted to the organisation and each SaaS contract.

Note: The example with 500 licences is a deliberately simplified decision model. It is not a blanket savings assumption.