How Effective is SAP in its Acquisitions?

Executive Summary

  • Why are SAP’s new acquisitions forecasted without analyzing how SAP’s previous acquisitions fared?
  • Find out how well SAP tends to do with acquisitions.

Introduction

SAP acquisitions follow a very familiar path. We call this the “acquisition algorithm.”

The Acquisition Algorithm

  • The acquisition target is announced.
  • Top executives go on a full charm offensive selling what a good idea the acquisition will be.
  • IT Analyst, Wall Street analysts, and media entities normally weigh-in that the acquisition fills some of the need or provides some “synergy,” or they cover the topic merely announcing the acquisition without any commentary of any kind.

And this algorithm applies to not only SAP but also to the media coverage of non-SAP acquisitions.

The Important of Never Looking Back

In analyzing many articles from major IT media that cover SAP’s acquisitions, one thing that is nearly never done is to analyze the previous history of acquisitions. Once the vendor is acquired, its financials are subsumed into the overall SAP revenues, and it becomes very difficult to check how the vendor grew or did not grow post-acquisition.

In this way, SAP and those that promote the acquisition are never questioned on the accuracy of their projections. SAP does not take out advertisements that say..

“we completely failed in XYZ acquisition,”

…and the IT analysts and IT media entities normally just move on to the next topic.

Our SAP Acquisition History Scoring Method

While researching the Qualtrics acquisition we came across the Wikipedia entry for SAP that shows all of SAP’s acquisitions. According to Wikipedia, Qualtrics is SAP’s 69th acquisition. So the question we wanted to answer is “what is the average score of an SAP acquisition.

In terms of our method, we scored each of the 69 acquisitions on the basis of the degree to which the acquisition became an important component of SAP. The scoring was not based on how good the acquisition was for customers. That would be a completely different scoring and would be lower. Let us take the example of the Business Objects acquisition to explain the logic.

The Business Objects Acquisition

The Business Objects acquisition was very bad for the previous Business Objects customers. Support for Business Objects severely declined not long after SAP made the acquisition and prices increased. Many customers that did not want to work with SAP when they first purchased from Business Objects were now subject to SAP account reps, and SAP’s acquisition of Business Objects lead to Business Objects stagnating as a product, undermining the investment by Business Objects customers in the solution. When Business Objects was purchased it was a frequently discussed vendors in BI circles, now your barely hear about the Business Objects product. Years later, Business Objects is far less important as a product in the BI space that it was in 2007 because SAP has allowed the solution to stagnate.

Secondly, the promised integration with SAP BW, a primary reason given for the acquisition, never came. On one project we tested a new crossover component which was supposed to replace the BEx, and it broke so often we stopped using it. At the time of the acquisition, there was all manner of promises by SAP of how SAP BW and Business Objects would work together. Every year that passes, we hear less about Business Objects.

SAP never changed the name of Business Objects. Yet since the acquisition in 2007, the term Business Objects has declined from (in the US) from a search term popularity of 72 to 8, where it stands now. Is this acquisition a success? It depends upon your perspective. One SAP resource told me that the acquisition was successful because Business Objects was cutting into BW sales, so the acquisition neutralized a competitor. This brings up the question of whether all of the promises made by SAP to make BW work with Business Objects were fake. 

If the rating were based upon how it benefited Business Objects customers we would assign a rating of 1 out of 10. However, SAP did get a temporary bump from acquiring Business Objects, acquired some customers and was able to ruin a competitor, etc..

We assigned a 6.5 out of 10 in that it was leveraged to some degree by SAP. SAP failed to meet any of its promises around Business Objects at the time of the acquisition, but from a purely SAP perspective, and without considering the dislocation to Business Objects customers, and how it undermined their investment, the acquisition was still mildly beneficial to SAP.

SuccessFactors

SuccessFactors was another of the most successful of SAP’s acquisitions. Notice the increase in popularity as tracked by Google Trends.

