SAP Negotiations

Vendor Management Guide: Managing SAP as a Strategic Enterprise Vendor

SAP is among the most complex enterprise vendors to manage — spanning ECC, S/4HANA, RISE, Digital Access, and a vast product portfolio. This guide provides practical strategies for CIOs and vendor management teams to control costs, optimise licensing, negotiate effectively, manage audits, and govern the SAP relationship for maximum value.

Vendor Management GuideSAP Licensing & NegotiationsFredrik FilipssonJuly 2025
~90%SAP Customers Overpay Due to Over-Licensing
10–20%Typical Over-Licensing in User Counts
~22%Annual Maintenance as % of Licence Cost
£54.5MDiageo Indirect Access Judgment (2017)

📑 In This Guide

  1. SAP Licensing Models: S/4HANA vs. ECC, Users & Packages
  2. Cloud vs. On-Premises: RISE with SAP, Hyperscalers & HEC
  3. Contract Governance, Pricing Negotiation & Cost Optimisation
  4. SAP Support, Escalation & SLAs
  5. Navigating SAP Sales & Account Management Tactics
  6. Audit Risk Management & Indirect Access Mitigation
  7. Renewals, Expansion Planning & Renegotiation
  8. Tools & Advisory Services for SAP Vendor Governance
📋

Section 1 — SAP Licensing Models: S/4HANA vs. ECC, Users & Packages

SAP offers two fundamental licence models: named user licences (assigned to individual people) and package/engine licences (based on usage metrics like transactions, employees, or orders). Understanding these models — and the critical differences between ECC and S/4HANA — is essential to controlling costs.

Licensing

Named User Licences & ECC Basics

+
In legacy SAP ECC, customers typically buy perpetual licences for specific user types: Professional User (broad system access, high cost), Limited Professional, Employee Self-Service (far cheaper, very limited functionality), and others. Each user requires the correct licence type for their role. Many companies accidentally over-licence users at higher levels than needed — a costly oversight. Package/engine licences cover specific SAP functions measured by metrics (employees, sales orders, CPU capacity). SAP audits engine usage — one spike can trigger a compliance bill.
Example: One firm found it had tagged many employees as "Professional Users" in ECC when "Limited Professional" would suffice — correcting this before negotiations yielded significant savings.
Licensing

S/4HANA Licensing Approaches

+
S/4HANA can be licensed two ways: traditional perpetual (like ECC) or subscription-based via cloud offerings. On-premises S/4HANA still uses named users and package metrics, but SAP simplified the core ERP bundle as a single package licence covering many modules. In subscription models (S/4HANA Cloud, RISE with SAP), SAP uses Full User Equivalents (FUE) instead of individual named users — aggregating different user types into a weighted unit under one contract. Don't assume a 1:1 swap when moving from ECC to S/4HANA; SAP's conversion programs may credit existing licences, but you often won't get full value.
Critical: Optimise your user licence assignments before migrating. Overestimating FUE count inflates subscription costs. Scrub your user list and eliminate or downgrade unnecessary licences before the FUE calculation.
Risk

Indirect Access & Digital Access Licensing

+
A perennial SAP compliance risk: indirect access — when non-SAP systems or external users use SAP data or functions indirectly. SAP's contracts require a licence for anyone or anything triggering SAP system processing, even without direct login. SAP won a £54.5M judgment against Diageo in 2017 and pursued Anheuser-Busch for $600M for unlicensed indirect use. To address ambiguity, SAP introduced the Digital Access model in 2018, licensing nine document types (Sales Orders, Purchase Orders, etc.) created by external systems. Key guidance: identify all third-party applications, interfaces, and bots that read/write SAP data. Decide whether named user licensing or the Digital Access document model is cheaper for your environment.
Rule of thumb: Traditional model may be cheaper with minimal third-party integration. Digital Access prevents huge compliance penalties in environments with heavy external platform integration (e-commerce, manufacturing systems feeding SAP).

Actionable Licensing Tips

Maintain Detailed Inventory

Map every user to the correct licence type and every interface to the proper licensing mechanism.

Run USMM/LAW Quarterly

Don't just run measurement tools annually for SAP's audit — run quarterly for your own insight.

Re-Harvest & Reassign

Organisations are typically over-licensed by 10–20%+. Proactively reclaim licences from departures and role changes.

Monitor Indirect Usage

