Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Doug Henschen

Doug Henschen

Executive Editor, InformationWeek

SAP Plugs Profit Hole With Support Price Hike

SAP increases Standard Support maintenance contracts by 5.5% to 19% of the software's original cost each year. That could reopen old support price-hike wounds.

A controversy around the price for SAP software support dogged the brief tenure of former company CEO Leo Apotheker, and now the topic has reared its head again. SAP resurrected the topic by telling customers Monday that it will increase the annual cost of new Standard Support contracts from 18% to 19% of the original software licensing, effective July 15.

The first to shed light on SAP's announcement was independent analyst and blogger Frank Scalvo, who in a stinging post pointed out that the seemingly small single-point change amounts to a 5.5% increase. Scalvo encouraged customers to pepper SAP with questions around a central theme of "What are we getting for our money?"

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

An SAP spokesperson on Tuesday told InformationWeek that the planned increase will be "relevant for a relatively small group of SAP customers" because the "new customer adoption rate for Enterprise Support is 95%." Enterprise support is 22% per year. The increase on Standard Support will not apply to the (small-business-oriented) BusinessOne app or to contracts already in force.

However, that 95% only refers to new customers making this choice since this option was available. Don't confuse this adoption-rate stat with the current ratio of all customers on Enterprise versus Standard contracts. That's a figure the spokesperson said SAP does not divulge. If the total on Standard Support isn't much higher than 5%, it's hard to believe the company would bother revisiting this PR nightmare of a topic.

[ Want details on the 2010 compromise on software maintenance? Read SAP Introduces Two-Tiered Support. ]

Until 2008, all SAP maintenance support contracts were 17% of the original software licensing annually, but in July 2008 the company announced it would step up the fees to match rival Oracle and many other enterprise software companies that charge 22% per year. A customer outcry ensued -- understandable given that largest customers faced cost increases of millions of dollars per year, just as the recession was getting underway.

SAP relented in 2010, coming up with a two-tier plan offering Standard Support and Enterprise Support options with gradual, year-by-year increases offered to companies stepping up to 22% by 2016. The support issue quickly died down after these changes, and SAP started sharing the high adoption-rate figure with each and every quarterly financial report.

Standard Support helps customers keep systems up and running with bug fixes, support and software upgrades. SAP describes it as a reactive, break-fix approach. Enterprise Support promises to be proactive. It includes everything in Standard Support plus best practices guidance for IT operations along with Solution Manager software that monitors systems, identifies baseline performance and helps customers institute best practices for system optimization.

So what more are Standard customers getting now that would justify a 5.5% increase? SAP told analyst Dennis Howlett that "there is ongoing expansion of value, for example a continuous flow of innovation through enhancement Packs while SAP Standard Support is covering a broadening solution portfolio." Enhancement packs are SAP's vehicle for adding new features, functions and upgrades to its Business Suite applications.

What's really at stake here is profits. SAP has a standing promise to shareholders that it will reach 20 billion Euros ($27.1 billion) in revenue and a 35% operating margin by 2015. But last year's SuccessFactors and Ariba acquisitions -- not to mention aggressive hiring to drive Hana and cloud-services sales -- have made it harder to reach that margin goal. SAP's operating margin declined to 25.1% in 2012, down from 34.3% the previous year. Where to make up the difference? Well, support accounted for 8.2 billion Euros ($11.1 billion) -- about half -- of SAP's 16.2 billion Euros ($22.0 billion) in total revenue for 2012.

Support services are highly profitable. Just ask third-party support providers such as Rimini Street and Spinnaker. These are small companies (Rimini had $43 million in revenue in 2012) that pick off a tiny share of customers that typically want to support stable versions of aging software. Rimini's standard pricing approach is to charge half of what Oracle and SAP charge for supporting enterprise applications. A Rimini executive told Howlett that margins for the big OEMs are as high as 90%.

It's hard to introduce price increases without raising objections, but SAP could have been more forthright in handling this one. First, it didn't offer much of an explanation for the price increase in its initial announcement beyond the statement, "In order to ensure the same high level of quality support in the future." That throw-away line just made subsequent statements about "expansion of value" seem like trumped-up afterthoughts. Second, SAP tried to convince me and others that "a relatively small group" will be impacted by this change by pointing to a misleading 95% adoption-rate figure. When pressed, SAP wouldn't say what percentage of all customers are now on Enterprise versus Standard support.

SAP warned customers, back in 2010 when it set up two-tier support, that Standard Support would be subject to increases based on inflation. The company also deserves credit for putting the word out five months in advance and making it clear that customers should renew before July 15 to get 18% deals while they can. But even long-term contracts eventually come to an end. And when that happens, that little 1 percentage point -- the 5.5% hike -- will hit customers, and help fulfill that 2015 promise to the financial markets.



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.