Knowledge Assistant

Answers from your own documents, with the source for each one.

  • How long4 to 8 weeks
  • How we workSet-up and subscription

What you receive

?

Your team asks a question in plain words and gets the answer from your own documents, with the source, in seconds.

  1. thinkUnderstand the problem

    Which documents should it use?

    You receiveA review of your source documents

    Out-of-date documents give out-of-date answers.

    What it is. A review of your policies, manuals and files: which are current, which conflict and which to leave out.

    Why it matters. Out-of-date documents give out-of-date answers. This step prevents that.

  2. buildEngineer it

    Will it know about changes?

    You receiveYour documents brought in and kept up to date

    Answers stay current without anyone remembering to update them.

    What it is. Your documents loaded, and kept in step when they change.

    Why it matters. Answers stay current without anyone remembering to update them.

  3. buildEngineer it

    Can we trust the answer?

    You receiveAn assistant that cites its sources

    People can check, and they learn where things are.

    What it is. Every answer links to the document and section it came from.

    Why it matters. People can check, and they learn where things are.

  4. buildEngineer it

    Will people see things they should not?

    You receiveAccess rules for each role

    Sensitive information stays with the right people.

    What it is. Permissions so people only get answers from documents they are allowed to see.

    Why it matters. Sensitive information stays with the right people.

  5. testProve it works

    How accurate is it?

    You receiveA test set to check its answers

    You know how well it works before your team relies on it.

    What it is. A set of real questions with known answers, used to measure accuracy.

    Why it matters. You know how well it works before your team relies on it.

  6. shipLaunch it

    Where do we ask it?

    You receiveA web or Teams interface

    It fits where your team already works.

    What it is. Ask questions in a web page or inside Microsoft Teams.

    Why it matters. It fits where your team already works.

  7. shipLaunch it

    Who looks after it?

    You receiveAn admin guide

    Your team can run it without us.

    What it is. A guide for adding documents, managing access and checking quality.

    Why it matters. Your team can run it without us.

01thinkUnderstand the problem

Which documents should it use?

A review of your source documents

What it is

A review of your policies, manuals and files: which are current, which conflict and which to leave out.

Why it matters to you

Out-of-date documents give out-of-date answers. This step prevents that.

02buildEngineer it

Will it know about changes?

Your documents brought in and kept up to date

What it is

Your documents loaded, and kept in step when they change.

Why it matters to you

Answers stay current without anyone remembering to update them.

03buildEngineer it

Can we trust the answer?

An assistant that cites its sources

What it is

Every answer links to the document and section it came from.

Why it matters to you

People can check, and they learn where things are.

04buildEngineer it

Will people see things they should not?

Access rules for each role

What it is

Permissions so people only get answers from documents they are allowed to see.

Why it matters to you

Sensitive information stays with the right people.

05testProve it works

How accurate is it?

A test set to check its answers

What it is

A set of real questions with known answers, used to measure accuracy.

Why it matters to you

You know how well it works before your team relies on it.

06shipLaunch it

Where do we ask it?

A web or Teams interface

What it is

Ask questions in a web page or inside Microsoft Teams.

Why it matters to you

It fits where your team already works.

07shipLaunch it

Who looks after it?

An admin guide

What it is

A guide for adding documents, managing access and checking quality.

Why it matters to you

Your team can run it without us.

From brief to done

  1. 1

    Weeks 1 to 2

    Review

    Documents reviewed and access rules agreed.

  2. 2

    Weeks 3 to 6

    Build and test

    The assistant engineered and checked against the test set.

  3. 3

    Final weeks

    Launch

    Live in the web or Teams, with the admin guide.

Where would AI actually help us?

AI opportunity map. The three places in your business where AI would save the most time, what each would need, and the risks to watch.

  1. A 45-minute call about how your team works today
  2. A two-page report: three opportunities, what each needs, the risks, and a rough size of effort
  • It is free. There is nothing to pay and nothing to sign.
  • The report is yours to keep and share, whatever you decide.
  • No sales call unless you ask for one.

Get it free

Your time: 45 minutes of your time

Only your email is needed. The rest helps us start sooner; anything you skip, we will ask by email.

A few examples are plenty.

No sales call. One follow-up email at most. Privacy · Other free first looks

Questions people ask

How much does it cost?

We send a written quote after your request: what it covers and what it does not. The tier, scope and timing set the price.

Could I just use AI for this?

Who owns the work?

You do. Code, designs, files and documents are yours, and the quote says so in writing.

Can we change the scope?

Yes. If something needs adding or removing, we agree it in writing before we do it.

Can we stop?

Yes. The quote states the notice period. Usage such as messages, ads or AI is charged at the rate in the quote and stops when you do.

Hire us for Knowledge Assistant

Know what you need

Five short questions. We reply with questions or a written quote.

Hire us
or

Not ready to commit

A small piece of real work, written up and yours to keep.

Get a free first look

Questions first? Email [email protected]