| Status | |
| Owner | KUTANI-ext, Karunakar |
| Stakeholders |
Syensqo requires a robust CRM system to support its sales lifecycle and currently relies on multiple customized instances of Salesforce (Core CRM and ICARe). These instances are integrated with various backend systems (PRS, PF1, WP1) and point solutions (Dynasys, Gensuite, Qualtrics, Qliksense, etc.). However, the existing architecture, built on a heavily customized Salesforce environment with numerous bespoke interfaces, is creating challenges related to process and data consistency, scalability, and integration complexity.
These inefficiencies are hindering Syensqo’s ability to deliver a seamless and consistent customer experience, while also misaligning with the company’s strategic goals of simplification, agility, and innovation.
There are 3 KDDs in the CRM space.
Aligning with KDD040's recommendation of "Greenfield CRM implementation with Single Instance for all GBUs", we propose implementing Salesforce as the single-instance CRM and CX solution for all GBUs, to deliver a seamless customer experience, efficient processes, and consistent data management through a unified platform.
Highlights of the recommended Option B: Harmonize Salesforce by unifying Core CRM and ICare, removing non-CRM features, and integrating Salesforce CRM capabilities with SAP S/4HANA:
Syensqo's current customer relationship management (CRM) processes are supported by a complex architecture that involves multiple applications, including two Salesforce instances, On-Premises and Cloud applications, and various manual and automated system interfaces. The various functions implemented, along with their current challenges, are detailed below in the following exports from the LeanIX enterprise architecture tool: Core CRM interface provider.pdf and Core CRM interfaces consumer.pdf
The Composites GBU uses the ECC Quotation process, which differs from OneQuote due to material group level differences. The outputs of OneQuote and ECC Quote vary significantly in detail and format across GBUs. For forecasting purposes, quotes from both systems are integrated with Dynasys, but quote reporting is done in different tools.
Given the complexities and challenges identified in Syensqo's current CRM processes - including multiple applications, custom interfaces, and manual intervention - it is clear that a transformation is necessary. This KDD aims to explore potential solutions that will standardize CRM processes, providing a single customer view, efficient workflows, and automated processes. This will lead to improved efficiency, accuracy, and customer satisfaction.
No constraints identified; further updates may be determined during detailed design phase.
There are currently no known rules identified, but we will revisit and update if any emerge during the detailed design phase.
Objective: This option utilizes a comprehensive SAP solution, encompassing the full SAP stack, to empower and streamline business processes. The primary benefit of this approach is that it leverages native/standard integration across all SAP products, thereby eliminating the need for duplicate data entry, ensuring alignment of enterprise structure and master data, and providing end-to-end traceability and transparency from 'Lead to Cash'.
Approach:
Objective: This option utilizes Salesforce's CRM platform and capabilities to consolidate the current multi-tenant landscape into a unified Salesforce environment, in line with KDD040's recommendation for a "Greenfield CRM implementation with a Single Instance for all GBUs." Additionally, any non-CRM functions that can be transitioned to S/4HANA will be migrated to streamline core CRM functions. This approach will necessitate integration between Salesforce and S/4HANA to facilitate a seamless Lead to Cash execution process and enhance end-to-end business process execution and reporting capabilities.
Approach:
Streamline master data processes by retaining Prospect creation and Customer conversion in Salesforce, eliminating PRS, and integrating Salesforce with S/4HANA for real-time data replication. Align GBU segmentation with S/4HANA's organizational structure and map team assignments to S/4HANA's business partner concepts, reducing interfaces and enhancing efficiency.
Continue using Salesforce for lead and opportunity management, and revenue projection maintenance. However, leverage S/4HANA data for forecasting and realized sales/revenue data, ensuring an accurate view of sales performance.
Price setting will continue in Salesforce, integrated with Dataiku for price optimizations. Salesforce will remain the platform for price execution via quotation creation. Once quotations are released, prices will be replicated to S/4HANA. Furthermore, Salesforce quotations will be replicated to S/4HANA to ensure end-to-end Quote-to-Cash process integration. To enhance visibility, Price Transparency dashboards will be implemented using S/4HANA data, covering sales revenue, prices, forward costing, orders, and contract information.
Contract management will be centralized in S/4HANA, simplifying processes, reducing errors, and boosting efficiency. S/4HANA will serve as the single source of truth, providing accurate and visible data for informed decision-making. The contract dashboard and KPIs will be driven by S/4HANA data, offering real-time insights and performance metrics. Additionally, necessary metadata required for contract database management will be replicated from S/4HANA to Salesforce.
Salesforce will handle case management and approvals, integrating with S/4HANA for quality notifications and corrective actions. S/4HANA will manage investigation outcomes, including returns and settlements, and update Salesforce cases for tracking. Feedback tracking will remain in Qualtrics, with reporting in both Salesforce and S/4HANA for a unified view.
Salesforce manages and approves samples, then integrates with S/4HANA for logistics and fulfilment. Third-party integrations remain in Salesforce, with S/4HANA updates flowing in for tracking and monitoring purposes.
Objective: This option retains current Salesforce setup, including its custom solutions and third-party application integrations, while establishing integration with S/4HANA. S/4HANA will be utilized as a logistics execution tool, and the existing ECC interfaces will be redesigned to connect with S/4HANA, incorporating necessary modifications for optimal performance.
Approach:
Retain Salesforce for Prospect and Customer conversion and maintain PRS as the central system for corporate master data management, integrating with S/4HANA for data synchronizations. Align GBU segmentation with S/4HANA's organization structure, map team assignments, and retain data governance tools like Mappy and Gridbuddy.
Utilize Pardot for lead generation and integrate with Salesforce for nurturing and conversion. Continue using Salesforce for opportunity management, revenue projections, and manual sales tracking using S/4HANA reports. However, leverage S/4HANA for opportunity dashboards and forecasting, providing a unified sales performance view.
Implement Price Transparency dashboards in S/4HANA for sales revenue, price analysis, and forward costing, integrating with Dataiku for price optimization. Continue using Salesforce for sales price setting and execution, replicating accepted quotations to S/4HANA for pricing determinations. Update document flow from S/4HANA to Salesforce for Quote to Cash integration.
Salesforce will remain the contract management hub, integrating contract data with S/4HANAand reporting tools for comprehensive contract and customer 360 dashboards.
Salesforce will handle case management and approvals, while Gensuite tracks corrective and preventive actions. Integrate Salesforce cases with S/4HANA for commercial responses and returns, and manage returns and replacements in S/4HANA, syncing updates back to Salesforce. Feedback tracking will remain in Qualtrics, with reporting visible in both Salesforce and S/4HANA.
Salesforce will manage and approve samples, integrating with S/4HANA for logistics and fulfilment. Third-party integrations will remain in Salesforce, with S/4HANA updates flowing in for tracking and monitoring purposes.
Option A - Transition from Salesforce to SAP CX and integrate with SAP S/4HANA | Option B - Harmonize Salesforce by unifying Core CRM and ICare, removing non-CRM features, and integrating Salesforce CRM capabilities with SAP S/4HANA | Option C - Maintain Salesforce in its current state, retaining Core CRM and ICare, and integrate it with SAP S/4HANA. | |
|---|---|---|---|
| Alignment with "Simplification principle" |
|
|
|
| Alignment with "Standardization principle" |
|
|
|
| System Integration |
|
|
|
| Implementation Time |
|
|
|
| User Training & Change Management |
|
|
|
| Cost of Implementation |
|
|
|
| Long-term Scalability |
|
|
|
| Customization Flexibility |
|
|
|
| System Maintenance |
|
|
|
| Risk of Disruption |
|
|
|
| Customer Experience Impact |
|
|
|