SAP Negotiations

Negotiating Multi-Year SAP Cloud Subscription Deals

Multi-year Cloud Subscription Deals  sap

Mastering SAP License Negotiations: Global Volume Deals and Multi-Year Cloud Contracts

SAP license and subscription deals are major investments for enterprises, so negotiating favorable terms is critical. CIOs and CTOs can leverage global purchasing power to obtain volume discounts and secure flexible contract terms.

A strategic approach, covering internal license optimization, timing, competitive leverage, and multi-year deal structures, helps maximize discounts (often 40โ€“60% or more off list) and protect against cost escalations.

This advisory outlines how to negotiate SAP enterprise agreements globally and structure multi-year cloud subscriptions (for offerings such as SuccessFactors, Ariba, or RISE with SAP) to reduce long-term costs and risks.

Global Enterprise Agreements and Volume Discounts

Consolidate for Leverage: Multinational organizations should negotiate global SAP enterprise agreements rather than siloed regional deals. By consolidating demand across all business units and countries, you present a larger contract value to SAP.

A larger deal size directly translates toย higher discount tiersย โ€“ for example, bundling multiple country contracts into a single global agreement can result in discounts of 30% or more.

Coordinating purchases company-wide prevents SAP from giving smaller discounts on separate deals. Use your global scale as a bargaining chip to unlock volume-based pricing incentives.

Coordinate Regions and Currencies: When crafting a global agreement, involve stakeholders from each region (IT, procurement, and finance) to speak with a unified voice. Address local needs, such as data residency or compliance, early, so theyโ€™re built into a single master contract.

Negotiate currency terms to mitigate FX risks in global deals โ€“ e.g., pricing in local currencies or quarterly exchange rate adjustments if the contract is in a single currency. This protects your costs against currency volatility in multi-year international agreements.

Tiered Discount Structure: SAPโ€™s price lists often have built-in volume discounts at thresholds. Ensure your global deal benefits from these tiers.

For instance, if adding another 500 users bumps you into the next discount bracket, highlight the total volume to SAP and request that larger tier discount for the entire purchase.

Itโ€™s common for enterprises to achieve 40โ€“60% off list prices for large deals, and in strategic customer situations or competitive environments, even deeper cuts can be achieved.

Insist on transparent pricing breakdowns โ€“ SAP should display the list price and discount percentage per item, not just an overall blended discount.

This prevents SAP from quietly giving a high discount on one product but a low discount on another. Every component of your global agreement should reflect aggressive volume pricing commensurate with your scale.

Flexible Global Terms: Volume isnโ€™t just about price โ€“ negotiate flexibility in a global agreement. Strive for a co-terminous contract (all licenses/subscriptions renewing at the same time worldwide) to simplify management and renewal negotiations.

This also avoids missing renewal dates in one region that could auto-renew at full price. Additionally, seek a master agreement that allows shifting licenses across regions or entities as needs change (e.g., if one division shrinks and another grows, you can reallocate users rather than overpay).

A well-structured global deal strikes a balance between maximum discount and the flexibility to adapt usage across your enterprise over time.

Read SAP Termination and Downsize Rights for S/4HANA and ECC Contracts.

Internal Audit and License Optimization Before Negotiating

โ€œClean Houseโ€ First: Before sitting at the table with SAP, CIOs should audit their current SAP usage and licenses. Identify any shelfware or oversized licenses internally โ€“ these are leverage points.

For example, eliminate unused accounts (e.g., those of employees who have left or duplicate users) and remove or downgrade unnecessary licenses.

If you find 15% of your named user licenses arenโ€™t actively used, plan to drop them or convert them to smaller licenses.

Showing SAP that you know your exact license needs (and will not buy excess) strengthens your negotiating stance. It also ensures youโ€™re not paying maintenance on unused licenses.

One global firm discovered that it was paying annual support for a legacy SAP module that was no longer in use, costing $ 250,000 per year.

They negotiated to terminate those licenses in the renewal, freeing budget to invest in new SAP cloud services โ€“ a direct saving that became a negotiation win.

Right-Size License Types:

Examine your mix of license types (e.g., Professional, Limited, Self-Service) and engine metrics to optimize your setup for optimal performance. Are some users on expensive licenses they donโ€™t need? Over time, itโ€™s common to have misaligned license assignments โ€“ for example, users with full Professional licenses who only need Employee Self-Service access.

