Software maintenance

via Judith Hurwitz

Judith is bringing, as usual, interesting feeds for thoughts, this time in the field of software maintenance fees.

[…] As the world slowly moves to cloud computing for economic reasons there will be a major impact on how companies pay for software. Salesforce.com has indeed proven that companies are willing to trust their sales and customer data to a Software as a Service vendor. These customers are also willing to pay per user or per company yearly fees to rent software. Does this mean that they are no longer paying maintance fees? My answer would be no. It is all about accounting and economics. Clearly, Salesforce.com spends a lot of money adding functionality to its application and someone pays for that. So, what part of that monthly or yearly per user fee is allocated to maintaining the application? Who knows? And I am sure that it is not one of those statistics that Salesforce.com or any other Software as a Service or any Platform as a Service vendor is going to publish. Why? Because these companies don’t think of themselves as traditional software companies. They don’t expect that anyone will ever own a copy of their code.

The bottom line is that software will never be good enough to never need maintenance. Software vendors — whether they sell perpetual licenses or Software as a Service– will continue to charge for maintance. The reality is that the concrete idea of the maintenance fee will evolve over time. Customers will pay it but they probably won’t see it on their bills. Nevertheless, the impact on traditional software companies will be dramatic over time and a lot of these companies will have to rethink their strategies. Many software companies have become increasingly dependent on maintenance revenue to keep revenue growing. I think that Marc Benioff has started a conversation that will spark a debate that could have wide ranging implications for the future of not only maintenance but of what we think of as software.

Interesting!

Cross-posted on the Innoveo Blog.

Leave a Reply