Somewhere between the contract being signed and the project getting underway, momentum was lost. A priority shifted. A project slipped a quarter. Budgets moved, internal resources were redirected or another transformation project took precedence.
Now, months or even years later, those SAP CX licences may still be sitting largely unused while the licence cost continues to appear on the balance sheet. The question is no longer “what did we buy?” the question is now “how do we turn what we already own into something the business can actually use and see value from?”
Read The Contract Before Writing The Roadmap
SAP CX is a portfolio, not a single product. Depending on the agreement, it may include SAP Sales Cloud, SAP Service Cloud, SAP Commerce Cloud, SAP Engagement Cloud or SAP Customer Data Cloud. Those products solve different challenges and carry different dependencies.
Before business leaders, IT teams and procurement start defining what a new CX initiative should look like, they need a shared view of what the organisation already owns and how far, if at all, it has been put to use. Start by establishing the facts:
#1 Which products, editions and entitlements are in the contract?
#2 Which environments already exist?
#3 Has anything been configured, integrated or used by a pilot group?
#4 Who owns each licence commercially and operationally?
#5 Are renewal dates or product changes likely to affect the decision?
It sounds basic but this is where assumptions surface. A sales leader may believe Sales Cloud is ready to deploy while IT knows that customer and account data still sits across three systems. Procurement may understand the licence position but have no view of the intended process. Put those people in the same room before anyone promises a date. Getting those perspectives together early creates a common starting point and avoids building a roadmap around assumptions that turn out not to be true.
Follow The Broken Customer Journey
Unused software is only half the story. The other half is the work people do around it. You may recognise some of this. Sales teams build forecasts in spreadsheets because opportunity data is inconsistent. Service advisers switch between a case system and SAP Cloud ERP 9S/4HANA) to check an order. A B2B customer reaches the checkout and finds their contracted pricing missing. Marketing holds plenty of customer records but no reliable view of consent.
Each of these describes a specific process failure and each points to a different part of the portfolio. Sales Cloud addresses account and opportunity visibility. Service Cloud supports case handling and service context. Commerce Cloud connects the buying experience with products, pricing and orders. Customer Data Solutions provides the identity and consent foundation that engagement depends on.
Start with the problem and choose the product to fit it. Organisations that work the other way round tend to implement features nobody asked for.
Define What Value Means Before Delivery Starts
“Improve customer experience” is too vague to run a project against. For a service team value might mean less time spent checking order status or fewer cases passed between teams. For sales it could be clearer pipeline visibility or fewer hours spent reconciling forecasts. For commerce it might be fewer abandoned journeys caused by missing account information, pricing or stock data.
Choose a measure the business already recognises and record the current position. Name the person responsible for the result. If nobody can explain how the proposed change will affect a customer, an employee or a commercial measure, the scope is not ready.
Check The Foundations Without Turning It Into A Year Long Study
SAP CX relies on the processes and systems around it. A short, focused readiness assessment should answer the questions that will shape the first delivery phase.
#1 Customer data: Where are customer, account, product and consent records held? Which system is authoritative? How many duplicates or incomplete records are already causing trouble?
#2 Process ownership: Who owns the process from the customer’s point of view? A journey that crosses sales, service and fulfilment needs decisions that cross the same boundaries.
#3 Integration: Which information must pass between SAP CX, SAP S/4HANA, SAP Business Technology Platform and non-SAP systems? Which connections already exist and which ones need design work?
#4 People: Who will use the solution each day? What do they do now? Which workarounds have become part of the process however unofficially?
This assessment is there to make a delivery decision. It should expose genuine constraints without becoming a comfortable substitute for action.
Pick A First Use Case With A Clear Edge
The first phase should be narrow enough to control and important enough to matter. That could be Service Cloud for a single service process where advisers currently rekey information. It could be Sales Cloud with one sales team whose pipeline data is already well understood. It could be Commerce Cloud connected to account specific pricing for one customer group. In each case the boundary is a single process with a single user group and a defined result, with just enough integration to prove the route.
Once that use case is working the organisation has evidence. It can see how the data behaves and how users respond and what the next phase should address. That is far more useful than a roadmap built entirely on workshop assumptions.
Integration Deserves An Honest Conversation
SAP CX rarely delivers value as an island. Each part of the portfolio depends on information held elsewhere.
| SAP CX area | What it needs from the wider landscape |
| Sales | Relevant account, product and order information |
| Service | Access to deliveries, warranties and previous interactions |
| Commerce | Accurate pricing, availability and fulfilment data |
| Engagement | Identity, consent and behaviour that the organisation can trust |
This is where SAP Cloud ERP (S/4HANA) and SAP BTP become part of the CX discussion. Connect only what supports a process decision or removes a known point of friction and be clear about each of the following:
| Integration design point | What to be clear about |
| Latency | How quickly information needs to reach the other system |
| Ownership | Who is responsible for each connection and the data passing through it |
| Error handling | What happens when a connection fails or a record is rejected |
| Security | How access and data are protected across systems |
“The systems will talk to each other” is a hope and not an integration design.
Adoption Starts While The Process Is Being Designed
Users can usually spot a poor process before the project team can. Ask service advisers to show you how they resolve a real case. Watch a salesperson prepare for an account meeting. Follow an order from a Commerce Cloud interaction into fulfilment. These sessions reveal the gaps that process diagrams politely ignore.
Training should draw on the same real work. A generic tour of the menus teaches people where the buttons are but says nothing about how their decisions, responsibilities and handovers have changed.
Where We Fit
Birchman works across the SAP landscape so a CX conversation does not stop at the edge of the customer-facing application. We help organisations understand what they already own, where the real gaps are and what needs to happen to turn SAP CX investment into measurable business value.
| Area | What Birchman can do | What it helps establish |
| Licence and value assessment | Review your SAP CX licences, entitlements and current usage. | What you own, what is being used and where there may be untapped value. |
| Process and data assessment | Review the customer processes, data foundations, integrations and ownership around the platform. | Whether the organisation is ready to implement or whether other issues need addressing first. |
| Use case definition | Identify and shape an initial use case linked to a measurable business outcome. | Where to start and what success should look like. |
| Solution design and delivery | Design and implement the relevant SAP CX solution, including integration through SAP BTP and SAP Cloud ERP (S/4HANA) where required. | How the CX capability will work as part of the wider SAP landscape. |
| Business change and adoption | Support the people, process and organisational change needed around the technology. | How to make sure the solution is adopted and delivers value in practice. |
The outcome is not automatically a recommendation to implement. Sometimes the assessment confirms that the business is ready to move ahead with SAP CX. In other cases, it highlights gaps in data, process or ownership that need attention first. Both are useful outcomes because the aim is to identify the right next step, rather than spend more simply because the licences already exist.
If SAP CX licences are sitting in a contract while customer teams are still working around gaps, a licence and value assessment is a sensible place to start. Bring the agreement, the current processes and the people who work with them day to day and Birchman can help establish what you have, what is holding you back and what is worth doing first. We’re here when you are ready.
