Analytics Legends logoAI & Analytics Legends Sign inSign up
Guide

SAP Analytics Cloud pricing: the published anchors and the real drivers

As of 2026-11-07

SAP publishes no per-user list price for SAP Analytics Cloud: its pricing page offers subscription and pay-as-you-go plans, says the price is tailored to the organisation and asks you to request a quote. What SAP does publish is the mechanism. Under Business Data Cloud, SAC draws on a capacity-unit pool at per-user values listed in SAP's service description guide, for example 25.60 units per business intelligence user per month in the 25 to 200 band. The currency price per unit is in your contract.

What is actually published

The SAP Analytics Cloud pricing page shows plans, not prices: subscription or pay-as-you-go, a price tailored to the organisation, and a quote request. Figures that circulate on third-party sites are reports of individual deals, not an SAP list, and this page does not repeat them.

What SAP publishes is a rate card in capacity units. In the SAP Business Data Cloud service description guide, v9-2026, business intelligence users run from 25.60 units per user per month in the 25 to 200 band down to 10.54 above 5,000 users, and standard planning from 72.85 to 41.57. SAP's presentation of 16 April 2026 cites a minimum of 640 capacity units as the smallest viable implementation: 25 business intelligence users × 25.60 = 640. The service description guide v10-2026 does not contain that figure; its clause 6.3.2 gives 1,000 capacity units a month.

Under Business Data Cloud, SAC, Datasphere, BW Cloud, HANA Cloud and SAP Databricks draw on one capacity-unit pool, per SAP's presentation of 16 April 2026. SAC users therefore compete with Datasphere compute and storage for the same units: a seat count never tells you the platform bill. For Datasphere sizing, SAP publishes no fixed floor; use the official capacity estimator in the SAP Discovery Center.

Decision table — what actually moves the number

How many people need to write, not just read → the planning tier commonly costs two to three times the BI tier per user → licence BI broadly, restrict planning to the finance population that writes, typically fifty to two hundred users.

Are stories embedded in another application → embedded deployment is a separate licence → its own line, not a configuration of an existing seat.

What sits underneath → Datasphere or Business Data Cloud capacity is a separate bill → an SAC quote that does not name the platform is half a budget.

Live or import → live spends source-side query capacity, import spends storage → often close commercially, but they fail differently at scale and that is where the cost tail lives.

Custom widgets or scripted applications → an ongoing maintenance line nobody budgets → each release can break a widget, so regression testing per release is part of the price.

A closed loop into S/4HANA → a programme cost, not a licence delta → our corpus puts the initial build at €300,000-€700,000.

Building a defensible budget without a list price

Start from the write population — the people who will type a number and expect it saved. That is the planning tier and the expensive one; everyone else is a consumption seat. Getting this split wrong in either direction is the largest single error in an SAC budget.

Size the platform separately. Whatever sits underneath has its own commercial model, and the connection mode decides how hard SAC leans on it: a widely consumed dashboard on an import model shifts load off the source, and the same dashboard live puts it back.

Then add the lines that are not licences: story iteration across five to ten review rounds, ownership of every custom widget and scripted application through each release, and monitoring of import refresh jobs, which are infrastructure with an alert rather than a schedule set once.

Reading any published SAC price honestly

Three checks apply to every figure, including ours. What is its evidence grade — vendor list price, aggregator report, or a generalised deal? What date does it carry, given the field is repricing toward capacity? And does it name the tier, since a BI seat and a planning seat differ by a factor of two to three?

Reading a per-user SAC price found on an aggregator

Every aggregator page that ranks on this query shows a per-user monthly figure, and the figures disagree. That is not a data error; it is the absence of an SAP list price. The figure SAP does publish is in capacity units per user, and its currency value depends on the price per unit in your contract. Convert the units at your contract rate before comparing SAC with a tool that publishes a currency list price.

Before a figure goes into a budget, read six things next to it: the edition (business intelligence or planning — the planning tier commonly costs two to three times the BI tier per user), the date it was collected, the currency and whether tax is included, the minimum number of users the quote assumed, whether Datasphere or Business Data Cloud capacity sits underneath as a separate bill, and whether the seller was SAP or a reseller. A figure without those six answers is a rumour with a dollar sign.

The decision table above lists what actually moves the number. The defensible budget is built from those drivers, then checked against whatever aggregator figure is closest in edition and date — never the other way round.

SAP Analytics Cloud pricing 2026: the delivery cost beside the licence

Once consultants arrive, the licence is the smaller part of an SAP Analytics Cloud programme. Our band-model median for an SAC consultant is €630 a day for France at senior level (19 October 2026), against a €650 marketplace median across all seniorities (26 March 2026); an advanced SAC Planning credential adds €30 a day. Enterprise stories typically run five to ten stakeholder review rounds across four to eight weeks, so budget the iteration, not only the build. A closed loop into S/4HANA is a programme: our corpus puts the initial build at €300,000-€700,000.

What we cannot assert

SAP publishes no per-user currency price for SAP Analytics Cloud and no currency price per capacity unit; the values here are capacity units from SAP's service description guide v9-2026. We could not fetch sap.com directly (HTTP 403), so the pricing page's wording rests on search-result excerpts. We hold no verified effective price for any specific customer and publish no all-in estimate.

Frequently asked

How much does SAP Analytics Cloud cost per user?

SAP publishes no per-user currency price; its pricing page asks for a quote. Under Business Data Cloud, SAP's service description guide lists 25.60 capacity units per business intelligence user per month in the 25 to 200 band, falling to 10.54 above 5,000 users; standard planning runs from 72.85 to 41.57. The euro value depends on your contract's price per unit.

Is SAC Planning priced differently from SAC BI?

Yes, and materially — the planning tier commonly runs two to three times the per-user cost of the BI tier. That is why most enterprises licence BI broadly for consumption and scope planning to the population that genuinely needs write access.

Why is SAP Analytics Cloud pricing so hard to find?

Because the enterprise data platform field has moved from per-user list pricing to capacity and negotiated models, and SAC sits at the boundary — a per-user front end on a capacity-priced platform. Published minimums exist for the platform layer; effective spend is negotiated and workload-shaped.

SAP Analytics Cloud pricing: how do I budget without a list price?

Start from the write population, the people who will type a number and expect it saved; that is the planning tier, commonly two to three times the BI tier per user. Size the platform underneath separately, then add the lines that are not licences: five to ten story review rounds, ownership of every custom widget and scripted application through each release, and monitored import refresh jobs.

SAP Analytics Cloud implementation cost: what comes on top of the licence?

Once consultants arrive, the licence is the smaller part of an SAP Analytics Cloud programme. Our band-model median for an SAC consultant is €630 a day for France at senior level (19 October 2026), against a €650 marketplace median across all seniorities (26 March 2026). Enterprise stories typically run five to ten stakeholder review rounds across four to eight weeks, so budget the iteration, not only the build. A closed loop into S/4HANA is a programme of its own: our corpus puts the initial build at €300,000-€700,000.

Engage the editor

This guide is written by . 27 years of SAP — Datasphere, Business Data Cloud, SAC Planning, Joule. Freelance or permanent · Hybrid / remote · Anywhere in EMEA.

Profile and contact

What this page is built on

External sources

Read next

Alert me to new SAP Analytics Cloud missions

No account needed. We first ask you to confirm by e-mail; nothing is sent without that confirmation, and every alert has a one-click unsubscribe link. Privacy

Open missions

89 live roles and contracts in SAP Analytics Cloud right now — see the SAP Analytics Cloud missions · freelance SAP contracts.