Why Did SAP Stop Reporting HANA Numbers After 2015?

Executive Summary

  • SAP reported customer numbers on HANA — right up until 2015.
  • The question we cover is what happened to this reporting and what it means.

Introduction

SAP has two ways of speaking in general. One is when they are speaking to an audience that is compliant, like at SAPPHIRE, to media they pay to cover them and on analyst calls. On analyst calls SAP makes confident statements about the growth of its products, but the evidence is normally lacking.

In this article, we will address the peculiar decline in reporting on HANA implementation numbers.

The Diginomica Article

In Q2 of 2015, one of the last definitive statements around customer numbers was issued. Diginomica is paid by SAP, so they are a compliant media outlet for them. Every single time we evaluate the accuracy level of an entity that is funded by SAP, we find high levels of inaccuracy. And this has been true of every Diginomica article we have reviewed.

Here is a screenshot of the article from 2015.

The revenue growth from HANA is described as explosive by John Appleby.

“…the explosive revenue growth from HANA continues, even if average deal volume has decreased, because there are plenty of sell-ons to existing customers. Therefore your original projections are probably about right. This means that HANA is supporting core revenue quite significantly by now. But also, every deal is a HANA deal, and deals are bundled.” – John Appleby

John Appleby was a primary shill for SAP in the past. And at this time in 2015, he was a primary source of information on HANA.

After Appleby, one of least accurate sources of information on SAP is Ron Enslin (how now works at Google), and he had the following to say.

“This quarter, the number of HANA customers surpassed 7,200 compared with 3,600 a year ago.”

So there is the definitive quote. 7,200 customers in the 2nd quarter of 2015.

Dennis Howlett, the article’s author stated the following:

“This is a crucially important point because now, SAP is recognizing the need to be aligned to ‘solving the unsolvable’ and ‘imagining the unimaginable’ problems that former board member Vishal Sikka, now CEO Infosys envisioned back in 2010-12 and which he is carrying through in his current company.”

This is an amazing quotation, because it is a writer repeating another highly unreliable source, Vishal Sikka, without even filtering the observation.

Furthermore, even in 2015, it was known that Vishal left SAP under unusual circumstances.

Where Are the 2016, 2017 or 2018 HANA Customers?

We searched online for HANA customers in 2016, 2017 and 2018 and could not find any statements from SAP on HANA customer numbers. If the growth was explosive in 2015 — why did the reporting of customer numbers stop in 2015?

Interestingly, SAP appeared to change the narrative to S/4HANA, and began quoting S/4HANA customers numbers rather than HANA customers.

The Customer Estimate from iDatalabs

We found that iDatalabs tracks the number of HANA customers. iDatalabs is a sales intelligence firm, so they profile the usage of applications and databases in order to sell the data to companies that want to sell into customers that have ABC or XYZ product already.

We have reviewed iDatalabs in the past and found their estimates to seem reasonable, and they do not have an incentive to overestimate or underestimate the number of customers.

“We have found 7,370 companies that use SAP HANA. The companies using SAP HANA are most often found in United States and in the Computer Software industry. SAP HANA is most often used by companies with 50-200 employees and 1M-10M dollars in revenue. Our data for SAP HANA usage goes back as far as 3 years and 9 months.”

If this is accurate it means that SAP has not grown its HANA customers since it last reported the HANA numbers in 2015. For another data point, we went out to DB Engines, which tracks database popularity.

Notice that HANA begins to stall in 2015. Up until that point, SAP had a growth story, but growth was much more difficult to come by after this. Would this explain why SAP simply stopped reporting customer numbers? 

Customer Numbers Versus Number of Instances

A customer that brings buys a single instance of HANA is a customer of HANA. But one customer can have any number of individual HANA database instances. Therefore, the overall popularity would be measured by the total number of instances rather than the number of customers. Oracle, as an example, will normally have customers that use many instances of their Oracle database. HANA is not like this. HANA normally comes into the company through a conversion for the BW, but then new HANA instances are slowed because the cost and expensive and overhead of HANA becomes apparent. SAP tells massive lies to customers to get them to convert (I receive the documents that SAP provides through customers — documents that are not published on SAP’s website, but which tell customers that they HAVE to use HANA if they want various application benefits).

