Customer support
Agents get answers from manuals, product sheets and past tickets while the customer is on the line.
“Does the X200 support 220 V, and which adapter ships with it?”
RAG knowledge assistants
Retrieval-augmented generation (RAG) lets an AI assistant answer from your own contracts, manuals, policies and tickets, and show the passage each answer comes from.
Why RAG
It has never seen your price list, your contracts or last week’s policy change, and when it doesn’t know, it guesses. RAG fixes that. Before answering, the assistant searches your documents, reads the relevant passages and answers from them.
Add or change a document and it is searchable within minutes. No retraining.
Every answer links to the passage it came from, so people can check it in one click.
The whole pipeline, model included, can run on your own servers.
Use cases
Typical questions by team. These are examples, not client results.
Agents get answers from manuals, product sheets and past tickets while the customer is on the line.
“Does the X200 support 220 V, and which adapter ships with it?”
Specs, pricing rules and approved answers for RFPs and security questionnaires.
“What discount can I offer on a three-year contract?”
Employees find answers in handbooks and benefit documents instead of emailing HR.
“How many days of parental leave do I get in Texas?”
Find clauses and compare terms across hundreds of agreements.
“Which suppliers can terminate with less than 60 days’ notice?”
Procedures, maintenance manuals and safety instructions, searchable from the shop floor.
“What is the lockout procedure for line 3?”
Troubleshooting from your internal knowledge base, with links to the right article.
“How do I reset VPN access for a new laptop?”
How it works
Most RAG projects that disappoint fail on parsing, search or permissions, not on the model. That is where we spend the effort.
SharePoint, Google Drive, file shares, Confluence, email archives or databases, kept in sync so new and changed documents are picked up automatically.
Tables stay tables, scanned pages go through OCR, slides and spreadsheets keep their structure. Answer quality starts here.
Hybrid search combines vector embeddings with keyword search, so the assistant finds “payment terms” and also the exact clause that says “net 45”.
The best passages are reranked, the model answers only from them, cites each source, and says so when the documents don’t contain the answer.
Search is filtered by each user’s access rights, so people only get answers from documents they are allowed to open.
We build a test set from real questions your team asks and track three numbers before go-live and after every change: whether the right passages are found (retrieval recall), whether answers stick to them (faithfulness), and whether citations point to the right place.
What you get
RAG or fine-tuning
Fine-tuning changes how a model writes and behaves. RAG gives it your facts. Most projects start with RAG and add fine-tuning only if needed.
| Criterion | RAG | Fine-tuning |
|---|---|---|
| Teaches the model | Facts from your documents, looked up at question time | Style, format, vocabulary and narrow tasks |
| When content changes | Add the document; searchable in minutes | Retrain the model |
| Shows its sources | Yes, for every answer | No |
| Respects document permissions | Yes, per user | No; everything trained in is visible to everyone |
| Usual order | First | Later, if the pilot shows a need |
Where it runs
The assistant works the same way in all three setups. What changes is where your documents and questions are processed.
Claude, GPT or Gemini under business terms that exclude training on your data. Fastest to start, paid per use.
An open-source model on GPUs rented in your own cloud account. No outside AI provider involved.
An open-source model on a server in your office or data centre. Nothing leaves your network.
Open-source LLMsTechnology
We pick components for your volume, budget and privacy needs, and you own the result.
How we work together
Every project goes through the same three stages. You decide at the end of each one whether to continue, and you can stop after any stage and keep everything built so far.
We look at your process, your data and your systems, then tell you plainly whether AI is worth it, which approach fits, and what it would cost to build and run.
You get a written recommendation with scope, timeline and cost.
A working version on your real data, used by a few of your people, with results measured against questions and cases from your own business.
You get a working pilot and an evaluation report.
We secure it, connect it to your systems, roll it out to your team and keep it running: monitoring, model updates and improvements.
You get a production system, documentation and ongoing support.
We list them in the assessment, so the full cost is clear before you commit.
Only if you choose to. We can run the entire pipeline, including the language model, on your servers or in your private cloud. If you prefer a cloud model for quality or cost, we use providers’ business terms that exclude training on your data.
PDF (including scanned documents, through OCR), Word, Excel, PowerPoint, email, web pages and plain text, from SharePoint, Google Drive, Confluence, file shares or databases. If your content lives somewhere else, we write a connector.
The model is instructed to answer only from the passages it retrieves, to cite them, and to say when the documents don’t contain the answer. We then measure this on a test set of real questions before launch, and keep measuring afterwards.
Yes. Search results are filtered by each user’s permissions in the source system, so an employee never gets an answer drawn from a document they could not open themselves.
A pilot runs on a sample of your real documents, with a handful of users, and ends with an evaluation report. We agree its scope and timeline in writing during the assessment.
It depends on the number of users and documents, and on whether the model runs on your hardware or through an API. The assessment gives you a running-cost estimate for each option before you commit.
Often, yes. We first measure it on a test set of your questions to find where it fails. That is usually document parsing, search or how documents are split, rather than the model. Then we fix those parts and keep what works.
Access to a representative sample of documents, 20 to 50 real questions with the answers your experts would give, and one person who can judge the results.
No call needed to start. Send a short brief and we’ll reply in writing with what we’d do and what it would take.
Houston, Texas · Working with clients worldwide