Explore the Secrets of SAP Software Contracts to Optimize Spend and Reduce Compliance Risk
Overspending and becoming noncompliant with SAP is easier than you think. Assess your contract and build a strategy to negotiate from a position of strength.
- SAP has strict audit practices, which, in combination with 50+ types of user classifications and manual accounting for some licenses, make maintaining compliance difficult.
- Mapping and matching SAP products to the environment can be highly complex, leading to overspending and an inability to reduce spend later.
- Beware of indirect access to SAP applications from third-party applications (e.g. Salesforce).
- Products that have been acquired by SAP may have altered licensing terms that are innocuously referred to in support renewal documents.
Our Advice
Critical Insight
- Focus on needs first. Conduct a thorough requirements assessment and document the results. Well-documented license needs will be your core asset in navigating SAP licensing and negotiating your agreement.
- Examine indirect access possibilities. Understanding how in-house or third-party applications may be accessing the SAP software is critical.
- Know what’s in the contract. Each customer agreement is different and there may be terms that are beneficial. Older agreements may provide both benefits and challenges when evaluating your SAP license position.
Impact and Result
- Conduct an analysis to remove inactive and duplicate users as multiple logins may exist and could end up costing the organization license fees when audited.
- Adopt a cyclical approach to reviewing your SAP licensing and create a reference document to track your software needs, planned licensing, and purchase negotiation points.
- Learn the “SAP way” of conducting business, which includes a best-in-class sales structure, unique contracts and license use policies, and a hyper-aggressive compliance function. Conducting business with SAP is not typical compared to other vendors, and you will need different tools to emerge successfully from a commercial transaction.
- Manage SAP support and maintenance spend and policies. Once an agreement has been signed, it can be very difficult to decrease spend, as SAP will reprice products if support is dropped.
Explore the Secrets of SAP Software Contracts to Optimize Spend and Reduce Compliance Risk
Start here – read the Executive Brief
Read our concise Executive Brief to find out why you need to understand and document your SAP licensing strategy, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.
1. Establish licensing requirements
Begin your proactive SAP licensing journey by understanding which information to gather and assessing the current state and gaps.
2. Evaluate licensing options
Review current licensing models and determine which licensing models will most appropriately fit your environment.
3. Evaluate agreement options
Review SAP’s contract types and assess which best fit the organization’s licensing needs.
4. Purchase and manage licenses
Conduct negotiations, purchase licensing, and finalize a licensing management strategy.
Member Testimonials
After each Info-Tech experience, we ask our members to quantify the real-time savings, monetary impact, and project improvements our research helped them achieve. See our top member experiences for this blueprint and what our clients have to say.
9.8/10
Overall Impact
$60,658
Average $ Saved
9
Average Days Saved
Client
Experience
Impact
$ Saved
Days Saved
NZ Department of Corrections
Guided Implementation
9/10
$123K
16
Distribuidora la Florida S.A
Guided Implementation
7/10
$12,733
2
Alcoa Corporation
Guided Implementation
10/10
$127K
N/A
About Info-Tech
Info-Tech Research Group is the world’s fastest-growing information technology research and advisory company, proudly serving over 30,000 IT professionals.
We produce unbiased and highly relevant research to help CIOs and IT leaders make strategic, timely, and well-informed decisions. We partner closely with IT teams to provide everything they need, from actionable tools to analyst guidance, ensuring they deliver measurable results for their organizations.
What Is a Blueprint?
A blueprint is designed to be a roadmap, containing a methodology and the tools and templates you need to solve your IT problems.
Each blueprint can be accompanied by a Guided Implementation that provides you access to our world-class analysts to help you get through the project.
Need Extra Help?
Try Our Guided Implementations
Get the help you need in this 4-phase advisory process. You'll receive 11 touchpoints with our researchers, all included in your membership.
Guided Implementation #1 - Establish licensing requirements
- Call #1 - Engage in a scoping call
- Call #2 - Assess the current state
- Call #3 - Determine licensing position
Guided Implementation #2 - Evaluate licensing options
- Call #1 - Review product options
- Call #2 - Review licensing rules
Guided Implementation #3 - Evaluate agreement options
- Call #1 - Review contract option types
- Call #2 - Review vendors
Guided Implementation #4 - Purchase and manage licenses
- Call #1 - Determine negotiation points
- Call #2 - Finalize the contract
- Call #3 - Discuss license management
- Call #4 - Evaluate and develop a roadmap for future licensing