Models
via Optimisation
Terms
Before Signing
📖 In This Guide
- Introduction: Why SAC 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, often as a replacement for legacy SAP BusinessObjects or SAP BPC deployments, or as a required component of broader RISE with SAP and S/4HANA Cloud initiatives.
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), and the right choice depends on how your organisation consumes analytics. Choosing incorrectly can result in significant overspend: enterprises with broad but infrequent analytics usage may pay for hundreds of unused named-user licences, while organisations with intensive daily usage may find capacity-based pricing unpredictably expensive.
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 does not resell SAP licences and 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 rather than standalone subscriptions. This guide reflects the current (2025) licensing landscape, but procurement teams should verify the latest SAP packaging with their account team or an independent advisor.
User-Based Model
Fixed subscription per named user. Predictable, simple to budget, but creates shelfware risk if user counts are overestimated.
Capacity-Based Model
Pay per consumption (data volume, compute). Flexible for large user populations but costs vary with usage patterns.
Bundling Leverage
SAC pricing improves significantly when bundled with RISE with SAP, BTP credits, or multi-product enterprise agreements.
Renewal Trap Risk
First-year discounts often vanish at renewal. Secure price protections and escalation caps upfront before signing.
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 licensing approaches:
Per-User Licensing
Pay a fixed subscription fee for each named individual who will access SAC. Costs scale linearly with headcount. Simple, predictable, but rigid.
Capacity-Based Licensing
Pay 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. It is also worth noting that SAP has progressively integrated SAC into the SAP Business Technology Platform (BTP) framework, which means capacity-based consumption can sometimes be funded through BTP cloud credits rather than through a standalone SAC contract.
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. Lower cost tier, suitable for consumers of analytics who do not create their own content.
Planning & Analysis Access
All BI capabilities plus financial planning, budgeting, forecasting, and data input. Higher cost tier, typically 2-3x the price of a standard BI licence. Only assign to users who actively participate in planning processes.
Advanced Design & 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-40% of named-user licences going unused or underused within the first 12 months. Users are licensed during the procurement phase based on projected adoption, but actual uptake invariably falls short of projections.
SAP's standard contractual terms make it difficult to reduce user counts mid-term. Licences are typically committed for the full subscription period (1-3 years), and you cannot downsize until the next renewal window. The lesson: start conservative, licence only confirmed users, and negotiate contractual provisions allowing mid-term additions and, critically, end-of-year true-down rights.
Best-Fit Scenarios for User-Based Licensing
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-500 users, finance departments using SAC for planning and consolidation, and operational teams with daily dashboard requirements. If more than 70% of your licensed users will access SAC at least weekly, the per-user model is likely your most cost-effective option.
Right-Sizing SAC Licences for a Global Manufacturer
Situation: 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/yr in wasted spend.
Lesson: Licence for confirmed demand, not projected adoption. Negotiate true-down rights or phased deployment commitments to avoid locking in shelfware.
Related Guide: For broader strategies on avoiding shelfware across all SAP products, read our Top 15 SAP Negotiation Tricks for IT Sourcing Leaders.
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 drawn down against a prepaid credit pool. The key distinction is that there is no hard limit on the number of users who can access the system, provided total consumption stays within the purchased capacity envelope.
When Capacity Licensing Makes Sense
Capacity-based licensing delivers its greatest value in scenarios where 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 actual consumption is modest in aggregate. Other strong use cases include extended enterprise scenarios (giving suppliers, partners, or customers analytics access), organisations undergoing rapid headcount growth, and companies embedding SAC analytics into other applications via APIs.
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. To manage this risk, procurement teams must ensure the contract clearly defines: how consumption is measured and reported, what happens when usage approaches the capacity limit, what the overage pricing is (and whether it is capped), and whether unused capacity rolls forward to subsequent periods.
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 workloads. Ensure your SAP agreement clearly allocates BTP credits by service, or establish internal governance to track credit consumption across all BTP services.
Capacity Model Saves 55% for Retail Chain with 5,000 Occasional Users
Situation: 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-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/yr, a 55% 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-200 analysts, planners, and content creators), while a capacity-based allocation covers the broader population of occasional dashboard viewers and report consumers. SAP does not always proactively offer hybrid structures, but they are achievable through negotiation, particularly when supported by detailed usage modelling.
Comparing User vs. Capacity Licensing Models
The following comparison framework summarises the key differences across the dimensions that matter most to procurement teams and IT leaders.
| Dimension | User-Based Licensing | Capacity-Based Licensing |
|---|---|---|
| Cost Metric | Fixed fee per named user per year | Variable fee based on consumption (data, compute, sessions) |
| Cost Predictability | High: linear scaling, easy to budget | Low to medium: varies with usage patterns |
| User Flexibility | Rigid: must buy more licences to add users | High: unlimited users within capacity envelope |
| Shelfware Risk | High: unused licences still incur full cost | Low: you pay for what is consumed |
| Overage Risk | None: costs are fixed regardless of usage | High: usage spikes can trigger unplanned costs |
| Contract Complexity | Simple: count users, multiply by price | Complex: requires defined measurement, caps, rollover |
| Best For | Defined teams of 50-500 active daily users | Broad populations of 1,000+ occasional users |
| Worst For | Thousands of infrequent dashboard viewers | Small teams with intensive, predictable daily usage |
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 our advisory experience, the crossover point is typically around 500-1,000 users. Below 500 active users, per-user pricing is usually more cost-effective. Above 1,000 users, particularly if many are occasional consumers, capacity-based pricing often delivers a lower total cost. Between 500 and 1,000 users, the optimal model depends heavily on usage intensity.
The default choice for most enterprises is user-based licensing because it is simpler. But "simpler" is not the same as "cheaper." We routinely see organisations with 2,000+ occasional SAC users paying 40-60% 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 standalone after the RISE deal is signed eliminates 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 allocation is contractually clear.
📦 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 always advertised; you often need to ask explicitly.
📦 Align Contract End Dates Across SAP Products
If you hold multiple SAP agreements with different expiration dates, your negotiation leverage is fragmented. By aligning contract end dates (co-terming), you create a single, large renewal event where your total SAP spend is on the table simultaneously. This gives procurement maximum leverage to negotiate SAC pricing as part of a comprehensive multi-product deal.
🎯 Bundling Checklist Before Your Next SAC Negotiation
- Map your entire SAP estate: Identify every SAP agreement, its end date, and its annual value.
- Identify co-terming opportunities: Can you align SAC with other SAP renewals?
- Check for conversion credits: Do you hold legacy SAP BusinessObjects, BPC, or Lumira licences?
- Quantify BTP credit availability: Model whether funding SAC through BTP credits is more cost-effective.
- Time the negotiation: SAP's financial year ends in December. Q4 deals often attract better pricing.
Related Guide: For comprehensive SAP negotiation strategies, see our SAP Contract Negotiation Service and our guide to cutting SAP ECC maintenance costs before 2027.
Negotiation Recommendations
Beyond choosing the right licensing model and leveraging bundling, there are several negotiation-level tactics that 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 users by role: daily power users (BI analysts, finance planners), regular consumers (weekly dashboard viewers), and occasional users (monthly report consumers). This user segmentation directly informs whether user-based or capacity-based licensing is optimal.
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-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 lock in pricing without locking in volume.
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-30% of the total SAC cost, because Planning licences are typically 2-3x the price of 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. SAP's standard terms often include uplift provisions of 3-5% per year, which compound significantly over a 3-year term.
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-200 daily users) combined with a capacity-based model to extend SAC access to a broader population (1,000+ occasional consumers). Run the cost comparison for both components to ensure the hybrid approach delivers a lower total cost.
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.
SAP's analytics licensing has become significantly more complex as SAC evolves and BTP integration deepens. The enterprises that save the most are those that engage independently before the SAP sales cycle begins, not after the quote has arrived and the negotiation timeline is already compressed.
Five Actions to Take Before Signing
Before executing any SAP Analytics Cloud agreement, every procurement team should complete these five steps.
1 Map Your Requirements
Document how many people will use SAC and what they need it for: viewing only, creating reports, planning input, or advanced modelling. Categorise users by role and usage frequency. This user map becomes the foundation for every subsequent decision about licensing model, licence mix, and volume commitment.
2 Request Both Pricing Options from SAP
Ask SAP to provide parallel quotes: one for a defined number of named users (broken down by licence tier) and one for an equivalent capacity metric. Ensure the capacity quote specifies exactly how usage will be measured, what the overage terms are, and whether unused capacity rolls forward.
3 Simulate Your Costs Over 1-3 Years
Project your SAC costs under each model using your organisation's data, not SAP's assumptions. Factor in realistic adoption curves (typically 60-70% of projected users are active in Year 1, rising to 80-90% by Year 3), seasonal usage variations, and planned growth. Identify the crossover point.
4 Plan Your Negotiation Strategy
Define your targets before engaging SAP: maximum acceptable unit price, desired contract length, required flexibility provisions (true-down rights, licence swaps, price escalation caps), and walk-away thresholds. Gather leverage: total SAP spend across all products, competitive alternatives (Power BI, Tableau, Looker), and timing alignment with SAP's fiscal calendar.
5 Scrutinise the Contract Before Signing
Review all terms in detail. Confirm that negotiated discounts, price caps, and flexibility provisions are explicitly documented. Check for automatic renewal clauses. Verify that measurement definitions for capacity-based models are unambiguous. Pay particular attention to data portability and exit terms: ensure the contract explicitly addresses data export rights, the format in which data will be returned, and the timeline for data retrieval after contract expiration.
Related Reading
Frequently Asked Questions
What is the difference between user-based and capacity-based SAC licensing?
User-based licensing charges a fixed subscription fee per named user, simple to budget but creates shelfware risk if adoption falls short. Capacity-based licensing charges based on consumption (data processed, compute used) regardless of user count, flexible for large populations but variable in cost. The right choice depends on your user count, usage intensity, and budget tolerance for variability.
How do we determine which model is more cost-effective?
Request parallel quotes from SAP for both models and run a break-even analysis. Calculate total cost over the contract term under realistic adoption scenarios. Typically, user-based pricing is cheaper below ~500 active users; capacity-based pricing is cheaper above ~1,000 users, but the crossover depends on usage intensity. An independent advisor can benchmark SAP's quotes against market rates.
Can we switch licensing models mid-contract?
Generally, your contract specifies one model for the term. Switching mid-contract is technically possible but typically requires a commercial amendment with SAP. The best approach is to negotiate model-switch provisions upfront as part of the original agreement, or plan the switch for the next renewal window. Some enterprises use a hybrid approach to avoid the need to switch entirely.
How can bundling SAC with other SAP purchases improve pricing?
SAP provides better per-unit pricing when SAC is included in larger deals. Bundling SAC with RISE with SAP, S/4HANA Cloud, or a multi-product enterprise agreement increases total deal value, which gives SAP's sales team justification for deeper discounts. Additionally, legacy SAP analytics investments (BusinessObjects, BPC) can sometimes be converted into SAC credits. The key is to negotiate SAC pricing while the larger deal is still being finalised.
What pitfalls should we avoid when negotiating SAC licences?
The five most common pitfalls are: overcommitting on user counts before adoption is proven; accepting SAP's first-year discount without securing renewal price protection; choosing capacity-based licensing without contractual overage caps; failing to negotiate true-down rights that allow licence reduction at anniversary points; and procuring SAC as a standalone deal when it could have been bundled with a larger SAP negotiation for significantly better pricing.
Negotiating an SAP Analytics Cloud Deal?
Do not accept SAP's standard pricing without independent benchmarking. A brief consultation with Redress Compliance can identify the right licensing model, optimal deal structure, and negotiation leverage to deliver measurable savings on your SAC investment.
SAP Contract Negotiation Service → Book a Consultation