Optimize this now: plan to swap high-cost licenses for cheaper ones where appropriate. SAP will rarely volunteer this trade-down, but if you present a clear case (โ€œWe have 200 Professional licenses not fully utilized; we want to convert 100 of them to Employee licensesโ€), you can negotiate it as part of the deal. Optimizing license types reduces shelfware and proves to SAP that you wonโ€™t overbuy beyond actual requirements.

Accurate Forecasting:

Prepare a realistic forecast of your SAP usage over the next three to five years.

This includes user counts, transaction volumes, and any planned new SAP modules or cloud services. Neither overestimate (leading to paying for shelfware) nor underestimate (which could weaken your volume leverage).

Show SAP a data-driven demand plan: โ€œWe expect to add 300 SAP users in Asia next year due to a new plant, and possibly SuccessFactors for 5,000 employees in two years.โ€

With this, you can negotiate volume pricing upfront for future growth โ€“ for instance, pre-negotiate that those 300 users next year will be priced at todayโ€™s discount rate.

SAP, having seen that youโ€™ve done your homework, will treat your request as credible. Internal preparation not only avoids surprises but also signals to SAP that youโ€™re a sophisticated customer who wonโ€™t accept a subpar deal.

Read SAP Global License Agreement Strategy for CIOs and CTOs.

Timing and Negotiation Tactics to Maximize Discounts

Leverage SAPโ€™s Quarter-End Urgency: SAP sales teams have quarterly and annual targets. Plan your negotiation timeline to hit these pressure points.

Ideally, align final negotiations with SAPโ€™s Q4 (year-end) when reps are eager to close deals by December 31.

Enterprises often see initially modest discounts swell dramatically as the deadline approaches โ€“ for example, an SAP initial offer of 35% off might climb to 60% off by mid-December if the representative needs the sale to meet quota.

Donโ€™t be shy about extending a renewal a few months to line up with year-end โ€“ the additional discount can save millions.

Similarly, the end of Q1, Q2, and Q3 can also yield additional incentives (though Q4 is the most significant). Time is your friend: be patient and let SAP come under deadline pressure, but set your internal deadlines so SAP knows you are prepared to close by that time (on your terms).

Foster Competitive Tension:

Even if you are committed to SAP, letting them know you have options is key. Gather benchmark pricing from peer companies or conduct a soft market check with competitors (such as Oracle, Microsoft, Workday, etc., depending on the specific SAP product).

If SAP believes an alternative is on the table, they will sharpen their pencil. For instance, if negotiating SuccessFactors (SAPโ€™s HR cloud), mention that Workday was also evaluated โ€“ this reminder can prompt SAP to improve their offer without you ever issuing a formal RFP.

Some companies even obtain a quote from third-party support providers (like Rimini Street) for their SAP environment, giving leverage to negotiate down SAPโ€™s 22% maintenance fee.

The goal is to show SAP that youโ€™re an informed buyer with viable alternatives, increasing their incentive to grant concessions (bigger discounts, flexible terms) to win or retain your business.

Bundle Strategically:

Use bundle deals to your advantage. If you anticipate multiple SAP purchases over a year or two, such as S/4HANA licenses, Ariba, and a BusinessObjects expansion, consider negotiating them together. A larger bundle raises the total deal size, which SAP rewards with higher discounts.

Also, bundling global requirements (as discussed earlier) prevents SAP from treating each piece as a small sale. However, be careful to only include what you truly intend to use; donโ€™t let SAP entice you into adding โ€œextraโ€ modules you have no firm plan for, even if theyโ€™re on sale for 90% off.

A discount on something you donโ€™t need is not a saving โ€“ itโ€™s a future cost (maintenance or subscription fees on that item). Bundle to maximize needed volume and walk away from โ€œempty caloriesโ€ in the deal.

Maintain Control of the Narrative:

Throughout negotiations, maintain a professional but firm posture. Communicate your business objectives and constraints (e.g., budget limitations, ROI requirements) to effectively justify your requests.

By grounding demands in business needs (โ€œWe cannot proceed without a cap on renewal costs due to budget predictabilityโ€), you frame concessions as necessary to do the deal.

At the same time, manage the relationship by keeping discussions respectful and solution-focused. If you reach an impasse, express willingness to pause or walk away. Being ready to say โ€œweโ€™ll hold off until next quarterโ€ is a powerful move โ€“ more than once, when a customer hit pause, SAP returned swiftly with a significantly improved offer.

