Private AI document search

Private AI document search for the files your team already has.

Ask a question in plain English and get an answer with the document and page it came from. Private knowledge systems that respect the permissions you have already set.

Where the time goes

Folder search finds file names. Your team wants the clause, the figure or the procedure, and does not know which folder it is in.

01

Five folders could hold the answer, and only one person remembers which

02

Keyword search returns forty files and none of them open at the right page

03

The current version and the superseded one sit side by side with no marking

04

Public chatbots are quicker, but nobody can say what happens to the file once it is pasted

How we solve it

We connect to the stores you already use, index what is in them, and return answers with the source attached rather than a list of filenames.

Custom RAG & domain LLMs

Ask in plain English

Type the question as you would to a colleague and get the passage that answers it, with the document, section and page linked.

Custom RAG & domain LLMs

Permissions carried over from your stores

Answers draw only on material the person asking is already cleared to open, using the access rules set in SharePoint or Google Workspace.

Custom RAG & domain LLMs

Private deployment, no data resale

Run in your own cloud, a private environment we manage, or on premise. Your documents are never used to train third-party models.

Custom RAG & domain LLMs

Says when it does not know

If the archive has no answer, it reports that instead of writing something plausible, and points at the folders closest to the question.

Custom RAG & domain LLMs

Checked against your real questions

We test retrieval on your actual archive, including scanned material, and show which folders answer well before your team depends on them.

Project stories

What this could look like in your business.

Structural engineers · Cheshire

Past expertise, without another interruption.

An engineering practice with calculations and reports going back to 2011, filed differently by every engineer who wrote them. Graduates keep interrupting directors with the same questions.

A private knowledge assistant now indexes the archive, keeps the existing folder permissions and links every answer straight back to the source file it came from.

Older scanned drawings still give patchy results in places. The team reviewed retrieval quality together before relying on it for anything that matters.

Directors get fewer interruptions, and new colleagues find their own answers from day one.

Industrial distributor · West Midlands

Quotes that don't wait for Dave.

A second-generation fixings and industrial supplies business. Dave has been there 22 years and holds most of the customer pricing in his head. When he's on holiday, repeat quotes stall at the counter.

We connected an assistant to their existing CRM and five years of order history. Anyone on the counter can ask for a customer's last price on M10 resin anchors and pull up the order it came from.

The product codes needed cleaning up before the answers could be trusted, so that came first. Dave still handles the tricky quotes himself.

Repeat quotes no longer wait for one person to be back at his desk.

What to measure

Agree the targets. Test the improvement.

These are measures for a pilot, not claimed client results. We agree your starting point and targets during discovery, then review the evidence with your team.

Time spent searching

Minutes from a question to a sourced answer, compared with folder browsing today.

Answers without asking a colleague

Questions resolved independently instead of waiting for the person who knows.

Confidence in the source

Whether people can see which document an answer came from and check it.

Archive coverage

Share of real questions answered well, and the folders that still need work.

Systems we connect
SharePointGoogle DriveOneDriveConfluenceSalesforceHubSpotNotionWindows file serversAnything with an API

We build around the tools you already run. Anything with an API or a database is fair game, with access and scope agreed during discovery.

Who this is for

For any team whose answers are written down somewhere, and whose data cannot be pasted into a public tool.

  • Professional services holding contracts, reports and client history
  • Engineering and technical practices with long archives
  • Distributors with product, pricing and order history across systems
  • Groups with several sites sharing policies and procedures
How we work

Discover, build, evaluate, operate.

01

Discover

Start with the task taking too much time. We look at the data, the systems and the constraints, then agree a starting point and the measures that show whether it worked.

02

Build

We build a focused version on one high-value problem, with the boundaries, permissions and approval points your team needs.

03

Evaluate

Your team compares the result against the agreed starting point. Gaps and teething problems are reviewed together before a wider rollout.

04

Operate

We monitor quality, cost and drift, then extend the system where it earns its place in the workflow.

FAQs

Questions, answered.

What the system does, what stays with your team, and how your data is handled.

What does your team search for most?

Tell us the question and the store that should hold the answer. We will test how well it responds.