AI for Legal tech

AI for legal document and knowledge software

Cited answers from the files, contract clauses read into fields, writing help that keeps the facts, and drafts checked against the record.

For legal document, knowledge and records software. AI legal document review that cites the page or declines, writing tools that never change an approved name or figure, contract clauses read into your fields with the page behind each value, and originals left in your system.

Built for: Legal document management, knowledge and research platforms, records and archive software.

Already built or tried AI? Get it scored with the AI Scorecard.

tessaline.example/merrow-vance/matters/okafor-v-thistle

Merrow & Vance · Recordly

Demo
  • When did Thistle first learn of the brake defect?

Step 1 of 5

Illustrative demo on a fictional agency and firm. Not client work.

Where these products get stuck

What gets in the way, and how we handle it.

  1. 01

    Answers without the page

    Cite, or decline

    Each claim cited to its passage, and a clear decline when the files are silent.

  2. 02

    Files copied into an AI tool

    Approved text only

    Your system sends approved text and metadata; originals stay in your system.

  3. 03

    Rewrites that change facts

    Locked terms, checked spans

    Approved terms locked first, and only flagged spans rewritten.

What your customers' counsel asks first

Short answers your team can repeat.

  • Answers come only from documents the user is allowed to open.
  • Every claim cites its page; the system declines when the files are silent.
  • Originals stay in your document system.
  • We work within your privilege and confidentiality obligations and privacy requirements.

AI inside your product

The modules that fit this kind of platform.

Each one is shown on a fictional customer. It is built into your codebase and ships under your name, on an engine we license to you.

What it connects to: Your document system's APIs, roles, matters and clearances, and your approved list of names and terms. Sprints use sample case files.

Proof

What we have built that this rests on.

57 featured AI case studies: AI products and AI built into live products, each written up on our Work page.

NenoBrief by Neno Technologies

Document AI · Cited answers in production

Archive officers get cited answers inside their live document system, files never copied

Archive records could not reach an outside AI. Now the client's live document system calls our self-hosted gateway for cited answers.

Brownfield AIInside a live productCited answers
Read case study

NenoDoc Lexicon by Neno Technologies

Document AI · Self-hosted workspace

Archive teams get cited answers in French and English on one client-owned GPU

Sensitive archives could not go to an outside AI. Now teams ask in French or English and get answers cited to the page, all on the client's GPU.

AI-native productCited answersDocument intelligence
Read case study

NenoDoc Lexicon by Neno Technologies

Document AI · Writing that keeps the facts

Archive indexers fix grammar and style without a name, date or figure changing

AI rewrites can quietly alter names and numbers. Ours edits only flagged spans, and approved terms are locked before the model sees them.

AI-native productHuman approvalDocument intelligence
Read case study

WikiTeq

AI engine · Cited document answers

WikiTeq's self hosted AI chat now answers from its documents, citing every source

The chat could not answer from the firm's own documents. Now a separate retrieval service feeds it passages and shows the source of each answer.

Brownfield AICited answersInside a live product
Read case study

SovrenAI

Verification · Claim checking

Claim verification on the founder's own ontology, where the language model only suggests

A founder's AI-coded prototype could not be measured or audited; now rules anchor every verdict and each answer shows how it was reached.

AI-native productAudit trailProduction AI
Read case study

How it works

Three ways to start, each at a fixed price.

Most document platforms start with Recordly in a Build Sprint: scoped retrieval and cited answers on one document type.

Legal Tech Platform Product Review · 30 minutes, no chargeStart here. We look at your platform with you, agree the outcome you want for your users, and tell you which of the three below fits.

Book a 30-minute Product Review

No AI yet, and a module fits

Build Sprint

$10,000 fixed3 weeks

Pick it when: One of our modules delivers the outcome you want.

Recordly · Clausely · Redactly · Proofly · Attestly

  • One user outcome (2 to 3 related capabilities) working in your staging, behind a feature flag
  • Pull requests to your repo, built on sample transcripts, case files and synthetic matters
  • Quality and safety evals, the cost per user and a packaging recommendation
  • A fixed-price quote for production

Something new, or a plan first

Planning Sprint

$5,000 fixed2 weeks

Pick it when: You need something our modules do not cover, or want a plan before you build.

  • Where AI fits across your platform, including beyond our modules
  • A prioritized capability map, with what each one depends on
  • A readiness review of your architecture, data, integrations and permissions
  • A fixed-price quote to build it and take it to production

AI already built or tried

AI Scorecard

$5,000 fixed2 weeks

Pick it when: You have already built or tried an AI feature in your platform, live or not.

  • One AI feature you have built, tested in staging on 50 of your own cases, with names and contact details removed
  • Tests for invented names and citations, another matter's documents, changed figures and prompt injection
  • Cost per user and a packaging recommendation
  • A scorecard, ranked fixes, draft security answers and a fixed quote

Not a compliance audit or certification.

How the AI Scorecard works

Production, at a fixed quote

We take what your Sprint built or planned live for your users, by pull request, with no standing production access. It typically includes load testing at your peak and a spend cap per firm. Your Sprint or Scorecard fee counts toward it.

After go-live, optional support

The product is finished and yours to run. If you want us to stay on: a named lead engineer, a monthly quality and cost report, testing before any model change, and more capabilities, each at its own fixed quote.

Stop after any Sprint and keep what you got.

How a Build Sprint runs

  • In the setup week we map your platform, documents and roles and agree what the Sprint touches.
  • We follow your coding standards, tests and CI; your engineers review and merge every pull request.
  • Half at signature, half when the Sprint Pack is delivered.
  • Your time: about 2 to 3 hours a week from a product owner, plus an engineer to review pull requests.

Product improvements you can measure

What we agree to measure: quality and cost on test sets in the Build Sprint, adoption and outcomes once it is in production, so the decision to go further is made on evidence.

01

Answers users can check

Measure

Share of answers with a cited page

02

No invented answers

Measure

Questions declined when the files are silent

03

Cleaner drafts

Measure

Conflicts with the record caught before review

We set the success measures with you in the setup week.

Built for confidential legal records

Controls your customers' security reviews ask about.

Each control is a design fact about how the module is built and how we work, not a compliance claim.

  • Files stay with their owner

    Extraction in the user's browser or from approved text only, with originals left in their system of record.

  • Cite, or decline

    Every answer cites its passage, and the system says so when the files do not hold the answer.

  • People decide

    Records publish, files release and edits apply only when a person confirms them.

We work within your privilege and confidentiality obligations, court rules and privacy requirements. Compliance depends on the complete product, contracts, policies and operating environment; Datics does not present software engineering alone as legal certification, and nothing a module shows is legal advice on its own.

How we handle confidential legal records

Questions we hear on the first call

Straight answers before you book.

Can it run fully self-hosted?

Yes. We have run document AI, OCR included, on client-owned GPU hosts with no outside AI service, portable to local hardware.

Do you work with legal research and e-discovery tools?

Our document work covers cited answers, version comparison, entity extraction and writing tools. Tell us what your product does, and we say plainly in the Product Review where we fit.

See it on your own platform.

Bring one product, workflow or AI feature. In 30 minutes we tell you which of the three ways to start fits, what it would cost to serve per user and what your customers' counsel will ask.

Calls run in US Central time. No generic AI presentation: we discuss your product, users and production constraints.