News Stay informed about the latest enterprise technology news and product updates.

CRM horror stories: Obstacles plague Owens Corning, Perseus Development

Two companies share tales of CRM woe in hopes that others don't make the same mistakes. Owens Corning's problems came when projects kept getting derailed and Perseus Development had to rebound from a bad integration decision.

Owens Corning is an archetypal Fortune 500 industrial. Its headquarters lobby on the banks of the Detroit River,...

in Toledo, Ohio, includes a 10-foot-long map of the world with color-coded lights representing the company's dozens of installations around the globe. But in the early 1990s, because of its formidable size, the company's dealings with customers were a mess.

Owens Corning was acquiring a number of smaller companies to expand its product portfolio beyond insulation, a strategy that was creating more points of contact with customers. At around the same time, senior executives were dabbling in another bit of strategic broadening, using the company's well-known Pink Panther icon as the wedge for a new positioning of the company as a home-improvement expert. Unfortunately, all this expansion was creating widely varying levels of service experiences for customers, and often a confusing duplicating of information about a single account in several databases, each of which had been organized around a different product line.

There were different electronic pockets of customer responses that had been collected, says Richard Kaverman, a marketing staff member at Owens Corning through most of the '90s. One was from people who'd called in for roofing products, another for insulation products, and yet another for windows. In some places, Kaverman says, the data storage was as crude as having actual warranty cards that were stuffed in shoeboxes.

The chaotic systems caused problems for some customers that escalated all the way to the chairman, one of Owens Corning's marketing executives from the early '90s said.

At 84 Lumber Co., a big customer for insulation and roofing products, Owens Corning's problems "definitely led to some confusion on our end," says Alex Eadie, director of contract purchasing for 84 Lumber.

"In terms of marketing philosophy," Kaverman says, "[Owens Corning] just wasn't there yet. Rather than having a [sophisticated, data-intensive] approach to marketing, they had this belly-to-belly concept: If you could just get me down in front of this person across a table, that's how I'm going to market."

Owens Corning did possess a strategic advantage that was unusual for an old-line supplier of such mundane goods as shingles and insulation: It had a cadre of young managers who understood the promise of CRM and was pressing to exploit it.

A guerrilla corps of CRM-oriented operatives inside the marketing and information-technology departments had met marketing consultant Martha Rogers at nearby Bowling Green State University and got fellow Owens Corning managers to gather with her and hear her ideas on one-to-one customer relationships and how to manage them. The managers pushed for funding and won approval for some pilot projects, such as one to improve the call center for 1-800-GETPINK, a general direct-response number that ran in the company's television ads.

Still, CRM work was stymied every time it seemed to be building momentum. For example, there was a pilot project to test a CRM model in connection with a new line of roofing products being test-marketed in Portland, Ore., but the project was scotched when Owens Corning quickly decided to roll out the products nationwide. For three years in a row, beginning in 1997, the CRM enthusiasts were told to put together budgets outlining their plans for seven-figure investments in various expansions of the company's customer-relations capabilities. Then the funding would disappear.

"We'd turn in our budgets in July, during the budgeting cycle, and those would get approved. By October, they'd be cut significantly. By January, they'd be cut back so far that we only could operate what already was in existence at the beginning of the [prior] year," Kaverman remembers. "So, by 1999, we'd arrived at the same place with CRM that we were in 1992."

Much of the money that might have gone to CRM was siphoned off into a massive enterprise-resource-planning project that was designed to replace 200 disparate computer systems with a single platform that could support the operations of multiple business units across multiple countries. The seven-year effort cost $280 million.

"You have to have your internal transactions, your base transactions and processes, in place and operating appropriately, effectively, and reliably before you automate anything to the end customer," says David Johns, currently the chief information officer with Owens Corning.

Johns acknowledges that Owens Corning had purchased a CRM system from German software producer SAP AG as part of the enterprise-resource planning package it bought from the software company and could have kicked CRM into action anytime. But "everything was being sunk into core business systems," says Steve Smoot, a former Owens Corning marketing executive. CRM "didn't sink in as a priority at the time."

Johns thinks the CRM advocates "had good intentions" but "got the cart ahead of the horse"—in particular, in wanting to use CRM software to deal with customers over the Internet. The advocates' approach "just would have provided inaccurate data, faster," Johns says. The CRM boosters "thought that the Internet was some sort of magic technology platform that made everything in the back office work perfectly," he says.

