Data & Vector Databases

RAG Explained: Retrieval-Augmented Generation for Business AI

RAG puts your own documents in front of the model before it answers, which is what makes enterprise AI knowledge systems work. How it works, and what breaks.

By Published

Retrieval-augmented generation means finding the relevant documents first, then asking the model to answer using them. It is the difference between asking a smart stranger what your refund policy is and handing them the policy before you ask.

Almost every useful internal AI system is built this way, because the alternative is a model guessing at facts specific to your business that were never in its training data.

The four steps

Someone asks a question. The system searches your document store for passages that relate to it. Those passages are put into the prompt alongside the question. The model answers using them, and cites what it used.

The search step is usually semantic rather than keyword-based, which is what vector databases are for. A question about "time off" finds a policy titled "annual leave" because the two are near each other in meaning, not because they share a word.

Why it is worth the work

The model stops inventing. It is summarising supplied text instead of reconstructing from memory, and the failure mode changes from confident fabrication to "I could not find that", which is a far better failure. Answers carry citations, so a reader can check the source rather than trusting the tone. And the knowledge stays current, because updating the document store is cheaper than retraining anything.

What actually breaks

Retrieval, almost always. If the search returns the wrong three passages, a perfect model gives you a wrong answer built from them. Most RAG projects that disappoint have a search problem, not a model problem, and the team spends weeks on prompts instead.

Documents that disagree. Two versions of a policy in the store and the system will confidently quote whichever one it found. Nobody notices until it quotes the old one to a client.

Permissions. A retrieval layer that can reach everything will answer questions using documents the person asking is not allowed to see. Permissions have to follow the person, not the system.

Chunking. Split documents badly and you retrieve half a sentence of context. This is unglamorous and it decides whether the thing works.

What has to be true first

You can say which system is authoritative for each fact. Where two sources disagree and nobody has decided which wins, the answers inherit the disagreement and people quietly stop trusting them.

// the_list

Get the next one.

Field notes from real deployments, written the way this one was. No schedule promised and nothing sold to you. Unsubscribe whenever.

Frequently asked questions

What is RAG?

Retrieval-Augmented Generation. LLM combined with retrieval from external data. Enables AI to answer using your specific data with citations.

Why RAG over fine-tuning?

Easier to update (just update data), better citations, lower cost. Most enterprise use cases prefer RAG. Fine-tuning still relevant for specific style/behavior.

Best vector database?

Pinecone managed dominant. Open source options (Weaviate, Chroma, Qdrant) growing. Cloud platforms (AWS, Azure, GCP) increasingly include vector. Choice based on scale and integration.

When does RAG not work?

When data quality is poor, when retrieval is poor, when LLM ignores retrieved context. Quality of each component matters.

Building RAG systems?

LangChain or LlamaIndex frameworks accessible. Plus vector database and LLM. Many enterprises building internal RAG over knowledge bases.

Related guides

Need help implementing this?

Prometheus does AI consulting and implementation, remote, with onsite days available in Milwaukee. We set it up, train your team, and make sure it works.

let's talk