SAP Software License
For those who may not be aware, SAP is not the first company to require user licenses for third Party or “indirect Usage.” It is becoming more commonplace and some companies are quite aggressive with it. This follow up to last week’s post on SAP Third Party – Indirect Usage Licensing Part 1 will address real opportunities here.
Over the years SAP has set itself apart by aggressively pursuing sales while generally maintaining good customer relations. It is a balancing act that has served SAP well. Over the years SAP has avoided the market perception of a ruthless, do anything to get the sale, software vendor.
This whole third party, indirect software usage can undermine that.
But there IS an answer!
SAP Are You Listening? There IS a Third Party / Indirect Usage WIN-WIN Here!
Like any other company, revenue growth is a primary focus. For software companies, directly related to revenue growth there is also expanding the software footprint within the customer base.
SAP as a company wants to grow revenue and expand their software footprint. What if there IS a way to achieve this AND satisfy your customers too.
Would you agree this would be a WIN-WIN?
Customer Perception of the SAP Third Party Indirect Usage Licensing
Purchasing licenses for “indirect usage” feels to a customer like they are paying for something and not receiving any benefit. There is no “value” in this approach from a customer perspective. Yes SAP, you have your Intellectual Property (“IP”) to protect, and yes, you developed that IP.
I am not talking about a legal issue with your IP, instead I am referring to a sales, marketing, and customer relations issue.
Add a customer’s lack of awareness to the perception of “no value” and you have a recipe for difficult customer relationships. SAP third party or indirect software usage presents an unbudgeted “pure expense” from a customer viewpoint. Most customers really are not aware of the indirect usage requirement so they don’t budget for it!
SAP, Your Third Party or Indirect Usage Answer
Provide your customers a value added alternative to indirect usage or third party compliance issues. Give them an option to substitute the third party or indirect usage cost they would have incurred in the form of other SAP applications or solutions. In this way your customers are receiving something of value, you are expanding your software footprint, and you are still gaining the revenue you were looking for without the nasty reputation. If necessary, give them a deferred payment window so they can plan for and budget the change.
Provide your customers a value added alternative to indirect usage or third party compliance issues.
You can gain a HUGE advantage by targeting certain application deployments–, for example if you want to expand your Cloud sales, HANA, or mobile, you could pick the various products you will allow as a substitute for the indirect usage fees. This in turn boosts your sales of these newer products and provides your customers with something that is meaningful. This has huge strategic benefits, for example, each HANA sale potentially displaces Oracle. Each CRM sale substitute (for the indirect usage) potentially displaces Salesforce.
Expand Application Footprint and Increase Revenue
ALWAYS be ready to trade the 3rd party integration for a deeper footprint which keeps a competitor out of the client. Clients benefit from new software capabilities and SAP benefits from a revenue stream WITHOUT the negative relationship consequences of “forcing” the 3rd party maintenance issue. This also becomes a differentiator with Oracle and other vendors who will push the 3rd party issue. SAP STILL gains the additional revenue.
ALWAYS be ready to trade the 3rd party integration for a deeper footprint which keeps a competitor out of the client
You could structure contracts to defer 3rd party usage fees by adding some tradeoff in contracts like “as long as annual license revenue is at least ‘x’ no 3rd party licenses.” By doing this you are taking a “gentler” approach in preparing customers for a possible future license event. This takes the surprise, frustration, and shock out of the equation while keeping your revenue stream more predictable and giving them a chance to budget for the spend.
Conclusion on SAP Indirect Usage or Third Party Usage Sales and Marketing Options
Seriously SAP, you have a LOT of options here. You can be less adversarial and note that you will defer indirect usage or third party fees as long as a customer’s annual, net new license spend is “X” amount a year. If they need new licenses for additional users the customer perceives this as a benefit and they can gain additional time to budget for an eventual indirect usage fee. You are still satisfying your CORE requirement to grow revenue while increasing your solution footprint within your customer base AND in a way that is less offensive than the customer perception of a cost for no benefit. Many customers look at this as a penalty for choosing SAP solutions. While the IP is yours SAP, it is offensive to a customer because the data and business are theirs.
This creates a more open environment and many more customers may be willing to “come clean” about indirect usage. By providing some kind of perceived benefit they are more likely to address the compliance (rather than hiding it) AND the customer AND SAP gain something of value. Talk about a “Win-Win”!
=========================
Contact me today through our site contact form ( http://www.r3now.com/contact ), phone, or e-mail.
Bill Wood
+1 (704) 905 – 5175
=========================
Related Posts:
Popular Searches:
- sap indirect usage licensing
- crm licensing fdor direct and indirect users
- indirect usage license
- DIRECT INDIRECT USAGE OF SAP
- indirect usage of software language
- indirect use SAP
- sap wm third part
