Skip to content
What Do SAP CX Consulting Agencies Actually Do?
Insights · ·7 min read

What Do SAP CX Consulting Agencies Actually Do?

Dario Pedol

Dario Pedol

CEO & SAP CX Architect, Spadoom AG

Share

You’ve decided to implement SAP CX. Now you need a consulting agency to help you do it. But what do these agencies actually deliver? And how do you compare one against another when they all claim to do the same thing?

This guide breaks down the services SAP CX consulting agencies offer, the delivery models they use, and the cost structures you’ll encounter. It’s meant to help you understand what you’re buying — before you sign anything.

TL;DR: SAP has over 24,000 partners worldwide (Houlihan Lokey, 2024). SAP CX consulting agencies offer six core services: discovery workshops, solution architecture, implementation, integration, change management, and managed support. The delivery model — fixed-scope, time-and-materials, or hybrid — determines how risk is shared. Evaluate agencies on service depth and V2 delivery experience, not partnership tier alone.

What Services Do SAP CX Agencies Offer?

The customer experience management market reached $15.55 billion in 2025, growing at 15.8% CAGR (Grand View Research, 2025). At that scale, agencies have specialised into distinct service lines. Here’s what a full-service SAP CX agency typically offers.

Discovery and scoping. A paid workshop (typically 2-5 days) where the agency maps your business processes, identifies integration points, and produces a scope document with deliverables and estimates. This is where project success or failure is usually determined.

Solution architecture. Designing the technical blueprint — data model, extension strategy, integration patterns, and BTP service selection. This happens before anyone writes configuration.

Implementation and configuration. The build itself — configuring SAP Sales Cloud V2, Service Cloud V2, or Commerce Cloud according to the scope document. Includes sprint delivery, demo sessions, and UAT.

Integration development. Connecting SAP CX to ERP, marketing automation, external data sources, and third-party tools. This is almost always a separate workstream from configuration.

Change management and training. End-user training, key-user workshops, documentation, and adoption tracking. Fifty-one per cent of companies experience operational disruptions at go-live (Panorama Consulting, 2025) — most are adoption failures, not technology failures.

Managed support. Post-go-live support: bug fixes, configuration changes, quarterly update impact analysis, and ongoing optimisation. Some agencies offer this as a retainer; others don’t.

SAP CX Agency Services: Typical Effort AllocationDiscovery5-8%Architecture8-12%Implementation30-40%Integration20-30%Change Mgmt10-15%Testing / UAT10-15%Based on Spadoom project data across 25+ SAP CX implementationsIntegration consistently consumes more effort than initially estimated
Integration and change management are the most under-budgeted service areas. Projects that allocate appropriately finish on time.

How Do Delivery Models Differ?

Only 48% of digital initiatives meet or exceed their business outcome targets (Gartner, 2024). The delivery model you choose affects which half you land in.

Fixed-scope, fixed-price. The agency commits to defined deliverables for a fixed amount. Overruns come from their margin. Best for implementation projects where the outcome is well-defined. Forces the agency to scope honestly — they lose money if they get it wrong.

Time-and-materials (T&M). The agency bills by the hour or day. You pay for time consumed, regardless of output. Best for genuinely uncertain scope — advisory engagements, R&D, proof-of-concepts. Risk sits with you. If the project takes longer, you pay more.

Hybrid. Fixed-scope for the implementation, T&M for discovery and post-go-live support. This is often the most practical model for SAP CX projects — you get price certainty for the build phase while keeping flexibility for the unknowns.

Which model should you choose? Ask yourself: do I know exactly what I need? If yes, fixed-scope. If not, start with a T&M discovery phase, then switch to fixed-scope for the build.

What’s the Difference Between Large Consultancies and Boutique Agencies?

Organisations that engage experienced ERP consultants report an 85% success rate in implementations (Panorama Consulting, 2025). But “experienced” means different things at different firm sizes.

Large consultancies (Accenture, Deloitte, IBM, NTT DATA) offer global reach, deep bench strength, and multi-product capability. They can staff a 30-person project across three time zones. The trade-off: the senior architects who win the deal often aren’t the people who deliver it. Junior consultants may be learning V2 on your budget.

Boutique agencies (10-50 people) offer senior-level attention throughout the project. The people who scope are the people who build. The trade-off: smaller bench means less flexibility if a team member leaves, and they may not have every niche specialisation in-house.

