Permissions travel with the answer
The assistant only ever surfaces what that specific person could already open themselves. Access control is enforced at retrieval, not filtered afterwards, so a search box never becomes an accidental data leak.
Your company already knows the answer. It is in a wiki nobody maintains, a PDF on a shared drive, a Slack thread from last March, and one person who is on holiday. We build the layer that finds it, answers in plain language, and shows exactly where it came from.
From$15,000
One source indexed with permissions enforced at query time, deployed where your team already works.
Indicative starting price. The fixed fee for your scope is quoted after the two-day diagnosis, before any build begins.
What makes it work
The assistant only ever surfaces what that specific person could already open themselves. Access control is enforced at retrieval, not filtered afterwards, so a search box never becomes an accidental data leak.
Every answer links back to the document and section it came from, with a freshness date. People verify in one click, and the habit of checking survives - which is what keeps the system trustworthy at month six.
We index your sources where they already live. There is no prerequisite project to consolidate everything into one tool, because that project is how most knowledge initiatives quietly die.
Capabilities
Wikis, shared drives, PDFs, tickets, chat history and database records, searched together rather than one tool at a time.
Existing permissions from your identity provider respected per user, per document, at query time.
Source, section and last-modified shown alongside every answer, so stale content is visible rather than silently repeated.
A report of the questions people ask that your content genuinely cannot answer - usually more valuable than the assistant itself.
Slack, Teams or your intranet, rather than one more tab nobody opens.
In detail
A category name is not a scope. These are the individual pieces of work inside this practice - take the two that apply to you and ignore the rest.
Indexing wikis, shared drives, PDFs, tickets, chat history and database records where they already live, with no migration project first.
Access control from your identity provider enforced at query time, so a person only ever sees what they could already open themselves.
Every response linked to the source document and section with a last-modified date, so stale content is visible rather than silently repeated.
Follow-up questions understood in context, deployed in Slack, Teams or your intranet rather than as one more tab.
A version scoped to new starters, which is usually where the return is largest and the risk smallest.
Answering the recurring internal questions about leave, expenses, IT access and process that consume a surprising amount of senior time.
A standing report of questions your documentation cannot answer, which is frequently more valuable than the assistant itself.
Turning recordings and threads into searchable records of what was decided and why.
What you receive
Around three weeks end to end. That comes from scoping tightly to one workflow - not from skipping a phase. Each still ends in evidence you can check.
Let's talk
Pick a single source - the shared drive everyone complains about is ideal - and we will index it and run your team’s real questions against it. You will see the answer quality and the content gaps before committing to anything wider.
Related practices