Represent regional variation through configuration, not CRM forks
Legitimate local differences belong in declared configuration points and, rarely, registered extensions—never in copies of the global data model or lifecycle.
Independently created. Contains no employer or client implementation detail, internal names or figures.
01Context
A global CRM serves subsidiaries with genuinely different legal rules, approval thresholds, sales channels and local ERPs. Each rollout copied record types, automations and layouts per country. Global changes now need testing in every subsidiary, and global reports need country corrections.
02Decision drivers
- D01
One lifecycle and data model for global reporting
- D02
Legal and fiscal differences are real
- D03
The shared platform must stay upgradeable
- D04
Local teams need controlled autonomy
03Options considered
| Option | Right when | Cost / trade-off | Verdict |
|---|---|---|---|
| Country copies of the configuration | Speed of the first rollouts matters more than a shared model | Every global change multiplies; the models drift apart | Rejected |
| A separate platform per region | Unrelated businesses | No shared customer or pipeline view | Rejected |
| Global core, configuration points, registered extensions | A shared model with legitimate differences | Needs a variation register and governance | Selected |
Every option is right under some premises. The verdict applies to the context above.
04Decision
Keep the lifecycle, canonical data concepts and reporting semantics in a global core. Express approved variation through declared configuration points—thresholds, assignment, local roles and selected validation. Allow local extensions only for legal, fiscal or ERP constraints, registered with an owner and a review date. Absorb ERP differences in the integration layer, not in the CRM model.
05Consequences
What this choice changes elsewhere in the system.
- Change & release
A global release is tested once per configuration point, not once per country.
- Data model
Local fields are declared extensions; global fields are never redefined.
- Reporting
Reports stay comparable because stage and KPI definitions cannot vary.
- Governance
Every extension has an owner and a review date—and can be retired.
06Revisit when
The decision holds while its context holds. Challenge it when:
A subsidiary’s business diverges enough to need its own lifecycle.
The platform gains native, upgrade-safe support for local variants.
07Where this decision is applied
The decision says why this path was chosen; each case shows how it takes part in a larger architecture.
08Related decisions
Decisions this one depends on, or constrains.