AI in the company: who it is for

Your teams live inside specialist software

Every profession has its own, with their portals, their screens and their documentation. That documentation is often good, in fact. ACD's online help has 886 articles, EBP's has 715, Pennylane's has 684. Nobody reads them.

Here's what actually happens: a team member gets stuck on a screen and turns to the desk next door. The desk next door knows, answers, goes back to work. A fortnight later, someone else hits the same screen. The answer had been written down all along, somewhere.

An internal assistant reads that documentation once and for all, and resyncs when the vendor publishes. A question asked in plain language gets its answer, with the link to the original article.

The answer already exists, somewhere else

In an old email, in a shared folder, in the head of someone who is on leave this week. Your company is not short of knowledge: what is missing is the path to it at the moment the question comes up.

The second layer of knowledge is written down nowhere: what your teams get each week on the phone with a support desk, the way your house does things, the little tricks of the trade. At our first client, this consolidated memory now runs to 2,752 articles and 27,154 indexed passages. Not one of them was written for the occasion. They come from daily use.

Your team changes

Every new arrival starts from scratch. Every departure takes away part of what the firm knew how to do, and nobody has time to explain it all again.

The Generative AI at Work study, published in 2025 in the Quarterly Journal of Economics after following 5,179 support agents, measures that the gap closes most for newcomers: 14% more cases resolved per hour on average, 34% among those who have just arrived. That is exactly the position of a team member discovering your software and your habits.

Your data never leaves your firm

You won't put your client files into a public service, and you're right not to. Your instance is isolated, in your name, on your own server or on a server that belongs to no one but you. The semantic analysis of your documents runs locally, on the machine.

Your teams are already using public assistants. Sometimes with data that should never go there. Giving them an internal assistant you control settles the problem better than a memo.

It's not for everyone

If your work fits into three procedures everyone knows by heart, if nobody ever asks the same question twice, and if you are never left waiting on a vendor's support, we will bring you nothing. One more tool that goes unused is one tool too many.

The tipping point we see is around ten people sharing files and software. Below that, the office next door is often enough.