Where you will run into SAP (5)
- S/4HANA customer, often on RISE or GROW with SAP, where the SAP account team adds Sales Cloud or Service Cloud to an ERP expansion.
- SAP CRM 7.0 on-premise customer facing the end of mainstream maintenance in 2027 and choosing between SAP Sales Cloud and Salesforce.
- Existing SAP Sales Cloud V1 customer being guided to Version 2, which SAP describes as a migration.
- Manufacturer, distributor or consumer products company with field sales or retail execution, where SAP's visit planning and perfect store features come up.
- IT-led evaluation where an SAP center of excellence owns the roadmap and the sales team has little voice.
Competitor snapshot (9) Verified facts
| SAP Sales Cloud list price (as of October 2026) | USD 136 per user/month, contract 3 to 36 months, auto-renewal. Service add-on USD 22 and field sales add-on USD 53 per user/month. SAP notes other pricing structures are available on request. Source |
|---|---|
| SAP Service Cloud list price (as of October 2026) | USD 112 per user/month, contract 3 to 36 months, auto-renewal. Sales add-on USD 46 and utilities add-on USD 67 per user/month. Source |
| Joule and SAP AI pricing model | Base AI, including Joule Work Base and embedded AI, comes with every SAP cloud subscription at no extra cost. Premium AI, including Joule Agents, is paid with AI Units bought annually; unused units expire after 12 months. Source |
| Joule Agent consumption rates | Standard agents use 0.02 AI Units and advanced agents 0.05 AI Units per agent action; a task can take several actions. The pricing page we reviewed shows no dollar price per AI Unit and directs buyers to their SAP account team. Source |
| S/4HANA integration | SAP says Sales Cloud connects with SAP ERP and S/4HANA so sellers see accounts, product availability, pricing, quotes, orders and order status. Sales Cloud is also offered as part of GROW with SAP S/4HANA Cloud Public Edition, premium. Source |
| Version 1 to Version 2 move | SAP describes moving from classic Sales and Service Cloud to Version 2 as a structured migration (explore, plan, migrate, launch) with AI-assisted migration tools and partner support. Source |
| SAP CRM 7.0 maintenance timeline | Mainstream maintenance for SAP Business Suite 7 core applications, including SAP CRM 7.0, ends at the end of 2027. Optional extended maintenance runs 2028 to 2030 at a premium of two percentage points on the maintenance basis. Source |
| MuleSoft connectors for SAP | MuleSoft documents an SAP S/4HANA OData connector for S/4HANA Cloud and on-premise, and an SAP connector for NetWeaver-based systems such as ECC and CRM using BAPIs and IDocs. Source |
| Salesforce list prices for comparison (as of October 2026) | Sales Cloud and Service Cloud: Pro Suite $100, Core $195, Advanced $395, Max $550 per user/month billed annually. Agentforce add-ons $125 per user/month. Flex Credits $500 per 100,000; a standard action uses 20. Source |
As of October 27, 2026. Vendors change packaging and prices often; confirm before quoting a number to a customer.
Who decides, and how to talk to them (5) Approach
CIO / SAP center of excellence
Cares about: One vendor relationship, S/4HANA integration with less custom work, and a clean roadmap off SAP CRM 7.0.
Your angle: Respect the SAP estate. Show the S/4HANA integration plan with MuleSoft's documented connectors, and ask who will own CRM change requests: the SAP CoE, already busy with ERP, or a team close to sales.
CRO / VP Sales
Cares about: Rep adoption, forecast accuracy, territory and quota changes, and a tool reps open without being told.
Your angle: Make this persona the owner of the scripted demo. Run their pipeline review and forecast call on Sales Cloud. Ask how sellers check order status and pricing today and how long that takes.
CFO / procurement
Cares about: Per-seat price, contract alignment with the SAP agreement, and AI spend they can predict.
Your angle: Agree SAP's list price is lower than Core. Build a three-year model with the same scope: users, add-ons, AI Units or Flex Credits, integration, implementation and admin staff. Put Pro Suite on the table where scope allows.
VP Customer Service
Cares about: Resolution time, self-service, and seeing orders, deliveries and warranties from S/4HANA on the case.
Your angle: Demo a service case with S/4HANA order and delivery data on the record, then hand a routine request to an Agentforce agent. Ask which data the agent needs to resolve their top two request types.
Marketing / digital commerce
Cares about: Lead flow, campaign attribution and ecommerce data reaching sales.
Your angle: Ask which marketing and commerce tools they run and whether those are SAP. Show lead-to-opportunity on Salesforce and Data 360 unifying behavior across systems.
Where Salesforce wins (6) Approach
A CRM chosen by the people who use it
SAP's argument starts from the ERP. Start from the seller and the service agent. Sales Cloud and Service Cloud are the core Salesforce products, with forecasting, pipeline inspection, case management and a large ecosystem built around them. Ask the CRO what share of reps keep the CRM current and what they track in spreadsheets instead. Adoption decides data quality, and data quality decides whether the ERP gets good orders.
See the proof →S/4HANA integration with documented connectors
Buyers assume only SAP's CRM can reach S/4HANA cleanly. MuleSoft documents an S/4HANA OData connector for cloud and on-premise S/4HANA, and an SAP connector for ECC and CRM using BAPIs and IDocs. Recommend the buyer list the flows sellers need, usually accounts, materials, prices, availability, orders and deliveries, and the freshness each needs. Then show the integration plan rather than debating it in the abstract.
See the proof →A migration either way
SAP CRM 7.0 loses mainstream maintenance at the end of 2027, and SAP describes the move from Sales Cloud Version 1 to Version 2 as a migration with its own tools and steps. So many SAP CRM customers face a project regardless. Use this to level the field: if the team must re-implement anyway, the right question is which platform serves sales and service best for the next decade, not which one is already installed.
See the proof →Agentforce with published prices
SAP prices Joule Agents in AI Units per action, but the pricing page shows no dollar figure per unit, and units expire after 12 months. Salesforce publishes Agentforce add-ons at $125 per user/month, Flex Credits at $500 per 100,000 with 20 per standard action, and $2 per conversation. Suggest the buyer price one real scenario, such as a month of order-status requests, on both platforms and compare the cost and the resolution rate.
See the proof →Data 360 for customer data beyond SAP
Few SAP shops run only SAP for customer data. Marketing automation, ecommerce, support tools and product usage data usually live elsewhere. Data 360 unifies those sources for segments, analytics and agents, while MuleSoft handles S/4HANA transactions. Lead with this when discovery finds three or more systems holding customer data, and ask who reconciles them today.
See the proof →Ecosystem and talent
Salesforce has a large admin and developer community, Trailhead training and AgentExchange apps for telephony, e-signature and industry processes. Ask the buyer how quickly they could hire an SAP Sales Cloud administrator in their market, and whether their SAP CoE has capacity for CRM requests on top of S/4HANA work. Then make a small configuration change live in the demo to show who can own the system.
Where SAP is strong, and how to respond (4)
Acknowledging these builds credibility. Buyers already know them.
Lower published list price
SAP lists Sales Cloud at USD 136 and Service Cloud at USD 112 per user/month, with contracts from 3 to 36 months, against Salesforce Core at $195. A sales user adding service costs USD 22 more on SAP. On a seat-price spreadsheet SAP looks cheaper.
How to respond: Do not dispute the numbers. Offer Pro Suite where scope allows, and expand the model to three years: add-ons, AI usage, integration, implementation and administration for the same scope.
Native fit with SAP ERP
SAP says Sales Cloud connects with SAP ERP and S/4HANA for accounts, availability, pricing, quotes, orders and order status, and offers it inside GROW with SAP S/4HANA Cloud Public Edition, premium. For an SAP-centered IT team, that is a real advantage in effort and governance.
How to respond: Acknowledge it plainly. Scope the integration for Salesforce with the same list of objects, and ask which of those flows truly need real time. Then return to user outcomes.
Base AI included with every cloud subscription
SAP includes Joule Work Base and embedded AI with every cloud subscription, with no AI Units required. Premium agents cost AI Units, but basic conversational help and navigation come at no extra cost.
How to respond: Separate assistance from resolution. Ask which customer requests the buyer wants resolved by an agent, and compare cost per resolved request with Agentforce on that scenario.
Field sales and retail execution depth
SAP Sales Cloud includes dynamic visit planning, route optimization and perfect store features with planograms and visit surveys for consumer products retail execution, plus mobile apps that work offline.
How to respond: If retail execution is central, bring an industry cloud or AgentExchange partner into the demo. If it is a side need, keep the focus on pipeline, forecasting and service.
Discovery questions that change the deal (13) Approach
Business
- Who will be measured on this CRM's success, and what number do they report to the board?
- Where do sellers lose time today: finding pricing, checking availability, chasing order status, or updating the CRM?
- If you run SAP CRM 7.0 today, what is your plan for the end of mainstream maintenance in 2027?
SAP and integration
- Which S/4HANA or ECC data do sellers and service agents need, and how fresh must each piece be?
- Are you on RISE or GROW with SAP, and is CRM being discussed inside that agreement?
- Who owns CRM changes today, and how long is that team's ERP backlog?
- Which non-SAP systems hold customer data, such as marketing, ecommerce or support?
AI and service
- Which two or three customer requests would you want an agent to resolve first?
- How will you budget AI: per user, per conversation, or per action, and who approves overages?
- Has SAP shown you what a Joule Agent costs for your volume in AI Units and dollars?
Decision
- Who besides IT has a vote, and what would make the sales or service leader push back?
- What would a three-year cost comparison need to include for your CFO to trust it?
- If you are on SAP Sales Cloud V1, what has SAP told you the move to V2 involves?
Objections, and what to say (6) Approach
"We run S/4HANA, so CRM should be SAP."
Agree the ERP is the financial backbone, then separate ERP fit from CRM fit. Ask which S/4HANA data sellers and agents need, and how fresh. Show the integration plan using MuleSoft's S/4HANA connector, then run the scenarios the sales leader owns. Suggest scoring both platforms on rep adoption, forecast quality and time to change a process, with integration effort as one line, not the whole decision.
Proof to send →"SAP Sales Cloud is cheaper per user."
Confirm the list prices honestly: SAP Sales Cloud is USD 136 and Sales Cloud Core is $195 per user/month. Then ask to price the same scope over three years: add-ons, AI Units or Flex Credits, integration, implementation, and the people who run it. If the scope is simple, put Pro Suite at $100 on the table. Offer to fill in the Salesforce side line by line.
Proof to send →"Joule is already included with SAP."
Agree that SAP includes Base AI and Joule Work Base with cloud subscriptions. Then point out that SAP prices Joule Agents separately in AI Units per action, with units that expire after 12 months. Ask the buyer to get SAP's dollar figure for their agent volume, and compare it with Agentforce on the same scenario: cost, resolution rate and the systems each agent can act on.
Proof to send →"Integrating Salesforce with SAP is too risky."
Take the concern seriously and make it concrete. List the flows, the pattern for each, the system of record per field, and who handles errors. MuleSoft documents connectors for both S/4HANA and older NetWeaver-based SAP systems. Share our ERP integration patterns guide and offer a scoped integration estimate that sits inside the three-year cost model.
Proof to send →"We already own SAP CRM; switching is too disruptive."
Ask what the plan is for the end of SAP CRM 7.0 mainstream maintenance in 2027, or for the move from Sales Cloud V1 to V2, which SAP itself treats as a migration. If a project is coming either way, the disruption is not unique to Salesforce. Suggest phasing by team or region and running parallel forecasts before cutover.
Proof to send →"Our SAP agreement gives us a discount on CX."
Do not race to match. Ask how long the discount lasts, what the CX lines renew at, and whether AI Units and implementation are inside it. Then bring the business owner back in: a discounted CRM that reps avoid still produces weak forecasts. Ask the CFO to weigh three-year cost alongside adoption and speed of change.
Traps that lose these deals (5)
- Criticizing S/4HANA or the SAP program. The CIO's career may be tied to it; position Salesforce as working next to it.
- Arriving without an integration plan. The SAP team will test you on materials, pricing conditions and order status.
- Letting the SAP center of excellence run the evaluation without a sales or service owner scoring scenarios.
- Disputing SAP's published list price. It is public; win on scope, adoption and three-year cost.
- Claiming Joule has no agents. SAP sells Joule Agents; compete on cost clarity and outcomes.
Qualify honestly
Strong fit for Salesforce
- A sales or service leader owns the decision and wants faster change and better adoption.
- Customer data sits in several non-SAP systems that must come together for analytics or AI.
- SAP CRM 7.0 customer that must re-platform before maintenance ends anyway.
- The buyer wants customer-facing AI agents with a clear, priced business case.
- Several clouds in scope: sales plus service, field service, CPQ or marketing.
Risky fit
- CRM is bundled into a RISE or GROW deal that closes before an evaluation can run.
- The SAP CoE owns the budget and no front-office leader is engaged.
- Seat price alone decides and scope fits SAP's base offer.
- Retail execution is the main use case and the buyer is deep in SAP consumer products processes.
Salesforce products to lead with (6)
Moving the customer off SAP
Moving from SAP CRM or SAP Sales and Service Cloud to Salesforce is a re-implementation built around the S/4HANA or ECC integration. Agree the system of record for business partners, materials, pricing conditions, quotes, orders and deliveries before mapping. SAP business partners map to accounts and contacts, and partner functions often become account relationships or contact roles. Rebuild workflows and approvals in Flow, and plan how pricing is handled: read from SAP at quote time or synced on a schedule. Decide which sales history to load and which to leave in SAP for reporting. Clean and deduplicate customers first. Run parallel forecasts for one cycle, then cut over by sales org or region.
Questions AEs and buyers ask (5)
How much does SAP Sales Cloud cost?
As of October 2026, SAP lists Sales Cloud at USD 136 per user/month with contracts from 3 to 36 months, and Service Cloud at USD 112. Add-ons such as service for Sales Cloud (USD 22) and field sales (USD 53) are extra.
How are SAP Joule Agents priced?
Joule Agents use AI Units: 0.02 per action for standard agents and 0.05 for advanced agents. AI Units are bought annually and expire after 12 months; SAP's pricing page directs buyers to their account team for the dollar price.
Can Salesforce integrate with S/4HANA?
Yes. MuleSoft documents an S/4HANA OData connector for cloud and on-premise S/4HANA and an SAP connector for ECC and CRM using BAPIs and IDocs. Most projects focus on accounts, materials, pricing, orders and deliveries.
When does SAP CRM 7.0 maintenance end?
SAP says mainstream maintenance for Business Suite 7 core applications, including SAP CRM 7.0, ends at the end of 2027. Optional extended maintenance runs through 2030 at a premium.
When should an AE walk away from an SAP deal?
When CRM is part of a RISE or GROW agreement that closes before an evaluation, and no sales or service leader is engaged. Also when seat price alone decides and the scope fits SAP's base offer.
Sources (11)
- SAP: Sales Cloud pricing
- SAP: Service Cloud pricing
- SAP: Sales Cloud overview
- SAP: Sales and Service Cloud evolution to V2
- SAP: Business AI packages and pricing
- SAP Support: Maintenance strategy for S/4HANA and Business Suite 7
- MuleSoft: SAP S/4HANA OData Connector
- MuleSoft: SAP Connector
- Salesforce: Sales Cloud pricing
- Salesforce: Service Cloud pricing
- Salesforce: Agentforce pricing