Skip to content
AI practice

AI agents and RAG assistants for business: answers that cite your documents

For SMEs and mid-sized companies: your teams ask their questions, and the agent answers from your procedures, contracts or reference standards, cites its source and says when it does not know.

Data sovereignty: hosted in France by defaultTrusted by the public and private sectorsYou own your intelligence

An AI agent grounded in your texts that cites its sources

An AI agent answers from your own documents, procedures, contracts or reference standards, and can take action in your tools. Before answering, it looks for the relevant passages, builds its answer from them and cites the source. This is known as RAG, and Bonne Idée applies it to all its agents so that every answer can be checked.

A language model on its own answers with confidence, even when it is wrong. Grounded in your texts, the agent instead says it cannot find an answer when nothing in your documents matches.

It can also act: answer your teams from your procedures, check a contract or a file against a reference standard, gather the documents for a file, prepare follow-ups. Human approval remains built in wherever a mistake is costly.

Our own agent, CoBIos, co-built with the Orléans Commercial Court Registry, works this way. Our AI agents are built on your documents; CoBIos is our ready-made agent for accounting and law firms; BIA is our sovereign AI workspace, run locally.

Our commitments

The quality rules our AI agents follow

Every answer cites its source

The agent answers from your documents and points to the passage its answer is based on. An answer without a source is not sent: the person reading it can trace it back to the text in one click.

Answer accuracy is measured

Before go-live, the agent is run on a test set of questions written with you. The share of correct, sourced answers is known, then measured again whenever the model or the documents change.

The agent says when it does not know

When nothing in your documents answers the question, the agent says so. What it is allowed to do on its own, and what waits for human approval, is decided action by action.

Our method

From your documents to a live agent

Two weeks of scoping, then two-week sprints.

  1. 1

    Scoping and the corpus

    The questions the agent has to handle, the documents that are authoritative, those that are out of date, and who is allowed to see what.

    YouGather the reference documents.
    UsThe corpus and the fixed quote.
  2. 2

    Prototype

    A first agent on a sample of documents, queried with real questions from your teams.

    YouProvide a list of real questions.
    UsAn agent you can query.
  3. 3

    Quality measurement

    A test set of questions written with you, with the correct answers. We measure the share of correct, sourced answers before any go-live.

    YouApprove the expected answers.
    UsThe agent's score, question by question.
  4. 4

    Go-live

    The agent connected to your tools, access rights respected, your teams onboarded.

    YouName who keeps the corpus up to date.
    UsThe agent, live.
  5. 5

    Monitoring

    Unanswered questions feed the corpus, out-of-date documents are removed, and quality is measured again.

    YouOne check-in a month.
    UsThe agent's monitoring dashboard.

How long a first agent takes, and what changes the timeline

A first agent can be queried from the first two-week sprint, after the two weeks of scoping. Three things change the timeline:

  • The state of the corpus. Documents that are up to date, organized and free of duplicates shorten everything. Conflicting versions need sorting out, which is part of the project.
  • Access rights. An agent that has to respect who is allowed to see what takes more work than an agent on documents open to everyone.
  • Actions. An agent that answers is quicker to deliver than an agent that acts in your tools, because every action has to be tested and kept within limits.

A narrow first agent that is live and measured is better than an agent that covers everything and that nobody dares to use.

Measuring made-up answers before go-live

The risk of a made-up answer never falls to zero. It can be measured, and that is the condition for putting an agent in your teams’ hands.

The test set of questions

We write a series of real questions with you, each with the correct answer and the document that supports it. Every version of the agent is run on this set, and every answer is classified: correct and sourced, correct but poorly sourced, wrong, or « I don’t know. » An agent that admits it cannot find an answer is better than one that makes things up, so the last category counts as good behavior.

What we do with the result

Errors almost always point to a specific cause: a missing document, an out-of-date version, an ambiguous question. We fix the corpus, measure again, and go-live only happens once the score agreed during scoping is reached. The same set is then used every time the model or the documents change.

What an agent is allowed to do on its own

An agent can read, search, summarize, prepare a document, fill in a field or suggest a follow-up. The line between what it does on its own and what waits for human approval is drawn during scoping, action by action, according to what a mistake would cost.

The rule we apply: anything that goes out to a customer, commits money or changes reference data goes through a person. Every action is recorded in a log, so you know at any time what the agent did, based on which source, and who approved it.

When the agent needs to trigger sequences of steps in your tools, we back it with an automation hosted in your own environment. If your teams first need to learn how to use it, the Consulting practice prepares the ground with adoption and change management.

A worked example: the internal procedures agent

Take a common situation: an SME whose quality procedures, technical data sheets and internal rules are spread between a file server and a few people’s heads. The same questions come back every week, put to the same people.

  • Scoping lists the most frequent questions, identifies the authoritative documents and sets aside out-of-date versions.
  • The prototype answers these questions on a first batch of documents, each answer with a reference to its source.
  • Measurement runs the agent on the test set of questions written with you, before any go-live.
  • Go-live opens the agent to a team, in the tool it already uses, with a process for handling unanswered questions.

Unanswered questions show which documents are missing, and that is often the first benefit of the project.

The building blocks we put together

See all our tools

Security of the documents the agent queries

An agent reads your documents: where they are stored and who has access to them matters as much as the quality of the answers. The agent respects the access rights already defined in your tools. A data processing agreement (DPA) is signed with the contract, everything is hosted in France by default, or on your own infrastructure when nothing must leave, and no model is trained on your documents.

We integrate AI for commercial court registries, public and ministerial officers who are demanding on this point. Human review and what GDPR and the EU AI Act require are set out on our AI guarantees and data sovereignty page.

FAQ

Frequently asked questions about AI agents

Retrieval-augmented generation: the model first searches your documents, then answers from what it found. This is what makes it possible to cite a source and limit made-up answers.

A chatbot answers. An agent can also act in your tools: fill in, check, prepare, follow up. During scoping we define what it is allowed to do on its own and what requires approval.

By requiring the agent to cite its sources, by having it say when it cannot find an answer, and by measuring its quality on a test set of questions before go-live. The risk never falls to zero, hence human approval wherever a mistake is costly.

Often not quite, and that is normal. Scoping identifies the documents that are out of date, contradictory or impossible to find, and decides which ones are authoritative. Putting them in order is part of the project. A smaller but up-to-date corpus gives better answers than a complete one where three versions of the same procedure contradict each other.

In France by default, or on your own infrastructure when nothing must leave. The agent respects the access rights already defined in your tools.

Documents your teams go looking for every week?

A free first call, by video: the first agent to build, and on which documents.

Book a call