Infinite Menus, Copyright 2006, OpenCube Inc. All Rights Reserved.


ENTERPRISE RESOURCE PLANNING | CRM SOFTWARE IMPLEMENTATION  


sfa sfa

AN EXECUTIVE'S GUIDE TO CRM SOFTWARE IMPLEMENTATION

crm CRM IMPLEMENTATION APPROACHES
No line of business within most organizations has less structured business processes than the sales group. While lines of business such as finance and accounting, production, manufacturing, human resources, distribution or pretty much any other insist upon efficient, refined and repeatable business processes in order to function at peak capacity, sales (often along with marketing) often begin a CRM software implementation without the benefit of structured processes.

Information system automation and the resulting benefit of productivity is contingent upon the sequence and repitition of optimal steps necessary to complete varying business processes. Trying to implement CRM software for a sales or marketing group before optimal business processes have been designed or proven is clearly putting the cart before the horse. CRM software implementations, moreso than other application system type, require sound business processes in order for the implementation to be successful.

Business Process Reengineering

Business Process Reengineering (BPR), or oftentimes simply called Business Process Improvement (BPI), is an essential CRM software implementation prerequisite step for companies which have faulty business proceses or no formal business processes. The macro level diagram below highlights a very simple BPI approach.

bpr

Analyze As-Is Processes: During this step the current business processes are documented with the objective of identifying process activities, workflow, decision points and required documentation. The current (‘As-Is’) processes provides a foundation upon which the future (“To-Be”) processes can be developed.

Develop To-Be Processes: During this step, the future envisioned business processes are defined. In addition to the AS-IS analysis, the key inputs to this step are recognized best practices and the functionality of the COTS (commercial off the shelf) CRM software product being implemented. These three inputs provide a basis for developing the “To-Be” business process. Typically these processes will be documented in the form of visual diagrams called process maps.

Identify Functional Gaps: Many functional gaps between the To-Be process and the CRM software product will be identified and documented in the previous step. During this step, the To-Be processes are compared directly against the “out-of-the-box” functionality of the COTS CRM solution product being implemented.

Categorize Gaps: At this stage each gap is prioritized into the following schema: Required By Regulation/Authority, Required By Organization, Required By Department, Desirable and Non-Essential. Based on the priority of the gap, alternative methods to meet the process requirement will be considered. The options for consideration are:

i) Configuration. This means that the functional gap can be overcome by making some changes to the configuration of the COTS CRM software product. This is usually accomplished through the vendor’s supplied tool kit and does not require the product to be customized.

ii) Workaround. It is possible that an acceptable work around can be identified to meet the process requirement.

iii) Customization. Customization is typically the most expensive option to meet the process requirements.

saas

crm ERP IMPLEMENTATION FAILURE RATE
ERP software implementation failures have made media headlines for over a decade. Despite publicly available best practices and lessons learned literature, improved project management methods, increasingly mature software and more experienced implementation project teams, both commercial and government ERP software implementation failures continue to be unacceptably high.

In September of 2008, ERP.asia assembled a focus group of several industry veterans and acquired numerous publications related to the best practices and lessons learned surrounding both successful and unsuccessful ERP implementations. A summary of the group's resulting research is titled Top ERP Implementation Failure Factors.


On Demand ERP Systems  

CRM Software Implementation

spacer
spacer spacer spacer
Most common 5 phase approach:
spacer
spacer spacer spacer
spacer
saas

Planning Phase

saas
Conference Room Pilot
saas
Conversion and Integration
saas
Training Phase
saas
Parallel Processing
saas
Go-Live and Stabilization
spacer
spacer

 

ondemand
ERP software implementations are a constantly evolving process. ERP application software projects should be thought of as a 'journey' and not a 'destination' achieved upon the go-live event. Recurring measurement and continuous process improvement are essential if ERP software systems are to deliver strategic objectives for the organization.

saas

 

tags Tags:
software implementation
crm software implementation, big bang, crm 2.0, sales force automation, crm solution, siebel, erp.asia, government crm software, sfa, crm accounting software, saas, crm implementation failures

 

 

 

 

 

erp

crm crm


Home | Contact | Search | Sitemap | Terms