Knowledge lookup
Staff ask a question in plain language and get an answer drawn only from your own files, with the source shown.
A lookup system over your approved documents: policies, procedures, precedents, product notes, contracts. Staff ask in plain language and get an answer with the passage it came from, within the permissions they already hold.
- Setup, once
- $3,000
- Run, monthly
- $400
Prices are in Canadian dollars and do not include tax.
How it works
The pipeline, step by step.
- 01
Sources are approved
You choose which folders, systems and documents the system may read, and who may see each.
- 02
Documents are indexed
Each one is split into passages and kept current as the source changes.
- 03
A question is asked
From a chat window, your intranet or the tools your team already uses.
- 04
Passages are retrieved
Only from sources the person asking is allowed to see.
- 05
An answer is written
With a citation for each claim and a link to the passage.
- 06
A gap is reported
If the sources do not answer the question, the system says so and offers to route it to a person.
Connects to tools such as
- Google Drive
- SharePoint
- Notion
- Slack
- Microsoft Teams
These are examples. We confirm the method for each of your tools before we build.
Where a person approves
The points where the system stops and waits for a person.
- You approve the source set and the permission map before anyone asks a question.
- Answers on sensitive topics can be routed to a named person instead of being shown.
- Your experts review a sample of answers each month and correct the sources where needed.
How it is measured
Named measures, scored on your own files before launch and after every change.
- Answer and citation accuracy on a question set written by your own experts.
- Permission tests: users cannot retrieve what they are not allowed to see, checked on every release.
- Coverage: the share of questions the sources could answer, and the gaps that need a new document.
How it is run
After launch: monitoring, updates and what you own.
- Monitoring on every query: errors, slow answers and permission denials raise an alert.
- Sources re-index as they change; releases are re-scored on the question set first.
- Handover: a runbook, a data map and code owned by the business.
What it will not do
Limits we set on purpose.
- It does not answer from the open internet or from documents outside the approved set.
- It does not invent an answer when the sources are silent. It says so.
- It does not show a passage to someone who could not open the original.
- It is not exposed to customers unless you decide it should be.
Sectors we build for
The business types this system is built for.
Questions
What can it read?
The documents you approve: policies, procedures, precedents, contracts, product notes. In the folders and systems you already keep them in.
How do permissions work?
The system reads your existing permissions. A person gets answers only from documents they could open themselves. We test this on every release.
What if the answer is not in our documents?
It says so. It does not guess. You can have those questions sent to a named person so the gap gets filled.
What if we have more than a few hundred documents?
Then it is a knowledge system, quoted to your scope: more sources, permissions that differ by team, documents that change daily. The method is the same; the build is larger. Its page under Engineering says where the line is.
Can we trust the citations?
Each answer links to the passage it came from, so a reader can check in one click. Citation accuracy is one of the three measures we score.
Talk to us about knowledge lookup
Fifteen minutes on a call is enough to tell whether it fits your work. If it does not, we say so.