What Do SAP CX Consulting Agencies Actually Do?

You’ve decided on SAP CX. Now you need someone to help you build it. But what do consulting agencies actually deliver? And how do you tell them apart when every single one claims to do the same thing?

I’ve been on both sides of this table for years. I’ve been the customer evaluating agencies, and I run one. So I’ll give you the honest version of what you’re buying, what the delivery models look like, and what things actually cost in DACH markets.

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. Here’s what a full-service SAP CX agency actually delivers.

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 gets decided. Skimp here and you’ll pay for it ten times over during the build.

Solution architecture. The technical blueprint: data model, extension strategy, integration patterns, BTP service selection. This happens before anyone writes a line of configuration. Skip it and you end up with a mess that’s expensive to untangle later.

Implementation and configuration. The build itself. Configuring Sales Cloud V2, Service Cloud V2, or Commerce Cloud according to the scope document. Sprint delivery, demo sessions, UAT.

Integration development. Connecting SAP CX to ERP, marketing automation, external data sources, third-party tools. This is almost always a separate workstream from configuration. And it’s almost always under-estimated. Every single project. We warn people and they still under-estimate it.

Change management and training. End-user training, key-user workshops, documentation, adoption tracking. Fifty-one per cent of companies experience operational disruptions at go-live (Panorama Consulting, 2025). Most of those disruptions are adoption failures. The technology works. People don’t know how to use it.

Managed support. Post-go-live help: bug fixes, configuration changes, quarterly update impact analysis, ongoing optimisation. Some agencies offer this as a retainer. Others disappear after go-live. Ask upfront.

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 end up in.

Fixed-scope, fixed-price. The agency commits to defined deliverables for a set amount. If they go over, it comes from their margin. Works best for implementation projects with a well-defined outcome. Forces honest scoping, because the agency loses 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 work, R&D, proof-of-concepts. The risk sits with you. If it runs long, you pay more.

Hybrid. Fixed-scope for the implementation, T&M for discovery and post-go-live support. Often the most practical model for SAP CX projects. Price certainty for the build phase, flexibility for the unknowns.

One question cuts through the decision: do you know exactly what you need? If yes, fixed-scope. If not, start with a T&M discovery phase, then switch to fixed-scope for the build. That way nobody’s guessing.

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

Organisations that engage experienced ERP consultants report an 85% success rate (Panorama Consulting, 2025). But “experienced” means different things depending on firm size.

Large consultancies (Accenture, Deloitte, IBM, NTT DATA) bring global reach, deep bench strength, multi-product capability. They can staff a 30-person project across three time zones. The tradeoff? The senior architects who win the deal are often not the people who deliver it. Junior consultants learning V2 on your budget. We’ve seen it happen. More than once.

Boutique agencies (10-50 people) give you senior attention through the entire project. The people who scope are the people who build. Tradeoff: smaller bench means less flexibility if someone leaves, and they may not have every niche specialisation in-house.

Solo freelancers offer the lowest cost and highest flexibility. No overhead. Tradeoff: single point of failure. Illness, another project, holiday. Your project stops.

For mid-market SAP CX projects (CHF 50K-500K), boutique agencies typically deliver the best value. Senior expertise without paying for the overhead of a large firm’s sales team, office space, and management layers. I’m biased (obviously), but I reckon most people in the DACH market would agree with that assessment.

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 the noise. Here’s what to actually look at.

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

2. Named team. Who specifically will work on your project? What’s their SAP CX background? If the agency won’t name the team before you sign, they don’t have the team yet. That’s a red flag.

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

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

5. Integration capability. In-house BTP developers and integration architects, or do they subcontract? Nearly half of C-suite executives say more than 30% of IT projects go over budget (BCG, 2024). Integration is the top reason.

6. Methodology. SAP Activate? Working software within the first month? Or three months of blueprinting before you see anything? Nota bene: long blueprinting phases often mean the agency is figuring things out on your clock.

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. 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 vary by scope complexity, integration requirements, and how many markets and languages are 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 handles large-scale, multi-product SAP landscapes: S/4HANA, SuccessFactors, Ariba, and CX together. An SAP CX agency specialises in customer experience specifically. For CX-only projects, a specialist 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?

Depends on whether they genuinely have expertise in both. Some agencies are strong in Sales/Service Cloud V2 but weak in Commerce (or the other way around). Ask for separate references for each product. Two specialists may beat one generalist who’s only spot on in one area.

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

Use SAP’s Partner Finder tool. Enter the name, check the tier (Silver, Gold, Platinum), certified competencies, and specialisations. Then cross-reference with direct questions about V2 delivery. Partnership tier alone 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 (Sales + Service + ERP integration): 6-12 months. Average ERP 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 I’d strongly recommend it. Most agencies offer paid discovery workshops (2-5 days) where the assigned consultant scopes your project. It’s a working relationship test before committing to a full implementation contract. If the workshop doesn’t go well, you’ve spent CHF 5,000-15,000 and learned something. Not CHF 200,000.