Canyon didn't need a new architecture. They needed someone who could walk into a running SAP + Salesforce estate, find the sync failures, and ship a fix that their own team could own afterwards. No lock-in, no year-long programme. Shop-to-ERP data flowing reliably, in the platform they already pay for.
Canyon asked us in to bring an external perspective on their tech landscape. The symptom: data communication between their legacy systems was breaking — shop to ERP especially. The deeper issue: no experienced architects or engineers on hand to operate and fix the sync problems from the inside.
They had the platforms. SAP as the system of record. Salesforce as the commercial front. SAP Integration Suite in between. What they didn't have was someone who could read the integration layer end-to-end, diagnose why records were drifting, and make surgical fixes without stopping the business.
The ask we accepted: bring senior SAP and data-architecture capacity into the Canyon team, work shoulder-to-shoulder with their own SAP consultants and Salesforce specialist, and leave behind a data-sync setup Canyon could maintain themselves. No parallel programme, no external dependency afterwards.
The frame we agreed on: fast, isolated shipment. Fix the worst data flows first inside SAP Integration Suite, add script-based enhancement where the platform fell short, and lay out a strategy for a longer-horizon data hub — event-based and API-first — that Canyon could decide to build later, on their own timeline.
We started in the SAP Integration Suite — inside the platform Canyon already owned. Flow by flow, we rebuilt the data processes that were failing. Each fix went live on its own, without waiting for a full cutover, and without touching flows that were healthy.
Some flows needed logic the Integration Suite doesn't express natively — reshaping, enrichment, conditional routing. We added targeted scripts rather than bending the platform. Each script was code-reviewed with Canyon's SAP consultants so ownership could transfer on day one.
Customer-visible flows moved off nightly batches toward event-driven synchronisation. Not everywhere — only where the business case was clear. Batches stayed where they were cheap and good enough.
In parallel to the fixes, we wrote a strategy document for Canyon leadership: what a data hub on top of SAP + Salesforce should look like if they decide to build it — event-first, API-first, and explicit about what does and doesn't belong in SAP. No commitment to buy, no vendor recommendation. Their decision, informed.
The shipped work sits inside SAP Integration Suite — no new SaaS, no new vendor. The decisive additions are the individual enhancement scripts and the reshaped data flows, paired with a small set of rules about how SAP and Salesforce are allowed to speak to each other going forward.
On top of that: a strategy memo for an event-based, API-first data hub. Not something we built. Something Canyon can decide to build — on their terms, with a clear starting point. Their architects and SAP consultants were co-authors, not spectators.
Engagement close: end of 2024. Canyon's SAP consultants and Salesforce specialist kept operating the platform throughout. When we left, nothing on the critical path required prodct to stay.
30 minutes with the partner leading [Elements]. We'll tell you within the call whether this shape fits yours.
Canyon's engagement sits under client-grade access terms: architecture, decisions and outcomes shown to named readers only. One short form and the full dossier opens now — plus a signed PDF mirror in your inbox.
~ 30 seconds · instant access + PDF mirror emailed · no marketing follow-up