SAP License Optimisation
Most enterprises are overpaying for SAP by 15–35%. Not because of poor negotiation — because SAP's licence classification rules are deliberately complex. We run a forensic analysis of your Named Users, engines, and Digital Access consumption, then rebuild your licence position from the ground up.
The Problem SAP Created
SAP's Named User licence framework — with its hierarchy of Professional, Limited Professional, Employee, ESS, Developer, and Functional user types — was not designed with enterprise clarity in mind. It was designed with SAP's revenue targets in mind. The result: most enterprises have the wrong users in the wrong user types, paying Professional rates for users who qualify as Limited Professional, and often failing to spot Functional Users entirely. Our SAP User Classification Defence guide covers every named user type in forensic detail — including how USMM applies LTDR rules and where misclassification typically originates. Before any reclassification programme, we recommend a structured SAP licence baseline benchmarking exercise to establish an accurate starting point and quantify the optimisation opportunity across usage, compliance, architecture, and cost dimensions.
The engine licences are worse. SAP's package metrics — whether you're running advanced analytics, BW/4HANA, or SAP Datasphere — are calculated using measures that enterprise IT teams rarely understand until an audit makes the gap impossible to ignore. And SAP's annual system measurement via USMM and LAW doesn't benefit the customer. It benefits SAP's commercial team, who receive the ELP (Effective License Position) data and use it to build their upsell case.
Without independent SAP licence optimisation, you are not in control of your own licensing position — SAP is.
SAP's system measurement tools — USMM, LAW, and STAR — report what you have, not what you legally need. There is almost always a gap between what these tools count and what your Master Agreement actually requires you to licence. That gap is where most SAP licence optimisation savings live.
SAP Enterprise Support is charged at 22% of licence value per year. Every unnecessary Professional User licence you carry costs not just the licence fee — it also adds 22% annually in maintenance on top. A 1,000-user estate with 200 mis-classified Professional Users can cost £500K+ extra in maintenance alone over a 5-year contract term.
What We Deliver
We don't produce a spreadsheet and call it a report. We produce a legally defensible, evidence-based licence position that tells you exactly where you're overpaying and exactly how to fix it.
We analyse every user in your SAP landscape against your current Master Agreement and SAP's licence definitions. We identify every user mis-classified at a premium rate and build the reclassification case with documentary evidence SAP's commercial team cannot easily challenge.
We reverse-engineer how SAP has measured your engine licences — BW, Analytics, Datasphere, Integration Suite — against your actual consumption. We identify where SAP is applying peak rather than sustained metrics, and where you have headroom to renegotiate quantity or metric type.
SAP's Digital Access licence model charges per document type — Order, Delivery, Invoice, Material. We map every third-party integration against SAP's Digital Access definitions to confirm which document flows are chargeable, which are not, and where SAP's measurement tools are overcounting.
We produce a fully independent Effective License Position — not one generated by SAP's tools, but one built from first principles using your actual system data, contract entitlements, and SAP's published licence definitions. This becomes your baseline for any negotiation or audit response.
SAP Order Forms, BoMs (Bills of Materials), and the Master Agreement often contain entitlements customers have forgotten about, or restrictions SAP's commercial team conveniently omits to mention. We read every line and identify rights you already hold — rights you may currently be paying to add in new Order Forms.
With SAP Enterprise Support charged at 22% of licence value, right-sizing your licence position immediately reduces your annual maintenance obligation. We calculate the maintenance savings from every reclassification and right-sizing action, giving your CFO a total cost of ownership picture — not just a one-time saving.
How We Work
SAP licence optimisation fails when it's done based on assumptions. Ours is built on evidence — system data, contract documents, and SAP's own published definitions cross-referenced against your actual usage patterns.
We start with your current contract documents — Master Agreement, all Order Forms, BoMs, and any amendment letters. Simultaneously, we request system measurement extracts from USMM and LAW, plus any existing ELP reports SAP has issued. We establish your current contractual position before any analysis begins.
We run our own analysis against your system data — separately from any SAP-provided tool output. We cross-reference actual user activity logs against SAP's licence definitions to identify every reclassification opportunity. We apply the same methodology SAP uses in an enhanced audit, but in your favour.
For every optimisation opportunity identified, we calculate the licence cost saving, the maintenance reduction, and the total 5-year impact. We segment findings by risk — changes that are contractually unambiguous versus those that may require negotiation with SAP's licensing team — so your decision-makers understand the confidence level behind each recommendation.
We deliver a comprehensive report that functions as both an internal briefing document and a negotiation brief. Every claim is evidenced — user-level data, contract clause references, SAP licence type definitions. This is the document you take into your conversation with SAP's commercial team.
We support you through the reclassification conversation with SAP — whether that's a formal contract amendment, a measurement dispute, or a pre-renewal restructuring discussion. Where SAP pushes back, we counter with evidence. We do not stop at the report — we stay with you until savings are realised in your contract.
Who This Is For
CIO / IT Director
Multiple ERP instances, multiple Order Forms, users with duplicate access — you know the position is inefficient, but you don't have the resource or the SAP contract expertise to untangle it without independent support.
CFO / Finance Director
When maintenance is 22% of licence value and licence value has crept up through successive Order Forms, the compounding effect becomes significant. A forensic optimisation review is the fastest route to a defensible cost reduction.
ITAM / Procurement Lead
SAP's commercial team will arrive at your renewal with their own position. Without independent analysis — your own ELP, your own user classification evidence — you're negotiating blind against a counterparty who already knows your numbers.
COO / Operations
Transformation events are the best time to right-size SAP licensing. The landscape is changing anyway — do it with an independent review that ensures you don't carry legacy over-licensing into the new structure.
Track Record
Read our SAP licensing case studies to see how we've delivered results across financial services, manufacturing, healthcare, and retail.
Related Services
Start Your Optimisation Review
Our SAP licence optimisation review takes 3–6 weeks and typically identifies savings that pay for the engagement many times over. The conversation starts with a free, no-obligation consultation.
Frequently Asked Questions
Across our engagements, we identify an average of 15–35% overspend on the current licence position. The exact saving depends on how long the estate has been in place without independent review, whether the organisation has gone through acquisitions, and how aggressively SAP's commercial team has up-classified users in previous discussions. We have never completed an optimisation review without finding material savings — the question is always how large, not whether they exist.
SAP will often push back — but a push back without evidence is not a refusal. Our optimisation reports include the documentary evidence required to defend every reclassification: the specific clause in your Master Agreement or Order Form, the SAP licence type definition, and the user activity data that supports the lower classification. When challenges are evidence-based, SAP's commercial team has limited ability to override them without escalating internally — which they are unlikely to do for well-documented positions.
For a full ELP analysis, we work with USMM and LAW extracts, plus your contract documents. We do not need direct system access — we work from anonymised or aggregated exports. All client data is handled under strict confidentiality agreements. We are completely independent: nothing we receive is shared with SAP or any reseller channel.
The optimal window is 12–18 months before your SAP contract renewal. This gives enough time to build and document the reclassified position, negotiate any disputes with SAP, and ensure the corrected position is formalised in the new contract before it executes. However, an optimisation review can also be triggered by an incoming SAP audit — in which case, acting immediately is essential. Contact our team to understand the right approach for your timeline.
An SAP audit measures your actual usage against your contracted entitlements and identifies gaps. An optimisation review builds the most favourable defensible licence position before that measurement happens. If you've already received an audit notification, our SAP audit defence service applies the same methodology — but with the urgency and adversarial framing an active audit demands. See our SAP audit guide for a full overview of the audit process.
Yes. Under RISE with SAP, the licence model shifts partly to consumption-based metrics, but Named User classifications still apply, and the BTP component introduces additional consumption variables that many enterprises contract incorrectly. Our RISE with SAP advisory service covers the specific optimisation considerations for cloud-migrating organisations.