Choosing a CRM is the easy part. Wiring it into a real enterprise estate so that the customer experience it promises actually holds together end-to-end is where most digital transformation programmes fall short. This is the story of one that didn't.
The real challenge underneath the customer-experience promise
A multi-brand automotive importer and retail group operating six international car brands had made a strategic decision: Salesforce at the centre of customer experience, across sales, after-sales and service. The ambition was clear. The complexity underneath it was significant.
Ten enterprise systems needed to participate: SAP, multiple ERPs, banking APIs from several financial institutions, an e-signature platform, a contact centre, file storage and more. Each carried its own protocols, its own ownership, its own failure modes. Adding point-to-point links for each one would have created exactly the fragile estate the programme was designed to replace.
The integration backbone had to be different. Bidirectional, resilient, observable, and architected to absorb whatever the group launched next, not just what was in scope today. Ampleshift joined as integration architecture lead. The engagement is ongoing.
Architecture leadership, earned across the engagement
From day one, Ampleshift led the integration architecture alongside Salesforce Professional Services. Salesforce PS on the Salesforce side, Ampleshift on MuleSoft and the overall integration design. One coherent architectural narrative across both platforms. No finger-pointing when things needed to change.
The foundation was API-Led Connectivity: System APIs exposing each enterprise system once, Process APIs orchestrating the customer-experience flows, Experience APIs serving Salesforce-side consumers. The estate compounds in value rather than fragmenting with every new project.
Amazon SQS was introduced as the async-messaging spine, on Ampleshift's recommendation, to absorb the operator's volatile release cadence and decouple enterprise systems from each other's failure modes. When peak load hits or an upstream system has a bad moment, the integration layer holds.
CI/CD pipelines on Azure DevOps, Common Assets and the logging framework applied from sprint one. Operational and business dashboards built on top of the estate. The operator now has visibility into the integration layer that didn't exist before.
The numbers that define the programme
The first integration Ampleshift delivered was also one of the most demanding: migrating over 12 million customer and consent records from ERP to Salesforce at a 0.1% error rate. Zero event loss, validated through end-to-end reconciliation. The bar set on the first integration carried into everything that followed.
Today, ten enterprise systems are integrated bidirectionally with Salesforce. A small senior team of two architects and two developers has carried this enterprise-scale work without offshore handoffs or approval-layer drag. The 24/7 maintenance and all-hands deployment posture means the operator never has to wonder who is watching the platform during a release.
From delivery partner to trusted architect
The relationship evolved across the engagement in a way that fixed-term projects rarely allow. Ampleshift became the operator's default route for integration architecture decisions, not because of a contract, but because of trust built through delivery. That depth of trust is what allowed the engagement to grow from an initial brief into a programme covering ten enterprise systems and the Salesforce-at-the-core CX transformation that depends on them.
For multi-brand automotive distributors and importers, the digital transformation challenge is rarely choosing the CRM. It is wiring the CRM into a real enterprise estate so that customer experience is genuinely connected end-to-end. This is what a Salesforce-at-the-core programme, backed by a serious integration architecture, looks like in practice.
