Getting the Best Deal on SAP Analytics Cloud: User vs. Capacity Licensing Explained

Why SAP Analytics Cloud Licensing Is More Complicated Than It Looks

SAP Analytics Cloud (SAC) combines business intelligence, planning, and predictive analytics in a single platform. That integration is its primary commercial proposition — and also the source of its most common licensing problem. Because SAC bundles multiple capabilities into a single product, the licence type a user is assigned must accurately reflect what that user actually does in the platform. Misclassification — in either direction — creates either a compliance exposure or an overpayment that persists for the life of the contract.

SAP's sales teams are incentivised to sell at the highest possible licence tier. Left to their own recommendation, they will typically propose Planning Professional licences for any user who touches a planning model — regardless of whether that user is creating and modifying planning models or simply entering data in a predefined template. The commercial difference between these two activities is significant. The licence type difference between a BI user and a Planning Professional user is approximately three to five times the cost per user per month at list pricing.

For an organisation deploying SAC to 500 users — a realistic enterprise deployment — the choice between classifying 200 of those users as Planning Standard versus Planning Professional represents an annual cost difference of hundreds of thousands of euros. Making that classification on the basis of SAP's recommendation rather than an independent analysis of actual usage requirements is one of the most consistent sources of SAC overspend we observe across our client base.

The Three User Types: What Each Actually Entitles You To

SAC Business Intelligence (BI) User

The BI user licence is the entry-level SAC licence. BI users can access published dashboards and stories, run reports, consume visualisations, export data, perform ad-hoc analysis on existing data models, and interact with live data connections. They cannot create or modify planning models, enter or edit planning data, or run complex scenario simulations. At list pricing, a BI user costs approximately €180 per user per month, though negotiated rates for volume commitments typically land between €70 and €120 per user per month for enterprise agreements.

The BI user licence is the correct licence for the largest population in most SAC deployments: people who consume analytics outputs rather than build or modify them. Finance leadership reviewing monthly performance dashboards, sales managers monitoring pipeline reports, and operational teams accessing production KPI displays are typically BI users. Many organisations over-classify this population as Planning Standard or Planning Professional because their SAP account team characterised any access to financial data as a planning activity.

SAC Planning Standard User

The Planning Standard licence includes everything in the BI licence plus the ability to enter and edit data within existing planning models, adjust budget figures within predefined templates, contribute to collaborative planning workflows, and participate in planning processes that have been configured by a Planning Professional user. Planning Standard users cannot create new planning models, define new dimensions or hierarchies, or access the advanced analytical features of the Planning Professional tier.

Planning Standard is the appropriate licence for budget owners, cost centre managers, and business unit contributors who participate in planning cycles but do not own or configure the planning infrastructure. In a typical annual budgeting process, the 80 percent of users who review and edit their own cost centre budgets within a pre-built template are Planning Standard users. The 20 percent who configure the planning model, build the budget templates, and manage the allocation logic are Planning Professional users.

SAC Planning Professional User

The Planning Professional licence is the most comprehensive and most expensive SAC tier. Professional users can create and modify planning models, define dimensions and hierarchies, build and modify stories and dashboards, access advanced predictive analytics, run complex multi-scenario analyses, and configure the planning environment that Standard and BI users access. At list pricing, a Planning Professional licence is approximately three to five times the cost of a BI user licence, depending on volume and the commercial relationship.

Planning Professional licences are genuinely required for a specific population — typically FP&A analysts, financial controllers, analytics engineers, and planning architects. The error we consistently see is organisations where every finance team member has been classified as Planning Professional because their role involves financial data, when the majority of those users are executing data entry and review functions that Planning Standard or even BI licences adequately support.

Named User vs. Capacity Licensing: The Model Decision

How Named User Licensing Works

Named user licensing — the default SAC commercial model — assigns a specific licence type to each individual user, billed monthly regardless of how frequently or intensively that user actually accesses the platform. An organisation with 200 BI users pays for 200 BI user months every month, whether each of those users accessed SAC daily or once in the quarter.

Named user licensing delivers value when usage is reasonably consistent across the licensed population — when 70 percent or more of licensed users access the platform regularly and use the capabilities their licence tier provides. It creates waste when a significant portion of the licensed population has intermittent or seasonal access patterns, or when users are licensed at a tier they rarely fully utilise.

How Capacity-Based Licensing Works

SAP Analytics Cloud is also available through a capacity-based licensing model under the SAP Business Data Cloud (BDC) framework, which charges by Capacity Units (CU) rather than by named user. Capacity Units are a combined measure of the computational, storage, and memory resources consumed by SAC workloads. Instead of paying per user, an organisation purchases a bundle of Capacity Units and consumes from that bundle based on actual platform usage.

Capacity-based licensing delivers better value in specific scenarios: organisations with large populations of occasional users who access SAC infrequently, environments where usage is highly seasonal (annual planning cycles, quarterly reporting periods), and deployments where a significant proportion of SAC access is by external stakeholders who require limited, periodic access. It creates unpredictability risk in environments where usage patterns are variable and difficult to forecast, as overconsumption of the Capacity Unit bundle triggers overage charges at rates substantially above the bundle average.

