You usually have either a harness that mainly works with a code interpreter that is able to execute Python, and does all the necessary data extraction from sources + the creation of office documents via your typical libraries, or you additionally enhance it with specific tools for each major office file format.

Source: Building a "harness" for organizations with deep MS Office suite integration at https://github.com/EratoLab/erato

▲

hypfer 4 hours ago | parent [-]

Huh.

So that is mainly a chat window like that Hubspot widget?

I mean I guess that gets stuff done, but I was expecting some fresher ideas perhaps?

	▲	hobofan 3 hours ago \| parent [-]
		It's mainly a full chat app like e.g. ChatGPT. However our platform also comes with a Outlook/Office add-in, where our UI is directly displayed besides the email/document you are actively working with. There we are mostly restricted by the surface that the add-in system provides us. To some level we can take current user interactions into account (e.g. what email are you currently viewing), which already helps a ton, but there are other restrictions that can get quite limiting. So you have two main modes of operations: One-shot "I have this input; give me this output" which people usually do via the web-app, and more interactive editing to documents (usually larger ones) that happens directly in the applications the users are already working in. And yeah, that's what ultimately gets the job done. We've seen competing solutions dive much deeper into building their own native editors, but they always lack the fidelity required by power-users, and are usually not as acepted by the broader workforce that are entrenched in their ways (our typical end-user is 50+ in a enterprise-like organization structure), so we try to meet the organisations where they are.