- draft emails or presentations.
- prepare meetings and provide the current context to the employees.
- update clients information after meeting based on transcripts or employee notes.
- query different sources in order to gather how our system is working for a particular client.
I've been looking for ways to implement this but I can't seem to get to a clear path, I've some online sources and a few things in mind but I'm not convinced enough.
My current plan is the following one:
- A llm wiki to store "slow moving" data: company strategy, OKRs, clients status, transcripts..
- "fast moving" data (databases, logs, client tickets) has to be retrieved directly from sources, maybe using some company shared skills.
- Each employee can use a coding agent or a chat interface to "communicate" with the data through a MCP or something.
- There's an 24x7 agent who owns the llm wiki and skills repo and has access and knowledge about how to get data from the "fast moving" sources.
That is my current idea but I've so many doubts to move forward: - the 24x7 agent has to be constantly working, how much money could it cost?
- what happens when multiple people are working on the same data at the same time? can the agent do something to orchestrate the work?
- what kind of agent should I put there?
- Do I need to put an agent there?
- is there a better way to accomplish this? Am I over complicating things? Am I over simplifying things?
Are you working on this? What do you think? What would you do if you were in my shoes? (quitting is not possible :))
nycdatasci•36m ago
When I recently spoke to their engineers about this, they mentioned graph maintenance is very expensive and would likely be cost prohibitive for most orgs.