Top Customers of HANA

iDatalabs lists the following top customers for HANA.

“Royal Dutch Shell PLC shell.com Netherlands >1000M >10000
ICS Consultancy Services icsconsultancy.com India 10M-50M 50-200
Mawai Infotech Limited mawai.com India 10M-50M 50-200
Birlasoft (India) Ltd. birlasoft.com India 200M-1000M 1000-5000
SuccessFactors, Inc. successfactors.com United States 200M-1000M 1000-5000”

Notice that three of these companies are SAP consulting firms, and a fourth (SuccessFactors) is actually an SAP company.

Faux Customers Through SAP Consulting Firms

Something that is not generally explained is that the vast SAP ecosystem adopt SAP products, not to use them internally, but to build skills. Therefore they bring up a demo environment to show customers, and they are counted as a customer of that product. We found this repeatedly in the S/4HANA space, where again, many customers of S/4HANA, particularly S/4HANA cloud were SAP consulting firms.

Notice anything curious about the customers listed on this slide for S/4HANA? Why are so many customers SAP consulting firms? Do SAP consulting firms really need an ERP system? Dickinson & Associates is not even a consulting firm, they are an SAP recruiters. Recruiters require ERP systems now?

A representative from Dickinson & Associates debated me as to the benefits of S/4HANA for customers. For a person with a technical background, it does not get any lower than debating a recruiter as to what is technically true and false. Its the equivalent of looking for a fight at a preschool.

These kids are not far off in their SAP knowledge from SAP recruiters. But where recruiters really make up the difference is……confidence. 

As with S/4HANA Cloud, this means that a sizable component of the early growth of HANA “customers” was to the consulting ecosystem. It should go without saying that these are not real customers.

And when SAP has so many SAP consulting firms that it can transfer licenses to at very low cost, this is a primary way that SAP rigs the growth numbers of new products to make them look more successful than they actually are. By the time the growth slows down (as has now happened with S/4HANA) SAP simply pivots the reporting to a new product, which again is early in its lifecycle and being adopted by the SAP consulting firms.

Project Examples with HANA

We have it from a reliable source that SAP won a head to head project that contained no HANA. The reason for this was that the SAP management had substantial compensation incentives for HANA the put it into the already confirmed and priced BOM. At zero discount and discounted everything else so HANA, a product not used or needed, was 30% of the total cost.

The salesperson did not achieve his targets when HANA was not included. Due to this, the salesperson told the customer price stays the same, and they threw in a new product at no cost.

SAP management made their HANA number, but the customer now pays a support fee (which is based on the list price, not the discounted price) for a product that they do not use. SAP counts this as a customer, even though HANA was not implemented.

The following is a quote from a person with intimate knowledge of the HANA deals made by SAP.

“Nearly all orders we filled were BS and customer didn’t need. Even on BW – the implementations were so complex and so much fine tuning as soon as the experts left, or the scope changed – problem.”

The Asian Airlines that Lost on HANA

“An Asian airline was implementing a new sap ERP a few years back and did not choose HANA. After buying SAP had another go and brought in their top people. It still didn’t make business sense and airline couldn’t justify the price. There was simply no ROI. Finally SAP played the “no future new functionality” card and said the module the Asian airline wanted (flight planning) was only available on HANA. At that point the airline felt they were essentially forced to buy.”

This quote paints another picture of SAP pushing HANA for SAP rather for any reason that the customer needs.

This story gets even stranger because there is no product in SAP’s product list that has the word “flight” on the list. It is a secret product or perhaps vaporware?

Secondly, a planning module like that will be processor intensive, but it is not going to be read access intensive. So this is another example of SAP overgeneralizing the benefits of HANA. I have never run into flight planning before, but there is going to be best of breed solutions that are developed by people with years of flight planning experience that SAP won’t be able to compete with. Sabre has a solution. So SAP is going to compete with Sabre?

Furthermore, there are a series of free flight planning websites that are easily available online. Upon investigation, the number of flights that are planned on HANA globally is very close to zero.

Companies that Bought HANA, With No Intention of Using It

