Table of Contents
- Introduction: Why SAP Analytics Cloud Licensing Matters
- Understanding the Licensing Landscape
- User-Based Licensing: Paying per Named User
- Capacity-Based Licensing: Paying for Usage
- Comparing User vs. Capacity Models
- Bundling Strategies to Maximise Value
- Negotiation Recommendations
- Five Actions to Take Before Signing
- Frequently Asked Questions
Introduction: Why SAP Analytics Cloud Licensing Matters
SAP Analytics Cloud (SAC) has become SAP's flagship analytics platform, combining business intelligence, planning, and predictive capabilities in a single cloud-native solution. For enterprise IT leaders and procurement teams, SAC is increasingly appearing on renewal agendas and digital transformation roadmaps, and the commercial terms are frequently more complex than they appear.
The licensing model you choose for SAC has a direct and lasting impact on your total cost of ownership. SAP offers two fundamentally different approaches: user-based licensing (paying per named user) and capacity-based licensing (paying per usage volume). The right choice depends on how your organisation plans to deploy SAC, who will use it, and how often.
This guide explains both models in detail, provides a structured comparison framework, identifies the bundling and negotiation strategies that deliver the best commercial outcomes, and outlines the five actions every procurement team should take before signing an SAC agreement. The advisory is independent — Redress Compliance has no commercial relationship with SAP.
A note on terminology: SAP has rebranded and restructured its analytics portfolio several times in recent years. The capacity-based model has evolved alongside SAP's broader Business Technology Platform (BTP) strategy, with SAC increasingly positioned as a BTP service that can be consumed through cloud credits. We address this in the bundling section.
Understanding the SAP Analytics Cloud Licensing Landscape
SAP Analytics Cloud is sold exclusively as a subscription service. There are no perpetual licence options. This means you are committing to an annual or multi-year recurring cost, and the terms you negotiate at the outset will govern your spend for the duration of the agreement.
SAP offers two primary approaches:
The per-user model charges a fixed subscription fee for each named individual who will access SAC. Costs scale linearly with headcount. Simple, predictable, but rigid.
The capacity-based model charges based on usage metrics — typically data volume processed, compute resources consumed, or query throughput. No hard user limit. Flexible but variable.
The choice between these models is not merely a procurement decision. It is a strategic one that shapes how broadly your organisation can deploy analytics, how you budget for growth, and how much negotiation leverage you retain at renewal. SAP has progressively integrated SAC into the broader BTP ecosystem, which means procurement decisions about SAC now have downstream implications for BTP credit consumption.
User-Based Licensing: Paying per Named User
The most common licensing model for SAP Analytics Cloud is per-user subscription pricing. Every SAC user must be assigned a named-user licence. There is no concept of concurrent or shared licensing. SAP offers multiple user licence tiers:
Standard Analytics Access
View and interact with dashboards, reports, and stories. Run queries and schedule reports. This is the lower-cost tier, suitable for consumers of analytics who do not create their own content.
Planning and Analysis Access
All BI capabilities plus financial planning, budgeting, forecasting, and data input. Higher cost tier, typically 2 to 3 times the price of a standard BI licence. Assign only to users who actively participate in planning processes.
Advanced Design and Modelling
Full design capabilities for creating stories, models, and analytic applications. Often bundled with the Planning licence or available as a separate tier. Assign to analytics teams building content for others.
Cost Dynamics and Shelfware Risk
Per-user pricing makes budgeting straightforward. However, the model creates a significant shelfware risk. In our experience advising enterprises on SAP licensing, the average SAC deployment sees 25 to 40 percent of named-user licences going unused or underused within the first 12 months. Users are licensed during deployment planning before adoption has been proven.
SAP's standard contractual terms make it difficult to reduce user counts mid-term. Licences are typically committed for the full subscription period (1 to 3 years), and you cannot downsize until the next renewal window. The lesson: start conservative, licence only confirmed users, and negotiate contractual provisions for mid-term scaling rather than buying for projected demand.
Case Example: Right-Sizing SAC Licences for a Global Manufacturer
A manufacturing firm initially licensed 150 SAC users (130 BI licences and 20 Planning licences). After 6 months, usage data showed only 85 BI users and 18 Planning users were active. The 45 unused BI licences represented approximately $180,000 per year in wasted spend.
Lesson: Licence for confirmed demand, not projected adoption. Negotiate true-down rights or phased deployment commitments to avoid locking in shelfware.
User-based licensing works best when your SAC user population is well-defined, relatively stable, and actively engaged. Typical good-fit scenarios include dedicated analytics teams of 50 to 500 users, finance departments using SAC for planning and consolidation, and operational teams with daily dashboard workflows.
See how a global manufacturer reduced SAP spend by 28%
Capacity-Based Licensing: Paying for Usage
For certain deployment scenarios — particularly those involving very large or unpredictable user populations — SAP offers SAC licensing based on consumption rather than headcount.
How It Works
Capacity-based SAC licensing ties costs to system usage metrics rather than the number of named users. The specific metric varies depending on how SAP structures the deal, but common measures include data volume processed (in GB), compute resource hours consumed, monthly active sessions, or, increasingly, SAP BTP cloud credits consumed.
When Capacity Licensing Makes Sense
Capacity-based licensing delivers its greatest value when the user population is large but usage per user is low or sporadic. Consider a global retail chain that wants 5,000 store managers to access weekly sales dashboards. Licensing 5,000 named users would be prohibitively expensive, but the aggregate consumption of 5,000 users checking dashboards for 15 to 20 minutes per week is quite modest.
Risks and Cost Management Challenges
The primary risk of capacity-based licensing is cost unpredictability. A sudden surge in data volumes, an unanticipated adoption spike, or a change in how users interact with the platform can push consumption above the purchased capacity, triggering overage charges.
Watch Out — SAP BTP Credit Consumption: If SAC consumption is funded through SAP BTP cloud credits, be aware that other BTP services (Integration Suite, Data Intelligence, Launchpad, etc.) may also draw from the same credit pool. Without careful monitoring, SAC usage can quietly consume credits intended for other services.
Case Example: Capacity Model Saves 55% for Retail Chain with 5,000 Occasional Users
A global retail chain wanted to give 5,000 store managers weekly access to sales dashboards. Under a user-based model, 5,000 BI licences would have cost approximately $2.4M per year. Each manager would only access SAC for 15 to 20 minutes per week.
Approach: Redress helped the retailer model aggregate consumption across 5,000 users at projected usage intensity. The total was equivalent to approximately 400 full-time users.
Result: Capacity-based licensing at $1.1M per year — a 55 percent saving compared to the user-based alternative, with all 5,000 managers retaining full access.
Takeaway: When the ratio of occasional users to power users is high, capacity-based pricing almost always delivers superior economics. The key is modelling actual consumption, not headcount.
Hybrid Models: Combining Both Approaches
An increasingly common and often optimal approach is to combine both licensing models within a single SAC deployment. In a hybrid structure, named-user licences are procured for a core group of daily power users (typically 50 to 200 analysts, planners, and content creators), while a capacity-based allocation extends SAC access to a broader population of occasional consumers. This preserves cost predictability for the core team while avoiding the shelfware risk of licensing thousands of infrequent users at a named-user rate.
Comparing User vs. Capacity Licensing Models
The following comparison framework summarises the key differences across dimensions that matter most to procurement teams.
| Dimension | User-Based | Capacity-Based |
|---|---|---|
| Pricing basis | Per named user per year | Per consumption unit (data/compute/sessions) |
| Cost predictability | High — fixed subscription | Variable — depends on usage patterns |
| Shelfware risk | High — unused licences still billed | Low — pay only for actual consumption |
| Best for | Defined, active, regular users | Large populations, infrequent access |
| Scaling | Linear with headcount | Scales with usage not users |
| Mid-term flexibility | Low — committed licence count | Medium — with overage controls |
| BTP integration | Standard subscription | Can fund via BTP credits |
Finding the Break-Even Point
The most effective way to choose between models is to calculate the break-even point. Request quotes from SAP for both models based on your projected user count and usage volume. In advisory experience, the crossover point is typically around 500 to 1,000 users. Below 500 active users, per-user pricing is usually cheaper. Above 1,000 users, capacity-based pricing typically wins.
The default choice for most enterprises is user-based licensing because it is simpler. But simpler is not the same as cheaper. Organisations with 2,000 or more occasional SAC users routinely pay 40 to 60 percent more than they would under a capacity-based model, simply because no one ran the break-even analysis before signing.
Bundling Strategies to Maximise Value
SAP's pricing for any individual product, including SAC, improves when it is negotiated as part of a larger commercial relationship. Procurement teams should exploit this dynamic aggressively.
Bundle SAC with RISE with SAP or S/4HANA Cloud
If your organisation is adopting RISE with SAP for ERP transformation, SAC should be negotiated as part of that deal, not procured separately. SAP routinely offers preferential SAC pricing (sometimes including complimentary SAC licences or BTP credits) as an incentive for RISE adoption. Procuring SAC separately after the RISE deal is signed forfeits this leverage entirely.
Use SAP BTP Credits for SAC Consumption
If you already hold or are about to purchase SAP BTP cloud credits, SAC consumption can often be funded from those credits rather than through a separate SAC subscription. This is particularly advantageous if you have excess BTP credits that would otherwise go unused. However, ensure that BTP credit consumption terms are clearly defined and that SAC does not cannibalise credits needed for other services.
Leverage Legacy SAP Investments
SAP sometimes offers migration incentives for customers transitioning from legacy analytics tools. If you hold existing SAP BusinessObjects, SAP BPC, or SAP Lumira licences with active maintenance, ask SAP whether these investments can be converted into SAC subscription credits. Such programmes are not broadly advertised but are often available for large customers.
Align Contract End Dates Across SAP Products
Co-terming SAC with other major SAP renewals (S/4HANA, SuccessFactors, Ariba) creates a high-value renewal event that gives procurement maximum leverage. SAP's sales teams are motivated to close large deals, and a unified renewal is significantly harder for SAP to walk away from than an isolated SAC renewal.
SAP Licensing Intelligence
Negotiation Recommendations
Beyond choosing the right licensing model and leveraging bundling, several negotiation-level tactics consistently deliver better SAC deals.
1. Assess Your Usage Profile Before Engaging SAP
Analyse how many users truly need SAC access and how they will use it. Categorise by role: daily power users (BI analysts, finance planners), regular consumers (weekly dashboard viewers), and occasional users (monthly report consumers). This segmentation directly informs whether user-based or capacity-based pricing is optimal, and what licence tier mix to request.
2. Start Small and Scale
SAP's sales teams are incentivised to sell the largest possible initial commitment. Resist this pressure. Pilot SAC with a core group of 50 to 100 confirmed users, prove the value, then expand based on demonstrated demand. Negotiate contractual provisions for mid-term scaling at pre-agreed unit rates to avoid paying for growth before it materialises.
3. Optimise Your Licence Mix
Assign expensive Planning licences only to users who actively participate in planning, budgeting, or forecasting processes. Every other user should receive a lower-cost BI licence. In large deployments, this tier optimisation alone can save 20 to 30 percent of the total SAC cost, because Planning licences are typically 2 to 3 times the price of standard BI licences.
4. Negotiate Flexibility and Price Protection
Push for contractual terms that allow adjustments: the right to swap licence types, the ability to reduce quantities at annual anniversary points (true-down rights), and multi-year price locks that prevent SAP from increasing unit prices at renewal. Negotiate an explicit cap on any annual price escalation clause.
5. Consider a Hybrid Approach
In some cases, the optimal structure is a mixed model: named-user licences for your core analytics and planning team (50 to 200 daily users) combined with a capacity-based model to extend SAC access to a broader population (1,000 or more occasional consumers). Run the cost comparison for both components to ensure the hybrid delivers a genuine saving.
6. Monitor and Adjust Continuously
SAC licensing is not a set-and-forget decision. Track actual usage throughout the contract term: identify underused licences that can be reallocated or eliminated at renewal, detect usage trends that signal a need for additional capacity, and build the data case for your next negotiation.
Download the SAP Analytics Cloud Licensing and Negotiation Guide
Five Actions to Take Before Signing
Before executing any SAP Analytics Cloud agreement, every procurement team should complete these five steps.
Before your SAP Analytics Cloud renewal, five steps separate enterprises that save from those that overspend. The difference is preparation, not negotiation talent.