- AWS created a presentation to show the relationship with SAP.
- How much of the information provided around the co-interests of SAP and AWS are true?
One of the most interesting developments in public cloud is how the public cloud service providers like AWS or GCP or Azure will work with the on-premises vendors. Oftentimes things are presented by companies for political reasons rather than what is true. We found the following slides from a presentation by AWS.
This slide from a presentation by AWS shows a very complimentary relationship between AWS, SAP and a number of partners. However, the reality is quite a bit different. Not only SAP, but many of the partners on this slide intent to significantly intermediate between AWS and the final customer.
This slide (by AWS) shows what is feasible, but not necessarily what is desirable for customers. Under the scenario where the SAP Cloud is the origination, the prices are dramatically higher. The table to the right shows that AWS claims a far more complete offering than GCP or Azure.
How SAP Plans on Maintaining its Margins
All of SAP’s recommendations for cloud come with a markup over the cloud provider, which SAP does not discuss and pretends does not exist. Cloud service providers that seek to gain SAP business must tread very carefully around the topic of SAP’s markup on their services, as we covered in the article How to Understand SAP’s Upcharge as a Service Cloud. Repeatedly circumvented SAP to sell directly to SAP customers rather than giving them a markup, SAP will immediately disappear from SAP’s recommended providers listing. SAP will try to direct customers to cloud service providers that allow for SAP to obtain their margin. In fact, this may be the main strategy that SAP will use to increase their margins.
See this comment from the SAP Q3 2018 analyst call.
As customers choose to switch to cloud, vendors have to deal with shifting from the upfront cash earned in on-premises deals to the ongoing subscription costs associated with cloud services.
On the earnings calls, execs argued that, as cloud has more lifetime value and more predictable future revenues, the firm was going in the right direction in the long term.
Insisting that the core business was stable anyway, CEO Bill McDermott said they should be “celebrating with champagne… that the cloud is soaring”, adding that if cloud was flat with a “rock solid core”, analysts would be “worried about the future”.
CFO Luca Mucic said the firm would always trade a software dollar for a cloud dollar, and “will not artificially slow cloud growth to optimise our P&L in the short-term”.(emphasis added)
Under what scenario where the vendor cannot markup the cloud services of other companies, this explanation is not true?
How can we say this?
Well, the most profitable vendors in software are the on-premises vendors. Vendors like Salesforce, the most prominent SaaS vendor has historically had low profitability. AWS is probably the most profitable cloud entity. And they are the exception.
Where Do SAP’s Margins Come From?
SAP has around an 85% margin on support. This is by far their largest margin item and the only real part of SAP’s revenues that are growing. SAP’s margin on applications and database licenses is far lower. The quotation above leaves out the fact that for SAP’s internally developed products, SAP’s cloud is just a passthrough. The actual infrastructure and real work is performed in either a public cloud or private cloud service provider. SAP spends extremely little on their own cloud infrastructure. The cloud can become a very profitable item for SAP — if, SAP can trick companies into using SAP Cloud as an intermediary rather than going direct to the cloud service provider. The way to do this is to hide the margin from the customer. However, with public cloud, this is tricky as the pricing is public.
See this pricing estimate. SAP wants to mark this cost up by a factor of between 3 to 10 times. SAP wants to be paid for this simply for “originating the deal.” This is the only way that SAP can grow its revenues from the cloud. The SaaS applications that SAP purchases have a low margin, and several years after being acquired, the applications begin to decline in the marketplace. Cloud markup is where SAP’s financial future is.
SAP has a long history of marking things up that they do not put work into developing. Databases are a good example of this. For decades SAP has been marking up the Oracle database and IBM DB2. Customers could have received a lower price by going through those vendors directly, but both vendors allowed SAP to serve as a reseller of their databases, which resulted in big profits for SAP, and higher costs for SAP customers.
SAP can worry less about the margin on its applications and databases if they can simply markup the cost of other cloud service providers. This will be easier with “private cloud” providers because the pricing is hidden. However, for this strategy to work, the private cloud providers must cooperate with SAP, and refer customers back to SAP rather than provide a direct bid. As soon as the customer finds ou the real cost, SAP will lose their position as intermediaries. To do this SAP will have to enforce very strict rules for how private cloud providers communicate costs.
At the time of publication, this is still a “story.” That is in the IT media and on calls with Wall Street analysts, the question is not asked for SAP where these margins are coming from. That is it is not very much discussed that SAP’s strategy outside of its SaaS acquisitions is to markup the offering of other cloud service providers. In the quotation from Luca Mucic above,
“always trade a software dollar for a cloud dollar,”
..the fact that the software dollar that is being traded will in many cases not be for an SAP SaaS/cloud application, but a dollar of revenue that SAP plans to markup by 3 to 10 times over AWS/GCP/Azure/HPE/IBM/etc. Under that scenario, SAP could have the highest cloud margins in enterprise software, while doing the least actual cloud “work.”
The Problem: A Lack of Fact-Checking of SAP
There are two fundamental problems around SAP. The first is the exaggeration of SAP, which means that companies that purchased SAP end up getting far less than they were promised. The second is that the SAP consulting companies simply repeat whatever SAP says. This means that on virtually all accounts there is no independent entity that can contradict statements by SAP.
Being Part of the Solution: What to Do About SAP
We can provide feedback from multiple SAP accounts that provide realistic information around SAP products — and this reduces the dependence on biased entities like SAP and all of the large SAP consulting firms that parrot what SAP says. We offer fact-checking services that are entirely research-based and that can stop inaccurate information dead in its tracks. SAP and the consulting firms rely on providing information without any fact-checking entity to contradict the information they provide. When SAP or their consulting firm are asked to explain these discrepancies, we have found that they further lie to the customer/client and often turn the issue around on the account, as we covered in the article How SAP Will Gaslight You When Their Software Does Not Work as Promised.
If you need independent advice and fact-checking that is outside of the SAP and SAP consulting system, reach out to us with the form below or with the messenger to the bottom right of the page.
Financial Bias Disclosure
Neither this article nor any other article on the Brightwork website is paid for by a software vendor, including Oracle, SAP or their competitors. As part of our commitment to publishing independent, unbiased research; no paid media placements, commissions or incentives of any nature are allowed.
Search Our Other SAP Cloud Content
The Public Cloud Revolution Book
Interested in how to open source is powering public cloud providers like AWS and Google Cloud and what this means for the different modalities of computer hardware (cloud, on-premises proprietary server, mainframe, and appliances?). This book covers many topics that are greatly underrepresented in the common IT media coverage of these topics.