Designing customer ownership in a multi-subsidiary organization
A fictional operating-model case: “who owns this customer?” has at least four correct answers—and each needs a name.
Independently created. Contains no employer or client implementation detail, internal names or figures.
01The outcome
Every level of the customer has a named owner with defined rights; the global relationship is coordinated through one plan; local transactions stay local; conflicts go to a named arbiter with a time limit.
A group customer buys from several subsidiaries; three teams call it “my account” and nobody can resolve the disagreements.
Who owns the relationship, each transaction and the global account data—and who resolves ownership conflicts?
Separate ownership of the relationship, the local transaction and the account data, and give global coordination a plan and an arbiter rather than a shared “owner” field.
Large customers are groups with several legal entities, buying from several subsidiaries through different sales teams. A global account manager exists for the biggest groups; local teams execute orders; master data maintains legal identities. The CRM already models commercial identity separately from legal identity (see the Systems case). What is missing is the ownership model that sits on top of it.
02The reality · current state
How the organization operates today.
- Three teams consider the same group “their” account
- Local teams change global account data they do not own
- The global account manager cannot see local pipeline
- Conflicts are escalated by email and resolved by seniority
- Credit decisions and commercial plans are made separately
- Reports double-count group revenue across subsidiaries
03Operating model
The design, layer by layer.
- 04Ownership
Relationship, local account, transaction and data owners named per level
- 05Systems
Visibility follows ownership level; local ERPs own transactions
- 06Data
Legal identity owned by master data; commercial hierarchy by the global account owner
- 08Governance
A named arbiter per region; conflicts resolved within two weeks
- 09Measurement
Group revenue attributed once, with local credit rules
04Key dimension · Relationship vs transaction vs data ownership
Four levels, four owners—and a rule for conflicts
Each level has an owner, rights and limits. Conflicts have a rule and a named resolver.
- Global account manager
May Set the group account plan; see all pipeline
May not Change local transactions or legal data
- Local account owner
May Run local opportunities and quotes
May not Change the group hierarchy or plan
- Subsidiary (order and invoice)
May Execute orders under local terms
May not Change group commercial terms
- Master data (legal) · Global account manager (hierarchy)
May Maintain identity and group structure
May not Assign commercial ownership
| Conflict | Resolved by | Rule |
|---|---|---|
| Two teams pursue the same opportunity | Regional sales director | The team with the buying entity leads; the other is credited by rule |
| Local team needs a group-level price | Global account manager | Group terms apply; local exceptions are recorded |
| Group structure is disputed | Master data with the global account manager | Legal evidence decides the hierarchy |
A single “account owner” field could not hold this. The model names who owns what at each level; the CRM implements it through visibility and edit rights.
05Decision rights
Who decides what, with which evidence, within what time.
| Decision | Decides | Approves | Consulted | Evidence | Within |
|---|---|---|---|---|---|
| Change the group hierarchy | Master data | — | Global account manager | Legal documents | 10 working days |
| Set group commercial terms | Global account manager | Finance | Local account owners | Group volume and margin | Annual |
| Resolve an ownership conflict | Regional sales director | — | Both teams | Buying entity, history | 2 weeks |
06Governance
The forums that run and change the model.
| Forum | Decides | Evidence |
|---|---|---|
| Global account reviewQuarterly | Group plan, coordination, conflicts escalated | Group pipeline and revenue across subsidiaries |
| Regional sales reviewMonthly | Ownership conflicts within the region | Conflict log, pipeline |
07The trade-offs
Credible options, judged against these premises.
One owner per group, everywhere
Centralized selling
Cost: Local execution without authorityEvery subsidiary owns its own view
Unrelated local customers
Cost: No group coordination; double countingOwnership per level with a coordination plan and an arbiter
Groups buying from several subsidiaries
Cost: A plan per group and a conflict route08The second layer
Questions that change the design.
Ownership
- Who owns the commercial relationship?
- Who owns each local transaction?
- Who may update global account data?
Visibility
- Who sees what?
- Does the global owner see local pipeline?
- How is revenue credited once?
Conflict
- Who resolves ownership conflict?
- Within what time?
- How does global coordination work?
09Decisions & outputs
What the work produces.
- 01Ownership levels model
- 02Rights per level
- 03Conflict rules and arbiters
- 04Group account plan
- 05Credit attribution rules
- 06Visibility requirements