Expertise
Three pillars of equal weight. The SAP core carries the facts, the digital systems carry the experience, and the architecture layer makes sure both mean the same thing.
- 01SAP & Enterprise CoreThe core where price, stock, article and order come into being. What stands here carries everything else — and what stands wrong here is wrong everywhere later.3 Fields
- 02Digital Commerce, Apps & ExperienceThe systems customers and staff actually work with. They decide the experience — and they are only as good as their access to the core.4 Fields
- 03Enterprise Architecture & TransformationThe layer that turns two worlds into one governable system: integration, data, identity, decision paths. Without it you have two programmes, not one architecture.3 Fields
SAP & Enterprise Core
The core where price, stock, article and order come into being. What stands here carries everything else — and what stands wrong here is wrong everywhere later.
SAP S/4HANA & Retail Core
Target state, core boundaries and retail master data in S/4HANA — brownfield and greenfield.
What belongs in the S/4HANA core — and what deliberately does not?
Store, POS & Retail Operations
Till, store systems and backend connected so selling continues when the line does not.
How do store operations and goods flow stay stable during the transformation?
Supply Chain & Logistics
Procurement, replenishment and goods flow — and the question of which stock figure to believe.
Which stock figure do store, online and planning believe — and why the same one?
Digital Commerce, Apps & Experience
The systems customers and staff actually work with. They decide the experience — and they are only as good as their access to the core.
Commerce & Omnichannel
Online and store as one business — with one truth for product, price, availability and order.
How do commerce, POS and ERP reach the same product, price and order data?
Enterprise Apps, Fiori & Mobile
Applications for customers and staff, cleanly separated from the logic they sit on.
How does the interface stay agile without business logic migrating into it?
CRM, Customer Service & Contact Center
One customer view across brands, countries and channels — and a service case that knows the order.
Where does customer data live authoritatively, and what does service see when the customer calls?
Digital Product & Platform Leadership
Platform rather than point solution — with roadmap, release governance and teams that deliver.
Do we build, do we buy — and who owns the evolution afterwards?
Enterprise Architecture & Transformation
The layer that turns two worlds into one governable system: integration, data, identity, decision paths. Without it you have two programmes, not one architecture.
Integration, BTP & Enterprise Platforms
Contracts rather than point-to-point: APIs, events and master data flows with named error ownership.
Does this capability belong in the core, in an extension, or on a platform of its own?
Data, Reporting & Analytics
Figures with a provenance — and master data with an owner.
Where do price, stock, customer and master data live authoritatively?
Enterprise Architecture & Governance
Target state, design authority and a decision log that holds up in the steering committee.
How are architecture decisions made accountable to the steering committee and the CFO?
Does this match your landscape?
Twenty minutes is usually enough to say whether I can help or not.