How to Choose an SAP CX Implementation Partner

Choosing an SAP CX partner comes down to two things: whether the firm has delivered your exact product, and whether the people it puts on your project are the ones who did it. Everything else (the badge, the slides, the day rate) matters less than those two facts. The cost of getting it wrong is rarely just money. A stalled implementation typically costs a year, internal goodwill and the patience you will need for the restart.

Below are eight questions to ask any SAP CX partner, us included, followed by how to evaluate the individual consultants they propose. If our answers do not hold up, choose someone else.

TL;DR: Ask for completed V2 projects on your product, the names of the people who will do the work, and a reference you can call. Check how the partner prices, scopes the ERP integration and handles change. Judge consultants on hands-on project detail, not on certificates alone. Start with a short paid discovery workshop before you sign the full project.

What an SAP CX partner should deliver

Before comparing firms, be clear about what you are buying. A full SAP CX engagement covers six things, and a partner should be able to name who does each one:

• Discovery and scoping: a short workshop that maps your processes and integration points and ends in a scope with deliverables and estimates.
• Solution architecture: data model, extension strategy, integration patterns and the SAP BTP services you will need, decided before configuration starts.
• Implementation: configuring Sales Cloud V2, Service Cloud V2 or Commerce Cloud in short iterations with regular demos.
• Integration: connecting CX to the ERP, marketing and other systems, usually as its own workstream.
• Change management and training: key-user workshops, end-user training and adoption tracking.
• Support after go-live: fixes, configuration changes and impact checks for SAP’s regular releases.

If a partner offers only some of these, ask who covers the rest and who is accountable when a problem crosses the boundary.

Question 1: Do they have real V2 experience?

Sales Cloud V2 and Service Cloud V2 are different products from SAP Cloud for Customer (C4C): different architecture, data model, extension framework and integration patterns. A partner with many C4C projects has not automatically earned the right to deliver V2.

Ask them:

• How many Sales Cloud V2 or Service Cloud V2 projects have you completed? Not started: completed.
• Can you show me a working V2 system with real configuration?
• Which SAP BTP services have you used in production V2 projects?

If the answers are vague, the team would be learning V2 on your budget.

Question 2: Who actually works on your project?

The most common complaint about large consultancies is the handover: impressive architects in the proposal meeting, a different team after signature.

Ask them:

• Give me the names and CVs of the people who will work on my project.
• What share of their time is allocated to us?
• What happens if one of them leaves?
• How many years of SAP CX experience does each person have?

A good partner names people. A partner that describes “roles” and promises to “finalise staffing after kickoff” does not yet have the team.

Question 3: Fixed price or time and materials?

Time and materials: the partner bills by the day. Suitable for genuinely uncertain work such as advisory, proofs of concept or discovery.

Fixed scope, fixed price: the partner commits to defined deliverables for an agreed amount, and overruns come out of its margin. Suitable when the outcome can be defined.

Hybrid: discovery and support on time and materials, the implementation at a fixed price. For most SAP CX projects this is the most practical model: price certainty for the build, flexibility for the unknowns.

A partner confident in its estimate will offer a fixed price for a well-defined implementation. Ask how change requests are priced and approved, whichever model you choose.

Question 4: What is their go-live track record?

Ask them:

• Which of your SAP CX projects went live on the committed date, and which did not?
• Can I have references for three completed projects similar to ours?
• Can I speak directly with the sponsor or project manager on the client side?
• Have you had a project that did not go live? What happened?

A partner who claims it has never missed a date is either very selective about what it counts or not being candid. “Once, and here is what we changed” is the more trustworthy answer. Published customer stories help, because they name the customer and the scope. Ours are on our customer stories page.

Question 5: Do they understand your industry?

SAP CX works across industries, but implementations do not. A manufacturer’s quoting process looks nothing like a retailer’s service desk. The partner should recognise your processes without a long explanation.

Ask them:

• Have you implemented SAP CX in our industry? For which companies?
• What industry-specific problems did you run into?
• How do you handle our regulatory requirements (in Switzerland, the nFADP alongside the GDPR)?

Question 6: What is their SAP BTP capability?

SAP Business Technology Platform is where everything beyond standard configuration happens: custom logic, specialised integrations, external data sources. If your project needs any of that, BTP capability is not optional.

Ask them:

• Do you have BTP developers on your own staff, or do you subcontract?
• Which BTP services have you used in production?
• Can you show me an integration architecture diagram from a previous project?

The last question is a good filter. A partner that has done the work can show the diagram.

Question 7: How do they handle the ERP integration?

Integration is where CX projects most often go off track. In our experience it can take a substantial share of the total effort, so an estimate that treats it as a minor item deserves hard questions.

Ask them:

