Case study
Enterprise MDM platform for a global agriculture machinery leader
A live, multi-region master data platform unifying 6+ systems into a single customer profile with automated GDPR consent. One of three technical architects - I technically owned a dedicated workstream end to end for ~1 year.
A live, multi-region master data platform unifying 6+ systems into a single customer profile with automated GDPR consent. I joined the in-flight program as one of three technical architects and technically owned a dedicated workstream for ~1 year.
Context
A global agriculture machinery manufacturer - $10B+ revenue, 22,000+ employees, operations across EMEA, NA and SA. By the time I joined, an enterprise MDM program was already running, consolidating a customer base of ~10M Accounts and ~40M Contacts previously scattered across multiple Salesforce orgs and customer-facing applications.
Role
Salesforce Technical Architect - one of three architects on the vendor side. I joined an established, in-flight program and owned one workstream end to end for ~1 year: authoring technical designs and driving delivery in collaboration with Product, BAs and the stream team.
System landscape
| Layer | Components |
|---|---|
| Sources | Salesforce orgs (warranty registration, dealer data), customer-facing apps |
| Integration | Informatica ETL, MuleSoft Anypoint, Platform Events + CDC |
| MDM core | Salesforce Data Cloud; Databricks (dedup + stewardship); DemandTools (merge/validation) |
| Consent & privacy | Salesforce Privacy Center (consent, lawful basis, retention) |
| Identity | Azure B2C |
| Consuming surfaces | Experience Cloud, Adobe Experience Manager, corporate apps (IoT Connect, telemetry) |
| Delivery | Copado |
What I drove
- Raised golden-record mastering from 70% to 80% of customer data
- Improved duplicate auto-reconciliation from 45% to 60%
- Reduced auto-merge defects, hardening merge reliability across 6+ integrated source systems
- Drove EMEA consent intake from 5+ source systems - aligning per-system rules and partnering with owning teams to submit via a shared API
- Surfaced consent reporting in Tableau
- Applied retention policies to consent data
Timeline & team
~1 year, completed early 2025. Vendor side: 3 technical architects across workstreams, plus BAs, developers, DevOps and QA.