Skip to content

RAG · RETRIEVAL-AUGMENTED GENERATION

AI that looks it up first, then answers with the source.

RAG stands for retrieval-augmented generation. In plain English: before the AI answers, it finds the relevant passage in your own documents, answers only from that passage, and shows you where it came from.

Book a pilot call

Free · 20 minutes · no commitment

Why ordinary AI gets it wrong.

A general AI assistant answers from what it learned on the internet. It has never seen your rate card, your safety manual or last year's contract, so when it is asked about them it produces something plausible. In a business, a confident wrong figure is worse than no answer, because nobody catches it until it is a dispute.

How it works, in three steps.

  • Your documents are indexed: manuals, rate cards, contracts, procedures, past jobs. The index is built in your own accounts.
  • When someone asks a question, the system retrieves the passages that answer it, and only the ones that person is allowed to see.
  • The AI writes the answer from those passages alone, with a citation to each source. If nothing relevant is found, it says it does not know.

Twenty minutes, no deck. Bring the question your team asks most.

Book a pilot call

When your business needs it.

When the answers already exist and the problem is reaching them. The same questions go to the same two senior people all day. A new hire takes months to learn where things are written down. Staff quote from memory because finding the document takes longer than the call.

When it does not.

When the problem is missed calls, slow follow-up or work typed into two systems, RAG will not fix it, and we will say so on the call. It also cannot answer what was never written down: the first finding of many projects is the list of questions nobody has documented.

What we build and what you keep.

  • A citation on every answer, so it can be checked, not taken on trust.
  • Access controls, so people reach only what they are entitled to see.
  • An agreed refresh process for when your documents change.
  • A log of the questions it could not answer: a precise list of what your documentation is missing.
  • The index and the source documents, in your own accounts, with retention agreed before anything is loaded.

RAG

Is this the same as uploading files to ChatGPT?

The idea is related, but a business system needs what a chat window does not give you: access by role, a source on every answer, a refresh process when documents change, and the documents kept in your own accounts.

Can it still be wrong?

Yes, and the design is about making that visible. Every answer shows its source, so a person can check it in seconds, and when two documents disagree it shows both instead of picking one.

Where do our documents go?

Into infrastructure under your own accounts. What is loaded, who can see it, and how long it is kept are agreed before anything is ingested.

How many documents do we need?

There is no minimum. What matters is that the answers people keep asking for are written down somewhere. A single rate card and a procedures binder are a reasonable start.

Bring us one bad week.

Book a pilot call. Tell us where the week goes wrong, and we’ll tell you what an Operations Diagnostic would map and measure.

The first paid step has a clear scope and an end date, and the pilot after it is one workflow — not a platform, and not an open-ended retainer.

Free · 20 minutes · no commitment