Rimini Street’s new model?
Salesforce’s embrace of Rimini Street’s third-party support services is a significant departure that has transformed the support vendor from competitor to partner—at least with Salesforce. It might also offer insight into changing cloud business models. At least it helps to make sense of recent litigation involving Rimini and Oracle.
Rimini Street began life as a support vendor for enterprises running Oracle and SAP software in the traditional on-premise model. In this incarnation Rimini quickly and inevitably became a direct competitor taking support revenue from enterprise vendors. Competing for support revenue is legitimate provided the third-party vendor conducts itself lawfully, respecting patents and copyrights to intellectual property concerning the systems being supported. The third-party also has to grapple with providing patches and updates that an OEM can provide.
Typically, enterprise software vendors charge a flat percentage of the licensed software fee for support services. Regardless of the terms of the deal a business strikes with a vendor over the software purchase, the services fee is almost always calculated on the list price; so with fees around 20 percent an enterprise can end up re-buying the product every five years or so.
To be fair, there’s a significant cost built into providing service and support which includes on-going R&D, patches, updates, fixes, and bulletins, as well as live support based on a service level agreement of SLA. Customers are always trying to get a better deal and vendors need to hold the line on pricing to cover their costs and generate a profit, which is the point after all.
Third parties have a lower bar—since they don’t write the original software or upgrades their overhead is lower. But that’s the point. They don’t own the source code and so they can’t patch it, a key reason for buying support in the first place.
Rimini has announced what we can call “patches to patching” which it named holistic and virtual patching. But each of these ideas works several levels of abstraction above the source code never actually patching it. The result is that systems are still in jeopardy. So the basic low cost inducement of third-party support vendors is in some cases, specious. They charge less but they also deliver less and the difference can leave an enterprise vulnerable to hacking, and down stream effects like brand erosion and lost trust and lost revenue.
Oracle has had a long simmering law suit against Rimini, which exhausted the appeals process recently. In the verdict, Rimini was shown to have “borrowed” materials from Oracle by simply downloading them from support sites.
After Rimini lost on appeal, it issued a strange statement that was carried in the UK Register and elsewhere saying,
“The Court of Appeals, while affirming the jury’s finding of ‘innocent’ copyright infringement for processes that Rimini Street claims are no longer in use since at least July 2014, stated that Rimini Street‘ provided third – party support for Oracle’s enterprise software, in lawful competition with Oracle’s direct maintenance services,”
Which roughly translates as, we did nothing wrong and we won’t do it again.
It’s quite hard to provide in-depth support if you don’t have inside knowledge of how systems work and don’t have the source code which you need to make a patch. Oracle’s case revolved around Rimini Street’s appropriation of copyrighted support materials produced by Oracle. Specifically, the enterprise vendor accused Rimini of violating up to 93 copyrights on its support and materials and the judgements, including appeals, went against Rimini though some monetary awards were later reduced.
A new model
Since the rulings and fines, Rimini has been seeking a better way to do business and it may have found it with Salesforce. If so, it could be a new model for other cloud vendors as well.
Rimini provides 24/7/365 support for selected Salesforce applications, which now include Salesforce Sales Cloud and Service Cloud, with 15 minute response time. Salesforce and other cloud vendors offer services for their products too but generally customers have to pay more for the advanced features that Rimini provides standard. So the competition is between Rimini and, in this case, Salesforce’s advanced support services, a choice that customers are free to make. Judging by the announcement of the services, Salesforce is in favor of the arrangement and views Rimini as a partner.
Here’s why. Rimini Street CEO Seth Ravin recently told ZDNet,
“The SaaS world is different in that maintenance is included in licenses and mostly bare bones.”
Simply put, there’s more room in a cloud situation for Rimini to add value.
Let’s separate call center service from updates and patches. Only Salesforce patches its products and it does so whenever needed as well as with three annual updates. So, the thorny issue of third-party patching is off the table in the Salesforce model. No patching requirement makes it much less likely that Rimini or anyone else will need to do the things that Rimini was found guilty of in the Oracle case.
With a cloud business model a vendor builds support costs into the monthly fee and that includes further product development and enhancement as well as some amount of live support but the cloud vendor gets paid no matter what. There’s no haggling over service fees—either the customer buys what the OEM has or goes to a third-party and pays there. As a result it’s far easier for Rimini to be seen as a partner by a cloud vendor, than as a competitor.
So the difference in how support is delivered and paid for may turn out to be a significant additional inducement to legacy customers contemplating a move to the cloud. In any event, it is reasonable to conclude that the on-premise version of service and support may be going away.
At some point companies like Oracle might begin to view third-party support service providers more as partners than competitors just as Salesforce does. But the change won’t be quick or uniform. Oracle’s bevy of cloud products still have numerous configurations that enable customers to straddle cloud and on-premise positions with different support modalities. For instance, Oracle’s BYOL, Bring Your Own License, program enables customers to move an on-premise app to Oracle’s infrastructure cloud (IaaS). So, the application retains its legacy character, and presumably its support liability, even though it runs in the cloud.
Deploying a modern, cloud version of the app might remove the annual support bill but at the cost of an incremental SaaS fee by the month or contract year.
Few enterprises will decide about moving to the cloud over the cost of application support alone. The move involves a complex matrix of costs for hardware and software—including everything in the stack. There are also considerations for labor. Given Oracle’s new push into automated products in database, security, integration and other areas we can expect cost savings for some premise-based systems but that remains to be seen.
Oracle is making its customers’ move to the cloud as cost effective as it knows how and it’s likely that early movers will get the best deals. Something else to consider for the vast majority of Oracle’s customer base with its feet planted firmly on the ground.