Ensure all promises from SAP are captured in writing. Verbal assurances, such as โ€œweโ€™ll freeze that price next year,โ€ mean nothing unless theyโ€™re included in the contract. Summarize the agreed-upon terms and codify them in the final agreement or amendment before it is signed.

Real-World Example:

A global manufacturer negotiated an SAP S/4HANA contract in Q4 with competitive bids in hand. SAPโ€™s initial proposal of a 35% discount improved to 60% by mid-December as the vendor fought to close the sale.

In addition, SAP conceded to cap maintenance fee increases at 0% for two years and included 100 free consulting hours for implementation. By staging the deal at year-end and showing a willingness to delay purchase, the company saved over $2 million and secured valuable extras.

Multi-Year Cloud Subscription Deals (SuccessFactors, Ariba, etc.)

Balancing Term Length and Flexibility: SAPโ€™s cloud offerings (such as SuccessFactors for HR, Ariba for procurement, or the bundled RISE with SAP service) are usually sold on multi-year subscriptions, often 3 to 5-year contracts.

Committing to a longer term can unlock substantial savings. SAP will often grant extra upfront discounts or price locks if you sign a multi-year deal, since it guarantees them recurring revenue.

For instance, a 5-year SuccessFactors contract might come with a 30% lower per-user price than a 1-year term would, because SAP is assured of the long-term business. Always weigh this trade-off: longer term = bigger discount, but less flexibility if your needs change.

If opting for a 5-year term, negotiate provisions to retain some flexibility, such as the right to reduce seats or modules in later years if usage is lower than expected (even if itโ€™s just a one-time adjustment right).

Fixed Renewal Rates:

One of the biggest risks in SaaS deals is the price jump at renewal. Vendors often offer an attractive initial term price and then hike fees 10โ€“20% (or more) when itโ€™s time to renew, knowing youโ€™re dependent on the service. To counter this, bake renewal protection into the initial contract.

For example, negotiate a clause that caps annual subscription increases to a certain percentage (e.g., โ€œnot to exceed 3% annuallyโ€) or even fixes the renewal price in absolute terms. Another approach is to commit to a multi-year term, but make years 4 and 5 optional at the same rate.

For example, a 5-year deal that allows you to exit after 3 years or continue years 4 and 5 at the pre-agreed-upon price. This way, you get the benefit of long-term pricing, but also have an escape hatch if things arenโ€™t working out.

Never accept an auto-renewal at list price โ€“ renewals should always be a point of renegotiation or governed by a cap.

Service Level and Performance Terms:

In cloud deals, SLAs and service terms are as important as price. Ensure the contract for SaaS products includes meaningful SLAs (uptime, support response) with remedies (like service credits) if SAP fails to meet them. SAPโ€™s standard cloud SLA is approximately 99.5% uptime. If your operations are mission-critical, consider requesting higher uptime or at least clarity on support escalation procedures.

Multi-year contracts should also cover data ownership and exit rights โ€“ negotiate how you can retrieve your data if the contract ends or if you switch providers. Having this spelled out in a long-term SaaS agreement prevents being โ€œlocked inโ€ not just by pricing, but by data or technical factors.

Example โ€“ RISE with SAP:

RISE is SAPโ€™s all-in-one cloud offering (infrastructure + S/4HANA + services) typically sold on a 3-5 year subscription.

Negotiating RISE involves many of the above elements: pushing for aย deep initial discount (30โ€“50% off the list price)ย by showcasing alternative cloud options, locking in renewal rates beyond the initial term, and insisting on migration flexibility.

Many RISE deals allow customers to convert existing on-premise investments into credits โ€“ e.g., if youโ€™ve spent $10M on SAP licenses historically, ask to apply a portion of that value towards the RISE subscription fee.

In multi-year cloud negotiations, SAPโ€™s desire to transition customers to the cloud can be leveraged; they might offer incentives such as extended payment terms, free migration support, or additional modular bundles at a discount to secure your commitment.

Seize those opportunities, but also ensure that if the cloud service under-delivers, you have contractualย remedies or exit options available after reachingย certain milestones.

Key Contract Clauses for Flexibility and Risk Mitigation

True-Down and Adjustment Rights:

