Deciding to transform the way your business operates with technology is not made without strategy and planning. Organizations often find themselves implementing both back and front office solutions at the same time, but also still have a business to run. This blog will give you a heads up on what to look for when managing all of those initiatives at once.
Implementing Oracle ERP and CX together can accelerate value, but it requires careful coordination to manage people, dependencies, and data changes that may affect both projects. At Motiv, we’ve guided clients through this exact scenario, and we’ve seen what works best to keep ERP and CX aligned.
Executive-Level Perspective
1. Assign a Leader to Manage People Across Workstreams
Regardless of whether the ERP portion of the project is live or not, Oracle CX introduces a new set of stakeholders. A strong program leader ensures alignment between teams, bridging ERP and CX, managing dependencies (see some common ones below), and keeping priorities in check with all parties. This role has been critical to ensure nothing falls through the cracks.
2. Manage Dependent Deliverables
The decisions made in ERP provide critical inputs for CX design and success:
- Accounts Table: ERP owns customer and account structures that Sales and CPQ rely on.
- Master Products Table: ERP owns product data that sales and CPQ will rely on for quoting and communication with contacts.
- Company Information: Items like company hierarchy, calendars, and master data must be locked down in ERP before CX can fully align pricing, quoting, and reporting.
- Order Flow: As CPQ is deployed, won quotes must flow seamlessly into ERP as orders. This requires both technical integration and business process alignment.
3. Anticipate and Manage Changes in ERP
Even if ERP is well underway or near go-live, adjustments can happen. Minor changes to account structures, pricing logic, or items in ERP can have a significant impact on CX implementation if not identified early. We’ve seen that clear communication channels between ERP and CX teams prevent small adjustments from becoming costly setbacks.
4. Balance Concurrent Timelines
Project timelines will vary in length. ERP projects are often longer, while CX projects can move quicker. Managing to periodic milestones will be important. Our experience shows that setting joint checkpoints between ERP and CX teams helps keep both tracks aligned without slowing momentum. Nothing is worse than having downtime while deadlines are approaching.
Motiv’s exclusive focus on Oracle CX means we act as the connective tissue with ERP implementers. We guide ERP teams on what CX requires, represent customer-facing priorities in ERP decisions, and ensure CX is launched in alignment with ERP without unnecessary disruption. Having done this with several clients, we know how to translate ERP structures into CX success.