Initiating an ERP or CRM implementation, is painful. It is expensive to begin with, and much more impactful is that during implementation the work systematically hijacks the focus of each department as new procedures were established and staff was trained on how to use the environment. Eighteen (18) months later, implementation is pretty much complete. You see lots of resistance from employees during the process and finally start to see the benefits from the system started to be recognizable. Unfortunately, the inability of the system to correctly replicate your business process across all departments resulted in modules that are only used minimally, or not at all. Was it the right decision to implement it? With some reluctance, probably....
Now you had some contract management issues: an unrecognized liability or some contract penalties that could have been avoided. Renewals or SOW milestones that needed to be shared were missed. Now your CFO, GC or Contracts Manager are pushing hard to purchase a separate contract management system.
Apparently, the CRM contract management module just isn’t it. Even if you went ahead with a centralized, collaborative data sharing implementation now you go ahead and implement full life-cycle contract management, what should you expect? How bad will it be? Will it be Act II of a badly written and acted two act play?
Is opensourceCM implementations different from what you’d expect?
Let set your expectation, here is the opensourceCM Proof of Concept (on-boarding process) that includes system analysis and setup:
opensourceCM goal is to establish the Client's opensourceCM account based on the client's needs and processes related to its internal contract lifecycle management flow and to insure the full operation and functionality of the account. Once goal will be reached (within the scope of time defined ~15 hours PoC) the client will decide whether he wishes to execute a licensing agreement with opensourceCM, based on the details already defined. If the client would like to add any additional features or would request for option incurring development/Non-Recurring engineering the related details will be revised and adjusted accordingly based on the pricing table detailed in the exhibit.
Scope of time and general guidelines:
Based on the information discussed in our prep meeting and the understanding of the framework of the client’s opensourceCM account, the "System analysis and Set-up" will include 15 guiding hours. We believe that this will provide sufficient time to ensure that client’s administrator/s will be able to manage the account and assist other users to use it as well as to assure you are satisfied with the workflow of the account.
It is necessary that the elected administrator/s on the client's side (they are kind of project manager/s) will be available and oriented to learn and understand the functionality of the system. With our support and technical team the account will be designed and tailored to the specific needs drafted during the system analysis phase. Changes and adjustments can be made with the administrator/s and team while moving along the process.
Phase 1 of PoC is system analysis - the goal: To configure and sketch the design of client’s opensourceCM account. Estimated time frame: 4-6 hours
Phase 2 of the PoC: Pre-production phase is continue setting up the account. Implementing all technical issues relevant to your account by our technical team and teaching your administrator/s on how to use the platform specifically to your needs. Estimated time frame: 8-7 hrs.
Phase 3 of the PoC: Production phase Insuring your satisfactory from the all templates and workflow of the account. Estimated time frame: 3-2 hrs.
Results? Insuring that we become long term partners
Tags: CM News, Features
click here to register.