Just prior to the acquisition in 2011, SuccessFactors had a popularity of 32, however recently they have had a popularity/interest over time of 52. SuccessFactors along with Ariba, have been two of the most heavily promoted acquisitions in SAP’s history, with the joke being that when Bill McDermott wakes up in the middle of the night from a deep slumber, he often screams “SuccessFactors.” 

However, any increase in SuccessFactors has not come from the originally intended place, which is migrating SAP HCM customers to SuccessFactors. According to Jarrett Pazahanick, our goto resource for all things SuccessFactors, SAP has only successfully converted roughly 7 percent of pre-existing HCM customers to SuccessFactors Employee Central.

SAP has kept SuccessFactors on the front burner in its marketing for seven years, and that by itself would have helped SuccessFactors’ market presence. SuccessFactors has also been pivotal for SAP in presenting itself as a cloud vendor to Wall Street. The acquisitions of both Ariba and SuccessFactors have been highly successful in giving the cloud SAP a cloud “halo” and helping to keep it’s multiple high.

SAP’s High Number of Acquisitions with a Score of One out of Ten

Many of the acquired vendor products (or renamed products) have disappeared from SAP’s focus, and the specialties they occupied are still not at all important to SAP. In fact, the promiscuous acquisitions are one reason why such a high percentage of SAP’s product list is filled with dead products (which we covered in the article How Many Products Does SAP Have?)

Perhaps VW should “unpimp” SAP’s acquisition strategy because so many of SAP’s acquisitions “get an F.” VW’s headquarters is in Wolfsburg, Gemany, which is only 275 miles from SAP’s headquarters in Waldorf, Germany, so it would be a reasonably short distance to travel. 

This means that these acquisitions (for which there are many) received a 1 out of 10 for acquisition effectiveness. If an acquisition is made, and then years later the specialty is either barely known and or SAP receives very little revenue from the category, clearly this cannot be considered a successful acquisition. Many of these acquisitions just seem to disappear a few years after the initial marketing push.

One prominent example is SAP’s acquisitions in the 2005 to 2008 timeframe when SAP acquired multiple manufacturing execution related vendors. Today SAP is not known for this software category in any way, even though they made three acquisitions in this space (Lighthammer, Factory Logic, and Visiprise).

Exclusions to the Scoring

The most recent acquisitions were excluded from the analysis. Qualtrics is an acquisition that has as close as possible to zero chance to be effective, but we did not want to mix up the future with the present.

Because the last seven SAP acquisitions are within a year or so old, it is not yet possible to evaluate if they have been successful. Therefore the most recent acquisitions are listed as “TBD” and not scored. Several other acquisitions were more of a consulting company than a software vendor, so we marked those as “N/A” and they were also not scored.

Having gone through these clarifying topics, we have included the following acquisition table.

The SAP Acquisition History Table

The columns in blue are directly from Wikipedia. The orange column is the Brightwork Research & Analysis score. Items in Orange text were adjusted after input from Mark Chalfen.

The average score for all of the acquisitions that were rated is a 2.2 out of 10. 

The first thing to notice is the high number of scores of 1 in history. This is applied when SAP does not have very much business in that software category or when we have first-hand knowledge that the acquisition did not do anything for SAP. The logic for acquisitions is often that the acquired vendor will grow because they will have access to SAP’s account base. But it is extremely difficult to find a small acquisition by SAP that did that. This means that the proposal that SAP makes sales increase because of account exposure is a myth. Interestingly, SAP has been able to force extremely weak products into customers. Applications ranging from PLM to BW. However, SAP is far better in pushing internally developed applications into customers than acquired applications.

Many of the acquisitions were in categories that are never discussed in SAP circles or on SAP projects. In fact, if you told many people that worked with SAP that SAP had an application that covered the area, they would not know.

The Acquisition Outlier of Top Tier

There is one very prominent exception to this pattern of failing to grow acquisitions, and that is the acquisition of Top Tier. Top Tier is one of the only acquisitions we could find that actually grew in a way it could not have without being acquired.

