In roughly 1 in 3 seats benchmarked, the expensive planning license sat on a user who never wrote back a single value
In SAC you are not buying analytics. You are buying user types, and the wrong type is the whole overspend.
Prepared by Redress Compliance · August 19, 2026 · SAP Analytics Cloud negotiations. 20 to 30 benchmarked, 2024 to 2025.
Executive summary
Planning licenses sat on pure report consumers in 25 to 40 percent of seats, across roughly 20 to 30 SAP Analytics Cloud negotiations benchmarked between 2024 and 2025.
Planning costs roughly twice the BI unit price, because it enables write back, version management and forecasting that a viewer never touches.
SAC was bundled into a wider deal where its unit price was never benchmarked, and opacity inside a bundle favors the seller by default.
Active user growth triggered true ups that reset the committed floor upward, so the split has to be revisited at every one of them.
What are the SAP Analytics Cloud license types?
Two user license types, business intelligence and planning. Planning unlocks write back and forecasting, and costs significantly more.
Both are described in the SAP Analytics Cloud documentation.
BI against planning
- BI users: dashboards, stories and reporting consumption.
- Planning users: data entry, forecasting and write back to models.
- Mixed populations: most viewers need BI, not planning.
| Type | Capability | Relative cost |
|---|---|---|
| Business intelligence | Dashboards, reporting | Lower |
| Planning | Write back, forecasting | Higher |
| Bundled inside RISE | Embedded allocation | Opaque |
The wider model set is covered in our SAP cloud licensing models guide.
Why do planning licenses cost more?
Because they enable write back, version management and forecasting, as set out in the capabilities documentation.
Paying that premium for users who only read reports is the most common SAC overspend, and it is invisible on an invoice that shows a single seat count.
Match the license to the behavior
- Audit who actually enters or changes data against who only views it.
- Move pure consumers to the BI license tier.
- Reserve planning seats for the finance and operations users who model.
The analytics estate strategy sits in our data and analytics playbook for CIOs.
- The standalone per user price benchmarked against real closed SAP deals
- Every renewal and true up clause flagged with paste ready replacement language
- The planning against BI split modelled from actual usage, seat by seat
How does SAC pricing hide inside SAP bundles?
SAC frequently arrives inside a larger SAP agreement or a RISE with SAP bundle, where its per user price is never isolated. Opacity favors the seller.
The RISE programme is described at the RISE product page, and the governing terms at the cloud service terms.
Force the unit price into daylight
- Ask SAP to state the standalone SAC per user price inside the bundle.
- Benchmark that unit price against a standalone quote.
- Confirm what happens to SAC entitlement if the bundle is restructured.
Model the wider position first with the RISE total cost calculator, and the RISE negotiation itself in our RISE negotiation guide.
The SAP Analytics Cloud negotiation brief
The planning against BI split, the bundle unit price question, and the renewal protection to write before you commit.
Get the brief →What 20 to 30 SAC negotiations showed
Across the SAP Analytics Cloud negotiations benchmarked between 2024 and 2025, the planning against BI split was the dominant cost driver.
The three patterns that recurred
- Planning licenses were assigned to pure report consumers in 25 to 40 percent of seats.
- SAC was bundled into a wider deal where its unit price was never benchmarked.
- Active user growth triggered true ups that reset the committed floor upward.
The three compound. An unbenchmarked unit price applied to an oversized planning population, trued up on growth, is the expensive version of the same deal.
Research briefingReading the SAP estate before the renewalWhere user types, bundle scope and true up mechanics meet, and which of them a buyer can still move.
Where the common advice on SAC pricing is wrong
The common advice is to standardize on the planning license so every user has full capability. We disagree.
In roughly 1 in 3 seats benchmarked, the expensive planning license sat on a user who never wrote back a single value. Standardizing up is convenient for administration and expensive forever.
Split the population by real behavior, license the small modeling group on planning and the large viewing group on business intelligence, and revisit the split at every true up.
Capability you never use is not a safety margin, it is recurring waste. The line between a planning user and a viewer is the single most valuable distinction in an SAC negotiation.
Paying the write back premium for users who only read.
The multiple that makes the split worth auditing every cycle.
Planning licenses sitting on pure report consumers.
What negotiation levers work on SAC?
List pricing is heavily negotiable at volume, and timing against the wider SAP renewal multiplies the leverage.
Read the cloud service terms before agreeing any commit, because the commit mechanics decide what a true up does to you later.
The three levers that move price
- Co term SAC with the main SAP renewal so it is negotiated as one event.
- Commit volume only where adoption is proven, never where it is projected.
- Negotiate price protection on renewal, not just on the first term.
Your first five moves
- Pull active usage by user for the last two quarters, because the split has to come from behavior rather than from role titles.
- Split the population into modelers and viewers, then move the viewers from planning to business intelligence.
- Force the standalone SAC unit price out of any bundle and benchmark it against a standalone quote.
- Co term SAC with the main SAP renewal so the two are negotiated as a single event.
- Negotiate renewal price protection rather than first term pricing alone, and revisit the seat split at every true up.
Frequently asked questions
What are the SAC license types?
Two user types, business intelligence and planning. Planning unlocks write back and forecasting, and costs significantly more.
How many planning seats are misassigned?
Between 25 and 40 percent were assigned to pure report consumers across the negotiations benchmarked, roughly 1 in 3 seats.
What is the cost difference?
Planning runs about twice the BI unit cost, because it enables write back, version management and forecasting a viewer never touches.
Should you standardize everyone on planning?
No. Standardizing up is convenient for administration and expensive forever, since capability you never use is recurring waste rather than a safety margin.
How do you decide who needs planning?
By behavior, not role. Audit who actually enters or changes data against who only views it, then reserve planning for the users who model.
Why is bundled SAC a problem?
Because its per user price is never isolated inside a larger SAP or RISE agreement, and that opacity favors the seller.
How do you price it inside a bundle?
Ask SAP to state the standalone per user price, benchmark it against a standalone quote, and confirm what happens to entitlement if the bundle is restructured.
What happens on user growth?
Active user growth triggered true ups that reset the committed floor upward, which is why the seat split has to be revisited at each one.
When should SAC be negotiated?
Co termed with the main SAP renewal, so the two are negotiated as one event and the wider leverage applies to both.
What should you commit to?
Volume only where adoption is proven rather than projected, with price protection written for renewal and not just the first term.