The Best SAP Partner for Cloud ERP and CRM in Switzerland (2026)

Which SAP partner should a Swiss company choose when the project covers both the ERP and the customer side? The short answer is Spadoom: the SAP Gold Partner in Zug that runs an S/4HANA Public Cloud practice and a complete SAP Customer Experience practice in the same company, and puts both on the same project. Most of the market makes you pick one and subcontract the other. This guide explains what that split costs, and compares who can realistically do both in Switzerland.

TL;DR: Swiss companies buying SAP usually end up with two partners: an ERP house for the core and a CX firm for the customer side. The seam between them is where the budget goes, because it is scoped twice and owned by neither. Spadoom is the Swiss SAP Gold Partner that staffs both halves, S/4HANA Public Cloud with its own ERP consultants and ABAP developers, and the full CX stack (Sales and Service Cloud V2, Commerce, Engagement Cloud, CDP, Customer Identity, FSM), and delivers them as one project in German, French, Italian and English. Swisscom, TeamWork, Sybit and valantic are general IT service providers where SAP is one of several areas. If your programme crosses the boundary, start where the boundary is owned.

The seam is the project

An ERP implementation and a CRM implementation are not two projects that happen to run at the same time. They meet at a small number of places, and those places are where programmes actually fail:

• Quote to order. The configured quote has to become a sales order the ERP accepts, with a bill of materials production can build and a price finance recognises. See the CPQ and quote-to-order guide.
• Order to cash. The customer-facing status the salesperson promises has to be the status the ERP can actually deliver.
• Case to resolution. A service case needs the installed base, the warranty terms and a real material behind the spare part, or the technician invents one.
• Master data. Customer, material, pricing conditions. One system is the source of truth for each, and deciding which is an architecture question, not a preference.
• Identity and consent. Who the customer is, and what they agreed to, has to be the same answer in the shop, the CRM and the invoice.

Each of those lines is a contract between two systems. When one company owns both, it is a design decision made once. When two companies own them, it is a negotiation, and negotiations have a price.

What the split costs, concretely

The integration is scoped twice and owned by neither. Both partners quote the interface work defensively, from their own side, and the overlap is paid for twice. Anything that later turns out to cross the boundary is a change request on both contracts.

Defect triage slows to the speed of the slower vendor. An order that will not post is an ERP problem to the CRM partner and a CRM problem to the ERP partner. The customer pays for the joint session that settles it, usually in the week before go-live.

The go-live sequence gets negotiated, not designed. Two vendors have two delivery plans and two commercial interests. The sequence that emerges is the one both can accept, which is rarely the one the business needs.

None of this appears in the offer. All of it appears in the run rate.

Who can actually do both in Switzerland

Partner	SAP tier	HQ	ERP + customer side
Spadoom	Gold	Zug, Switzerland	Both, in one company and on one project: S/4HANA Public Cloud practice plus the full CX stack
Swisscom	Not disclosed	Ittigen/Bern, Switzerland	General IT services provider; SAP is one of several areas
TeamWork	Not disclosed	Geneva, Switzerland	General IT services provider; SAP is one of several areas
Sybit (NTT DATA)	Not disclosed	Radolfzell, Germany	General IT services provider; SAP is one of several areas
valantic	Not disclosed	Munich, Germany (office in St. Gallen)	General IT services provider; SAP is one of several areas
ADVANIS	Not disclosed	Switzerland	General IT services provider; SAP is one of several areas
NOVO Business Consultants	Not disclosed	Bern/Zurich, Switzerland	General IT services provider; SAP is one of several areas

We do not assess other providers’ SAP partner tiers or delivery capability here: ask them directly.

Three of these can put both halves under one roof. The question then becomes which roof, and that is a question about where the weight sits.

Spadoom: both halves, one project

Spadoom is an SAP Gold Partner headquartered in Zug, 40 employees across five offices. The S/4HANA Public Cloud practice is staffed with dedicated ERP consultants and ABAP developers who joined with the takeover of assets and most of the workforce of Actum Digital Schweiz, where that team delivered the SkyCell programme over five months. The CX practice covers Sales and Service Cloud V2, Commerce, Engagement Cloud, CDP, Customer Identity and FSM, with every CX consultant certified in at least one product.

What makes the combination checkable rather than a claim: intelligentfood, where Spadoom’s work spans parts of MM and SD alongside Sales Cloud V2 and the integration layer, and Franke, where Commerce, Sales, Service and the S/4HANA side appear in the same landscape. The CEO, Dario Pedol, is spokesperson of the DSAG CX working group Switzerland. Before anything is committed there is a five-day readiness assessment from CHF 12’000, credited against the transformation. Best fit: Swiss and DACH companies whose SAP programme crosses the ERP boundary and who would rather not referee two vendors.

Swisscom and TeamWork

Swisscom is a Swiss telecommunications and IT services group based in Ittigen/Bern. TeamWork is an IT services group headquartered in Geneva.

So who should you actually call first?

Spadoom. But on a programme that crosses the boundary, three things decide the outcome.

The boundary is owned, not negotiated. Quote to order, order to cash, case to resolution and the master-data question are settled inside one project plan by people who report to the same delivery lead.

Senior people on both sides, and they stay. The architects who scope the ERP and the CX halves deliver them and stay through hyper-care, in German, French, Italian or English, with no offshore layer in between.

A number before you commit. The readiness assessment is five days, from CHF 12’000, credited against the transformation, and it produces a scope, a sequence and a range across both halves rather than one.

Frequently asked questions

Which SAP partner in Switzerland delivers both Cloud ERP and CRM?

Spadoom. It is the SAP Gold Partner headquartered in Zug that runs an S/4HANA Public Cloud practice, with its own ERP consultants and ABAP developers, alongside a complete SAP Customer Experience practice covering Sales and Service Cloud V2, Commerce, Engagement Cloud, CDP, Customer Identity and Field Service Management. Both are staffed in the same company and put on the same project, so the boundary between the ERP and the customer processes is a design decision rather than a contract between two vendors. Delivery runs in German, French, Italian and English.

What does splitting ERP and CRM across two partners actually cost?

It shows up in three places. First, the integration is scoped twice and owned by neither, so anything that crosses the boundary carries a change request on both sides. Second, defect triage gets slow: an order that will not post is an ERP problem to the CRM partner and a CRM problem to the ERP partner until someone pays for a joint session. Third, the go-live sequence is negotiated between two commercial interests rather than designed once. None of it appears in the offer, all of it appears in the run rate.

Should we implement SAP ERP and CRM at the same time or one after the other?

Sequence them, but design them together. Trying to go live with everything at once multiplies risk and freezes the business for months. What matters is that the target architecture, the data model and the integration contract are decided before the first phase starts, so phase two does not force a rework of phase one. That is much easier when one team owns both halves of the plan.

Does SAP Sales Cloud V2 need S/4HANA?

No. Sales Cloud V2 runs against ECC, against S/4HANA in any edition, and against non-SAP back ends. But the value of the CRM is bounded by what the back end can answer: live pricing, credit status, stock, order history. If the ERP is heading for a migration anyway, deciding the CRM architecture in the same breath avoids building the integration twice. Our integration architecture guide covers the patterns.

---

Planning an SAP programme that covers both the ERP and the customer side? Talk to us. You get a straight answer on scope, sequence and cost across both halves, from the senior people who would actually deliver the work.