Top Tier is one of SAP’s most successful acquisitions, and we gave it a score of 7 out of 10. Top Tier may be a particularly controversial scoring. SAP acquired Top Tier to obtain a small ERP system named Menahel or Top Tier, which would be renamed to BusinessOne. BusinessOne became a popular SMB ERP system and one with a fertile ecosystem that developed industry-focused extensions to the core ERP system. However, BusinessOne was never very profitable for SAP, and it also served to distract SAP by putting into a market for which it is a poor fit.

Secondly, customers that buy BusinessOne are not good customers for other SAP products, and BusinessOne integrates with few other SAP applications. Therefore BusinessOne customers have little follow-on purchases of other SAP products, primarily because they can’t afford them, and they are not designed to work with BusinessOne. Therefore while Menahel/Top Manage/BusinessOne did grow, it did not necessarily have a positive impact on SAP, and one could argue it simply distracted SAP. BusinessOne helped SAP get into the SMB market, but the SMB market is a very bad fit for SAP.

  • SAP’s bread and butter are extremely high-cost projects for large companies that can endure constant run rates of billing hours. This is not the SMB market. (See our TCO estimator for SAP ECC, and observe the difference in the TCO estimate for ECC versus BusinessOne).
  • Consultants that work on BusinessOne projects, don’t work on ECC projects. There is little overlap between BusinessOne and the rest of SAP. The term “red-headed stepchild” comes to mind.

The Top Tier acquisition also had negative side effects in that it brought in Shai Agassi into the company, which lead to problematic implications when he later headed up the Netweaver initiative. Netweaver was a failed program to modernize the integration and infrastructure of SAP. Many years after Netweaver, SAP continues to be as difficult to integrate to SAP and non-SAP applications as it was in the mid-1990s, a subject covered in the article How Non Programming Integration Hurts SAP Projects.

Netweaver left SAP with components that it continues to try to use but which handicap anything connected to them. Everything that is part of Netweaver has a better open-source offering.

Knowing what is known today, it is an interesting question to ask whether SAP would acquire Top Tier again.

An Incomplete Acquisition List

After we reviewed the list, we realized that this list is not a complete listing of SAP’s acquisitions. We covered in the article Did Hasso Plattner and His Ph.D. Students Invent HANA?, that SAP suppressed acquisitions that it made that made up what eventually became HANA. This is because SAP contributed very little to HANA.

SAP purchased both Trek and P*TIME but likes to pretend that they didn’t. This was to do to try to create a false storyline that attributed innovation specifically to Hasso Plattner that he had nothing to do with. Therefore, SAP’s policy with respect to publicizing an acquisition varies. If they want to pretend that they created something new, then they keep the acquisition secret.

I have not included a score for Trek and P*Time. However, their scoring would be complicated. HANA became a moderately popular database, but it has also been an enormous distraction, they are being sued by Teradata in what looks to be an expensive lawsuit to defend, and has alienated customers and vendors in a way that will cost SAP for years to come.

IT Analyst, Wall Street Analysts, and Media Coverage

Throughout the years, IT analysts, Wall Street analysts and media entities have normally framed SAP acquisitions in a positive light. There is a strong tendency of media coverage to put a positive spin on an acquisition, even though the history of acquisitions is quite poor. However, the evaluation of SAP’s history with acquisitions demonstrates that IT analysts, Wall Street analysts and media entities repeatedly provide inaccurate information on SAP acquisitions.

From a policy perspective, there is sufficient evidence for governments to deny acquisitions out of hand, and to only allow them on exceptional grounds. This subject broaches topics related to how to maintain competitive markets. Topics which IT media entities and Wall Street analysts have opposing interests. Media entities obtain advertising from large corporations that tend to make acquisitions, and Wall Street itself makes money from mergers and acquisitions and prefers monopolies. The perfect investment vehicle for Wall Street is a company whose customers have no options in the marketplace and are locked into a particular supplier. This is the final end state that Wall Street would prefer for each industry as it leads to the highest possible profits.

For these reasons, they both have undeclared financial biases when they make projections or otherwise comment on acquisitions. This brings up the question of when IT analysts, Wall Street analysts and media entities cast a provide views on a new SAP acquisition, are they offering an honest appraisal, or merely singing from their wallets?