“The customer said they had no plans to use HANA, so I asked why, then, had they bought it. They explained that their procurement had negotiated all the SAP modules they wanted and the price. The final order docs came back from SAP with HANA added to the product list as the last line, the entire order price allocated to HANA, and the word “Included” next to all the products that they were actually buying – as if the ERP modules were components of some sort of HANA “suite”.

So SAP found a way to book millions in revenue to Hana even though their customer had no use for it and didn’t want it. This customer didn’t object as they were told by SAP that they were getting a free product that they might use/need one day and would mature over time. So they let it go.”

And why was this done? So that SAP could report to Wall Street that HANA is growing, much more than it is.

Conclusion

SAP had grand plans for HANA, and when they did not pan out, SAP stopped reporting HANA customer numbers. Secondly, the numbers that were reported were significantly exaggerated because HANA was being adopted by consulting firms and other associated companies that are part o the SAP ecosystem that did not reflect real usage.

This is consistent that when the numbers are good, the numbers get reported, and when they are not, they don’t get reported, and the company moves to reporting on other things. Growth is easy to attain in the beginning, but as a product gets better known, if it is less effective than advertised, its growth slows. And HANA was far less effective than advertized. We began our own coverage on HANA’s inaccuracies around 2016 as evidence began to come in that all was not right on HANA implementations.

This article in Diginomica receives a 1 out of 10 for accuracy. Furthermore at the time of this article was published, Diginomica was a sponsor. This is the problem with a compliant media, that is looking for income from the entity they are covering.

The Necessity of Fact Checking

We ask a question that anyone working in enterprise software should ask.

Should decisions be made based on sales information from 100% financially biased parties like consulting firms, IT analysts, and vendors to companies that do not specialize in fact-checking?

If the answer is “No,” then perhaps there should be a change to the present approach to IT decision making.

In a market where inaccurate information is commonplace, our conclusion from our research is that software project problems and failures correlate to a lack of fact checking of the claims made by vendors and consulting firms. If you are worried that you don’t have the real story from your current sources, we offer the solution.

Financial Disclosure

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 HANA Implementations Content

References

https://diginomica.com/saps-q2-fy2015-more-color-on-the-results-s4-is-acoming-hana-revived/

https://idatalabs.com/tech/products/sap-hana

https://vfrflight.org/en/tutorials.html

https://www.iflightplanner.com/

https://www.sabreairlinesolutions.com/home/software_solutions/product/flight_planning/

https://db-engines.com/en/ranking_trend/system/SAP+HANA

TCO Book

 

TCO3

Enterprise Software TCO: Calculating and Using Total Cost of Ownership for Decision Making

Getting to the Detail of TCO

One aspect of making a software purchasing decision is to compare the Total Cost of Ownership, or TCO, of the applications under consideration: what will the software cost you over its lifespan? But most companies don’t understand what dollar amounts to include in the TCO analysis or where to source these figures, or, if using TCO studies produced by consulting and IT analyst firms, how the TCO amounts were calculated and how to compare TCO across applications.

The Mechanics of TCO

Not only will this book help you appreciate the mechanics of TCO, but you will also gain insight as to the importance of TCO and understand how to strip away the biases and outside influences to make a real TCO comparison between applications.
By reading this book you will:
  • Understand why you need to look at TCO and not just ROI when making your purchasing decision.
  • Discover how an application, which at first glance may seem inexpensive when compared to its competition, could end up being more costly in the long run.
  • Gain an in-depth understanding of the cost, categories to include in an accurate and complete TCO analysis.
  • Learn why ERP systems are not a significant investment, based on their TCO.
  • Find out how to recognize and avoid superficial, incomplete or incorrect TCO analyses that could negatively impact your software purchase decision.
  • Appreciate the importance and cost-effectiveness of a TCO audit.
  • Learn how SCM Focus can provide you with unbiased and well-researched TCO analyses to assist you in your software selection.
Chapters
  • Chapter 1:  Introduction
  • Chapter 2:  The Basics of TCO
  • Chapter 3:  The State of Enterprise TCO
  • Chapter 4:  ERP: The Multi-Billion Dollar TCO Analysis Failure
  • Chapter 5:  The TCO Method Used by Software Decisions
  • Chapter 6:  Using TCO for Better Decision Making