• Is integration a separate workstream with its own estimate?
• Which middleware do you use, and who builds and monitors the interfaces?
• How do you migrate data, and when do you load real data for the first time?
• What happens when the ERP side does not behave as expected?

This is also where the partner’s scope matters. If the CX partner stops at the CRM and another firm owns the ERP, every interface problem becomes a question of whose responsibility it is. A partner that delivers both S/4HANA Public Cloud and the CX stack can treat that boundary as a design decision instead. We explain why in choosing one SAP partner for Cloud ERP and CRM.

Question 8: Will they start small?

Ask for a paid discovery workshop of a few days, run by the consultants who would deliver the project, before you sign the full implementation. You get a scope you can compare and, more importantly, a test of the working relationship. If the workshop goes badly, you have spent a fraction of the project budget and learned something. A partner that will not do this is telling you something too. What such a workshop should leave behind (decisions, a traced transaction, an agreed ERP and CRM boundary) is described in why good SAP consulting leaves you with decisions, not slides.

How to evaluate the consultants they propose

A strong firm with the wrong person leading your workstream produces the same result as a weak firm. So evaluate the named consultants as well as the company.

Skills that matter:

• V2 product expertise from real projects, not V1 knowledge carried over.
• BTP and integration skills: SAP CAP, SAP Integration Suite or SAP Build from project work. The combination of V2 knowledge and BTP development skill in one person is rarer than either alone.
• Integration architecture: the ability to draw your system landscape and data flows on a whiteboard.
• Iterative delivery: experience with SAP Activate, sprints and user feedback.
• Industry knowledge: familiarity with your sales and service processes.

Certifications: useful as a baseline. Ask for current SAP certifications on the right product (the V2 certification, not C4C; SAP BTP and Integration Suite for technical roles) and check the consultant’s SAP digital badge. We explain partner levels and consultant certifications in what an SAP Gold Partner is. An experienced consultant with a lapsed certificate may still be the better choice; ask why they have not renewed it.

The most revealing question is not technical: “Tell me about a project that went wrong and what you learned.” Someone who cannot answer that has not been in enough real situations.

Green flags: names specific projects and configurations, says what the product does not do well, asks about your business before proposing anything, and pushes back on requirements that do not make sense.

Red flags: cannot name a V2 project they delivered, describes features they “know about” rather than ones they have configured, talks only technology and never adoption, and claims everything is possible.

Red flags in the partner

• No V2 references: C4C case studies presented as equivalent.
• Vague team composition: “we will assign the right resources”.
• Everything custom: building from scratch instead of using standard configuration.
• No methodology: no clear delivery approach or sprint structure.
• No direct contact with references: written testimonials instead of a phone call.
• Unrealistic timelines: a full Sales Cloud V2 implementation with ERP integration in six weeks means someone is underestimating.

If you are shortlisting in Switzerland, our overview of SAP CX consultancies in Switzerland applies these criteria to the firms you are likely to meet. For what goes wrong when partners get this wrong, see why we finish SAP CX projects when others don’t.

If you are choosing a partner for a Swiss project, our page on SAP CX consulting in Switzerland shows how this checklist translates into delivery: languages, offices and the ERP behind the CX.

FAQ

Does SAP Gold or Platinum status guarantee delivery quality?

No. The partner level reflects the company’s SAP business and competencies, not the quality of the team assigned to you. A large partner may have hundreds of consultants and only a handful who know V2. Check the level in the SAP Partner Finder, then ask about the named people.

How long does an SAP CX implementation take?

It depends on scope, integration and the number of countries. Our published Swiss projects give a realistic range: intelligentfood had Sales and Service Cloud V2 live in three months, OPO Oeschger had Phase 1 live three months after we took over, Nussbaum took five months from no central CRM, and Franke’s Commerce Cloud launch took 90 days. A partner should give you a plan with phases, not a single number.

Should I choose a large consultancy or a specialist firm?

Large consultancies offer global reach and a deep bench; specialist firms offer senior attention and the same people from scoping to go-live. For mid-market SAP CX projects, the deciding factor is usually continuity of the named team and whether the partner also covers your ERP side, not the size of the firm.

Should I hire a freelance consultant or go through a partner?

Both can work. A freelancer gives flexibility and lower cost but is a single point of failure: illness or another project stops your work. A partner gives you a bench, a method and accountability. For business-critical implementations, a partner is usually the safer choice.

How much should I budget for change management?

Plan training, key-user workshops and adoption tracking into the scope from the start rather than as an afterthought. Most go-live disruptions are adoption problems, not technical ones, and they are much cheaper to prevent than to fix.

How do I verify a partner’s claims?

Call the references and ask: did the project go live when planned, did the budget hold, did the same people stay throughout, would you hire them again? Published case studies with named customers and SAP awards such as the SAP Quality Award are also verifiable. When you are ready, talk to us and ask us the same questions.