The Implications of the Score in Forecasting Future SAP Acquisitions

An average effectiveness rating of 2.2 out of 10 is obviously a very poor score. It should be used to evaluate future SAP acquisitions to observe that SAP is not generally effective at performing acquisitions. And therefore, future acquisitions are also most likely to not be successful.

Motivation

It should be stated, we don’t care one way or another what is the final score for SAP’s acquisition effectiveness. This is our best estimate of SAP’s acquisition effectiveness. The curious thing is that no SAP partner or IT analyst would want to publish an analysis of SAP’s acquisition as they would fear the response from SAP. This fear of SAP prevents any analysis of SAP that might come up with “the wrong answer.” Not only will these entities not do it, IT media companies would never do it because a) they don’t perform historical analysis and b) they rely on SAP for revenue in the form of advertisements and paid placements.

For software buyers, this study shows that there is little reason to get excited by an SAP acquisition. SAP does a very poor job of managing its acquisitions and seems to perform acquisitions first and foremost to make an impression or “splash” with Wall Street.

If someone were to reach out and make a compelling case that a score should be changed, we would consider doing so if the argument were compelling. We can’t have specific knowledge of every single acquisition. However, even if several acquisition scores were increased or decreased, the overall tendency is quite clear.

Conclusion

History shows that SAP is ineffective in its acquisitions. Wall Street analysts and media entities have far more resources to do this simple checking that does Brightwork Research & Analysis, however, apparently, they have no interest in doing it. The reason I think this is cannot remember ever reading an article that analyzed SAP’s acquisition history, yet, analysts are quite willing to discuss the synergies that await SAP after each successive acquisition.

Secondly, this analysis underestimates the problems that acquisitions create for SAP. SAP suffers from a distinct problem in accomplishing things that it sets out to do internally. Each new acquisition puts SAP as the overseer into a new vendor, which is frequently in software categories that SAP has no experience in managing. SAP repeatedly finds itself out of its depth in trying to manage an increasingly unwieldy software empire.

As SAP has continued to make acquisitions, it has blurred its focus that much more than it was already blurred and reduced their ability to execute.

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 Other SAP Acquisitions Content

References

https://en.wikipedia.org/wiki/SAP_SE

How Accurate Was SAP on the Sybase Acquisition?

Executive Summary

  • SAP acquired Sybase in 2010 and Sybase has become almost invisible ever since.
  • We review what SAP said and the coverage of the Sybase acquisition by IT analysts.

Introduction

In 2010 SAP acquired Sybase. This is before HANA had been introduced. SAP was within a year to promote the idea that it had developed a massive innovation in in-memory and columnar database design, which was a pre-existing produce called Sybase IQ.

In this article, we will review the accuracy of the reported statements about the Sybase acquisition.

Quotations from Dennis Howlett’s Article in ZDNet

“John Chen, CEO of Sybase said: “We see potential in the combination of the leader in business applications and the leader in mobile…I firmly believe this transaction is about growth. ” Vishal Sikka said: “This will dramatically increase our presence in mobile…supporting all platforms, Blackberry…Windows…Google…Apple”

“The last couple of years, SAP has talked implicitly about proliferating SAP via devices so at one level this acquisition fits into a strategy that’s been unfolding for a while. However, as Ray Wang notes:

SAP has broken its promise of no more big acquisitions after the BusinessObjects deal.  However, these acquisitions make sense toward the path of next generation applications.”

IT Analysts Always Seem to Love Software Acquisitions

It might have, but the acquisition did not work. Is there some reason that IT analysts don’t ever seem to say that an acquisition is a bad idea? Is this, so they don’t lose access to the larger software vendors?

“During the analyst call, much was made of the in-memory database core that SAP has developed and Sybase column stores as an enhanced baseline requirement for analytics in large-scale environments.”

That is curious.

Hasso Plattner created a storyline where he and his PhDs invented HANA without the influence from much else outside of SAP. This is covered in the article Did Hasso Plattner and His Ph.D. Students Invent HANA?

