How To Protect Maintenance Revenues During the Recession
The recession is upon us and from all reports it looks as though it is going to be a long one. I will leave to others to discuss and argue if the current proposed stimulus package is indeed a real stimulus package or just a spending bill that will do little to nothing in the short term. In my practice I am beginning to receive an inordinate number of requests from software licensee’s to either cancel maintenance or reduce user counts in an effort to lessen the annual expense. Chris Dowse and Ben Galison have written a very important Op-Ed piece for SandHill.com entitled Software’s Clear and Present Danger. They begin their article with a no nonsense approach to the subject of maintenance revenues:
“… the software industry’s cash cow, maintenance and support revenue provides high margins that are the funding engine for new product research and development. The maintenance revenue stream is also used as a basis for company valuations in mergers and acquisitions and financing arrangements.”
Dowse and Galison have identified three major reasons placing downward pressure on the maintenance stream:
1. The customer’s perception of value has affected pricing, the basis for the maintenance calculation.
2. The recession has caused customers to postpone purchases and upgrades.
3. End User Monitoring (“EUM”) has created a new view into usage and so under-used applications are being targeted as a drain on ROI.
The approach that Dowse and Galison suggest as a remedy to the threat on the maintenance stream might seem simplistic at first blush. They suggest the Independent Software Vendor (“ISV”) become more customer-centric and strive to have a successful adoption of the software suite as opposed to the traditional implementation services. I suggest you read further and examine their three step approach and follow it in the sequence they suggest. It may be a bit of a paradigm shift for some ISVs, but at the very least it will take a lot of effort. I will try to summarize the three step approach, but please read their whole article to get the full impact. The three step approach is as follows:
1. Create a Positive Customer Experience: This enhances customer loyalty which is the first step in protecting the maintenance stream. However, more importantly, Support and Services must concentrate on an effective adoption of the applications. A significantly improved customer interaction of the delivered applications can have a direct and positive impact on the customer’s ROI. This should also eliminate the fragmentation that occurs when their customer information gets locked in silos. An effective adoption of the software suite should enable delivery of this customer information across the enterprise. The ISV must encourage cross-functional dialog and empower their employees to identify their Customer problems.
2. Understand Customer Usage: This has to be a proactive approach, hence my comment above that “at the very least it will take a lot of effort”. The ISV must strive to understand usage patterns and barriers to adoption. This is where the ISV should take advantage of the new EUM technology and use it to get past the reasons for downward pressure on maintenance. Once usage rates are indentified the ISV should intervene with perhaps more training or services. This activity could lead to new products and services to increase usage and eventually ROI.
3. Deliver Business Value, Not Just Technical Service: Customers want and will pay for services that will lead to effective adoption. Traditional implementation services do not go far enough. Placing the focus on user adoption yields tremendous benefits. Dowse and Galison state it best: “Effective user adoption increases customer switching costs, enables value-based pricing that prevents price erosion, produces visible ROI for customer success stories to drive other sales, and provides a platform for upselling and cross-selling.” Another by-product of this approach is a lower amount of the lower margin traditional implementation services required. The ISV’s service profitability should go up.
For another perspective on this topic see my November 24, 2008 post in this Blog: How to increase revenue in an Economic Downturn.
