SAP Analytics Cloud. User vs Capacity, Decided.

SAP Analytics Cloud offers a user based and a capacity based model, and the right choice depends on your concurrency profile, not on which one the account team leads with.

What are the SAP Analytics Cloud licensing models?

SAP Analytics Cloud offers a user based model, priced per named user, and a capacity based model, priced on consumption and concurrent activity. The two are not interchangeable, and the right one depends on how your audience actually uses the tool.

SAP sets out the product and its commercial structure on the SAP Analytics Cloud product pages, part of the wider SAP Business Technology Platform. The pricing detail sits in the order form, which is where the model decision is locked in.

The user based model

• Priced per named user: every assigned person carries a cost.
• Predictable: simple to budget when the population is stable.
• Penalizes casual audiences: a rarely used seat costs the same as a power user.

The capacity based model

• Priced on consumption: tied to concurrent activity, not headcount.
• Suits broad audiences: efficient when many view but few act at once.
• Needs measurement: you must understand your concurrency to size it.

Where is the break even between SAC user and capacity pricing?

The break even sits at the ratio of total named users to peak concurrent users. When that ratio is high, meaning a large audience but few using the tool at once, capacity pricing wins. When it is low, user pricing wins.

Headcount alone does not decide it. A 2,000 person audience with 150 peak concurrent users behaves very differently from 2,000 daily active analysts, and the two should not be on the same model. The SAP Analytics Cloud documentation defines how consumption is measured under the capacity model.

How to compute the break even

• Count named users: everyone who would need access.
• Measure peak concurrency: the most users active in one window.
• Compare both quotes: price the same estate under each model.

How does your concurrency profile drive the SAC decision?

Your concurrency profile is the share of your named audience active at the busiest moment. A low share favors capacity pricing because you pay for the peak, not for every name. A high share favors user pricing because the peak approaches the headcount anyway.

Most reporting heavy estates have far lower concurrency than they assume, which is why capacity pricing is so often the cheaper answer for a broad audience and so often overlooked. SAP product updates on the SAP Analytics Cloud news channel change feature scope, so revisit the model as the product evolves.

What to measure first

• Active window: when usage actually peaks during the day.
• Peak share: concurrent users as a fraction of named users.
• Audience type: analysts who build versus viewers who consume.

Where the common advice on SAP Analytics Cloud licensing is wrong

The standard advice, often from the account team, is to license SAP Analytics Cloud on the user based model because it is simple to budget. We disagree for broad audiences. In roughly 15 to 25 SAC decisions we advised across 2024 and 2025, estates with a large casual audience and peak concurrency under 20 percent were materially cheaper on capacity pricing, often by 30 to 50 percent. The user model charges the same for a daily analyst and a monthly viewer, which punishes exactly the broad reporting audiences that SAC is sold to serve. The buyer side move is to measure real concurrency first, price the estate under both models, and choose on evidence rather than on the simpler invoice. Simple to budget is not the same as cheap.

30 to 50%

Saving on the right model

Under 20%

Typical peak concurrency share

15 to 25

SAC decisions behind this read

Source: Redress Compliance advisory engagement file, 2024 to 2025.

On SAP Analytics Cloud, the simpler invoice and the cheaper invoice are rarely the same one. Measure concurrency before you choose.

What buyer side moves cut SAP Analytics Cloud cost?

The first move is to price the estate under both models before committing. The second is to strip SAC out of any bundle so its standalone unit cost is visible and negotiable on its own metric.

Bundling is where SAC cost disappears. When it rides inside a larger SAP agreement, the unit economics vanish, and a line you cannot see is a line you cannot negotiate.

The moves that work

• Dual quote: require both a user and a capacity quote for the same estate.
• Unbundle: price SAC as its own line even inside a wider deal.
• Right audience: license viewers and analysts on the model each suits.

Why renewal is the moment to revisit

Concurrency profiles drift as adoption grows, so the model that fit at first signature may not fit at renewal. Re measuring concurrency each cycle keeps the model matched to reality.

What should a buyer do next?

1. Measure peak concurrent usage and total named users across a representative period before choosing a model.
2. Request both a user based and a capacity based quote for the identical estate from SAP.
3. Compute the break even from the ratio of named users to peak concurrency, not from headcount alone.
4. Strip SAP Analytics Cloud out of any larger bundle so its standalone unit cost is visible.
5. License broad casual audiences on capacity and focused analyst teams on the user model where that fits.
6. Negotiate the chosen model on its own metric rather than accepting the bundled blended price.
7. Re measure concurrency at each renewal, since adoption drift can flip which model is cheaper.

Frequently asked questions

What are the SAP Analytics Cloud licensing models?

SAP Analytics Cloud sells on a user based model, priced per named user, and a capacity based model, priced on consumption and concurrent activity. The two are not interchangeable, and the cheaper one depends on how your audience actually uses the tool.

Which SAC model is cheaper?

It depends on concurrency. A focused analyst team with high concurrent usage is usually cheaper on the user model, while a broad casual audience with low peak concurrency is usually cheaper on capacity. Headcount alone does not decide it.

How do you find the SAC break even?

Count total named users, measure peak concurrent users, then price the same estate under both models. The decision hinges on the ratio of named users to peak concurrency: a high ratio favors capacity, a low ratio favors user pricing.

What concurrency share favors capacity pricing?

In our engagements, estates with peak concurrency below roughly 20 percent of their named population were materially cheaper on capacity pricing, often by 30 to 50 percent. Reporting heavy audiences tend to have far lower concurrency than assumed.

Why does bundling SAC raise cost?

Bundling hides the standalone unit cost. When SAP Analytics Cloud rides inside a larger SAP agreement, its unit economics become invisible, and a line you cannot see is a line you cannot negotiate, so over payment goes unnoticed.

Should viewers and analysts be on the same SAC model?

Not necessarily. Heavy analysts who build content can suit the user model, while large viewer populations who only consume reports are usually better served by capacity pricing. Matching audience type to model avoids paying power user rates for casual access.

Does the right SAC model change over time?

Yes. Concurrency profiles drift as adoption grows, so the model that fit at first signature may not fit at renewal. Re measuring concurrency each cycle keeps the licensing model matched to real usage.

Can SAP Analytics Cloud be negotiated on its own metric?

Yes, and it should be. Even inside a wider SAP deal, insist on a standalone SAC quote on its native metric so the unit cost is visible and negotiable rather than blended into the bundle price.