We’ve been running into the same problem over and over:
Team knowledge lives in Notion (or Confluence, Google Docs, etc), but updates actually happen in Slack threads, Zoom calls, and email chains. So the docs slowly rot — and nobody has time to keep them fresh.
We built AutoBase to try and solve this. It listens to those real-time channels — Slack, meeting transcripts, and email — and updates your internal docs when something changes. Kind of like a passive assistant that keeps your knowledge base accurate without manual effort.
We’re still early and looking for:
Feedback on the approach
Teams who want to pilot it (lightweight setup)
Insights into what tools people are using for knowledge bases right now
Would love to hear how others are handling this — what do you use to keep your team in sync? Is stale documentation something you've dealt with too?
ElfDragon11•7mo ago
We built AutoBase to try and solve this. It listens to those real-time channels — Slack, meeting transcripts, and email — and updates your internal docs when something changes. Kind of like a passive assistant that keeps your knowledge base accurate without manual effort.
We’re still early and looking for:
Feedback on the approach
Teams who want to pilot it (lightweight setup)
Insights into what tools people are using for knowledge bases right now
Would love to hear how others are handling this — what do you use to keep your team in sync? Is stale documentation something you've dealt with too?