Dear Pipedrive,

my company consists - through M&A and natural growth - of multiple "branches" that sometimes are practically identical to the existing company, and sometimes differ in various aspects of our business.
Also, while the naturally added branches are within the existing team structure, M&A brings in new teams with different structures, that are not always integrated into our extisting team structure.

Does anyone have experience with administrating pipedrive in such a situation?

Our current solution is, to focus on what the different branches demand from pipedrive. If it is largely the same as the existing branches, it just gets mixed with those and structured through custom data fields to keep things organised.
If it varies too much, we create a new Org for the new branch, and they build their own pipedrive according to their use case. I than just get added as a asmin-user and help out with things.

Does that make sense? Are there any useful tips for such a construction?Β