AI knowledge base chatbot for contracts and policies

Answers from your documents, with the clause cited

The agent searches your contracts, policies and internal guides. It answers briefly and shows the source right away: file, section, clause. If the documents don’t cover it, it says so.

The answer exists somewhere. Nobody can find it

  • A lawyer hunts for the penalty clause across forty supplier contracts, opening each PDF by hand.
  • A new sales manager spends a week asking colleagues how discounts get approved, though it’s all in the policy.
  • The shared folder holds three versions of the same policy, and nobody is sure which one applies.
  • A public chatbot doesn’t know your rules, and you can’t upload contracts to it anyway.

What changes after launch

  • 01Anyone finds the answer themselves without pinging legal or colleagues
  • 02Every answer is checkable: the quote and clause link sit right next to it
  • 03New hires learn from the actual policies, not from hearsay

How the agent works

  1. 01

    Collect the corpus

    Contracts, policies, guides, the wiki. Together with the document owners we drop duplicates and outdated versions, so the agent only answers from what you’ve approved.

  2. 02

    Split into fragments

    Documents are split by section and clause, keeping clause number, date and version. That’s why the link points to clause 4.2, not to “the whole contract”.

  3. 03

    Search first, then answer

    For each question the agent first retrieves matching fragments and writes the answer from them alone. This approach is called RAG.

  4. 04

    Show the source

    Every answer comes with a quote and a link to the file. Checking it takes ten seconds instead of blind trust.

  5. 05

    Say “I don’t know”

    If no fragment fits, the agent replies that the documents don’t cover it and offers to route the question to the person in charge.

  6. 06

    Keep the base current

    New versions enter the base by the rule you choose: from a folder, from the wiki or after sign-off. Old versions get flagged.

Which scale is yours?

One task, three different projects. Pick the one that looks like you and press “I want this” — your request arrives tagged, and we send an estimate in 1–2 days.

Small business

One team and one folder of policies that people keep asking the same questions about.

What we build

  • One document set, e.g. sales team policies
  • Employee chat in Telegram or the browser
  • Answers with a quote and a file link
  • Before/after measurement on one team
Integrations
A file folder or wiki; no connection to accounting systems
Where it runs
Cloud; the model is chosen to match your data requirements
Timeline
Orientation: 2–4 weeks

Mid-size business

common start

Several departments, hundreds of contracts and policies, and different people need to see different things.

What we build

  • Several document types: contracts, policies, guides, templates
  • Roles: sales can’t see HR policies, legal sees everything
  • Automatic updates from folders, the wiki or your document system
  • Find a contract by 1C or CRM details: counterparty, number, date
  • Log of unanswered questions — a to-do list for your policies
Integrations
1C, CRM, e-document exchange, corporate wiki, employee accounts for roles
Where it runs
Cloud or your own server, depending on your security team
Timeline
Orientation: 1–2 months and up

Enterprise

common start

Contracts contain trade secrets and personal data, and security won’t sign off on any cloud.

What we build

  • Model and knowledge base on your servers; data never leaves the perimeter
  • Access rights by department and document classification
  • Audit log: who asked what and which document they got
  • Architecture designed for Russian data law (152-FZ), agreed with security
  • SLA for support and knowledge base updates
Integrations
Document management system, 1C, e-document exchange, domain sign-in, your monitoring
Where it runs
Closed perimeter on your servers; GPU hardware is a separate line item
Timeline
Orientation: 2–3 months and up

Pilot from RUB 300,000. Beyond that we price by task and hours.

Questions

Won’t the agent make up a clause that isn’t in the contract?

Language models can be wrong, so we don’t ask the model to remember anything. It answers only from retrieved fragments and shows the quote. If nothing fits, the answer is “the documents don’t cover this”. Before launch we run a set of real questions from your staff and go through every miss.

Who gets to see which documents?

Permissions are set before launch. The agent only searches documents the employee’s role allows. A sales manager won’t get a quote from an HR policy, even when asking about it directly.

We have three versions of the same policy. Now what?

We sort that out at the start. The current version is marked, old ones are removed from search or kept with a “superseded” flag. The agent states which version its answer is based on.

Can it run without the cloud?

Yes. If contracts can’t leave the building, we put the model and the base on your servers. The architecture is designed for 152-FZ, and we work under NDA. GPU hardware is quoted separately, not hidden in a subscription.

Our older contracts exist only as scans. Will they work?

Yes, if the scan is legible. We run a sample through text recognition first and check the quality. Unreadable pages show up right away; rescanning them beats making the agent guess.

A quote in 1–2 days

Name the process that eats time. You get a pilot range, not a 40-slide deck.

Or message us