A common enterprise ask is the ability to adjust license quantities over time. Standard SAP contracts tend to lock you into the initial volume (especially in cloud subs). Negotiate clauses that allow for a true-down at renewal โ€“ meaning you can reduce user count or modules at the end of a term without penalty, aligning costs to actual usage.

In some cases, you might negotiate a one-time mid-term adjustment (e.g., after year 1 of a 3-year deal, you can decrease subscriptions by up to 10% if usage is below forecast). Having this flexibility in writing protects you if your business scales down or divests part of its operations. It ensures youโ€™re not overpaying for unused capacity in a long-term deal.

Conversion and Migration Clauses:

Given SAPโ€™s evolving product landscape (think of transitioning from ECC on-premise to S/4HANA cloud), itโ€™s wise to include conversion rights. For instance, if you still have some on-prem licenses, negotiate the right to convert their value to cloud subscriptions later.

SAP has offered conversion programs, but you want the terms locked in: e.g., โ€œCustomer may exchange up to $X of unused on-prem license value for equivalent cloud subscription value for [SAP cloud product] at predefined discount rates.โ€

This allows you to modernize on your timeline without double-paying for software. Additionally, ensure that any multi-year contract includes provisions for new SAP innovations. If SAP releases a new module or feature that overlaps with what youโ€™re buying, you might negotiate aย swap or upgradeย to that new tech at a favorable rate.

Audit Safeguards:

SAP contracts usually allow audits of license usage. You canโ€™t remove audit rights entirely, but you can negotiate reasonable audit terms to prevent surprises.

Specify details such as auditing no more than once every 12 months, requiring 60 daysโ€™ notice, and, importantly, pre-negotiated pricing for any compliance gaps.

That last point means if an audit finds you need additional licenses, the contract locks in the price or discount at which you can purchase them (avoiding a scenario where SAP uses an audit to charge full price under duress).

Clarity on indirect access is crucial here โ€“ define how third-party or indirect system use is licensed to avoid the infamous indirect usage fines. For example, you might include, โ€œDigital Access model adopted, covering up to X documents/year, any excess priced at the same unit rate as the initial purchase.โ€ The clearer and more capped these terms, the less risk of a nasty audit surprise down the road.

Exit and Renewal Terms:

Always scrutinize end-of-term clauses. Auto-renewal at full list price is a nightmare scenario โ€“ negotiate that away. Instead, require SAP to provide a renewal quote well in advance (e.g., 90 or 120 days prior to the term end) and stipulate that any renewal will be mutually agreed upon; otherwise, the services will terminate.

This forces a renegotiation (where you have leverage) instead of a default price hike.

Additionally, consider including anย exit assistance clauseย for the cloud. If you decide to leave SAP at the end of the term, SAP should assist with data extraction or migration for a defined period. Knowing you can leave smoothly keeps SAP motivated to treat you fairly at renewal time.

One-Time Extras:

In big negotiations, once major terms are set, donโ€™t forget to ask for a few sweeteners. SAP may include free training seats, several hours of consulting support, or temporary extra licenses for a pilot project at no additional charge. These perks often donโ€™t cost SAP much, but provide real value to your business.

For example, โ€œInclude 50 hours of SAP technical consulting to help us optimize our deploymentโ€ or โ€œProvide 20 free training licenses for our staff on the new system.โ€

These can often be added if you request them late in the negotiation, when SAP is eager to finalize the deal. Itโ€™s the classic โ€œlast mileโ€ tactic to squeeze extra value once youโ€™ve agreed on the money.

Risk Mitigation Table: Below is a summary of key risk areas in SAP contracts and how to address them in negotiations:

