Happy Webs
№ 01 / GlossaryPlain-English AI definitions

RAG (Retrieval-Augmented Generation).

A technique that lets AI answer questions about your specific business data — your jobs, your customers, your documents — without retraining the model. The AI looks up the relevant data and uses it to answer.

№ 02In plain English

In plain English

Retrieval-Augmented Generation (RAG) is how production AI applications answer questions about specific business data. The pattern: when a user asks a question, the system first retrieves relevant information from your knowledge sources (databases, documents, systems), then gives both the question and the retrieved data to the LLM. The LLM answers based on the retrieved data, not what it happens to remember from training.

Why this matters: out-of-the-box LLMs know what they were trained on — generally the public internet up to some cutoff date. They don't know your jobs, your customers, your past quotes, your inventory levels. RAG bridges that gap without the cost and complexity of training a custom model. You keep the LLM, you add a retrieval system over your own data, and suddenly the AI can answer "what did we quote Acme in March?" or "where's job 1647 right now?".

For practical SMB applications, RAG is the foundation of internal AI assistants. The assistant doesn't memorise your business — it queries your business when asked. That has three important properties: answers reflect current state (not a frozen snapshot), data stays in your environment (the model only sees retrieved snippets to answer one question), and you can update the underlying data freely (no retraining needed).

Deployment cost is much lower than fine-tuning, and the build is much faster. Most useful internal AI assistants are RAG over a structured database and a document store — usually 4-8 weeks of build for the first version.

№ 03Real examples

Real examples

What this looks like in practice.

  • Internal AI assistant: when someone asks "where's job 1647?", the system retrieves the current MES record and answers from that.
  • Customer history lookup: "What's our history with Acme Engineering?" pulls past quotes, jobs, communications, and summarises.
  • Document Q&A: "What does this contract say about termination notice?" retrieves the relevant clause and answers.
  • Quote follow-up context: when drafting a chase email, the system retrieves what was quoted, when, and what the customer's last reply said.
№ 04See in action

See in action

Where we deliver this for clients.

№ 06Apply it

Apply it

Want this in your business?

Book a free 15-minute call. We'll talk through whether this pattern actually fits your workflow — and tell you honestly if it doesn't.

Let's see if we can help.

A 15-minute chat with Chris & Kay. No slides. No pitch deck. You tell us what's on your plate; we follow up by email with real thinking.

Studio81 Penny Meadow, Ashton-under-Lyne, OL6 6EL
HoursMon–Fri · 09:00–17:00 GMT