Clause

Contract review was the slowest step in every deal.

Studio conceptAI-native product
Studio concept — Clause. Illustrative interface; no client, no claimed outcome.

The route.

How a request moves through the system, stop by stop. Illustrative, like the rest of this concept.

  1. Contract in
  2. Parse
  3. Clause extraction
  4. Risk check
  5. Reviewer
  6. Signed off
Illustrative route — Clause.
Type
Studio concept
Category
AI-native product
Our role
Product design, AI architecture and full-stack build
Outcome
Not applicable. Concepts don't get to claim results.
01

Overview

Clause is a studio concept for teams that review the same kinds of contracts every week. It reads the document, flags what deviates from the team's own playbook, and leaves the decisions to the people accountable for them.

02

The challenge

A model that is right most of the time is still wrong in front of a lawyer. The product had to make every suggestion checkable in seconds, and make it obvious when the model wasn't sure.

03

Scope

  • Playbook modelling
  • Retrieval and clause extraction
  • Review interface
  • Evaluation suite
  • Audit trail
04

Technical decisions

  1. Every flag cites its source.Flags link to the exact clause and the playbook rule they break. No citation, no flag.
  2. Evaluation before features.A labelled set of real-shaped contracts runs on every change, so quality is measured, not assumed.
  3. AI drafts. Engineers decide.The model drafts redlines; a person accepts, edits or rejects each one, and the decision is logged.
Illustrative excerpt
const flag = await review.run({ clause, playbook });
if (!flag.citation) return null;          // no source, no flag
if (flag.confidence < 0.7) flag.route = "needs-human";
audit.log({ clause: clause.id, flag, model: MODEL_VERSION });
05

Deliverables

  • Review web app
  • Playbook editor
  • Evaluation pipeline
  • Audit log
  • Model and prompt documentation

Technologies

  • TypeScript
  • Python
  • Retrieval
  • Structured outputs
  • Evaluation harness
  • PostgreSQL

Next studio concept.

Payments infrastructure

Payment events kept getting lost between services.Ledger railRead the case study

Got something complicated?

Tell us what you're building. You'll hear back from an engineer, not a sales team.