Enterprise System Spectator blog: ERP and enterprise system vendor evaluation, selection, and implementation.

The Enterprise System Spectator

Saturday, February 05, 2005

High software maintenance fees and what to do about them

There's an interesting side note to Oracle's takeover of PeopleSoft: it turned out that PeopleSoft's software maintenance business was even more profitable than Oracle realized. Once Oracle found out how much money PeopleSoft was making on its recurring maintenance business, it justified a sweetened offer that closed the deal.

If you're a corporate buyer of software, you might want to take a look at what you're paying for software maintenance.

What is software maintenance?
Maintenance fees pay for two services from the vendor to the customer. First, they pay for ongoing product development that provides new product features, regulatory updates (e.g. tax table updates), and bug fixes. (That's right. You pay for the software, and then you pay the vendor to fix defects in it.) Second, maintenance fees pay for phone and Web-based support for times when you need help with the system.

One little secret of the software industry: the maintenance business is really profitable for vendors. It's somewhat analogous to the situation when you shop for a big screen TV at Circuit City. You may be impressed with the terrific bargain you're getting on the sales price. But when you go to sign the deal, there's a lot of pressure for you to sign up for the extended warranty--where the store, and the salesman, make most or all of their profit. Buying enterprise software is similar, with the key difference being that you don't really have the option to forgo the maintenance contract.

I've long thought that software buyers are too focused on the up front license price and not paying attention to how much they are paying on the back end--in software maintenance fees. Buyers forget that when they pay a dollar for a software license, they pay that dollar once. But when they pay a dollar on software maintenance fees, they pay that dollar again and again, year after year, as long as they stay on maintenance. Over the life of the system, most customers pay far more in maintenance fees than they ever pay in up front license fees.

Software vendors understand this, and as new sales continue to be hard to come by, they are turning their attention to increasing revenues from their maintenance business.

Vendor tactics
Vendors are working to increase maintenance revenue in two ways. First, they are increasing maintenance fees directly. A few years ago, 15-18% of the software license fee was a typical benchmark. Now, I'm seeing vendors quoting 20% or even more. It might not sound like much, but run the numbers out three or four years and see the impact. On a $500,000 license deal, a five percent difference in maintenance fees is $125,000 over five years. That's like a price increase of 25% (not factoring in the cost of money, of course).

Second, vendors are tightening enforcement of existing agreements. In the past, vendors might not aggressively pursue customers that exceeded user counts, which usually form the basis for software pricing. Today, it's no more Mr. Nice Guy. Vendors are enforcing their contractual rights to audit customer usage of the software and are charging customers license fees for additional seats, plus the maintenance fees on those seats.

Balance of power
Why are vendors squeezing customers? First, it's a sign that, although we're not returning to the heyday of tech spending in the 1990s, business is improving. Vendors are finding that they don't need to make as many concessions as they have in the past. And, as we just saw, the easiest way to increase revenue is through maintenance fees.

But more significantly, vendors are increasing maintenance revenue because they can. Implementing an enterprise-wide system is a huge undertaking for most companies. Few customers are going to select a new system and go through the pain, risk, and expense of another implementation just because they are paying a bit more in maintenance fees than they had planned on. Customers are a captive audience--to a point.

My feeling is that if vendors continue along this path, there's going to be a backlash. There's a limit to what the market will bear, and I think some vendors are starting to reach that limit. A study by AMR last year found that because of maintenance policies, 22% of customers are considering switching vendors, 21% intend to stop taking upgrades, and 12% will discontinue paying maintenance.

Practical tips
If you are concerned about high software maintenance costs, there are several steps you can take to keep costs in line.

If you have not yet purchased the system, understand that your negotiating power will never be greater than before you sign on the dotted line. Maintenance fees as a percent of the license cost are not cast in stone. Everything is negotiable. For example, ask for a lower percentage. Ask for maintenance fees to be based on the discounted price of the software, not the list price. Ask for maintenance fees to be locked in, not allowing the vendor to increase fees from year to year.

Furthermore, don't buy software you don't need, even if the vendor offers a tremendous discount on additional modules. There's no free lunch. If the vendor is charging maintenance fees based on the list price of those modules, you'll likely be paying for software that you won't implement. If you think you'll implement it later, buy it later. That will encourage the vendor to be sure you're successful with the modules that you do buy.

If you are already a customer, your negotiating power may be diminished, but you still have options. First, check whether you are using all of the modules you purchased. If not, consider canceling maintenance on the modules you aren't using. Second, look hard at whether you are using all of the user seats that you originally purchased. Vendors will tell you if you exceed your user count but probably won't let you know if you have excess seats. Finally, if you plan on buying additional software from the same vendor, see whether you can negotiate a better deal on your existing modules in exchange for buying additional modules.

If your vendor is still not showing flexibility, consider whether more hardball tactics are warranted. Third party maintenance and service providers, offering lower fees, are one alternative. Canceling maintenance ("going naked") for older or less critical systems might be another alternative, especially if you seldom use the help desk and are not planning to upgrade in the future.

Then there's always the nuclear option: looking to other software providers. For some applications, open source software might be an alternative, with maintenance either provided in-house or through a third party.

Computerworld has more on trends in software maintenance. CFO magazine has further analysis of what vendors are doing to squeeze more revenues from existing customers.

Related posts
Customers pushing back against enterprise software maintenance fees
Software customers learn to just say no
Customers pushing back against Microsoft licensing program
Customers to Microsoft Licensing 6: thanks, but no thanks
SAP to provide maintenance for PeopleSoft products
Microsoft Software Assurance: no bang for big bucks
Software buyers turn cheap

by Frank Scavo, 2/05/2005 09:22:00 AM | permalink | e-mail this!

 Reader Comments:

Frank,
While maintenance and support can be highly profitable for companies over critical mass and large enterprise software vendors, there are thousands of small and up and coming vendors who rely on these revenues to continue to improve their products. Often these vendors, due to their size, are the ones squeezed from both ends. Buyers squeeze them on price then expect the maintenance fee% to hold or even be reduced while then being applied to the net license fee. Commentary such as this spurs them on to believing the situation you describe is true of all software vendors. Cut the small guys some slack - plenty of value is often delivered for the resonable fees charged by many software companies.
Paul Lavallee
CEO
www.VentureFuel.com
 
Frank,
Have you ever run a small software product company and seen how hard it is for niche software product makers to survive. Your commentary does encourage large enterprises to squeeze those people it can...not the Ciscos of the world, but the small companies. We personally believe in leasing and not licensing and charge very low fees each year...period! Yet our customers want to lower the upfront cost and yet pay only 20% of even the lease. The same software would cost the company more than twice as much to develop or maintain internally. Your commentary is totally lopsided and unfair.

Aparajit Agarwal
President
TrendWorks Data Analytics, Inc.
 
I am a software executive and I've been seeing an interesting trend towards boilerplate contracts with large end users quoting "12%" and mandating that with their vendors.

Normally I charge 20%, and for that 20%, I have 3-4 feature releases per year --- a very aggressive schedule, but one that delivers high value to my customers and speed-to-market for new business opportunities.

So to me, 12% vs 20% is fine. I just re-jig the contract to load the license with the difference in cost over five years, and I get more upfront rather than giving the option for the customer to spread the TCO over a longer period. It actually works to their disadvantage, but if they want to be inflexible about the 12%, I can make that work too.

You see, there is EBITDA for the company to consider. We price our products fairly, and we're industry-average for our profit line, which says that we're not taking any more than we deserve.

There may be companies taking more from the customer, but for the most part, companies aren't able to make enormous profits over and above their competitors. The marketplace abhors anomalies and creates competition to control outrageous profit.

There may be near-monopoly situations where that is possible (e.g., Oracle, Microsoft) but for non-monolithic vendors, your premise is generally false. By definition, smaller vendors HAVE to offer more value for the dollar otherwise they can't break open new markets in the first place.

Sorry for the anonymity, but my marketing folks would kill me if I slap my name on this.
 
To the previous commenter, thanks for the feedback. I am a big believer in the free market and agree with you that software vendors have the right to charge whatever they want. If the price they charge is out of line with the value they deliver, they will be at a competitive disadvantage.

But...that doesn't mean that customers shouldn't look for ways to lower software maintenance costs. You'll notice this was a 2005 post of mine, and there has been a lot of water under the bridge since then. The problem of software maintenance cost versus value has only gotten more pronounced since then, as you know, with some vendors.

The other problem, which I only touch on briefly in this post, is the issue/rights for third-parties to offer maintenance. I believe there needs to be a robust third-party maintenance industry to support the products of some large dominant vendors in order to restore some competition to the market place. It may take some anti-trust rulings to make this happen, similar to the IBM ruling back in the 70s that forced IBM to unbundle the OS from the hardware and led to the IBM plug-compatible industry (Amdahl et al).
 
Post a Comment
 

Links to this post:


 

Powered by Blogger

(c) 2002-2016, Frank Scavo.

Independent analysis of issues and trends in enterprise applications software and the strengths, weaknesses, advantages, and disadvantages of the vendors that provide them.

About the Enterprise System Spectator.

Frank Scavo Send tips, rumors, gossip, and feedback to Frank Scavo, at .

I'm interested in hearing about best practices, lessons learned, horror stories, and case studies of success or failure.

Selecting a new enterprise system can be a difficult decision. My consulting firm, Strativa, offers assistance that is independent and unbiased. For information on how we can help your organization make and carry out these decisions, write to me.

My IT research firm, Computer Economics provides metrics for IT management, such as IT spending and staffing benchmarks, ROI/TCO studies, outsourcing statistics, and more.


Go to latest postings


Search the Spectator!
Join over 1,700 subscribers on the Spectator email list!
Max. 1-2 times/month.
Easy one-click to unsubscribe anytime.

Follow me on Twitter
My RSS feed RSS News Feed

Computer Economics
ERP Support Staffing Ratios
Outsourcing Statistics
IT Spending and Staffing Benchmarks
IT Staffing Ratios
IT Management Best Practices
Worldwide Technology Trends
IT Salary Report

Get these headlines on your site, free!


Awards

2014 Best Independent ERP Blog - Winner

2013 Best ERP Writer - Winner

Alltop. We're kind of a big deal.
 
Constant Contact 2010 All Star Technobabble Top 100 Analyst Blogs


Key References
Strativa: Business strategy consulting, strategic planning
Strativa: IT strategy consulting
Strativa: Business process improvement, process mapping, consultants
Strativa: IT due diligence
Strativa: ERP software selection consulting and vendor evaluation
Strativa: CRM software selection consulting and vendor evaluation
Strativa: Project management consulting, change management
StreetWolf: Digital creative studio specializing in web, mobile and social applications
Enterprise IT News: diginomica


Spectator Archives
May 2002
June 2002
July 2002
August 2002
September 2002
October 2002
November 2002
December 2002
January 2003
February 2003
March 2003
April 2003
May 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
July 2008
August 2008
September 2008
October 2008
November 2008
December 2008
January 2009
February 2009
March 2009
April 2009
May 2009
June 2009
July 2009
August 2009
September 2009
October 2009
November 2009
December 2009
January 2010
February 2010
March 2010
April 2010
June 2010
July 2010
August 2010
September 2010
October 2010
November 2010
December 2010
January 2011
February 2011
March 2011
April 2011
May 2011
July 2011
August 2011
September 2011
October 2011
November 2011
December 2011
January 2012
February 2012
March 2012
April 2012
May 2012
June 2012
July 2012
September 2012
October 2012
December 2012
January 2013
February 2013
March 2013
May 2013
June 2013
July 2013
September 2013
October 2013
December 2013
January 2014
February 2014
March 2014
April 2014
May 2014
June 2014
July 2014
August 2014
September 2014
October 2014
November 2014
December 2014
February 2015
March 2015
April 2015
May 2015
June 2015
July 2015
September 2015
October 2015
November 2015
February 2016
May 2016
June 2016
July 2016
August 2016
September 2016
October 2016
Latest postings