Domain-Driven Design · Cobalt Giraffe Insights
When “customer” means three different things

A sales manager, a billing specialist and a support adviser sit down to agree what a customer is. Sales talks about the organisation that signs the deal. Billing wants to know which legal entity owes the money. Support asks which organisation uses the service and when it can call for help. In a simple subscription those roles may all belong to the same organisation. A group contract can spread them across several.
Domain-Driven Design (DDD) gives us a way to explore those differences. Start by listening to the people who do the work. Learn the distinctions they make and test the language against real decisions. A ubiquitous language is the vocabulary that domain experts and the team building the system use together within a particular context. A bounded context makes explicit where that vocabulary and its model apply.
Model one agreement from three perspectives
Imagine Northbridge Group signs a contract for a service used by Northbridge Retail. The parent company pays the setup charge in December. The subsidiary’s support starts in January.
| Context | What the model needs to express | Question it answers |
|---|---|---|
| Sales | Contracting organisation, signed agreement and services sold | What did Northbridge Group agree to buy? |
| Billing | Payer, billing account and charge schedule | Who owes the December setup charge? |
| Support | Service recipient, covered service and entitlement dates | Can Northbridge Retail get help today? |
These are candidate boundaries. Test them with people who handle amendments, cancellations and queries before settling the design. One useful test is a change of payer. If a different group company takes over payment in February, Billing needs a new payer relationship from the effective date. Support can keep using the existing entitlement if coverage is unaffected. That tells us which facts a payment change must carry and which decisions can stay local.
Agree what crosses the boundary
A shared party identifier can help teams recognise the same legal entity, where they have agreed how that identity is maintained. Each context still gives the party a role. Sales can pass an agreement reference and service details to the team that establishes coverage. Support then uses the recipient, service and effective dates to answer an entitlement query. A shared identifier alone cannot tell Support whether the caller is covered.
Separate models carry a cost. Someone has to maintain the mappings, resolve mismatches and decide what happens when a business rule changes. Start with a shared model wherever teams genuinely share meaning and rules. Explicit boundaries earn their keep when the same word hides different decisions and those decisions change independently. The organisational chart is one clue. The behaviour under change is a better test.
At the next modelling workshop, take one example that breaks the usual assumptions. Ask each team what it needs to know, what it can decide and what it needs from the others. In Northbridge’s case, the useful discovery is that the organisation that signs, the organisation that pays and the organisation entitled to help can be three different parties. Once those roles are explicit, the teams can agree what they share and build models that support the work each of them does.