Customer 360 Architecture for a Global Fashion Brand

Situation

Lacoste, the French fashion house, needed to unify its global CRM architecture around a Customer 360 vision: a single complete view of every customer across all touchpoints and channels. The engagement involved directing a €2M+ CRM portfolio and securing Global Executive Board validation for a 5-year digital roadmap that would frame how Lacoste used Salesforce for the next half-decade.

The stakes were high. Board-level programmes carry a different quality of scrutiny than standard delivery engagements. Every architectural decision would be visible to the people who controlled the budget, the timeline, and the decision to proceed. Success had to be defined before a single line of configuration was written.

Six business units sat behind the programme: in-store retail, e-commerce, marketing, service, loyalty, and B2B wholesale. Each generated its own version of the same customer, on its own data model, with its own refresh cadence. The architecture function had to deliver one definition of “customer” that all six could agree on, then design the data layer that made it work.

Challenge

“Customer 360” is simultaneously the most-cited goal in enterprise CRM and the hardest to actually deliver. It requires unifying data generated by fundamentally different systems: in-store POS, e-commerce platforms, marketing automation, customer service, loyalty programmes, and B2B wholesale accounts. Each system generates its own version of the same customer. Each operates on its own data model, its own identifiers, and its own refresh cadence. Unifying them is not a configuration task. It is an architecture problem.

The organisational challenge matched the technical one. Six business units needed to align behind a single architectural vision. A 30-person cross-functional team needed to execute in parallel across workstreams. Any failure in stakeholder alignment would surface as a launch failure, and the programme had no tolerance for that outcome given its board-level visibility.

The risk profile was also structural. Programmes of this scale and complexity typically surface failure conditions late, after significant investment, when scope changes are expensive and organisational patience is depleted. The architecture function had to identify and resolve these risks before they became delivery problems, not after.

What I told the Global Executive Board at the kickoff review

By the time we are deep into delivery, the architecture decisions are fixed. Either we make them deliberately now, with the data layer the goal, or the six business units make them by default through their own systems.

Action

The architectural foundation was a unified customer data layer that resolved identity across all six channels: in-store, online, wholesale, service, loyalty, and marketing. Rather than patching point-to-point integrations between existing systems, the architecture was designed as a single customer record of truth with well-defined ingestion patterns for each data source.

Defining “customer” took longer than configuring the integrations. Six business units, each with legitimate but different perspectives, had to agree on identity resolution rules, household relationships, product ownership attributes, and engagement history structure. The architecture function held the line on the canonical model and gave each business unit room to extend it where their channel genuinely needed local fields. The result was one model that six units owned, not a compromise nobody respected.

Result

The €2M+ CRM portfolio was delivered on time with the Customer 360 architecture operational across all six business units. The 50+ strategic risks identified pre-launch were resolved before they reached delivery. None became launch-blocking issues. All six business units achieved alignment behind the unified architecture.

The Global Executive Board validated the 5-year digital roadmap, providing the organisational commitment that a multi-year architecture requires. The 30-person cross-functional team executed the transformation with a clarity of purpose that multi-stakeholder programmes rarely achieve.

The Customer 360 architecture also established a data foundation that anticipates where Salesforce is going. Data Cloud was purpose-built to deliver exactly the unified customer view that was architected at Lacoste: identity resolution across channels, unified profile as the basis for all activation, real-time segmentation replacing batch processes. The architecture thinking is identical whether the implementation uses custom integration or Data Cloud. The difference is execution speed. With Data Cloud, the identity resolution and unification that took months to build custom now takes weeks to configure. The architecture decisions about what defines a customer, how channels relate, and what the activation model requires do not change.

Reflection

This pattern works when scrutiny is high, when alignment across business units is non-negotiable, and when leadership accepts that the data layer is the architectural decision rather than a downstream side effect. It is the right call when a board-level roadmap is in play and the architecture has to outlast the current implementation choices.

It works less well when there is no scrutiny budget for risk work upfront. Risk registers compress under pressure and lose their value if treated as a one-time artefact rather than a continuous control.

Worth doing earlier: the canonical customer definition. Six business units can debate it for months once delivery has started. Pinning it down before kickoff is what made every later integration decision possible without re-litigating the foundation.

Technologies used: Salesforce Sales Cloud, Service Cloud, Marketing Cloud, custom integration layer, data architecture design, stakeholder roadmap methodology, risk management framework