If new integrations are introduced, update licensing compliance immediately. Good governance avoids compliance surprises.

☁️

Section 2 — Cloud vs. On-Premises: RISE with SAP, Hyperscalers & HEC

The choice between on-premises, hyperscaler-hosted, and SAP's RISE offering has profound implications for cost structure, flexibility, and vendor management. Each path has trade-offs that CIOs must evaluate carefully.

DimensionOn-PremisesHyperscaler (BYOL)RISE with SAP
Licence ModelPerpetual + ~22% maintenancePerpetual (BYOL) + maintenanceSubscription (FUE-based)
Cost ModelCapEx heavy, OpEx for supportOpEx cloud + OpEx maintenancePure OpEx subscription
CustomisationMaximum flexibilityMaximum flexibilityPrivate cloud: moderate; Public: limited
InfrastructureYou manageCloud provider managesSAP manages (via hyperscaler)
Vendor RelationshipsSAP + hardware vendorsSAP + cloud provider (separate)SAP only ("one hand to shake")
Exit FlexibilityHigh (you own licences)HighLow (subscription, no ownership)
Cloud

RISE with SAP — Bundle Benefits & Risks

+
RISE bundles S/4HANA software, technical managed services, and infrastructure into one subscription. SAP becomes both software vendor and cloud service provider. Includes BTP credits, Business Network starter access, and basis support/SLAs. Scrutinise the contract: clarify allowed customisations, data residency, RACI matrix (who does what), number of included sandbox/dev systems, and DR environments. Standard RISE contracts often allow 3–5% yearly subscription increases and limit exit options.
Negotiate: Cap annual increases to a fixed % or tie to CPI with a reasonable max. Negotiate exit strategy: right to export data, migration assistance, and potentially an option to revert to on-prem licences at a defined price if you leave RISE.
Cloud

Running SAP on a Hyperscaler (AWS/Azure/GCP)

+
Many enterprises run SAP on cloud infrastructure using BYOL. You manage two relationships: SAP for software, cloud provider for infrastructure. SAP maintenance fees remain the same; you also incur hyperscaler costs. Manage these contracts in tandem: coordinate term of cloud agreement with SAP project cycles. Monitor total cost — cloud spend can spike if systems aren't right-sized. One benefit: you negotiate cloud resource discounts directly. Caution: if you later move to RISE, SAP controls the cloud contract and you lose direct negotiation on infrastructure costs. Always compare 5-year TCO of self-managing on hyperscaler versus RISE bundle.
Cloud

HANA Enterprise Cloud (HEC)

+
Before RISE, HEC was SAP's managed private cloud offering. Similar concept but more bespoke, sometimes with confusion over responsibilities and higher customisation costs. If you're on HEC, SAP will likely encourage transitioning to RISE. Apply the same diligence — understand cost structure and any changes in terms. Ensure you don't lose favourable legacy terms when migrating from HEC to RISE.
📋 Real-World Scenario

One company comparing RISE vs self-managed found that with RISE, SAP would handle basis operations and guarantee 99.5% uptime SLA, whereas on Azure their internal team had to meet business SLAs themselves. They chose RISE but negotiated an improved SLA of 99.7% with credits for downtime, as well as a clause capping price increases to 2.5% per year — ensuring predictable costs and service.

🤝

Section 3 — Contract Governance, Pricing Negotiation & Cost Optimisation

Managing SAP requires continuous oversight. Studies show up to 90% of SAP customers overpay due to over-licensing or unused licences. Strong contract governance and negotiation discipline are your primary tools to keep costs in line.

Negotiate

Plan Negotiations Well in Advance

+
Begin planning at least 6–12 months before a major contract event. Complete an internal "Phase 0" assessment before contacting SAP: inventory all licences and usage, identify shelfware, map over-privileged users. By coming to SAP with a precise understanding of your utilisation, you prevent SAP from dictating the narrative and can counter any "gap" claims. Align stakeholders (IT, procurement, finance, business units) and establish a communication plan — SAP's sales teams are adept at multi-threading and may approach executives directly to pressure a deal.
Negotiate

Control Scope & Use Facts, Not Fear

