Estimated reading time: 5 minutes · Last updated:
Marco Messinger of Nagarro argues that customer experience must be planned end-to-end and anchored in the operational stack rather than treated as a front‑end project. He says companies should align CX design with SAP S/4HANA, SAP Customer Experience and SAP BTP and begin with a single, scalable use case—for example a portal-driven service flow or an SAP Sales Cloud visibility module. Messinger published these recommendations on 7 October 2026 and frames the mechanism as a modular, AI-native approach that links sales touchpoints to ERP processes so new interfaces produce real business value.
“End-to-end” does not mean that companies must immediately roll out all CX components in full or launch a major transformation program.
Marco Messinger, Nagarro
Key takeaways
- Marco Messinger of Nagarro argues customer experience must be planned end-to-end with SAP Customer Experience, SAP S/4HANA and SAP BTP.
- Organisations should start small with a single, scalable use case such as an SAP Sales Cloud pipeline module or an SAP Service Cloud service process.
- AI should be embedded as a native component for use cases like intelligent service triage, next‑best‑action and automatic issue recognition.
- Modular portals can act as an entry point that bridges front‑end interfaces with SAP S/4HANA, SAP ECC and line-of-business systems.
Table of contents
- Key takeaways
- Why CX projects stall: the sales‑operations gap
- Design CX and SAP S/4HANA together
- Make AI native, not an add‑on
- Start small with modular portals and scale
- Events, dates and logistics named in the source
- What could make this approach work — and fail
- What to be careful about
- Frequently asked questions
Why CX projects stall: the sales‑operations gap
Many customer experience initiatives stall because the project stops at the user interface and does not change the underlying operational landscape. Data such as orders, contracts, availability, delivery status, invoices and service calls typically live in ERP or line‑of‑business systems, and when those sources are left out the new front end simply surfaces incomplete information.
Messinger stresses that when sales processes end at the ERP boundary the organisation loses end‑to‑end control: service teams handle cases without the contract and order context they need, and campaigns run without accurate customer data. The result can be higher friction for customers and lower returns for the business.
Design CX and SAP S/4HANA together
Planning customer experience in parallel with SAP S/4HANA work avoids creating new silos. The article names SAP Customer Experience, SAP S/4HANA and SAP BTP as the platform trio to align: SAP CX covers sales, service, commerce and customer data; S/4HANA supports core operational processes; and BTP provides integration, extensions, data services, automation and AI capabilities.
The practical implication is procedural: a service request must not be allowed to remain unresolved in a portal, and a commerce flow must be connected to pricing, availability, logistics and billing in the ERP to deliver consistent outcomes. That integration is where Messinger locates measurable business value.
Make AI native, not an add‑on
The author warns against treating AI as a bolt‑on widget such as a chatbot or an isolated text‑suggestion tool. Instead, AI should be built into process and data design from the outset so it can be applied in context to tasks like automatic issue recognition, intelligent service triage, next‑best‑action recommendations and summaries of customer history.
Messinger recommends using AI‑native templates and reusable building blocks so typical CX scenarios can be operationalised quickly while keeping clear human handoffs. The balance to strike is speed and context against trust: AI must speed resolution without becoming a digital rejection mechanism.
Start small with modular portals and scale
Modular portal solutions are presented as a tangible, incremental entry point. A portal can expose a single service or inquiry process to customers and employees, consolidate interactions, enable self‑service and initiate sales or service workflows without requiring a full enterprise rollout up front.
Because the portal sits at the visible edge, it also reveals integration gaps quickly: a portal that shows order status but cannot access the ERP highlights the exact workflow, data and responsibility changes needed to deliver value. Messinger’s prescription is to choose an initial step that delivers business sense and technical scalability.
Events, dates and logistics named in the source
The source lists summit and workshop logistics that include dates, venues, ticket prices and contact details. For the fourth time E3 magazine organises an S/4 groundwork summit: the event appears at FourSide Hotel Salzburg, Am Messezentrum 2, 5020 Salzburg, Austria, with a contact phone number +43-662-4355460 and workshops on Wednesday, June 10, and Thursday, June 11, 2026; the AI experience workshop is scheduled only on June 11, 2026 (limited places).
A second listed venue is Hotel Hilton Heidelberg, Kurfürstenanlage 1, D-69115 Heidelberg for Wednesday, April 22 and Thursday, April 23, 2026, with an AI experience workshop on April 23, 2026. Ticket pricing in the source is shown as EUR 305 excl. VAT, EUR 590 excl. VAT, EUR 390 excl. VAT and EUR 290 excl. VAT in the different categories, and the source notes the first 10 student tickets are free of charge.
| Product | Role in CX | Key integration point |
|---|---|---|
| SAP Customer Experience | Sales, service, commerce, customer data and order management | Front‑end CX and customer data consolidation |
| SAP S/4HANA | Core operational processes | Pricing, availability, logistics and billing |
| SAP BTP | Integration, extension, data, automation and AI | Platform services and AI support |
| SAP ECC | Legacy operational processes | Source of existing master and transactional data |
What could make this approach work — and fail
The case for
- Planning CX and S/4HANA together can turn a transformation into measurable business value by avoiding new silos.
- Starting with a modular portal or a single SAP Sales Cloud or SAP Service Cloud use case lets organisations prove integration and ROI before scaling.
- Using AI‑native templates and reusable blocks accelerates deployment of intelligent service triage, next‑best‑action and other use cases.
The case against
- Treating AI as an add‑on risks creating automation that frustrates customers unless data and handoffs are correct.
- Implementing new interfaces without changing processes or integrating with S/4HANA/ECC will surface incomplete information and little business impact.
- Siloed planning of S/4 transformation and CX work can produce duplicated effort and fragmented data rather than unified outcomes.
What to be careful about
- Investing in new UIs without updating underlying processes, which leaves defects and incomplete workflows in place.
- Fragmented customer data across multiple systems that prevents reliable AI outcomes such as next‑best‑action.
- AI automation applied without relevant contract, order and pipeline data can produce erroneous prioritisation or customer frustration.
- S/4HANA or ECC modernization planned in isolation from CX can create integration debt and additional rework.
The bottom line
Customer experience succeeds when it is more than a new interface: it must be anchored in the operational systems and processes that run the business. Marco Messinger’s practical prescription is to plan CX together with SAP S/4HANA and SAP BTP, pick a single scalable use case—often delivered first via a modular portal—and embed AI as a native component with clear human handoffs. That sequence reduces risk, reveals integration gaps early and creates a pathway to scale without a disruptive big‑bang transformation.
What to watch
- Watch for organisations publishing joint CX and SAP S/4HANA roadmaps; no date has been set.
- Watch for suppliers offering AI‑native templates and modular portal pilots to accelerate CX scenarios; no date has been set.
Frequently asked questions
What does 'end‑to‑end' mean here?
Messinger uses 'end‑to‑end' to mean designing processes, data and systems so an initial CX step is scalable across the enterprise architecture and connects to SAP S/4HANA, SAP Customer Experience and SAP BTP.
How should a company 'start small'?
Start with a single, high‑value use case such as an SAP Sales Cloud pipeline visibility module or an SAP Service Cloud service process; the source recommends a modular portal or an AI‑enabled automation block as practical entry points.
How can AI avoid harming customer trust?
Embed AI as a native element of processes and data models, use AI‑native templates, and ensure clear human handoffs for tasks like intelligent service triage, next‑best‑action and issue recognition.
Related reading
