How to Choose an SAP CX Implementation Partner

Choosing the wrong SAP CX implementation partner is one of the most expensive mistakes a company can make. Not because of the contract value — because of the 12-18 months you lose before realizing the project isn’t going to deliver.

We’ve seen it happen. Companies come to us after a failed or stalled implementation with another partner. By that point, they’ve spent the budget, burned internal goodwill, and now need to start over with higher expectations and lower patience.

This guide is genuinely meant to help you evaluate any SAP CX partner — including us. If you ask us these questions and our answers don’t hold up, choose someone else.

Question 1: Do They Have Real V2 Experience?

SAP Sales Cloud V2 and Service Cloud V2 are fundamentally different products from their predecessors (C4C / V1). Different architecture. Different data model. Different extension framework. Different integration patterns.

A partner who delivered 50 C4C projects hasn’t automatically earned the right to deliver a V2 project. The skills don’t transfer 1:1. V2 uses SAP BTP as its extension platform. It requires understanding of SAP Build, custom logic via BTP, and a completely redesigned UI.

What to ask:

• How many SAP Sales Cloud V2 or Service Cloud V2 projects have you completed? (Not started — completed.)
• Can you show me a working V2 demo with real configuration, not a standard demo environment?
• Which BTP services have you used in production V2 projects?

If they can’t answer these specifically, they’re learning V2 on your project.

Question 2: Who Actually Works on Your Project?

This is the question that separates boutique partners from large consultancies. In big firms, the proposal team and the delivery team are different people. The impressive architects in the sales meeting go back to other clients after you sign.

What to ask:

• Give me the names and CVs of the people who will work on my project.
• What percentage of their time is allocated to my project? (50% allocation across 4 projects is not the same as 100% on yours.)
• What happens if one of them leaves? What’s the backup plan?
• How many years of SAP CX experience does each team member have?

A strong partner will name specific people. A weak partner will describe “roles” and promise to “finalize staffing after kickoff.”

Question 3: Fixed Price or Time-and-Materials?

Both models exist for good reasons. But understand the incentive structure.

Time-and-materials (T&M): The partner bills by the hour or day. If the project takes longer, you pay more. The partner has no financial incentive to finish quickly. Good for genuinely uncertain scope — R&D, proof-of-concepts, advisory engagements.

Fixed-scope, fixed-price: The partner commits to a defined set of deliverables for a fixed amount. Overruns come from their margin. The partner has every incentive to scope accurately and deliver efficiently. Good for implementation projects where the outcome is well-defined.

What to ask:

• What is your standard pricing model for SAP CX implementations?
• If fixed-price: how do you handle change requests? What’s the process and typical turnaround?
• If T&M: what mechanisms exist to control costs? Is there a not-to-exceed cap?
• Can you share a sample project budget breakdown? (Not the total — the structure.)

A partner confident in their estimates will offer fixed-price. A partner who insists on T&M for a straightforward Sales Cloud V2 implementation may not trust their own scoping ability.

Question 4: What’s Their Go-Live Track Record?

This seems obvious. It’s not asked enough.

What to ask:

• What percentage of your SAP CX projects have gone live on or before the committed date?
• Can you provide references for 3 completed projects similar to ours?
• Of those references, can I speak directly with the project manager or sponsor on the client side?
• Have you ever had a project that failed to go live? What happened?

Honest partners will answer all four. The last question is especially telling. A partner who says “never” across 100+ projects is either very selective or not being truthful. A partner who says “once, and here’s what we learned” demonstrates maturity.

Question 5: Do They Understand Your Industry?

SAP CX is horizontal — it works across industries. But implementation nuances are vertical. A manufacturer’s sales process (configure-to-order, technical sales, long cycles) is nothing like a retailer’s (high volume, fast turnover, seasonal).

What to ask:

• Have you implemented SAP CX in our industry? Which companies?
• What are the typical industry-specific challenges you’ve encountered?
• How do you handle our regulatory requirements (if applicable)?

Industry experience doesn’t mean they need 20 references in your exact niche. But they should understand your business model and be able to describe how SAP CX fits it — without you having to explain everything from scratch.

Question 6: What’s Their BTP Capability?

SAP Business Technology Platform is the extension layer for all modern SAP CX products. If your implementation needs anything beyond standard configuration — custom business logic, specialized integrations, external data sources — BTP is where it happens.

What to ask:

• Do you have certified BTP developers on your team?
• Which BTP services have you used in production? (CAP, Integration Suite, SAP Build, Workflow Management?)
• Can you show me an integration architecture diagram from a previous project?

A partner who can only configure out-of-the-box features will hit a wall the moment your requirements go beyond standard. And they always do.

Question 7: How Do They Handle Integrations?

Integration is where most SAP CX projects go off the rails. ERP connectivity, middleware, master data synchronization, third-party systems — these are the areas that eat budgets and blow timelines.

What to ask:

• How do you scope integration work? Is it part of the main estimate or a separate workstream?
• What middleware do you typically use? Do you have certified integration consultants?
• How do you handle data migration? What’s your approach to data quality?
• What happens when the integration doesn’t work as expected? (Because it won’t, at least initially.)

The best answer includes: integration as a dedicated workstream, separate testing phases, dedicated integration consultants (not the same people doing CRM configuration), and an explicit error-handling strategy.

Red Flags to Watch For

Beyond the positive indicators, here are warning signs:

• No V2 references. They show you C4C (V1) case studies and claim they’re equivalent. They’re not.
• Vague team composition. “We’ll assign the right resources” means they don’t have specific people available.
• Everything is custom. A partner who wants to build everything custom instead of using standard configuration either doesn’t know the platform or is padding the estimate.
• No methodology. They can’t articulate their delivery approach, sprint structure, or testing strategy.
• Discouraging direct contact with references. “We can provide written testimonials” is not the same as letting you call a client project manager.
• Unrealistic timelines. If a full SAP Sales Cloud V2 implementation with ERP integration is quoted at 6 weeks, someone is underestimating. Deliberately or not, you’ll pay for it.

What About SAP’s Own Partner Tiers?

SAP partner certifications (Gold, Platinum, etc.) indicate a minimum level of competence and SAP investment. They’re a baseline filter, not a guarantee of delivery quality.

A Gold partner with 2,000 consultants may have 5 people who actually know V2. A smaller, specialized partner may have an entire team of V2 experts. The certification tells you about the organization. The questions above tell you about the team that’ll work on your project.

Look at SAP Quality Awards instead. These are given for specific project outcomes — verifiable evidence that the partner delivered successfully.

How We’d Answer These Questions

We’re transparent about our own positioning:

• V2 experience: Every SAP CX project we deliver is on V2. We migrated clients from C4C to V2 and implemented V2 greenfield.
• Team composition: You get names, CVs, and certifications before signing.
• Pricing: Fixed-scope, fixed-price. Change requests are priced separately and approved before work starts.
• Go-live record: 100%. Every project. Verified through client references.
• Industry experience: Manufacturing (Franke, Nussbaum), retail (ANWR Group, SPAR), life sciences (Miltenyi Biotec), distribution (Distrelec).
• BTP: Certified developers. SAP CAP, Integration Suite, and custom extension experience in production.

Are we the right partner for every company? No. We’re focused on SAP CX, we work best with mid-market and enterprise companies, and we’re deliberately small enough to stay senior-only.

But we’ll answer every question on this list — honestly — in our first meeting.

Start the conversation.