ADR / 006

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.

Reference pattern

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

  1. D01

    One lifecycle and data model for global reporting

  2. D02

    Legal and fiscal differences are real

  3. D03

    The shared platform must stay upgradeable

  4. D04

    Local teams need controlled autonomy

03Options considered

Options considered: when each would be the right choice, what it costs, and the verdict under these premises
OptionRight whenCost / trade-offVerdict
Country copies of the configurationSpeed of the first rollouts matters more than a shared modelEvery global change multiplies; the models drift apartRejected
A separate platform per regionUnrelated businessesNo shared customer or pipeline viewRejected
Global core, configuration points, registered extensionsA shared model with legitimate differencesNeeds a variation register and governanceSelected

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.

  1. Change & release

    A global release is tested once per configuration point, not once per country.

  2. Data model

    Local fields are declared extensions; global fields are never redefined.

  3. Reporting

    Reports stay comparable because stage and KPI definitions cannot vary.

  4. 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:

01

A subsidiary’s business diverges enough to need its own lifecycle.

02

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.

  1. Systems case / 05Designing a global CRM with a stable core and controlled local variationSeparating the global CRM core from configurable variation, integration mapping and rare local extensions—so the platform stays upgradeable, testable and comparable.Systems & CRM ArchitectureDigital Operating ModelData & IntegrationsArchitecture case · 8 min

Decisions this one depends on, or constrains.

  1. ADR / 016Record every local variation with a reason, owner, scope, cost and review dateLocal differences are decisions, not habits. Each one is classified—global change, configuration, local extension or rejected—and recorded with its reason, owner, scope, cost and review date.Proposed patternOperating model · Variation · Governance