Launching today
DocuSmart AI
Turning fragmented knowledge into one simple system
96 followers
Turning fragmented knowledge into one simple system
96 followers
DocuSmart AI lets you search all your internal documents using plain English — across Google Drive, SharePoint, Dropbox and more — from one place. No migration, no reorganising, no training required. Just ask a question and get the answer. Built for nonprofits and SMEs who are drowning in documents spread across too many systems. We're looking for early adopters, if document chaos costs your team time, we'd love to hear from you.
Payment Required
Launch Team / Built With
DocuSmart AI
@paulmurnane The failure mode I keep hitting isn't finding the doc, it's that three docs disagree and nobody knows which is current. Does it do anything with conflicting or outdated sources, or does it treat everything in the index as equally true? That's the bit that decided it for us last time we evaluated something in this space.
The 'search across Drive, SharePoint and Dropbox in place, no migration' approach is the right call — the moment a tool wants to re-home all our files it's dead on arrival for a small team. When it answers a question, does it index and embed the docs into your own store, and how often does it re-sync as files change, or does it read live at query time? And on setup, does it respect each source's existing permissions so someone only gets answers from docs they already have access to?
love that this works across multiple platforms without forcing a migration. one thing that would really help our team is ability to set permissions per source, so people only see answers from drives they're actually allowed to access. right now i assume it inherits whatever the source already has, but making that explicit in the ui would save a lot of "why can i see this" questions. also maybe a way to cite which folder a specific paragraph came from, kind of like footnotes
Congrats on shipping this, Paul. The no-migration approach would get me to try it, searching Drive and SharePoint in place beats re-homing everything into another silo. One thing I always check before wiring in an integration that touches client files: does the connect step scope to just the folders I point it at, or does it need broad read across the whole account to index? Curious how tight that can be kept.
"Fragmented knowledge into one system" is the BI pain point everyone underestimates.
Curious how you handle conflicting source of truth — e.g., when Slack, Notion, and email
disagree on the same fact. Great launch.
this is the exact problem my team has, knowledge spread across slack threads, old docs and random notion pages nobody updates. does it just index existing sources passively or do you need to actively feed it documents to keep it current?