Hey everyone, I'm struggling to keep the "knowledge layer" around my clients CRM current and aligned. Data definitions, field logic, process SOPs, what dashboards actually measure and why. It all ends up scattered across Notion, Google Docs, and notes buried inside dashboards, and it's outdated within months. How are you balancing keeping data definitions, process documentation, and business context up to date as things change? Are there actual tools for this, or is everyone just manually maintaining docs and hoping people read them? Thinking about building something if nothing exists.
The first things I will ask is which data is important for team and make decisions on. A lot of time people like to collect data but most of the times they are only using tiny amount of data points to make decisions. I will find those in crm and maybe integrated it with clay to update it on regular basis. If you are not doing much testing and it is just static claude code it
I think the challenge is that documentation lives outside the system it describes. The moment a field, workflow, or routing rule changes, the knowledge layer starts drifting. Curious whether you've looked at generating documentation directly from CRM metadata and workflow changes rather than maintaining it manually?