+
Be clear and firm about what you want to buy — and what you do NOT want. SAP's common tactic: bundle additional products or higher quantities than requested. Prevent this by stating required products/volumes in writing. SAP sales often use FUD (fear, uncertainty, doubt): competitor warnings, 2027 ECC deadline pressure, audit threats. Stay anchored in your business case and independent research. If SAP claims "price will increase 10% next year" or "offer valid this quarter only," verify it — those claims are often negotiable.
Timing leverage: SAP has strong incentives to book deals by quarter-end/year-end. A controlled delay (while appearing engaged) can yield better discounts. But balance with your own risk tolerance.
Negotiate

Optimise Existing Assets First

+
Before buying more, scrutinise current usage. If you find shelfware, raise it in negotiation. Request to swap unused licences for something of equal value, or to terminate their maintenance. Example: if you bought 1,000 CRM licences but only use 300, negotiate exchanging the excess 700 for a new SAP product (like SAP Analytics Cloud) rather than continuing to pay support on shelfware. Negotiate price protections now — a clause allowing you to buy more users or modules at the same discount within 2 years prevents SAP from quoting exorbitant prices later.
Negotiate

Leverage Competition & Escalate Smartly

+
For certain components (procurement, analytics, CRM, HR), alternatives exist. Evaluating Salesforce, Workday, or others in parallel creates leverage — but use carefully (SAP may stress integration/indirect access costs to discourage). Your counter: understand true indirect access cost and remind SAP you're prepared to invest elsewhere. When talks stall, escalate: CIO-to-SAP regional manager or CFO-to-SAP sales VP calls can unlock concessions the sales rep couldn't offer. Executive engagement can yield last-minute improvements even after a "best and final" quote.
Negotiate

Secure Future Flexibility & Cost Control

+
Don't just focus on the immediate purchase — set up for the future. For cloud/subscription deals, negotiate renewal terms now: cap price increases (e.g. 5% max) at renewal in year 4. For on-prem, lock in expansion pricing tied to current discount off list. Negotiate contractual protections: swap rights (ability to swap licence types of equal value), termination rights for cloud services if SLAs are consistently missed, language limiting audit frequency, and clauses excluding benign indirect uses from fees. If it's not in the contract, it's not guaranteed.

Facing an SAP contract negotiation or renewal? Get independent advisory support.

SAP Contract Negotiation →
🛟

Section 4 — SAP Support, Escalation & SLAs

Most large customers are on SAP Enterprise Support (~22% annual fee of licence value). Understanding your entitlements, premium options, and escalation paths is critical to getting value from this significant investment.

Support

Enterprise Support Entitlements

+
Enterprise Support provides 24×7 support for high-priority issues, SAP Support Portal, Solution Manager, knowledge base, and enhancement package updates. Includes service level commitments around response times (P1 cases get response within 1 hour). For critical production-down issues, log as "Very High" (P1) and call SAP support directly — don't passively wait for portal response. Leverage your SAP Customer Success Manager for liaison. Also use proactive services included: Continuous Quality Checks, EarlyWatch alerts, Maintenance Planner, and Upgrade Checks.
Support

Premium Engagements: MaxAttention & ActiveAttention

+
MaxAttention is the top tier — SAP provides a dedicated team of experts who deeply know your system and help with architecture, performance tuning, and go-lives. Typically for SAP's largest, most complex customers. ActiveAttention is scaled-down: access to a Technical Quality Manager off-site and specific expert services, but not a full embedded team. These are expensive and multi-year. Negotiate: insist on carrying over unused service days to next year, lock in resource rates for the duration, and benchmark what other clients pay.
Key insight: Many assume premium engagement pricing is fixed — but elements like included expert-days, hourly rates, and scope are all negotiable. Push for "use it or lose it" exceptions.
Support

SLAs & Escalation Best Practices

+
For on-premise, SAP's SLAs are usually about response time, not fix time. For cloud contracts (RISE, SuccessFactors), there are uptime SLAs (typically 99.5%) and sometimes resolution timeframes. If your business needs higher SLAs, negotiate. 99.5% allows ~1.8 days downtime/year — potentially too much for 24×7 global operations. Push for 99.7% or 99.9% and meaningful remedies for breaches (not just token credits). Develop an internal SAP escalation procedure: if P1 not resolved within X hours, escalate to Mission Control Centre. Use the magic words: "We need a global escalation." SAP may bring in product engineering when you do this.
📋 Real-World Scenario

A manufacturing company on SAP MaxAttention had chronic performance issues during quarter-end closing. After regular support channels failed for months, they invoked their MaxAttention escalation. SAP flew in a performance expert team for a week, identified a database indexing problem, and solved it — fulfilling the promise of premium support. The key was persistent escalation and use of paid entitlements.

