What Is SAP License Optimisation (And Why Most Enterprises Get It Wrong)
SAP license optimisation is the forensic analysis of your SAP licence position — user counts, user types, product scope, support entitlements — against actual usage patterns to identify gaps, reclassification exposure, and cost recovery opportunities. It's not negotiation. It's not procurement theatre. It's fact-based, defensible reclassification of your licence position to align spend with actual consumption.
Most enterprises get it wrong because they confuse optimisation with budget cuts. They approach it as a contract negotiation exercise: "We want a discount." SAP laughs. They then swing the other direction: "Let's audit ourselves and fix everything." But without a structured programme, random licence adjustments actually increase audit risk.
The right approach is methodical. It starts with honest usage analysis using SAP's own tools (USMM, LAW, STAR, Solution Manager). It then identifies which users are misclassified (paying for Named User Professional when Limited Professional is sufficient). It quantifies indirect access exposure. It benchmarks your support spend. Only then do you negotiate — from a position of strength, with defensible counter-proposals and third-party forensics to back them up.
Here's why this matters: 52% of SAP customers are audited more than twice in 18 months. When SAP audits you, they use USMM and LAW to suggest you're under-licensed or misclassified. A reactive optimisation programme — starting after an audit threat — costs 40% more to execute. A proactive programme, integrated into your renewal cycle, cuts audit risk by 60% and recovers $2-8M.
The Four Pillars of SAP License Optimisation
Enterprise SAP optimisation rests on four pillars:
1. Named User Classification and Reclassification
This is 60-70% of optimisation opportunity. SAP's licensing model assigns users to one of five types: Professional, Limited Professional, Developer, Employee, and Essential (ESS) or Field Sales (FUE). A Professional licence costs $3,500-5,000 annually per user. A Limited Professional, $800-1,200. The difference is feature access, not capability.
Most organisations don't audit this rigorously. They licence "all users" as Professional, then discover during an audit that 40-50% need only Limited Professional (customer service reps, warehouse staff, finance processors who read reports). SAP's audit report "suggests" reclassification. You then either pay the true-up or spend 6 months defending your position.
Proactive classification: Run USMM, identify feature access patterns, reclassify defensible users, document the decision. When SAP audits, you have a documented position. Risk drops; negotiating power rises.
2. Indirect Access Quantification
Indirect access is the second big exposure. If you have a custom portal, an analytics tool, or an integration platform accessing SAP without a named user logged in, that's indirect access. SAP's standard position: "You owe us an indirect access licence for every unique user, every 30 days." Indirect access licences cost 15-25% of a full Professional licence, so exposure scales quickly.
Most organisations discover this during an audit. SAP's Indirect Access Working Group (IAWG, now part of the broader licensing rules) reviews your system access logs, counts unique users per 30 days, and tables a 6-figure true-up. Optimisation firms specialise in proving that many "indirect users" are actually entitled (named user, subsidiary licence, etc.), or that the access pattern doesn't trigger licence.
Proactive analysis: Inventory all custom portals, integrations, and analytics tools. Audit 90 days of logs. Count unique users touching SAP via indirect paths. Determine which users are already licenced, which are spares, and which create genuine exposure. Quantify realistic true-up. Negotiate reduction using your forensics.
3. Support Cost Optimisation
SAP Enterprise Support costs 22% of licence value annually. That's standard. But not all customers need Enterprise Support at the same tier. Many organisations over-invest in support hours, response times, and ancillary services they don't use.
Optimisation here: Audit your support case history (SNOW incidents, SAP support tickets). Measure your actual support needs: incident volume, severity mix, average resolution time. Benchmark against your industry peer. Often you can shift to Standard Support (17-20% of licence), reduce named contacts, or negotiate response time SLAs lower than the standard Enterprise tier.
This alone recovers 8-15% of support spend. For a $10M licence base, that's $176K-260K annually.
4. Product Scope and Bundling Optimisation
Most organisations licence SAP products they don't actively use: BusinessObjects (BO), Signavio, SAC (SAP Analytics Cloud), BTP (Business Technology Platform). These get bundled, discounted, or forgotten. But if you're not using them, you're paying for them.
Optimisation: Audit which SAP products are actually used within your organisation. Scope them in your renewable. For unused products, negotiate removal or trade them for products you *do* need. This often shifts 5-10% of your contract value to higher-value products.
Named User Analysis: The Biggest Optimisation Opportunity
Named user classification represents 60-70% of the total optimisation opportunity. Here's why it matters so much.
SAP has five user types. The key three for optimisation:
- Named User Professional: Full feature access. Costs $3,500-5,000/year. Used for functional power users: supply chain planners, finance managers, procurement specialists.
- Named User Limited Professional: Restricted feature set. Costs $800-1,200/year. Used for transactional users: customer service reps, warehouse staff, HR coordinators, report readers.
- Developer: Development/testing only. No production access. Costs $1,500-2,500/year. Used for SAP developers, BASIS, and technical teams.
The problem: Most organisations default-licence everyone as Professional. Why? Because at initial go-live, scoping is rushed, and the default is "give everyone full access." By year 3, you have 500 Professional licences when 250 are sufficient.
The forensic process:
- Run SAP USMM to audit login frequency, module access, and feature usage by user.
- Segment users: high-frequency, complex-module users (genuinely Professional); transactional-only users (Limited Professional); testing-only users (Developer).
- Cross-reference with your HR/LDAP to validate user names and departments.
- Document which features each user tier needs (e.g., "Limited Prof needs MM module read-only, not purchasing approval rights").
- Identify which current Professional users can safely move to Limited Professional without operational impact.
- Build a reclassification proposal: "Moving 200 users from Professional to Limited Professional, retaining 50 Professional for functional leads."
Typical outcome: 30-40% reduction in user count via reclassification, worth $400K-800K annually for mid-market customers.
Deep dive: For a complete forensic guide to named user reclassification, including practical implementation, risk mitigation, cost modeling, and audit defense, see our complete SAP named user reclassification guide.
Indirect Access and Digital Access: Hidden Licence Exposure
Indirect access is the second-largest optimisation vector, and it's where audits cause the biggest damage. Here's how it works and how to defend against it.
What is Indirect Access? Indirect Access occurs when a non-licensed user accesses SAP without a named user login. Examples:
- A custom web portal (built on PHP, Node.js, etc.) that queries SAP using a batch account or service user.
- An ETL tool (Informatica, SAP Data Services) that reads/writes SAP data without a user logged in.
- A BI tool (Tableau, Power BI) connecting to SAP using a service account.
- A third-party ERP (NetSuite, Oracle) integrating with SAP via APIs.
SAP's position: Each unique user accessing SAP indirectly, per 30-day period, requires an indirect licence. A customer with a public portal used by 5,000 unique customers per month? That's 5,000 indirect licences. Cost: $200K-500K annually (assuming $40-100 per indirect licence).
The audit problem: SAP pulls 90 days of access logs from your system. They count unique users per 30-day rolling window. They then recommend true-up. Most organisations have no idea this exposure exists until audit.
The optimisation defense:
- Inventory all data access paths: Custom portals, integrations, BI tools, third-party systems. Document each one and the users accessing it.
- Audit 90 days of logs: For each path, extract unique user counts per 30-day window. This is your factual baseline.
- Classify users: Which of these indirect users are *already* licensed (named users with access to both direct and indirect paths)? Which are external (customers, suppliers) who might qualify for guest/partner licences? Which are genuinely unlicenced?
- Apply exemptions: SAP's rules allow exemptions for certain indirect access (e.g., public websites, read-only reporting). Identify which of your indirect access paths qualify.
- Quantify true exposure: Only count genuinely unlicenced, non-exempt unique users. This is your true indirect exposure.
- Negotiate reduction: If SAP later audits you, you have documented proof of your exposure and defensible reclassifications. This cuts their negotiating power significantly.
Typical outcome: 30-50% reduction in initial audit exposure via reclassification and exemption validation.
SAP Support Costs: The Overlooked Optimisation Lever
SAP Enterprise Support is 22% of licence value annually, on average. This is 33% of total spend (after licences). Yet most organisations don't scrutinise support — they pay it as a renewal line item and move on.
Support Tier Options:
- Enterprise Support (24x7, priority response): 22% of licence value. Used for mission-critical systems with SLA requirements.
- Standard Support (business hours, normal response): 17-20% of licence value. Sufficient for most systems.
- Custom Support Packages: Negotiable. Some customers pay for specific modules, incident caps, or response-time SLAs.
Most organisations default to Enterprise because "it's the standard." But forensic support analysis often shows Standard is sufficient.
The optimisation process:
- Audit 24 months of support cases: volume, severity, module, resolution time.
- Measure your actual SLA requirements: "Do we genuinely need 4-hour response, or is 24-hour acceptable?"
- Benchmark against peer organisations in your industry.
- Model cost of shifting to Standard Support, reducing incident caps, or negotiating custom response times.
- If your case volume is low and severities are mostly routine, negotiate down to Standard or hybrid support.
Typical outcome: 15-30% reduction in support spend, worth $100K-400K annually for mid-market customers.
How to Build Your SAP Licence Optimisation Programme
Optimisation shouldn't be ad-hoc or reactive (triggered by an audit). It should be a formal programme integrated into your annual renewal cycle.
Phase 1: Assessment (Months 1-2)
- Audit current licence position: user counts, user types, products, support tier.
- Run USMM, LAW, and STAR to assess actual usage.
- Document indirect access inventory and user counts.
- Audit support spend and case history.
- Identify 2-3 biggest opportunities (usually named user reclassification + indirect access).
Phase 2: Forensic Analysis (Months 2-4)
- Deep-dive into each opportunity: user-level reclassification, indirect user classification, support tier benchmarking.
- Quantify defensible reductions and cost recovery.
- Document all findings with SAP audit evidence.
- Build counter-proposal BOM with detailed justification.
Phase 3: Negotiation (Months 4-6)
- Present counter-proposal to SAP AE. Lead with data, not demands.
- Negotiate license reductions and support tier adjustments.
- Trade optimisation gains for extended terms or bundled product value.
- Document final position in renewal contract.
Phase 4: Governance (Ongoing)
- Establish quarterly review of new user additions and reclassifications.
- Track indirect access changes from new integrations.
- Audit support spend quarterly to prevent creep.
- Refresh analysis annually, 12 months before renewal.
This 12-18 month cycle ensures you're always audit-ready and negotiating from strength.
SAP Licence Optimisation in Practice: What Results to Expect
Real results from enterprise customers who executed a formal optimisation programme:
Case Study: Global Manufacturing Company ($25M SAP Spend)
Challenge: Facing second audit in 18 months. No documented licence strategy.
Optimisation executed:
- Named user reclassification: 450 Professional -> 200 Professional + 250 Limited Professional. Savings: $1.2M.
- Indirect access quantification: Reduced exposure from 3,000 to 800 indirect users via reclassification and exemption validation. Savings: $880K.
- Support tier shift: Moved from Enterprise to hybrid (Enterprise for production ERP, Standard for analytics). Savings: $450K.
Total annual recovery: $2.53M (10% of total spend). Audit risk reduced by 70%.
Case Study: Healthcare Organisation ($12M SAP Spend)
Challenge: Rapid growth, new integrations, no licence governance.
Optimisation executed:
- Named user audit and reclassification: 280 Professional -> 140 Professional + 140 Limited Professional. Savings: $490K.
- Product de-scoping: Removed unused BusinessObjects and BTP modules. Savings: $340K.
- Support optimisation: Reduced support package scope. Savings: $210K.
Total annual recovery: $1.04M (8.7% of total spend).
Frequently Asked Questions
Renegotiation is asking SAP for a discount. Optimisation is proving you're overpaying due to misclassification or scope misalignment, then reclassifying your position with forensic evidence. Optimisation is 3-5x more effective because it's fact-based and defensible.
A formal programme takes 4-6 months for assessment and analysis, then 1-2 months for negotiation. If you're proactive (12 months before renewal), you're not rushed. If you're reactive (during an audit), it takes longer because you're under time pressure.
Yes, if you have SAP BASIS expertise in-house. You'll need to run USMM, LAW, and STAR, and understand indirect access rules. But most organisations lack this expertise. External advisors bring audit-defence credibility that SAP respects and brings institutional knowledge of where hidden exposure lies.
If you've executed a formal programme with documented forensics, your audit risk drops 60%. SAP will still audit, but your position is defensible. You won't face surprise true-up demands because you've already justified your licence classification.
Internal programme: 2-3 FTE for 4-6 months. External advisors: typically 5-15% of identified savings (most work on success-fee basis). ROI is usually 3-5 months for enterprise customers, making optimisation self-funding.