The choice is about where the files live
The capability is much the same everywhere. What differs is who ends up holding your documents, how much work it is, and what happens when you want to leave.
1. A notebook product
Google’s NotebookLM is the best-known, and free at the time of writing. You add up to a few dozen sources (documents, PDFs, pasted text, web pages, a YouTube link) and ask questions across them. Answers carry inline citations back to the source passage, which is the feature that matters.
Strong points: nothing to set up, the citations are good, and it is deliberately confined to your sources rather than answering from general knowledge. It also generates summaries and study material from your own documents, which is more useful for training a new employee than it sounds.
Weak points: your documents sit in a large company’s cloud, the free tier’s limits change, and it is not designed as a permanent business system. Read the terms if the documents are sensitive.
2. A project inside the tool you already use
ChatGPT projects, Claude projects, Gemini in Google Workspace, Copilot in Microsoft 365. Attach files to a workspace, and every conversation in it starts with those files available.
Strong points: no new vendor, no new subscription if you already pay, and it sits where you are already working. For a business with fewer than twenty reference documents this is usually the right answer.
Weak points: file limits are modest, and how the files are used varies between products: some read everything, some retrieve passages, and the interface rarely tells you which.
3. Inside software that already holds the data
Your helpdesk, your CRM, your shop platform. If your help centre software has an AI answer feature, it is already grounded on your articles, and no document leaves a system you have not already trusted.
This is underrated for the same reason as before. The data is there, the contract exists, and there is no second copy.
4. On your own machine
Free and open: AnythingLLM, Open WebUI, or LM Studio, each paired with a local model through Ollama. Point them at a folder, and you have a private document assistant that works offline.
Strong points: nothing leaves the building, no per-question cost, no limits, and it settles most of the privacy conversation in one move.
Weak points: an afternoon of setup, answers a step below the best hosted models, and you are your own support desk. For a clinic, a law practice, an accountant or anyone holding other people’s confidential material, that afternoon is well spent.
Choosing
Ask three questions in order.
Is the material confidential? If yes, start at option four or option three, and treat one and two as unavailable until you have read the terms properly.
Do you already pay for something that does this? Usually yes, and usually nobody has looked.
How many documents? Under twenty, a project is fine. Under a hundred with citations mattering, a notebook product. More than that, or growing, you want something built for it.
The question to ask before you commit
How do I get my documents and my answers out?
Files you uploaded should be downloadable. Answers, summaries and any structure you built are often not, and rebuilding a library in a new tool takes an afternoon you had not budgeted. Keep the master copies of every document in a folder you control, and treat whatever the tool holds as a copy. That single habit makes every one of these four reversible.
What a small library actually looks like
Businesses that get value here are not running a document warehouse. A typical working set is six to fifteen files:
- The current price list.
- Terms and conditions, and the refund policy.
- The two or three procedures people ask about most.
- A frequently-asked-questions page built from real customer emails.
- Supplier lead times and delivery areas.
- The staff handbook, if you have one.
That is enough to answer most of what anybody asks in a week, and it is small enough that one person can keep it current in twenty minutes a month. Resist the urge to add the archive. A library grows in usefulness up to a point and then starts working against itself, because every superseded document is a chance to be quoted back at you.
A practical way to start
Take the last fifty questions your business was asked, by customers or by staff. Write down which document answers each one. The documents that come up repeatedly are your library. Anything that answers nothing goes in the archive folder, outside the tool.
This takes an hour and produces a better library than a month of adding files as you think of them, because it is built from what people actually ask rather than from what you imagine they need.
Every lesson here is open. Your progress is recorded once you pass the AI at Work exam.
Check your understanding
A physiotherapy clinic wants an assistant that answers staff questions from its clinical protocols and patient-handling procedures. Which route should it consider first, and why?
Pick the one you would defend. Your answer stays private.
Stuck on something?Ask Yetunde, your AI tutor
