Skip to content
Konsul
Menu
All examples

Example: Company answers

Ask a question, get the answer from your own files.

Anyone on the team asks in plain words and gets an answer quoted from your own documents, client notes and meeting notes, with the source and its date. A team of 20 that spends 2 hours a week each hunting for answers is paying for 40 hours of searching every week.

By hand

Hunting for answers in old files and threads. About 15 minutes each time, every time it comes up.

With a build

Handled for you, and nothing reaches a customer in words you have not approved.

What a diagnostic would check first

The diagnostic decides what gets built, or whether anything should. What follows is one way it could look.

  1. The questions the team asks every week
  2. Which tools hold the answers
  3. Who is allowed to see what today

One way it could look

Open the working example

Quick look. The full example has every screen. Made-up business and files. This demo matches words with fixed rules, not a live AI call. Nothing on this page reads your real files.

Want one shaped around your business?Tell us what's breaking

How it would work

  1. Step 1

    It reads where answers already live

    Google Drive, Gmail, Calendar, Slack, HubSpot or Notion. Only the tools and folders you name, and only to read.

  2. Step 2

    Anyone asks in plain words

    From Slack or a page in the browser. It searches only the files that person can already open, so a staff question never touches a managers-only file.

  3. Step 3

    It answers with its sources

    The answer quotes your files, and each line points to the file, the tool, the owner and the last updated date. A file over a year old is marked so someone checks it.

  4. Step 4

    It says when it does not know

    If your files do not answer it, you see "Not in your files" and the name of the person to ask. It does not guess.

Waits for your OK

  • Every new source. A tool or folder is connected only after its owner says yes.
  • Changes to your files. It reads and never edits, moves, deletes or sends a file. The one thing it adds is meeting notes, saved as a new doc in a folder you pick.
  • Who sees what. It follows the sharing your tools already have. A file a person cannot open in Drive or Notion stays out of their answers.
  • Who gets the morning briefing. Nobody is added to it without your OK.
Watched by Kustos

Konsul builds it. Kustos keeps it running and right.

Once it is live, Kustos checks it on a schedule and drafts a fix when something breaks. A person approves every change.

What could go wrong

A confident wrong answer.

Every answer quotes the passage it came from and names the file, so anyone can check it. When no passage matches well enough, there is no answer, only who to ask.

An old document gives an old answer.

Every source shows its last updated date. Anything over 12 months old is marked "may be out of date" with the owner's name, so that person can confirm it or fix it.

Private information reaches the wrong person.

Files a person cannot open are removed before the search runs, so they never reach the answer or the source list. If the only match is in one of those files, it says a document exists and who owns it. Nothing more.

Staff do not trust it at first.

It shows its sources every time and says "Not in your files" instead of guessing. Those unanswered questions become the list of what to write down next.

Next step

Start with the process that costs you the most.

Rough numbers are fine. Describing it takes about three minutes.

Tell us what's breaking