Standardizing a global commercial operation before scaling the CRM
Many subsidiaries and one CRM about to scale. Before scaling the platform, the work was to decide what the operation itself must share.
The case in brief
Current reality
Subsidiaries share—or are about to share—one CRM while running different businesses underneath it: different lifecycle meanings, approval cultures, routines and data.
What must become true
One global core every subsidiary runs, declared extension points for legitimate variation, a register that turns every local difference into a decision with an owner and a review date—and governance that keeps the model evolving after go-live.
Design question
What must mean the same thing in every subsidiary—and who decides when a local difference is legitimate?
01The reality · current state
What actually happens today.
A multi-subsidiary organization is preparing to scale one CRM across its subsidiaries. Earlier attempts failed in both directions: a rigid template that subsidiaries worked around, or local freedom that made the process—and its KPIs—impossible to compare. Local preferences arrived presented as requirements, and legal constraints were mixed with habits.
- Subsidiaries at different maturity levels, with different commercial habits and approval cultures
- “Qualified”, “won” and “customer” meant different things in each subsidiary
- Legal and fiscal constraints were mixed with local preferences presented as requirements
- Local ERPs imposed rules the global design never saw
- Management routines differed, so reviews could not rely on common evidence
- Parallel tools kept running beside the CRM
- Nobody owned the decision to allow—or refuse—a local variant
What made one process insufficient?
One template for every subsidiary failed, and so did one per subsidiary. These questions decided what could be shared—and what had to be governed as a difference:
- 01Lifecycle semanticsDo “qualified”, “won” and “customer” mean the same thing everywhere?
- 02Constraint or habitIs the difference required by law or tax—or is it how the team has always worked?
- 03Local system rulesWhich rules come from a local ERP rather than from the business?
- 04Roles and decision rightsWho decides what—especially in small entities with merged roles?
- 05Minimum operating dataWhat must exist everywhere for the global model to work?
- 06Management routinesWhich reviews need common evidence?
- 07Digital maturityWhat can each subsidiary actually adopt, and when?
- 08Evolution after go-liveWho may change the global core once it runs?
A global CRM does not create a global operating model. The operating model has to be designed and governed first.
02Target process
7 stages, 3 roles, 3 systems.
Design decision
Design and govern the operating model first—what is global, what may vary, who decides—and scale the CRM as the implementation of that model.
Each stage sits in the lane that owns it and shows what happens in each system at that moment. Select a stage for its anatomy; read the model through controls, exceptions or automation fit.
Classify the difference
- Trigger
Request logged
- Decision
Is this noise, preference, or a real constraint—legal, fiscal, ERP or market?
- Owner
Global process owner
- System action
The register records the class and links similar requests from other subsidiaries
- Data state
Variation · Classified
- Next stage
03 Impact assessment
- Evidence for the constraint
- Similar requests elsewhere
- The global rule it touches
- A preference is not a constraint: it needs a business case, not an exemption
- Evidence missing — Returned for evidenceDetected: Global process owner · Owner: Local process owner · Returns to 01 Local variation request
Keep human. Telling a constraint from a preference is the core judgement.
- Trigger
Request logged
- Decision
Is this noise, preference, or a real constraint—legal, fiscal, ERP or market?
- Owner
Global process owner
- System action
The register records the class and links similar requests from other subsidiaries
- Data state
Variation · Classified
- Next stage
03 Impact assessment
Information required- Evidence for the constraint
- Similar requests elsewhere
- The global rule it touches
Controls- A preference is not a constraint: it needs a business case, not an exemption
Exceptions- Evidence missing — Returned for evidenceDetected: Global process owner · Owner: Local process owner · Returns to 01 Local variation request
Automation suitabilityKeep human. Telling a constraint from a preference is the core judgement.
- Trigger
03Key dimension · Global core vs. governed local variation
Global template, controlled variation
The template fixes what must be the same everywhere. Variation is allowed only at declared points, with an owner and a review date.
Standardization fails when every difference is treated either as noise or as unique. The register turns each difference into a decision.
04Ownership & decision rights
One accountable role per decision.
| Decision | Local owner | Global owner | Process board | Platform team | Compliance |
|---|---|---|---|---|---|
| 01Declare a local difference | A Accountable | I Informed | Not involved | Not involved | Not involved |
| 02Class a constraint or a preference | C Consulted | A Accountable | Not involved | Not involved | Not involved |
| 03Change a global control | Not involved | R Responsible | C Consulted | Not involved | A Accountable |
| 04Approve a local variant | C Consulted | R Responsible | A Accountable | Not involved | C Consulted |
| 05Choose the extension point | Not involved | C Consulted | Not involved | A Accountable | Not involved |
| 07Retire a variant | C Consulted | R Responsible | A Accountable | Not involved | Not involved |
- 01Declare a local difference
- AAccountable
- Local owner
- IInformed
- Global owner
- 02Class a constraint or a preference
- AAccountable
- Global owner
- CConsulted
- Local owner
- 03Change a global control
- AAccountable
- Compliance
- RResponsible
- Global owner
- CConsulted
- Process board
- 04Approve a local variant
- AAccountable
- Process board
- RResponsible
- Global owner
- CConsulted
- Local owner · Compliance
- 05Choose the extension point
- AAccountable
- Platform team
- CConsulted
- Global owner
- 07Retire a variant
- AAccountable
- Process board
- RResponsible
- Global owner
- CConsulted
- Local owner
05Exceptions & failure paths
7 exception paths, each with an owner and a destination.
Registered and reviewed; repeated cases go to the board
- Detected by
- Template audit
- Owner
- Global process owner
- Route
- Registered after the fact and reviewed
Returned for evidence
- Detected by
- Global process owner
- Owner
- Local process owner
- Route
- Returns to 01 Local variation request
Compliance decides before the board does
- Detected by
- Assessment
- Owner
- Compliance
- Route
- Compliance review first
The subsidiary adopts the global step, with a transition plan
- Detected by
- Process board
- Owner
- Local process owner
- Route
- Adopt the global step with a transition plan
Back to assessment: the template needs a new extension point, or the variant is refused
- Detected by
- Platform team
- Owner
- Platform architect
- Route
- Returns to 03 Impact assessment
The workaround becomes a new variation request
- Detected by
- Usage signals
- Owner
- Local process owner
- Route
- Treated as a new variation request
The subsidiary moves to the global process
- Detected by
- Review
- Owner
- Local process owner
- Route
- Variant retired
06Process ↔ system
The process question first. Then the system question has an answer.
Global CRM templateLocal ERPsVariation register
- Process question: P1Which differences are real constraints?
- System question: S1Which extension points does the template offer for them?
- Process question: P2Who approves a local deviation?
- System question: S2Where is the variant registered, with its owner and review date?
- Process question: P3How does the global process evolve?
- System question: S3How is the template versioned and regression-tested for every legal entity?
07The second layer
Questions that change the design.
Differences
- Which differences are noise, and which are real constraints?
- Which constraints are legal or fiscal, and which come from a local ERP?
- Are two subsidiaries asking for the same variant?
Authority
- Who approves a local deviation?
- Who may change a global control?
- How do small entities with merged roles keep segregation of duties?
Evolution
- How does the global process evolve—and who can propose changes?
- When does a local variant become the global standard?
- When does a variant expire?
08Measurement
Process health, defined by owner and action.
No values are shown: in a design, the definition is the deliverable.
Registered variants by stage and reason
- Owner
- Global process owner
- Triggers
- A stage with many variants is a template design problem
Local changes found outside the register
- Owner
- Global process owner
- Triggers
- Tighten change control—or simplify the request path
Request to board decision
- Owner
- Process board
- Triggers
- Fast-track legal constraints; batch preferences
Variants past their review date that were not renewed, merged or retired
- Owner
- Process board
- Triggers
- No silent renewals
Global KPIs computed identically across legal entities
- Owner
- Commercial operations
- Triggers
- Refuse variants that break comparability without a strong reason
09What the work produces
Outputs and connections.
- 01Global operating-model core
- 02Controlled variation model
- 03Variation register
- 04Governance and decision rights
- 05Minimum operating data
- 06Post-go-live evolution model