🎯

Section 5 — Navigating SAP Sales & Account Management Tactics

SAP is a large enterprise vendor with a highly organised sales approach. Your account will have an Account Executive, Customer Success partner, and product overlays (cloud reps for Ariba, SuccessFactors, etc.). Knowing their playbook helps you maintain control.

Tactic

Leveraging End-of-Life Deadlines

+
SAP uses the 2027 ECC support deadline to create urgency — offering incentives to move to S/4HANA now, warning that waiting means losing out on deals. Counter: use the deadline as leverage back at them. They need your business too. "We know you want us to transition before 2027; we want a better price to do so." SAP is often more flexible now than after you've crossed the deadline.
Tactic

Audit & Compliance Pressure

+
SAP reps may surface indirect access or compliance issues outside formal audit: "Let's do a licence review to make sure you're compliant" — which conveniently finds a shortfall. Counter: do your own assessment first so you know the truth. If a shortfall exists, negotiate it as part of a broader deal rather than a standalone buy at list price under threat. Stay ahead of audits by self-auditing and addressing gaps on your own terms.
Tactic

Executive Access & "Top-Siding"

+
SAP will involve senior executives to woo your C-suite. Conversations are friendly and high-level but ultimately looking for upsell opportunities. Counter: prep your executives on SAP's likely goals so they respond with your company's needs, not SAP's agenda. Also watch for "top-siding" — going around the negotiation team to engage a C-level with promises or pressure. Nominate specific points of contact and instruct your team not to engage in off-script talks.
Tactic

Bundling & Discount Illusions

+
SAP proposes large bundles ("RISE + Ariba + Analytics all together for 30% off!"). The overall discount sounds great, but often includes products you don't need. Counter: always break down a bundle — ask for individual component pricing. Often one component is heavily discounted but others are not. Take only the attractive pieces. Also watch for "one-time" programs with fine print requiring long-term commitments. Evaluate against independent ROI analysis, not marketing brochures.

How to Handle These Tactics

Stay in Control of the Agenda

Refer back to your IT strategy and budget. Keep a roadmap document to share with SAP showing when you plan major changes.

Use Data & Third-Party Input

If SAP claims 30% savings, verify with external benchmarks or consultants. Build your own TCO models.

Give Small Wins Strategically

Buying a module you were considering anyway can relieve pressure elsewhere. Make trades explicit.

Get All Promises in Writing

Free training, migration support, consulting hours — if it's not in the contract, it's not guaranteed. Memories fade and reps change roles.

🛡️

Section 6 — Audit Risk Management & Indirect Access Mitigation

SAP licence audits (often yearly "LAW" requests) are a normal part of the relationship. Treat audit readiness as an ongoing discipline, not an ad-hoc fire drill. Indirect access is the single biggest audit risk for most SAP customers.

Audit

Ongoing Audit Preparedness

+
Keep user lists clean (remove access promptly for leavers), document every third-party system interaction with SAP, and run internal usage reports regularly. When SAP sends an official audit notice, respond cooperatively but carefully. You may discover an inadvertent shortfall — if so, you might purchase needed licences before submitting audit data (at a better negotiated rate than post-audit penalties). Always keep audit communications separate from sales discussions.
Audit

Identify & Map Indirect Access Exposure

