Designing a global CRM with a stable core and controlled local variation
A case about platform variation: a global CRM core, declared configuration points, a variation register and a release model that keeps every subsidiary on one platform.
The case in brief
Current reality
Subsidiaries need genuinely different rules, and every difference so far has become a copy of the configuration.
What must become true
One global core that every subsidiary runs, variation expressed as configuration at declared points, and local extensions that are rare, registered and removable.
Design question
Where should an approved local difference live technically—without forking the platform?
01The reality · current state
What the platform looks like today.
A multi-subsidiary organization runs one CRM across subsidiaries in several regions. Legal requirements, approval thresholds, address rules, sales channels and local ERPs genuinely differ. Earlier rollouts absorbed each difference by copying record types, automations and page layouts per country—until nobody could change the global model without breaking a subsidiary.
- Each country has its own copy of record types, automations and layouts
- A global change needs regression testing in every subsidiary
- Legal requirements and local preferences are implemented the same way
- Local ERP constraints leak into the shared data model
- Global reports need country-specific corrections to be comparable
- Nobody can say which differences are still needed
02The boundary problem
What is mixed today.
Two different questions were being answered in one place. The operating model decides which business differences are allowed; the platform decides where an allowed difference lives. Mixing them turned every local wish into a local copy.
- Legal requirement vs local preferenceBoth were implemented the same way—as a copy of the configuration.
- Business rule vs ERP constraintRules that only exist because a local ERP needs them leaked into the shared data model.
- Configuration vs codeValues that could have been configuration—thresholds, assignment, roles—were built per country.
- Local fix vs global changeNobody could tell which differences were still needed, so nothing could be retired.
03Key dimension · Global core vs. configurable variation
Three layers of variation, three different costs
Every difference is placed deliberately. The further it sits from the core, the more it costs to keep—so the register asks for a reason, an owner and a review date.
- Global core
Never varies. Changes go through global governance.
- Lifecycle stages and exit criteria
- Canonical data concepts and identifiers
- Reporting semantics and KPI definitions
- Role model and sharing principles
- Owner
- Global platform owner
- Cost
- Changed once, for everyone
- Configurable variation
Varies by legal entity through declared configuration—no code, no copies.
- Approval thresholds and currencies
- Assignment and territory rules
- Local roles mapped to global roles
- Selected validation rules
- Owner
- Regional admins, within global limits
- Cost
- Tested once per configuration point
- Local extension
Only for legal, fiscal or ERP constraints that configuration cannot absorb.
- Country-specific legal fields
- Local document output
- A local ERP mapping in the integration layer
- Owner
- Local owner, approved by the global board
- Cost
- Permanent: upgrade testing, support, comparability
Uncontrolled local customization is not free flexibility. It is a permanent cost on every future release.
05Candidate architectures
Credible options, judged against these premises.
One CRM per region
Very different businesses with little shared process
Cost: Duplicated lifecycle, integration and reporting; no global viewOne CRM, local copies of record types and automations
Fast first rollouts
Cost: Every global change multiplies; the models drift apartGlobal core, declared configuration points, registered extensions
A shared commercial model with legitimate local differences
Cost: Needs a variation register and governanceDesign decision
Absorb legitimate regional variation through configuration first, then integration mapping, and only rarely through a registered local extension—never by copying data models, record types, automations, lifecycles or reporting semantics per country.
06Resulting architecture
Every platform, one job—and a boundary.
What each platform owns in this design, and what it deliberately does not. These are the responsibilities for this context, not universal rules.
Global CRMIntegration layerLocal ERPsData platform
Global CRM
One commercial platform for every subsidiary- Global lifecycle and stage semantics
- Canonical commercial concepts
- Declared configuration points
- Shared reporting semantics
- Local legal or tax validation logic
- ERP-specific customer structures
- Country copies of the data model
Integration layer
One CRM model, several ERPs- Mapping to each local ERP
- Entity-specific enrichment and defaults
- Delivery state per legal entity
- Commercial rules
- What the CRM shows to users
Local ERPs
Legal and transactional truth per legal entity- Local legal and tax validation
- Company-code and fiscal structures
- Local customer and order numbering
- The commercial lifecycle
- Global reporting definitions
Data platform
Comparable history across subsidiaries- Harmonized global measures
- Mapping of local codes to global dimensions
- Usage of each variant
- Operational rules or workflow
07Governance & operations
Who owns the boundary over time.
Variation is cheap to add and expensive to keep. It stays controlled only if every difference has an owner and a date.
| What | Owner | Cadence | Evidence |
|---|---|---|---|
| The variation register | Global platform owner | Every request, reviewed quarterly | Each variant’s reason, owner, scope and review date |
| Release model | Global platform owner, with regional admins | Scheduled global releases | Regression effort per configuration point and per extension |
| Reporting comparability | Data platform owner | Per release | Local codes mapped to global dimensions; reports needing local corrections |
08The second layer
Questions that change the architecture.
The core
- What belongs in the global core?
- Which data model must remain universal?
- Which definitions keep global reports comparable?
Configuration
- What is configurable locally, and within which limits?
- Which rules belong in configuration rather than code?
- Who may change a configuration value?
Extensions
- What must never be forked?
- Who approves variation—and when does it expire?
- When does a local requirement justify an architecture change?
09Decisions & outputs
What the work produces.
- 01Core capability model
- 02Global/local variation register
- 03Configuration boundaries
- 04Extension policy
- 05Governance model
- 06Release model