Financial analysts are in a small funk because Oracle’s earnings were not as spectacular as they’d have liked. Actually, the revenue numbers were fine; they beat the street estimates of $9.57 billion for the just completed Q2 2018 with revenues of $9.63 billion. The cause of the consternation was a relatively weak cloud growth rate of “only” 44 percent after posting 51 percent growth in the prior quarter. That’s a downward trend and thus the consternation. What explains this?
Let’s focus on human nature. Financial analysts look for eye-pleasing graphics and numbers that tell wonderful stories of increase. But the reality is always more complicated. Orders don’t ship, customer CTOs get cold feet, CEOs find new bright and shiny objects to pursue. Stuff happens. As a result, often a vendor’s numbers don’t’ look as impressive as we’d like.
One specific area of concern for Oracle has been the speed at which the market is adopting its IaaS and PaaS (infrastructure and platform) product lines. The SaaS line seems to be good. Oracle sold $1.1 billion of SaaS in Q2 making it one of the biggest SaaS companies on the planet. But it’s still struggling with infrastructure and platform which combined brought in “only” $396 million in the quarter.
The SaaS business seems to be new deals won the old fashion way. But it takes more effort to grow the other two because much of the increase is logically expected to come from Oracle’s customer base. Analysts are expecting existing customers to swarm in to the new offerings but they seem to be taking their time. The maxim, if it ain’t broke, don’t fix it comes to mind.
Most enterprises have a huge investment in hardware and software, which they are naturally reluctant to discard. So while Oracle’s offer to let them migrate their existing licenses to the cloud in a program called BYOL or bring your own license, that offer is not sweet enough for many businesses with gear they’re still writing off.
At this rate it will take more than the efficiencies from better infrastructure to motivate many businesses to move, hence the disappointing numbers. But to be a bit more realistic, customers are moving to the cloud—$396 million is far from nothing. But it’s going to take more time than the optimists thought to get the migration moving at a faster clip.
At this point there are many things Oracle can do. First, it should count and publish the numbers of businesses coming to their infrastructure. This will likely represent customers gaining a toehold in the cloud. They’ll bring one application or department to the cloud as an experiment and Oracle should pay attention to this because it’s one sure method of growth.
Even if the revenue numbers are small the absolute number of businesses going to the cloud, even if only partially, will strongly suggest future acceleration. For all we know such information is already embedded in the $396 million Oracle already reported. Second, Oracle can sell platform. They do this already but perhaps some effort more squarely aimed at the small developer groups that just need a sandbox. That’s where early growth often comes from. Those groups are often oriented to Microsoft products running on AWS so the strategy works well in two directions. Lastly, when all else fails, the financial analysts could always try being a bit more patient.
My 2 bits
Moving to the cloud is an arduous event for any company. It calls for managers to tinker with the secret sauce, something they loathe. So it’s no surprise to me that moving is a slow process and that despite having all of the bells and whistles ready to go, Oracle is still in early market hurry up and wait mode. It can’t be helped—no vendor can expect to sell anything until it produces the whole product. Oracle CEO Mark Hurd is famous for saying they’ve built a skyscraper but couldn’t start renting units until the building was finished. That’s the time when financial backers begin asking about revenues.
But it takes more time than we care to admit to make a cloud. Oracle is showing some promising signs of early adoption but the situation still calls for patience.
Patience? What’s that?
(Cross-posted @ Beagle Research Group)