How do businesses design CRM systems for multiple departments?
Shared objects and properties at the center, department-specific pipelines at the edges.
Put the shared data at the center and the department differences at the edges: one set of contact and company records that everyone writes to, then separate pipelines, views, permissions and dashboards per team. Departments are allowed to have their own process. They are not allowed to have their own version of the customer.
What has to be shared
Contacts and companies, always. The lifecycle stage. Association rules, meaning how a contact connects to a company, a deal and a ticket. Anything that appears in a company wide report, such as lead source or industry or region. If two departments maintain two different values for the same fact, one of them is wrong and reporting becomes an argument.
Shared fields need an owner. Name a person, not a team, for each one. The owner decides the picklist values and whether a new option gets added.
What should be separate
- Pipelines. Sales deals, renewals, service tickets and onboarding projects are different processes with different stages. Give each its own pipeline instead of stuffing them into one with twenty stages.
- Views and dashboards. A rep should open the CRM and see their work, not everyone's.
- Permissions. Who can edit a shared field, who can delete, who can export. Export permission in particular tends to get handed out by default and should not be.
- Department specific properties. Fine, as long as they are named so it is obvious which team owns them and they do not duplicate a shared field.
Where this breaks
Two places, reliably. The first is duplicate properties: marketing creates Industry, sales creates Vertical, finance creates Segment, and now no report is complete. The fix is a property request process, not a cleanup project every year.
The second is departments running side systems. A spreadsheet, a separate email tool, a personal list. That is not a discipline problem. It usually means the CRM does not do something that team needs, and the honest response is to fix the system rather than send another reminder.
Our longer guide to multi-department CRM design walks through the structure, and our implementation service is where we build it.
Related: What are CRM custom objects and custom properties? | Which CRM fields should be required? | My data lives in 5 different tools. Can you help unify it?