Integrating the value of salespeople and systems: Adapting the benefits dependency network

Business-to-business (B2B) companies invest in customer relationship management (CRM), integrated with sales force automation (SFA) to achieve a return on investment, through improved sales force productivity, sales revenue, costs, customer satisfaction, process accuracy and customer knowledge. However, the devil is in the detail. CRM and SFA are multi-faceted. There are two main obstacles to successful implementation. One is the need for the customer to get some benefit out of the system; the other is ensuring that employees who are expected to use the system actually buy-in to its benefits, including what benefit they will gain as individuals. However, much planning is needed to manage the risks involved. The ‘benefits dependency network’ (BDN),1 designed to develop routes to successful implementation of IT, has been tested in CRM projects. The factors for success in CRM implementation in B2B companies, where the sales force must be involved, are many and varied, including proactive sales management, creating champions, consultation, training, incentives and culture change. Practicalities such as incremental application of the technology and a wide portfolio of metrics to monitor progress are also critical. In the light of the special considerations of sales force involvement, the authors propose an adaptation of the BDN to suggest a generic map for the implementation of CRM (with SFA) in B2B markets. This paper is based on the authors’ secondary research for two commercial sponsors in the utilities sector, supplemented by the authors’ extensive experience of working in this area.

[1]  Darrell K. Rigby,et al.  Avoid the four perils of CRM. , 2002, Harvard business review.

[2]  Edward Hess,et al.  The search for organic growth , 2006 .

[3]  M. Stone,et al.  What makes for CRM system success — Or failure? , 2008 .

[4]  Neil Rackham,et al.  Rethinking the Sales Force: Redefining Selling to Create and Capture Customer Value , 1999 .

[5]  C. Speier,et al.  The Hidden Minefields in the Adoption of Sales Force Automation Technologies , 2002 .

[6]  Ian Corner,et al.  Monitoring qualitative aspects of CRM implementation: The essential dimension of mangement responsibility for employee involvement and acceptance , 2005 .

[7]  Merlin Stone,et al.  Managing the quality and completeness of customer data , 2002 .

[8]  M. Stone,et al.  Degrees of separation: technological interactivity and account management , 2007 .

[9]  Christopher Bull,et al.  Strategic issues in customer relationship management (CRM) implementation , 2003, Bus. Process. Manag. J..

[10]  Sid L. Huff,et al.  An Examination of Customer Relationship Management (CRM) Technology Adoption and its Impact on Business-to-Business Customer Relationships , 2007 .

[11]  Earl D. Honeycutt,et al.  Impediments to sales force automation , 2005 .

[12]  H. Wilson,et al.  Justifying CRM projects in a business-to-business context: the potential of the Benefits Dependency Network , 2007 .

[13]  Ing-Long Wu,et al.  A hybrid technology acceptance approach for exploring e-CRM adoption in organizations , 2005, Behav. Inf. Technol..

[14]  Greg W. Marshall,et al.  Sales force use of technology: antecedents to technology acceptance , 2005 .

[15]  Todd J. Arnold,et al.  A Compendium of Sales-Related Literature in Customer Relationship Management: Processes and Technologies with Managerial Implications , 2005 .

[16]  Sholom M. Weiss,et al.  Analytics-driven solutions for customer targeting and sales-force allocation , 2007, IBM Syst. J..

[17]  Roger Elvin,et al.  A new framework for managing IT‐enabled business change , 1999, Inf. Syst. J..

[18]  Pushkala Raman,et al.  Leveraging CRM for Sales: The Role of Organizational Capabilities in Successful CRM Implementation , 2006 .

[19]  D. Pujari Self‐service with a smile?: Self‐service technology (SST) encounters among Canadian business‐to‐business , 2004 .

[20]  David C. Yen,et al.  Customer Relationship Management: An Analysis Framework and Implementation Strategies , 2001, J. Comput. Inf. Syst..

[21]  Wynne W. Chin,et al.  Factors Leading to Sales Force Automation Use: A Longitudinal Analysis , 2002 .

[22]  Fred D. Davis,et al.  A Theoretical Extension of the Technology Acceptance Model: Four Longitudinal Field Studies , 2000, Management Science.

[23]  Merlin Stone,et al.  The quality of customer information management in customer life cycle management , 2003 .

[24]  Andrew D. Brown Implementing MRPII: Leadership, Rites and Cognitive Change , 1994 .

[25]  Rolph E. Anderson,et al.  Customer Relationship Management: Its Dimensions and Effect on Customer Outcomes , 2004 .

[26]  Pj Smoot Coming Up Short on Nonfinancial Performance Measurement , 2004 .

[27]  Lynette Ryals,et al.  Using Real Options to Help Build the Business Case for CRM Investment , 2005 .

[28]  Anne P. Massey,et al.  Re-engineering the customer relationship: leveraging knowledge assets at IBM , 2001, Decis. Support Syst..

[29]  Merlin Stone Improving Marketing Effectiveness , 1999 .

[30]  Bernd H. Schmitt,et al.  Customer Experience Management , 2009 .

[31]  Christina Pries,et al.  Managing CRM implementation with consultants—CRM or change management? , 2004 .

[32]  M. Gibbert,et al.  Five Styles of Customer Knowledge Management, and How Smart Companies Use Them To Create Value , 2002 .

[33]  Niels Schillewaert,et al.  Why Sales Reps Should Welcome Information Technology: Measuring the Impact of CRM-Based IT on Sales Effectiveness , 2007 .

[34]  Ganaël Bascoul,et al.  Effects of Sales Force Automation use on Sales Force Activities and Customer Relationship Management Processes , 2008 .

[35]  Fred D. Davis Perceived Usefulness, Perceived Ease of Use, and User Acceptance of Information Technology , 1989, MIS Q..

[36]  Robert L. Engle,et al.  Sales force automation usage, effectiveness, and cost‐benefit in Germany, England and the United States , 2000 .

[37]  Dario Maio,et al.  A modular user-oriented decision support for physical database design , 1987 .