SAP Ended up Degrading Sybase Database Market Share

“One short-term problem will be a perceived confusion over database selection and the future of the relational database in SAP environments.”

This turned out to be a problem. SAP was not successful in migrating customers to Sybase databases, and Sybase databases have been in decline ever since the acquisition.

Howlett Gets it Right on SAP Penetrating Finance Industry

“Vishal Sikka disputes that, describing the market as both mature but diverse. Sybase has a significant market share in financial services, a market around which SAP sees huge potential despite the recent financial services sector meltdown. But how real is the likelihood of SAP emerging as a key FSI player?”

Vishal Sikka was wrong about this too. SAP never was able to leverage Sybase’s market share in financial services.

“Co-incidentally, earlier in the week, I heard a presentation from Deutsche Bank which showed SAP at the core of the bank’s applications strategy as part of a complete applications overhaul. SAP is only providing back office and even then a pared back version with emphasis elsewhere. It is others that are providing the applications and services that will make an operational and value led difference. Deutsche Bank is a marquee SAP customer in its own back yard. If this is representative of the extent of SAP’s ability to develop profitable relationships in this market then that is anything but a done deal.”

Dennis Howlett was prescient with this prediction.

Sybase’s Disappearing Mobility

“On the mobile side, questions must be raised about what this means for applications – again in the financial and telco utility space. Most applications in these markets are driven by opportunistic marketing campaigns requiring the development of new offers. That in turn often means custom development. Does SAP think that Sybase and in-memory gives them an entree to this massive market? If so how does it plan to manage all the integrations required? Where is the rapid apps development environment that would make SAP a natural choice? It has no real ownership in these markets such that the new combination makes direct sense.”

Here is what we wrote about the Sybase Acquisition back in 2012.

Will Things Change and Improve?

“In a word no.

Although SAP did purchase Sybase, but this does not change SAP’s history or its data architecture for the vast majority of its product database. SAP does not integrate their products with those companies that they acquire. Notice the lack of integration with Business Objects. SAP as a development organization is too self-centered to think that other companies have good solutions and they feel they are the best in every domain. This is called the “SAP Bubble,” and is very similar to the “Microsoft Bubble.” Therefore, most mergers are primarily driven not by development, but by the strategic decision makers in order to co-opt a vendor who is giving them trouble, as was the case with Business Objects. These acquisitions are driven by the desire to capture customers. Over time the main brains in the acquired company leave for other ventures and the captured customers are fed a steady diet of pro SAP marketing. There are questions to whether SAP bought Sybase really for its database or its lucrative customer base in the financial industry. The long and short of this is that SAP does not actually do much to leverage or further develop the technology that it purchases.”

SAP’s History With Their Data Layer

In order to understand why it is very unlikely that very much will change it is important to understand SAP’s history with data and data management in general. Unlike companies such as Teradata or Oracle, SAP, has no history of effective data management within any of their applications.

Examples of serious weaknesses in their data management development include the following:

  • No transactions to easily query the master data of a system (SE16 and SE16N are very limited, and too often lead to the brick wall of a Structure, which cannot be queried. While fields can be looked up in the SAP GUI, in many cases the table that the technical details will show is a structure. This is a virtual table and not a “real table.”
  • Poor data update tools
  • No ERD diagram or publication of all the SAP tables and how they relate to each other
  • No ability to use standard SQL tools to manage or interrogate the database. All data tools are custom front-ends and are universally terrible.
  • Why anyone would think that a company that is done this poorly bad at simple basic data strategies is strange, and why anyone would entrust their reporting solution to them, is even stranger. SAP built its empire based upon application logic, not on the user interface or data management. Essentially SAP just does not fundamentally “get” data, and they have created the very inefficient data backend of any enterprise application.

Sybase’s mobility applications turned out to be a total write off.

Conclusion

The Sybase acquisition did very little for SAP. Once again Vishal Sikka continued his losing streak of being wrong in his statements in this article.

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 Other SAP Acquisitions Content

References

https://www.zdnet.com/article/sap-acquires-sybase-for-5-8-billion-but-why/