Why Chiquita Said 'No' to Tier 1 ERP Providers and 'Yes' to SaaS Apps from Upstart Workday

The inside story of why Chiquita Brands CIO Manjit Singh ignored the SaaS FUD from the world's leading ERP vendors and, instead, chose an on-demand HR platform from upstart Workday to roll out to its global operations. The lesson: A bigger software vendor doesn't always equal a better ERP deal.

By Thomas Wailgum
Tue, April 07, 2009
Page 2

With the requirements in hand and vendors at the ready, Singh suffered some sticker shock. "Very rapidly we came to the conclusion that the amount of capital required to invest in those systems was going to be prohibitive to us," Singh says. "We'd rather divert that amount of capital into our transformational product sets instead of spending it on IT or HR."

Into the vendor discussions soon entered Workday, the on-demand ERP vendor cofounded by Dave Duffield, who had himself founded ERP juggernaut PeopleSoft in 1987. "Obviously, Workday had a great pedigree," Singh says of his first impressions. (Workday's other founder is Aneel Bhusri, who had been at PeopleSoft since 1993. For a profile of Workday, see "Can Two Legacy ERP Guys Get IT Executives to Buy into On-Demand Applications?")

Duffield was well aware of the competition. The plan he and Bhusri constructed in order to win the deal involved three things, he says via e-mail: "Demonstrating we could deliver a modern solution that would support their global HR operation; establishing a SaaS model that delivered significant cost savings; and then building a trusted partnership between our organizations."

"Going with a Startup Is Always a Little Bit of a Risk"

Chiquita would be, by far, Workday's largest implementation to date. Chiquita had dipped its toes in some SaaS applications, Singh says, but "we were not very adept when we started this process." Therefore, Singh and the senior management team had plenty of questions for Workday, beyond what they would have asked a Tier 1 on-premise vendor, such as about the vendor's application roadmaps, multiple language capabilities and customization options.

One of the long-standing hesitations around adopting SaaS-based ERP apps concerns storing critical corporate data offsite. This actually wasn't an issue for Singh, since his data centers are already outsourced. Next up was whether Workday had the capabilities to support Chiquita's global operations. "The established players had solutions that had existed for many years and had built out various localization modules," Singh says. "Would Workday have a development path that would meet our own internal time table for deployment?"

Then, there were the important "viability of the vendor" risk-management discussions, Singh says. "Going with a startup is always a little bit of a risk." First, what if Workday's growth exploded and Chiquita "was no longer a big fish in a small pond," Singh says. "Would we continue to get the attention and the resources?" On the flip side, of course, was what if Workday went belly up: What would be the implication for Chiquita's internal processes that were now tied to a solution that didn't exist anymore? In addition, would Chiquita be able to get its HR data back and make it usable again?

Workday's Duffield and Bhusri went to work in the latter half of 2007 to prove their product's mettle to Chiquita. Says Duffield: "Aneel and I personally spent a lot of time working with the Chiquita team to build that relationship."

ERP + SaaS = Successful Enterprise Strategy or Bad Plan?

When CIO magazine surveyed 400 IT leaders about their ERP systems in late 2007, CIOs said they remained committed to on-premise, traditional ERP systems—despite aggravating integration and high-cost headaches.

The results weren't that surprising. CIOs have been reluctant to take chances storing the sensitive data (accounting, HR, supply chain) contained in their ERP systems in another company's data center. In the survey, just 9 percent of respondents reported using an alternative ERP model, which included SaaS applications. SaaS has also suffered from a perception that it's "for SMBs only."

Not even two years later, things have changed considerably. SaaS ERP providers such as Workday and NetSuite have experienced greater acceptance of their house-your-ERP-data-offsite models, which in turn has allowed them to go from upstarts to viable industry players.

And enterprise giants have rolled out SaaS apps with increasing regularity. General Electric, for example, implemented a SaaS supply chain application from a relatively unknown vendor in GE's global supplier network: 500,000 suppliers in more than 100 countries that cut across 14 different languages. (See "GE CIO Gets His Head in the Cloud for New SaaS Supply Chain App.")

Ray Wang, VP and principal analyst at Forrester Research, says that market research and anecdotal conversations with Forrester clients demonstrate that many more companies—and most importantly, of all sizes—are open to going with SaaS vendors and applications. "The SaaS stigma has already changed," he says, "because the areas where companies are looking for innovation and not getting that from their existing vendors—like incentive compensation, talent management, e-recruitment—those are the areas where SaaS has proven itself in terms of delivering innovation."

SaaS has also become attractive to companies facing massive and expensive upgrades to their ERP systems. "For some people who didn't stay current on upgrades, the decision to move to the next release or the next version is almost the same [price] as doing a replacement," Wang points out. "And the cost of doing that makes it very comparable."

Selling ERP F.U.D.

Since Duffield and Bhusri founded Workday in January 2005, they've never missed a chance to bash the traditional ERP model that had enriched them so much, while propping up their new SaaS model. What traditional ERP vendors don't provide and what Workday does offer, Duffield contends, is a model that delivers modern capabilities at a fraction of what organizations currently spend on HR or financials.

Continue Reading

Our Commenting Policies