Still, Johns concedes that Owens Corning should have focused more on what customers wanted, rather than working only on getting its internal processes right. If he had it to do all over again, "We would have spent more time working with the customer and gone backward from there," Johns says.

John Sviokla, vice chairman of management-consulting firm DiamondCluster International Inc., says Johns is right. "These CRM journeys need to start out by working deeply with customers to discover what is critical to them. This work goes well beyond call-center operations to the design of the whole business. Great firms understand this."

The project to integrate its internal computer systems was a success, and, in the middle of 2001, Owens Corning began a drive to implement a program for dealing with customers on the Web, using SAP software and starting with a new home-handyman service called HomeExperts. But Owens Corning is now operating under the huge handicap of supervision by a U.S. bankruptcy court, where it sought protection from its creditors two years ago amid asbestos litigation. The company also is operating without its would-be CRM pioneers, including Kaverman and Smoot, who became frustrated and left in 1999 and 2000.

"There is no way of measuring what it might have cost Owens Corning by not doing [CRM] for six or seven years," says Rogers, the marketing consultant who encouraged Owens Corning's CRM advocates.

Technology trouble: Perseus Development Corp.

If there is any company that should have grasped the importance of CRM early on, it is Perseus Development Corp. After all, the company was founded nine years ago based on the value of communicating with customers: Its business is formulating and conducting customer surveys for other companies.

The company started out mainly providing survey-writing software for $179, and it quickly acquired a long list of customers, ranging from huge corporations to mom-and-pop outfits such as ophthalmologists' offices and college professors who polled students on their performance at the end of the semester.

Yet everybody at Perseus was so busy designing the next version of the software and expanding sales that nobody even transferred customer-registration information into something as basic as a contact-management program, admits Jeff Henning, co-founder and chief operating officer. "We were getting data spit back to us, but we weren't doing anything with them," recalls Scott Washburn, former head of marketing who left closely held Perseus in early 2002 to become a marketing consultant for Tusk Creative Group.

By 1999, Henning and others realized that Perseus simply had to keep better track of its customers and that, by allowing them virtually no way to interact except with its technical-support department, the company was missing out on many growth opportunities, such as the chance to sell extra software licenses to people calling in with unrelated questions. So Henning and Perseus co-founder and Chief Executive Richard Nadler decided to purchase a Clientele CRM module from Epicor Software Corp.

Incredibly, however, Nadler and Henning didn't take Epicor up on its proposal to fully integrate Clientele with Perseus's existing information systems at a cost of no more than another $20,000—despite Washburn's strong recommendation to do so. "We thought their product was easy enough that it wouldn't be difficult for us to integrate, because we didn't have a pre-existing CRM system that we had to work around—and we were a software-development shop," Henning remembers. "We felt at the day rate they would be charging to do it, we could get it done ourselves."

Right away, the technical-support manager Perseus assigned to integrate Clientele "began hitting walls," Henning says. For example, in allowing the Perseus sales force to place orders electronically, he couldn't reconcile Perseus's existing forms with the new forms called for by Clientele. Several more months went by, and Perseus's employees still were no more able to interact knowledgeably with customers than they had been before Clientele was installed. In the meantime, some of Perseus's competitors were raising the bar by completing their own, more successful CRM projects.

Each week, frustrated marketing staffers ended up manually pulling names in alphabetically organized batches out of Perseus's database of several thousand customers to e-mail them messages, such as reminders that their 30-day free trials were expiring. When customers reached Perseus, technical-support staffers didn't even have simple data points in front of them, such as the fact that the client would need to be upgrading its software soon. "Or it would take us a long time to answer a simple question such as how many licenses did they have or what was the status of an order," Henning says. "Sometimes it took a couple of days."

The recession in 2001 cooled activity at Perseus just enough so that Henning could collect his thoughts and hire an internal data manager, John Bowens, who is teaching Perseus to utilize the CRM system installed two years ago. This year, Perseus just missed Inc. magazine's list of America's 500 fastest-growing companies, at No. 520. "If we'd had our act together on CRM," Henning concludes, "we would have made that list a long time ago."

Washburn, the former marketing executive, says: "Revenue could have been 30% higher each year for the last two years."

This story originally appeared in Context magazine.

Dig Deeper on CRM strategy and implementation

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.