+
Map all data flows to and from SAP. Common culprits: middleware interfaces, customer/supplier portals, mobile apps, even Excel macros using ODBC. Classify connections: read-only exports ("Indirect Static Read" — currently no licence if done properly) vs. creating transactions in SAP (requires licensing). Close gaps on your terms. Options include: purchasing SAP Platform User licences, opting into Digital Access, or re-architecting (e.g. exporting data to a separate database so external access doesn't hit SAP directly).
Audit

Common Audit Triggers to Watch

+
SAP focuses audits when they suspect something: no recent licence purchases (suggests grown usage without licences), mergers or acquisitions (landscape changed), large increase in user counts, nearing contract renewal (to maximise position), or if you publicly announced a move to a competitor. If you fall into any scenario, double-check compliance before SAP comes knocking. During an audit, if they request non-SAP system logs, involve your legal team to verify the request is within the contract's audit clause.
Audit

Mitigate with Contract Clauses & SAP Programs

+
SAP's Digital Access Adoption Program (DAAP) allowed customers to trade existing licence value for digital document licences. In new contracts, explicitly limit indirect risk: add clauses that cloud product use won't count as indirect use back to your ERP. Gartner recommends wording ensuring new definitions only apply to the new product — preventing retroactive charges. If audit finds shortfalls, don't accept the first fee quote blindly — findings are negotiable. Convert audit findings into a purchase with discounts or roll into a broader contract deal.
Indirect use mitigation example: A company discovered a custom mobile app used one background SAP user to let 500 employees clock in/out — clear indirect access. Before SAP audited, they bought proper ESS licences (cheaper than any potential fine), reconfigured the app, and whitelisted the scenario in a contract amendment. Next audit: zero issues. Proactive approach cost far less than post-audit true-up.
🔄

Section 7 — Renewals, Expansion Planning & Renegotiation

An SAP renewal is not just a procurement event — it's a strategic checkpoint. Begin planning 6–12 months out. This is your chance to right-size, fix suboptimal contract terms, and set up for the next cycle.

Renewal

Right-Size & Clean Up Before Renewal

+
Perform internal licence audit and usage analysis well before renewal. Identify licences or subscriptions not fully used. It's much easier to non-renew or reallocate at the renewal point than mid-term. For cloud subscriptions: if you bought 1,000 users and only used 700, plan to renew for 700–800. If you need more, bring that into a negotiated package for a better rate rather than signing a separate expansion later at higher cost.
Renewal

Leverage Renewal for Better Terms

+
Renewal is your chance to fix contract terms that were suboptimal. Add price protection on elements that lacked it. Harmonise inconsistent discounts. Negotiate swap rights: the ability to swap unused licences for other licences of equal value. For cloud subscription renewals, push for renewal price caps and options to reduce quantities. For multi-year deals, ensure annual uplifts are clear and acceptable (try "CPI or 3%, whichever is lower").
Renewal

Plan Expansion in a Structured Way

+
Don't buy ad-hoc if you can help it — vendors love unplanned purchases because they have the upper hand. Anticipate expansions and bundle into planned negotiations. Example: "We'll likely need X licences for EWM next year — keep pricing consistent." Negotiate a "commit-and-phase" deal or pre-negotiate a framework: "Any additional S/4HANA users added in the next 2 years will receive the same % discount." Time expansion deals with SAP's fiscal calendar when possible — SAP is notably more flexible near Q4/Q1 end.

Renewal Negotiation Checklist

Control the Timeline

Don't let SAP dictate when quotes come and when they must be signed — manage dates yourself.

Align Internally

IT, procurement, legal, and finance should know goals and support them with a unified front.

Communicate Needs Clearly

State what you expect to renew and what not — otherwise SAP assumes you'll keep everything plus more.

Optimise First, Then Renew

Remove or repurpose shelfware. Improve terms, add flexibility, fix pain points in the new contract.

🔧

Section 8 — Tools & Advisory Services for SAP Vendor Governance

Managing SAP's complexity can be augmented with specialised tools and expert services. The right combination can uncover 15–20% cost savings on average through optimisation alone.

Tools

Licence Management & Optimisation Tools

+
SAP-focused SAM tools include Snow Optimizer for SAP, VOQUZ SamQ, ServiceNow SAM, and Aspera LicenseControl. These integrate with SAP to analyse user activity, licence assignments, and engine usage. They automatically identify mismatches — users with powerful licences who only perform low-level tasks. Ensure tools handle indirect usage tracking and stay updated with SAP's latest licence rules. SAP's own LAW tool shows raw consumption but doesn't suggest how to optimise or reduce costs.
Tools

Advisory Services & Expert Consultants

+
Specialised advisory firms like Redress Compliance offer licence audits, contract negotiation support, and benchmarking. An SAP licensing advisor can benchmark your proposed deal against hundreds of others to tell you if the discount is fair and where to push. They also identify soft spots in contracts that typical IT teams might miss. Engaging advisors can easily pay for itself in a big negotiation through cost avoidance. Also join SAP user groups (ASUG, DSAG) for community knowledge and peer insights.
Tools

Third-Party Support & Governance Automation

+
Providers like Rimini Street offer maintenance for SAP ECC at roughly 50% of SAP's fee. Switching cuts cost but you lose official SAP updates. Some organisations use this as leverage: the threat or move to third-party support pushes SAP to offer discounts or special support extensions. Others run hybrid: SAP support for critical systems, third-party for ancillary. Also automate licence management: integrate HR joiner/mover/leaver processes with SAP licence assignment so accounts are removed or adjusted automatically.
💡 Key Takeaway

Managing SAP as a strategic vendor is a continuous journey of measurement, optimisation, and negotiation. By treating SAP vendor management as a year-round discipline — not just a project when a contract is up — you will drive significantly better outcomes: controlled costs, a transparent and fair contract, minimised compliance risks, and a vendor relationship that supports your business goals on your terms.

🚨 The SAP Management Lifecycle

The key is proactive management at every stage: before signing (plan, audit, and negotiate), during the term (govern, monitor, and optimise), and at renewal (right-size, renegotiate, and improve terms). With SAP being so integral to operations, the effort invested pays back in both dollars saved and agility gained.

Frequently Asked Questions

What is SAP Digital Access and should we adopt it?+
Digital Access is SAP's document-based licensing model for indirect use, introduced in 2018. Instead of requiring named-user licences for every external system user, you pay for nine document types (Sales Orders, Purchase Orders, etc.) created by external systems. Adopt it if you have heavy third-party integration with SAP — it prevents huge compliance penalties. If you have minimal integration, the traditional named-user model may be cheaper. Evaluate both models before deciding, and ensure your choice is explicitly covered in the contract.
How should we prepare for the 2027 ECC end-of-support deadline?+
Don't panic, but plan proactively. Use the deadline as negotiation leverage — SAP wants your migration business. Complete a thorough licence and usage assessment. Evaluate RISE vs. self-managed S/4HANA on hyperscaler vs. on-premises. Optimise your user licence assignments before any migration to avoid inflating FUE counts. Negotiate conversion credits for existing perpetual licences, but don't expect full value. Start planning 12–18 months ahead and align stakeholders on the migration strategy.
Does RISE with SAP include indirect access/Digital Access rights?+
Generally yes — RISE subscriptions typically cover standard indirect usage under the FUE count and accompanying digital access rights. However, "all-inclusive" doesn't mean "unlimited." If your indirect usage is exceptionally high (IoT sensors generating millions of records, high-volume e-commerce), clarify with SAP and get written confirmation. Some RISE contracts include a certain number of Digital Access documents — verify how many and what happens if you exceed them. Never assume; always negotiate explicit terms.
How can we reduce SAP maintenance costs?+
Several approaches: (1) Right-size your licence estate — you only pay maintenance on what you own, so eliminating shelfware directly reduces fees. (2) Negotiate maintenance caps or discounts at renewal. (3) Consider third-party support providers (Rimini Street, Spinnaker) for stable ECC environments at ~50% of SAP's fee. (4) Use the threat of third-party support as leverage. (5) Ensure maintenance is calculated on your discounted price, not list price ("pegged support" trap). SAP has been raising maintenance fees recently due to inflation — push back and try to cap increases to 3% annually.
How can Redress Compliance help with our SAP vendor management?+
Redress Compliance provides independent SAP advisory services including licence optimisation assessments, contract negotiation support, audit defence, Digital Access strategy, and RISE evaluation. We benchmark your deal against hundreds of comparable enterprises, identify shelfware and over-licensing, develop give-get negotiation strategies, and sit alongside you during negotiations. Our clients typically achieve significant cost reductions while securing better contractual flexibility, compliance protection, and future-proofing terms.

Our SAP Advisory Services

🤝

Contract Negotiation

Learn more →
📊

Licence Optimisation

Learn more →
🛡️

Audit Defence

Learn more →
☁️

RISE Advisory

Learn more →

📥 SAP White Papers

Download our independent guides on SAP licensing, RISE negotiations, Digital Access strategy, and cost optimisation

Download White Papers

SAP Contract or Renewal Coming Up?

Share your current SAP landscape and timeline. We'll provide an independent licence assessment, pricing benchmark, and negotiation strategy — typically within 48 hours.

Related SAP Resources

FF

Fredrik Filipsson

Co-Founder @ Redress Compliance

Fredrik Filipsson brings over 20 years of enterprise software licensing experience, including tenures at IBM, SAP, and Oracle. For the past 11 years, he has worked as an independent consultant, advising Fortune 500 companies on complex SAP contract negotiations, licence optimisation, RISE evaluation, Digital Access strategy, audit defence, and vendor management across Oracle, Microsoft, SAP, IBM, and Salesforce.