When we talk about what we’ve built, we often use the familiar word “CRM” — a system for managing customer relationships. But that word is only an external view. Underneath it, we believe, lies a more general pattern that reaches beyond the customer relationship. CRM is, in fact, a special case of something larger.
The general pattern
This pattern has a few parts that together make a shared cognitive system. First, a semantic network that holds entities and the information about them. Second, an action layer that moves the work forward. Third, several cognitive roles that gather information, organise it, and decide when a matter advances to the next stage. Fourth, a human review loop that approves the proposals. And fifth, recorded reasoning: the trail of what each decision was based on.
These five parts are a pattern that applies to any shared cognitive problem — wherever information has to be gathered, organised, and turned into action.
Why CRM is one instance
In the case of CRM, the “matter” the system tracks is a relationship: a relationship with rights and responsibilities that grows over time. The network’s edges encode the structure of this relationship. But the same pattern works elsewhere too, if you change the matter. If the matter is a case file, or a project, or anything else that evolves over time and needs information gathering and decisions — the same structure holds. CRM is just the case where the matter is a relationship.
Why this view matters
This view isn’t just a theoretical nicety; it shapes how we build. When you see a system not as “a CRM” but as “one instance of a general pattern,” you build it so that its parts are reusable. The semantic network, the cognitive roles, and the review loop aren’t tied to one particular domain. That means when you reach the next cognitive problem, you don’t have to start from scratch; you apply the same foundation to a new matter.
Putting it together
We don’t see CRM as an endpoint, but as the first application of a more general idea: a shared cognitive foundation for matters that grow over time. This view both helps us build something that reaches beyond a single application, and reminds us that behind every familiar word — like CRM — a larger pattern is sometimes hidden, one worth seeing.