SAP Customer Experience is the publisher's CX cloud, running across Sales Cloud, Service Cloud, Commerce Cloud, Marketing Cloud and Customer Data Cloud. The licensing surface spans four module sets and a customer-data foundation. The buyer's commercial picture is the consolidated CX subscription posture.
SAP Customer Experience sells across four principal commercial module sets. Sales Cloud licenses the sales-team population (account managers, opportunity owners, sales operations) on a per-user, per-month subscription. Service Cloud licenses the customer-service team population (agents, supervisors, service-operations) on a similar per-user mechanic. Commerce Cloud licenses against a combination of named-user seats and transaction-volume bands, depending on the deployment shape (B2C, B2B, headless). Marketing Cloud licenses against marketing-contact volume and capability tiers.
Each module sells under its own commercial construct. The buyer running all four module sets has four distinct subscription positions on the order document, and the commercial sizing for each module is a separate procurement decision.
The full reading on the SAP application catalogue sits in the SAP pillar. The parallel reads on adjacent application surfaces are SuccessFactors licensing and Ariba and procurement licensing.
Sales Cloud and Service Cloud are the simplest CX modules to size. Both license against a named-user population on a per-month basis, with seat counts that map to the buyer's organisational structure.
The buyer-side complication is the seat-segmentation. SAP sells Sales Cloud and Service Cloud in tiered editions (typically Foundation, Performance and Premium for Sales; Foundation, Service Premium and Service Enterprise for Service). The default publisher position is to license every seat at the highest-tier the role might use; the Admodum methodology segments the seat population against the actual workflow requirement and licenses each segment at the tier that matches the workflow.
Where Salesforce Sales Cloud or Salesforce Service Cloud is the credible alternative (a common position for buyers with an existing Salesforce estate), the renewal negotiation runs against the Salesforce BATNA. The full reading on the parallel Salesforce surface sits in the Salesforce pillar.
Commerce Cloud licenses against a transaction-band mechanic that varies by deployment context (B2C consumer commerce, B2B trade commerce, headless API-first commerce). The transaction band is sized against the buyer's annual gross merchandise value and adjusted for the deployment shape.
The buyer-side question is whether the buyer's expected GMV aligns with the band that the publisher has proposed and what the upgrade-path cost looks like if GMV grows. The Commerce Cloud commercial mechanic is heavily back-end-loaded; the renewal economics differ materially across the bands.
The Admodum methodology models the expected GMV growth curve across the term, prices the band-upgrade cost at each step, and negotiates a longer-tenor commitment with built-in band-flex terms where the GMV forecast is uncertain. The detailed reading on the parallel Adobe Commerce surface sits adjacent in the Cisco / Adobe pillar.
Marketing Cloud licenses against marketing-contact volume (the population of contacts addressed through email, SMS, push and in-app channels in the buyer's marketing operations). The contact-volume mechanic is similar in structure to the Salesforce Marketing Cloud and Adobe Marketing Cloud commercial constructs.
The buyer-side question is the active-contact definition. SAP's published commercial mechanic prices against the contact population at the engagement layer; the buyer's procurement-side definition typically excludes inactive contacts, opted-out contacts and historically dormant contacts. The negotiation runs on the precise contact-volume definition inside the contract language.
Customer Data Cloud (the consent and identity layer formerly known as Gigya) reads as a separate commercial surface, priced against the customer-record population and the consent-management capability tier. The Customer Data Cloud is a distinct buy decision.
SAP CX renewal sits inside the wider SAP commercial relationship and the wider CX market. The renewal posture depends on the seat-population reconciliation across Sales and Service, the GMV-band read on Commerce, the contact-volume audit on Marketing, the Customer Data Cloud posture and the BATNA reads against Salesforce, Microsoft Dynamics, Oracle CX and Adobe Experience Cloud where credible.
The methodology runs four parallel reads (one per module set) against the publisher's renewal proposal, and consolidates the four into a single CX commercial picture for the CIO and CFO. The consolidated picture drives the renewal negotiation.
The renewal engagement runs under one of three Admodum frameworks: fixed fee, contingency / gainshare or annual retainer.
Six checks for the buyer running into an SAP CX decision: segment the Sales and Service seat population by tier. Model the Commerce Cloud GMV growth across the term. Audit the Marketing contact-volume definition inside the contract. Read the Customer Data Cloud as a distinct buy decision. Run the four BATNAs (Salesforce, Microsoft, Oracle, Adobe) before the renewal. Consolidate the four module reads into a single commercial picture.
For the wider SAP reading, return to the SAP pillar, visit the SAP knowledge hub, or open a private conversation with a senior Admodum SAP advisor through /contact/.
A senior Admodum SAP advisor will run the methodology through with your CIO, CFO, procurement team or audit response team on a private call. The engagement runs as fixed fee, contingency or annual retainer. Active SAP audits route directly to the Audit Defence programme.