Risk AreaPotential PitfallNegotiated Mitigation
Indirect AccessThird-party systems accessing SAP data can incur license fees unexpectedly (audits have penalized this).Clearly define and limit indirect usage in the contract. Adopt SAPโ€™s Digital Access license model with caps, or get indemnification for specified interfaces.
Price IncreasesAnnual maintenance or cloud subscription costs rising 5-10%+ per year due to contract silence.Cap annual increases (e.g. max 3-5%) or fix multi-year prices. Negotiate renewal terms upfront (no automatic list-price increases).
Shelfware / OvercommitPaying maintenance or subscription for unused licenses/modules (โ€œshelfwareโ€).Right-size licenses before signing. Include true-down rights at renewal to eliminate unused capacity. Avoid bundling extras you wonโ€™t use, despite discounts.
Auto-RenewalContract auto-extends at list price if notice isnโ€™t given, leading to cost spikes with no negotiation.Remove auto-renew clauses or ensure renewal requires mutual agreement. Set a long notice period for renewal quotes (e.g. 90 days) so you have time to negotiate or cancel.
Lack of FlexibilityInability to adjust to business changes (downturns, divestitures) leads to overpayment or penalties.Negotiate flexibility: ability to reduce licenses at renewal or even mid-term adjustment options. Include conversion rights to new SAP offerings if needed.
Data Lock-InFor cloud, risk of not being able to extract data or switch providers at end of term.Include data export assistance and transition support in contract. Ensure you retain ownership of data and have defined formats/procedures for retrieval.
Underperforming SLACloud service outages or poor support without adequate remedy.Raise SLA demands for critical systems (e.g. higher uptime or faster response). Get financial credits for SLA breaches. Possibly negotiate termination rights for repeated failures.

By proactively addressing these areas in your contract, you turn potential risks into managed outcomes and avoid costly surprises.

Recommendations

In summary, negotiating an SAP agreement requires diligence and a strategic approach.

CIOs and CTOs should follow these key recommendations:

  • Start Early and Prepare: Begin internal discussions at least 12 months before renewal or purchase. Inventory your current licenses, usage, and business needs. Early preparation prevents a last-minute rush and exposes opportunities for optimization.
  • Engage Stakeholders: Form a cross-functional team (IT, procurement, finance, legal, regional leaders) to develop a unified negotiation plan. Align on goals (cost savings, flexibility, future roadmap) and present a single cohesive front to SAP.
  • Benchmark and Seek Expertise: Utilize industry benchmarks for pricing and discounts โ€“ understand what your peers are paying. Consider hiring an SAP licensing advisor or consultant for large deals; their insight into typical discount ranges and contract gotchas can pay for itself in savings.
  • Leverage Volume and Competition: Consolidate purchases to maximize volume discounts, and let SAP know youโ€™re considering alternatives (other vendors or third-party support). A competitive atmosphere compels SAP to present its best offer.
  • Negotiate Multi-Year Contracts Wisely:ย If opting for multi-year commitments,ย demand protectionsย that include a cap on price increases, flexibility to adjust downward, and clearย performance/service expectations. Only commit long-term if the pricing and terms provide a clear advantage and escape routes if needed.
  • Donโ€™t Settle for Standard Terms: Almost everything is negotiable in an SAP contract. Push back on onerous clauses โ€“ whether itโ€™s unlimited audit rights, strict liability limits, or unfavorable payment terms. Custom-tailor the contract to fit your organizationโ€™s risk tolerance and objectives.
  • Document All Concessions: Get every promise in writing in the final contract. If SAP offers a special discount, a price hold, or a flexible term verbally, ensure itโ€™s written into the agreement or an addendum. Verbal assurances carry no weight later โ€“ only the contract language will matter.
  • Plan for Ongoing Management: Once the agreement is signed, actively manage it. Track your usage vs. entitlements, utilize any negotiated flex rights, and maintain regular dialogue with SAP. This ensures you realize the value you negotiated and sets the stage for even better terms in future renewals.

By following these practices, CIOs and CTOs can secure SAP deals that not only save money upfront but also support their companyโ€™s long-term strategic needs.

FAQ

Q1: How much of a discount off SAPโ€™s list price can large enterprises typically negotiate?
A1: It varies, but big enterprises seldom pay list price. Discounts of 40โ€“50% off the software list price are common in large deals, and can reach 60% or more for strategic, high-value agreements. For SAP cloud subscriptions, initial term discounts might be 20โ€“30% off (or higher if you commit to multi-year deals).

The exact figure depends on deal size, the number of products bundled, timing (year-end pushes result in larger cuts), and competitive pressure. Always ask SAP to express discounts as a percentage off the list โ€“ this helps benchmark if youโ€™re in a fair range. Well-prepared customers armed with benchmarks have successfully pushed SAP into the upper tier of discount ranges for substantial contracts.

Q2: What are the best tactics to negotiate SAP SaaS products like SuccessFactors or Ariba on a 3โ€“5 year term?
A2: For SAPโ€™s SaaS offerings, a multi-year term is a major bargaining lever. Let SAP know youโ€™re considering a 3-5 year commitment โ€“ they will often respond with a significantly lower per-unit price.