Solo freelancers offer the lowest cost and highest flexibility. No overhead. The trade-off: single point of failure. If they get sick or take another project, yours stops.

For mid-market SAP CX projects (CHF 50K-500K), boutique agencies typically deliver the best value. You get senior expertise without paying for the overhead of a large firm’s sales team, office space, and management layers.

How Do You Compare Agencies Beyond the Sales Pitch?

More than two-thirds of large-scale tech programmes miss time, budget, or scope targets (BCG, 2024). A structured comparison process cuts through marketing claims.

Compare on these dimensions:

  1. V2 delivery experience. How many SAP Sales Cloud V2 or Service Cloud V2 projects have they completed? Not started — completed. V1/C4C experience doesn’t transfer automatically.

  2. Named team. Who specifically will work on your project? What’s their SAP CX experience? A partner who won’t name the team before you sign is a partner who doesn’t have the team yet.

  3. Pricing model. Do they offer fixed-scope for implementation work? A partner confident in their estimates will commit to a fixed price. A partner who insists on T&M for a standard implementation may not trust their own scoping ability.

  4. Go-live track record. What percentage of their projects went live on the committed date? Can you speak to references — directly, not through curated testimonials?

  5. Integration capability. Do they have in-house BTP developers and integration architects? Or do they subcontract integration work? Nearly half of C-suite executives say more than 30% of their IT projects are over budget and late (BCG, 2024) — integration is the top reason.

  6. Methodology. Do they follow SAP Activate? Do they deliver working software within the first month? Or do they blueprint for 3 months before you see anything?

What Should You Expect to Pay?

Average ERP implementation timelines have dropped from 15.5 months to 9 months, driven by SaaS adoption and side-by-side extension patterns (Panorama Consulting, 2025). Shorter timelines generally mean lower total cost — but not always lower day rates.

In DACH markets, typical ranges for SAP CX consulting:

  • Discovery workshop (2-5 days): CHF 5,000-15,000
  • SAP Sales Cloud V2 implementation: CHF 80,000-250,000 (3-6 months)
  • SAP Service Cloud V2 implementation: CHF 60,000-200,000 (3-5 months)
  • Commerce Cloud implementation: CHF 150,000-500,000+ (4-9 months)
  • Senior consultant day rate: CHF 1,800-2,500/day
  • Managed support retainer: CHF 3,000-10,000/month

These ranges vary by scope complexity, integration requirements, and the number of markets/languages involved. Compare on value delivered — not cost per day.

FAQ

What’s the difference between an SAP CX agency and a systems integrator?

A systems integrator (SI) handles large-scale, multi-product SAP landscapes — S/4HANA, SuccessFactors, Ariba, and CX together. An SAP CX agency specialises in the customer experience suite specifically. For CX-only projects, a specialised agency typically delivers faster because CX is their core competency, not a side practice.

Should I use the same agency for Sales Cloud and Commerce Cloud?

It depends on whether they have genuine expertise in both. Some agencies are strong in Sales/Service Cloud V2 but weak in Commerce Cloud (or vice versa). Ask for separate references for each product. Using two specialists is better than using one generalist who’s strong in only one area.

How do I verify an agency’s SAP partner status?

Use SAP’s Partner Finder tool. Enter the agency name to see their partnership tier (Silver, Gold, Platinum), certified competencies, and specialisations. Cross-reference with direct questions about V2 delivery experience — partnership tier doesn’t guarantee product-specific expertise.

What does a typical SAP CX project timeline look like?

SAP Sales Cloud V2: 3-6 months. Service Cloud V2: 3-5 months. Commerce Cloud: 4-9 months. Multi-product implementations (e.g., Sales + Service + ERP integration): 6-12 months. Average ERP implementation timelines have dropped to 9 months with SaaS adoption (Panorama Consulting, 2025).

Can I start with a small engagement to test an agency?

Yes, and you should. Most agencies offer paid discovery workshops (2-5 days) where the assigned consultant scopes your project. This gives you a working relationship test before committing to a full implementation contract. If the discovery workshop doesn’t go well, you’ve spent CHF 5,000-15,000 — not CHF 200,000.

SAP CXCX ConsultingPartner SelectionSAP Sales Cloud V2Implementation
Next step

The Full SAP CX Portfolio

Explore all nine SAP CX solutions — from sales and service to e-commerce, marketing, and loyalty.

Related Articles

Ask an Expert