So for example, if you would pen an email/slack talking about a slide deck from a recent meeting, in the widget the product would have already found the deck ready for you to drag and drop it into the message.
It worked freakishly good, and saved a whole bunch of time trying to find a file in the mess that everyones Google Drive becomes.
The problem they were having was no enterprise wanted to hand over an entire copy of their data for them to index.
Using AWS for example all it takes is a misconfigured bucket to expose massive amounts of customer data.
Like your enterprises, no hospital (or equiv) would consider exfiltrating their data.
So our gear was physically deployed and operated on each hospital's own system. Our marketing and sales goons called this our "federated data model", which had no tangible connection to reality.
I likened the experience to building model ships in a bottle, while wearing mittens, while someone is punching you in the face. To mitigate, we created what would now be called CI/CD pipelines. We managed 100s of deployments with near zero downtime and effortless rollbacks. I'm rueful just thinking about it.
This strategy didn't survive the 2008 economic crash.
The challenge is the same as the main topic of this thread- change management. You have to force employees to manage their documents exclusively within this system rather than dumping everything into shared drives and using Outlook attachments for everything.
[1] One example: https://www.alfresco.com/ecm-software/document-management
That sounds like a reasonable response. At least, I know that would be a showstopper for me, personally.