Key tactics: (1) Lock in pricing for the full term โ€“ negotiate caps on annual increases or fixed renewal rates as part of the initial deal. (2) Include usage flex โ€“ e.g., a clause to adjust down user counts at renewal or even mid-term if your workforce changes. (3) Secure service guarantees โ€“ ensure the contract covers uptime, support response, and data exit provisions, since youโ€™re relying on them long-term. (4) Explore incentives โ€“ SAP may offer credits (for onboarding or migration), free modules, or extra services if you sign a longer contract.

Use the promise of a 5-year deal to extract those perks. In short, exchange the longevity of your commitment for not just a lower price, but also better terms and freebies that improve the overall value.

Q3: How can we negotiate SAP maintenance costs and annual support fee increases?
A3: Maintenance for on-premise SAP licenses is typically 22% of the license cost annuallyโ€”a significant ongoing expense. First, ensure that SAP calculates 22% on yourย net discounted price, not the original list price (this should be explicitly stated in the contract).

Next, aim to reduce or freeze maintenance escalation: SAP traditionally raised support fees ~3-4% per year, and recently even up to 5%. You can negotiate a cap (e.g., support fees wonโ€™t rise more than 2% per year) or even a flat freeze for a couple of years. Some customers have negotiated one year of maintenance at no charge on new licenses or deferred maintenance start dates until the system is live. If SAP resists lowering maintenance, consider leveraging alternatives: gather quotes from third-party support providers, even if you donโ€™t switch. Showing SAP that youย couldย leave their support can prompt them to grant a discount or concession to retain your maintenance business.

Q4: What should we watch out for in SAP contracts to avoid future surprises (like audits or hidden fees)?
A4: Be vigilant about any ambiguous terms or missing clauses that could expose you later. Common pitfalls include: Indirect usage (ensure the contract covers how external systems/users interact with SAP to avoid later license claims), shelfware bundling (donโ€™t get stuck with unused modules that you still pay for โ€“ only pay for what you need now, with options to grow later), auto-renewal (never allow auto-renew at list price โ€“ always keep renewal as a negotiable event), and undefined price increases (if the contract is silent, SAP can impose standard hikes โ€“ so add those caps or fixed rates).

Additionally, check for geographic usage rights (a global company should ensure licenses can be used worldwide, not restricted to a specific region unless intended) andย data residency/security commitmentsย when using the cloud (to ensure compliance with regulations). Essentially, assume that if a scenario isnโ€™t explicitly addressed in the contract, SAP has the upper hand by default. Close those gaps now โ€“ negotiate clarity and limits on all key terms (usage, audits, price, renewal, termination) to prevent headaches later.

Q5: How can we ensure flexibility if our business changes after signing a long-term SAP agreement?
A5: Flexibility can be built into the contract with foresight. First, include true-down rights at renewal โ€“ the ability to reduce license counts or switch modules when the term is up. For example, if you downsize, you can renew maintenance or subscription on only what you still need. If itโ€™s a cloud deal, consider including a clause that allows for a one-time mid-term reduction (even a small one, such as 10%) in the event of mergers, divestitures, or economic shifts that result in reduced usage.

Second, negotiate conversion rights โ€“ the option to pivot your investment to other SAP products. If you plan to move to the cloud, consider terms that allow you to credit unused on-premises licenses towards cloud subscriptions. Third, consider termination for convenience for parts of the deal โ€“ you might accept a penalty fee to exit early if needed, but at least you know the worst-case cost.

Finally, maintain a close vendor relationship: if circumstances change, sometimes SAP will be open to adjusting the deal (especially if it prevents losing you entirely). But your best safety net is having those flex provisions written in from the start. That way, youโ€™re contractually allowed to adapt the agreement in line with business changes, instead of being handcuffed to an outdated commitment.

Read more about our SAP Contract Negotiation Service.

Would you like to discuss our SAP services with us?

Please enable JavaScript in your browser to complete this form.
Name
Author
  • Fredrik Filipsson has 20 years of experience in Oracle license management, including nine years working at Oracle and 11 years as a consultant, assisting major global clients with complex Oracle licensing issues. Before his work in Oracle licensing, he gained valuable expertise in IBM, SAP, and Salesforce licensing through his time at IBM. In addition, Fredrik has played a leading role in AI initiatives and is a successful entrepreneur, co-founding Redress Compliance and several other companies.

    View all posts
Redress Compliance