The questions your team asks the same person every week

What shipped

Grounded retrieval has quietly become boring. Putting a small assistant on top of your own documents, so that it answers only from what you have approved and cites the file it used, is no longer a research project. It is a normal build, and the cost has fallen far enough that a 40-person business can justify one.

What has not changed is the reason you would want it. In most Irish SMEs there are two or three people who answer the same questions all week. How do we raise a purchase order for a new supplier. Which template do we send a client after the first call. Who signs off expenses over 500 euro. What do we do on a new starter's first morning. Where is the current version of that form. None of it is difficult. All of it interrupts somebody who was doing something else.

Vendor changes make it worse in bursts. When a tool everyone uses redesigns its interface, your internal instructions go stale overnight and the questions start again for a fortnight. The instructions were never wrong, they were just written against last month's screen.

Who should care

This is for operations managers, office managers, finance leads and the person who quietly became the company's help desk in a business of roughly 10 to 250 people. It matters most where the knowledge sits in a few heads, where the same handful of questions arrive by Teams message, and where an absence or a resignation would be genuinely disruptive.

The cost is hidden because it is never recorded. A three-minute interruption is not a ticket. A senior person walking to another desk to ask what the process is does not appear in any system. A question answered slightly differently by two people is only discovered later, when a client notices. These are the small leaks that make a business feel busier than its revenue suggests.

The signals worth watching are simple. Fewer repeat questions reaching your most interrupted people. Fewer versions of the same answer in circulation. Faster onboarding for new staff. Requests that arrive with enough context to be handled first time. A ranked list of the procedures that cause the most confusion, which tells you what to rewrite.

It is a poor fit if what you actually need is a decision made, an approval given or a system administered. That work stays with people. It is also a poor fit if your procedures do not exist in writing anywhere. In that case the first piece of value is the writing, not the assistant. If you are unsure whether what you have in mind is a workflow at all, this piece on what counts as an AI workflow is the shorter read.

A worked example

Take a Dublin professional services firm with 85 staff. Three people absorb almost all internal questions: the office manager, the finance lead and one IT-minded account director who never asked for the job.

Their procedures do exist. There are policies in a shared drive, a finance handbook, an onboarding checklist, a few notes on how the meeting rooms and shared devices work, and a folder of client templates. It is all there, and almost nobody can find the right piece of it quickly.

A first version does three things. It answers questions from those documents in plain English and names the file each answer came from. It says clearly when the documents do not cover the question. And when it cannot answer, it opens a structured request that captures who is asking, what they were trying to do, which document they were sent to, and how urgent it is.

That last part is the quiet win. After a month, the requests it collects are a ranked list of everything your written procedures do not explain. Rewrite the top five and the volume drops. Meeting rooms and shared kit usually appear on that list, alongside expenses and onboarding, which is how a small piece of AV confusion gets solved without buying an AV system.

A person still reviews anything that leads to action. The assistant is decision support. It gives people the current answer and gives you the evidence to improve it.

Where I'd start

Do not start with the technology. Ask your two or three most interrupted people to keep a note for one week of every question they answer more than once. You will have a list of ten to fifteen questions and it will be shorter than you expect.

Then check what document actually answers each one, and fix the ones with no answer or two conflicting answers. That step alone pays for itself. Ground an assistant in those documents only, keep it narrow, and let it hand anything else to a person with the context already captured.

Two weeks of that is enough to know whether it is worth widening. If you want a second opinion on where to point it first, that is the kind of thing our advisory and workflow design work is for.