How is this different from the search we already have?

Keyword search finds files containing your words. This answers the question. Ask what was agreed about out-of-hours cover and you get the clause, in a sentence, with a link to the amendment it came from and the date it was signed.

How do we know it is not making things up?

Every answer carries a citation to the document it came from, and you can open it. It answers only from your material, never from general knowledge, and where your material holds no answer it says so rather than guessing. That is a build rule, tested before launch, not a hope.

Will it show people things they should not see?

No. Answers are limited to what the person asking can already open in the source systems, so it inherits the permission model you already run rather than sitting outside it. We wire that in first and test it with real accounts before anyone else gets a login.

How much of our material does it need to be useful?

Less than people expect. We start with the sources that carry the most questions, usually contracts and support history, so your team is asking it things while the rest is still being connected. Every source added after that makes it better, and none of them has to be tidied first.

What do you need from us?

The brief, the brand and the access. What your people need to find and where it lives, how the answers should sound, and read access to the sources and the tools it will answer inside. Everything after that is us.

AI knowledge base and company search, with a source on every answer

Everything your company knows, behind one question box. Ask in plain English, get the answer in a sentence with its source attached, inside Slack, Teams or WhatsApp. You bring the brief and the brand. Everything after that is ours.

One question box, every answer

Everything your company has ever written down or said on a call, answered from in plain English. You point us at the sources and we do the rest.

Every source, as it isThe shared drive, six years of email, the wiki, contracts, support tickets, call transcripts. Ingested in whatever state they are in, no tidying first.
Answers in sentencesAsk what was agreed about out-of-hours cover and get the clause, not forty files with the words in them.
A source on every claimEvery answer links to the document it came from and the date it was signed. Open it, check it, act on it.
Your permissions, inheritedPeople see only what they could already open. Wired in before launch and tested with real accounts.
Kept current on its ownNew documents indexed as they land, superseded versions retired, so the answer is always the latest one.
Reported backWhat people asked, what it could not answer, and what to write next. The gaps become the to-do list.

Ask it where you already work

No new login and no new tab. The question box sits inside the tools your team already has open and the assistants they already talk to.

Slack
Teams
WhatsApp
Your website

Claude
ChatGPT
Gemini
MCP

Connected over MCP, so the assistant your team already uses can ask your knowledge base directly and cite the source in its reply.

Book twenty minutes →Send us the brief

Connected to where your knowledge already lives

Read access to the systems your material lives in, through your own accounts, is all it takes. A fixed price quoted before anything starts.

Google Drive
Microsoft 365
Gmail
Slack
Notion
Confluence
Dropbox
HubSpot
Zendesk
Intercom
GitHub
Zoom

It runs in your accounts and under your name, so nothing of ours needs switching off if we ever part ways.

How access and data are handled →

The day-to-day, all of it automated

Fourteen jobs a specialist does by hand. The run does every one, on a schedule, inside the tools you already use. You see the results, not the work.

Slack, illustrated with example figures: Slack: internal channel query regarding call-out fees answered concisely by AI assistant with source document link. — Slack: internal channel query regarding call-out fees answered concisely by AI assistant with source document link.

Document folders connected to central search regularly
User access rights checked to protect privacy
Search logs checked to find missing answers
Outdated procedure documents updated or archived
Source links checked to match official documents
Help assistant added to internal chat channels
Search libraries refreshed weekly as new documents arrive
Answer confidence scores checked to ensure accuracy
Unanswered staff questions turned into help articles
Content access logs checked for sensitive files
Document converters maintained for PDFs and Word files
Thumbs up ratings tracked to measure helpfulness
System rules refined to maintain clear summaries
Knowledge categories organised for easy document navigation

Notion, illustrated with example figures: Notion: company knowledge base home page listing documentation sections alongside recent verification dates. — Notion: company knowledge base home page listing documentation sections alongside recent verification dates.

Claude, illustrated with example figures: Claude: workspace query response drawing directly from connected company files and citing specific policy documents. — Claude: workspace query response drawing directly from connected company files and citing specific policy documents.

Illustrations of the tools in use, drawn for this page for an example business, Marlow & Finch. Every figure in them is an example, not a client's data, and any person in them is generated. Tap a picture to open it full size.

SlackAsk in the channel
Microsoft TeamsOr ask there
WhatsAppOr ask on the phone
NotionWhere the answers come from
Google DriveAnd from here, permissions kept
ClaudeThe reader that cites its source

The night shift

Nobody in the building. This is the job doing itself at eleven at night, and what you see in the morning.

Everything on the shelves behind one question box, with the source on every answer.

Questions we get asked about this

How is this different from the search we already have?: Keyword search finds files containing your words. This answers the question. Ask what was agreed about out-of-hours cover and you get the clause, in a sentence, with a link to the amendment it came from and the date it was signed.
How do we know it is not making things up?: Every answer carries a citation to the document it came from, and you can open it. It answers only from your material, never from general knowledge, and where your material holds no answer it says so rather than guessing. That is a build rule, tested before launch, not a hope.
Will it show people things they should not see?: No. Answers are limited to what the person asking can already open in the source systems, so it inherits the permission model you already run rather than sitting outside it. We wire that in first and test it with real accounts before anyone else gets a login.
How much of our material does it need to be useful?: Less than people expect. We start with the sources that carry the most questions, usually contracts and support history, so your team is asking it things while the rest is still being connected. Every source added after that makes it better, and none of them has to be tidied first.
What do you need from us?: The brief, the brand and the access. What your people need to find and where it lives, how the answers should sound, and read access to the sources and the tools it will answer inside. Everything after that is us.

Got a question the list did not answer? Ask it on a call, or send us the brief and we will come back with a fixed price.

Book twenty minutes →Send us the brief