For knowledge workers

Knowledge Engine

Your business system and your files, in plain English, for the people who run the business and do not write code.

What your staff get

Ask across systems in one question

Orders in the business system, drawings on the shared drive, quotes in a spreadsheet nobody owns. One question, one answer, with the sources attached.

Find a past job from a photo

A customer emails a picture and asks for a price on the same thing. Match it against decades of jobs instead of spending an afternoon on the shared drive.

Legacy work made searchable

Files going back to the early 2000s, indexed by what is inside them rather than by whatever the filename happened to be.

Institutional knowledge, captured

The two people who know how it all works are the reason the business runs. They are also the risk. This gets what they know into a form that outlasts them.

What it looks like to use

One page, one input field. It takes text, images and files in the same turn — because shop floor and field staff photograph things, they do not type part numbers.

In

  • A question in plain English
  • A photo of a part, a shelf label, a damaged unit
  • A whiteboard, or a screenshot of a legacy screen
  • A document dropped straight into the conversation

Out

  • An answer, with the data and documents it came from
  • An honest “I am not sure” where the data is thin
  • A refusal rendered as a refusal — never an empty result dressed up in prose
  • Something a person checks before it reaches a customer

Right-sized from the start

Three to five core users get trained properly and become the people everyone else asks. You do not buy a seat for all sixty staff on day one to find out whether this works.