OptiVis
Book a diagnostic

Co-developed with practicing Texas trial counsel

Private AI for legal and professional firms

Intake response, document review with verified quotes, and litigation research, inside documented data boundaries.

Book a diagnostic

Private retrieval

Answers from your own documents, with the passage shown.

We build retrieval that answers only from a client’s documents and shows the passage each answer came from. It runs on GPU compute we operate, alongside private inference on open-weight models.

Built for a Texas law practice. The model may only point to spans in the documents; it is not allowed to write a quotation of its own. Every quote is checked character for character against the source, and a quote that fails the check is refused, visibly.

It does not decide whether a document is the right authority, and it does not replace the attorney’s judgment. That stays with the attorney.

Status
Built for a Texas law practice.
Boundary
Documents are read by OCR in a service with no network access.
Acceptance
A quote that fails the character check is refused, and you see the refusal.

Intake

Speed is the case in PI intake.

A lead that waits for a callback may sign with another firm. PI ENGINE is in pilot with one firm. A first reply within a minute is a design target, not a guarantee.

Conversations the systems are built to handle

Illustrative examples of the message traffic PI ENGINE and LITIGATOR are built for. Not real clients; names and details are invented for the demo.

Examples. Names and details changed.
ExampleIntake · PI ENGINE
2:13
‹
L
Lead · (281) 555-0142
iMessage›
ExampleDiscovery deadline · LITIGATOR
10:02
‹
PM
Paralegal · Maria
iMessage›
ExampleDeposition prep · LITIGATOR
4:41
‹
RK
Atty · R. Khan
iMessage›

Measured against a baseline.

Every engagement starts with a diagnostic that records baseline numbers and writes acceptance tests, so the system is judged against your own records.

Evidence-backed retrieval

Answers point to the passages they came from. A quote that does not match its source is refused, not shown.

Written acceptance

Acceptance tests are written down before the build, and the build is accepted against them.

Written data boundaries

The boundary is a document, one per engagement.

“Private” is a claim a procurement reviewer should test, so we write it down. For every system we build, a data-boundary document states where each component runs, which model calls leave your environment and to which provider, and how OCR, embeddings, logs, backups and support access are handled, with retention and deletion. You get the first version in the diagnostic, before anything is built.

Client data is processed only within the deployment boundaries agreed in writing. Any external provider, data transfer, and retention policy is documented before use.

Component placement
Where each component runs
Model calls
Which provider receives which data
OCR
Where processing occurs
Embeddings
Where vectors are stored
Logs
What is retained
Backups
Where copies reside
Support access
Who can access what
Retention and deletion
Duration and removal procedure

These are the fields each document answers, not a record of a particular deployment.

Engagement

How an engagement is priced.

  1. Diagnostic

    $7,500

    Ten business days, one workflow. Credited in full against a build signed within 60 days.

  2. Production build

    From $25,000

    Fixed price, accepted against tests written before the build.

  3. Operate

    From $2,500 a month

    Bounded and optional.

Start with the diagnostic.

$7,500 fixed · ten business days · one workflow

Book a diagnostic