The Model Selection Framework

The Classification Trap: What SAP Does Not Tell You

There is a specific commercial dynamic in SAC licensing that SAP's sales teams consistently fail to disclose: the licence type classification is set at contract execution and does not automatically update when a user's actual behaviour diverges from their licence tier. A user classified as Planning Professional who spends 90 percent of their SAC time viewing dashboards and 10 percent entering budget data in a pre-built template could be legitimately reclassified as Planning Standard at renewal — reducing their licence cost by 60 to 80 percent — but SAP has no commercial incentive to suggest that reclassification.

Organisations that are approaching their SAC renewal should conduct an independent usage analysis — reviewing actual platform activity logs to determine what each licensed user does in the platform, not what their job title implies they might need. This analysis, conducted with an independent adviser rather than the SAP account team, consistently identifies reclassification opportunities that reduce the renewal cost by 20 to 35 percent for a meaningful proportion of the user population.

The BTP credit structure adds a further dimension. SAC deployed as part of a RISE with SAP or BTP agreement may consume BTP credits for certain workloads — particularly when SAC is integrated with SAP BTP data services, machine learning workloads, or advanced predictive capabilities. Organisations that licensed SAC as a standalone product may face incremental BTP credit charges when enabling features that are marketed as part of the SAC platform but that require BTP resources to execute. This consumption rarely appears in the initial licence discussion.

SAP Analytics Cloud and the SAP Business Data Cloud Transition

In 2025, SAP introduced the SAP Business Data Cloud (BDC) as a strategic repackaging of its analytics, data management, and AI capabilities — with SAP Analytics Cloud positioned as the primary analytics layer within the BDC framework. For organisations evaluating or renewing SAC, the BDC transition is relevant for two reasons.

First, SAP is progressively steering new SAC agreements toward the BDC/Capacity Unit model rather than the standalone named user model. Sales teams receive incentives for BDC agreements and may present the BDC capacity model as the recommended or default pathway. Capacity Unit pricing, particularly at the base tier, can appear competitive against equivalent named user costs at first comparison — but the total cost of ownership over a three to five year term depends heavily on actual usage patterns and the organisation's ability to forecast and manage CU consumption accurately.

Second, the BDC framework bundles SAC with other SAP data products — SAP Datasphere, SAP AI Core, and related data management services. Organisations that do not require the bundled services may find that standalone SAC, on a negotiated named user model, remains the more cost-effective approach for their specific requirements. Accepting the BDC bundle because it was the account team's recommendation — without independently modelling whether the bundled services will actually be used — is a predictable route to paying for capabilities that generate no operational value.

How to Negotiate SAC Effectively

Start With Usage Analysis, Not User Count

The correct starting point for any SAC licence negotiation is an independent analysis of actual or projected usage behaviour — what will each user type do in the platform, at what frequency, and with what computational intensity. This analysis is the foundation for selecting the right licence model, classifying users at the correct tier, and building a total cost model that SAP's account team cannot easily challenge because it is grounded in the client's own operational data.

Benchmark Against the Market

SAP Analytics Cloud pricing is negotiable at all volume levels, and the negotiated discount for enterprise agreements typically ranges from 35 to 60 percent off list, depending on total SAP relationship size, contract term, and the commercial context of the negotiation. Organisations that accept the first SAP offer without benchmarking against the range of outcomes achieved by comparable organisations are consistently leaving material savings on the table. Independent benchmarking provides the reference point that transforms a price discussion into a negotiation.

Lock In Annual Price Escalation Caps

SAC agreements without explicit annual price escalation caps are subject to SAP's standard contract renewal terms, which can include material price increases at renewal. For a multi-year SAC agreement, securing a contractual cap of three to four percent annual escalation protects the total cost of ownership across the contract term and eliminates the pricing uncertainty that makes multi-year SAC budget planning unreliable. This clause is available and is consistently granted to organisations that make it an explicit negotiation priority — SAP does not volunteer it.

Negotiate Right-Sizing Provisions

The usage patterns that apply at contract execution may not be the usage patterns that apply in year three of the agreement. Organisations whose SAC deployments are still in early stages of adoption should negotiate explicit provisions for licence type reclassification or user count reduction at defined intervals — typically annually — without penalty. This is commercially unusual in SAP agreements but achievable for organisations that make it a condition of the initial deal rather than a post-execution request.

The Bottom Line on SAC Licensing

SAP Analytics Cloud is a commercially capable platform that most organisations are overpaying for — not because the platform lacks value, but because the licence structure is designed to default to the most expensive classification at each decision point. The choice between named user and capacity models, the classification of users across three tiers with dramatically different price points, and the BDC transition that SAP is actively promoting all create commercial decision points where independent expertise consistently produces better outcomes than accepting the account team's recommendation.

For organisations with existing SAC agreements approaching renewal, the independent usage analysis is the starting point. For organisations evaluating their initial SAC deployment, the independent model selection and user classification exercise conducted before engaging SAP's commercial team is the prerequisite for a negotiation that reflects what your organisation actually needs — rather than what SAP's sales incentive structure was designed to deliver.