EN TR
Contract DNA · by ozDNA · Pilot open

Not a legal opinion.
A decision-ready map of what changed.

Upload two versions of a contract. Contract DNA finds every business-material change — payment, renewal, termination, liability, IP, data — and shows you the old text, the new text, where it sits, why it matters and how urgently a human should look at it. Every finding is linked to its source and recorded for audit.

Request pilot access See a sample report ↓
InputTwo versions · PDF or DOCX
MethodDeterministic diff first, AI second
OutputEvidence-linked report · PDF export
RecordSource, model version, human decision
01 — The problem

Redlines show you every comma.
They don't tell you which ones cost money.

A counterparty sends back "v4 — minor edits". Forty pages. Word's compare view lights up like a Christmas tree: reformatted headings, renumbered clauses, a few "shall"s turned into "will"s — and, buried in §12.2, a termination notice period that quietly dropped from 90 days to 30, for them only. Founders, procurement leads and small legal teams read these on Friday nights. Contract DNA reads them first, and points at the three things that actually moved.

02 — Sample output

This is the report.
Everything else is plumbing.

An illustrative Deal Diff on a fictional master services agreement. Three of eleven detected changes shown. Severity is a review priority, not a dollar figure — see the FAQ.

MSA — Acme Cloud × Northwind Retail v3 (2026-09-02) → v4 (2026-09-29)
Sample · fictional documents
Pages compared38 + 41
Changes detected11
Critical2
Material3
Critical Termination §12.2 Termination for convenience
v3 p.17 · v4 p.18
change_id CHG-0007
v3 — before
Either Party may terminate this Agreement for convenience upon ninety (90) days' prior written notice to the other Party.
v4 — after
Provider may terminate this Agreement for convenience upon thirty (30) days' prior written notice to Customer. Customer may terminate for convenience only upon ninety (90) days' notice and payment of the Early Termination Fee in Schedule 3.
Business impact

The right became one-sided. The vendor can now exit on 30 days; you still need 90 and pay a fee that did not exist in v3 (Schedule 3 is also new — see CHG-0008). With a 12-month migration path for this service, 30 days is operationally unworkable.

Suggested question: "Why did termination become asymmetric between v3 and v4?" Evidence: 2 spans · confidence high · review: required
Material Liability §14.1 Limitation of liability
v3 p.21 · v4 p.22
change_id CHG-0009
v3 — before
…shall not exceed the total Fees paid or payable in the twelve (12) months preceding the event giving rise to the claim.
v4 — after
…shall not exceed the total Fees paid in the six (6) months preceding the event giving rise to the claim, excluding any Fees for Professional Services.
Business impact

The cap halved, and the base it is computed on shrank twice: "payable" was removed (unpaid invoices no longer count) and Professional Services fees were carved out. Rough effect on a $20k/month engagement with $60k of services: cap moves from ~$300k to ~$120k.

Evidence: 3 spans · confidence high · review: recommended
Needs human review Data protection §9.4 Sub-processors
v3 p.12 · v4 p.13
change_id CHG-0004
v3 — before
Provider shall not engage a Sub-processor without Customer's prior written consent.
v4 — after
Provider may engage Sub-processors in accordance with the Data Processing Addendum.
Why no severity

The clause now defers to a document that was not uploaded. Whether this is a loosening (general authorisation with notice) or neutral (the DPA still requires consent) cannot be determined from the text in hand. Contract DNA abstains rather than guess, and asks for the DPA.

Evidence: 1 span · confidence insufficient — abstained · missing: Data Processing Addendum
diff engine det-diff 0.3 · analysis model m-2026.10 / prompt p-14 evidence hash sha256:4f1c…9ae2 reviewer — pending · generated 2026-10-01 14:22 UTC

AI-assisted review — does not replace human review and is not legal advice. Parties, clauses and figures above are invented for illustration.

03 — How it works

Diff first. Model second.
Human when it matters.

The language model never decides on its own that something changed. A deterministic comparison establishes what moved; the model explains why it matters, and must point at the exact text it relies on. If it can't, the finding is routed to a person instead of being dressed up as a fact.

01

Upload two versions

Text-based PDF or DOCX — the draft you sent and the one that came back. Pages are parsed into sections and clauses. Scanned documents need OCR, which we price separately and flag before you spend a credit.

02

Deterministic diff & clause matching

Clauses are aligned across versions even when they were renumbered or moved. Every insertion, deletion and rewording is captured mechanically. Formatting noise is separated from substantive change. This step is reproducible — run it twice, get the same answer.

03

Classification & business impact

Each substantive change is classified — payment, renewal, termination, liability, IP, data protection, security, audit — and explained in plain business terms, with a severity and review priority. Output is a structured record, checked against a schema and against the source spans it cites.

04

Report, record, decision

You get a shareable report and a PDF. Behind it sits an auditable record per change: source spans and their hash, the diff-engine and model/prompt versions that produced the finding, and the human decision — accepted, pushed back, escalated — with reviewer and timestamp.

04 — Scope

What it is. What it is not.

We would rather you know the edges before the pilot than after.

In the first release

Two-version comparisonText-based PDF and DOCX, up to 60 pages combined per standard comparison.
Clause-level diffAligned across renumbering and moves; formatting noise filtered out.
Change classesPayment, renewal, termination, liability, IP, data protection, security, audit.
Per-change explanationBefore/after text, page or section reference, business impact in plain language.
Severity & review priorityPlus explicit uncertainty: the system abstains and escalates when evidence is thin.
Exportable report & audit recordShareable link, PDF, and a traceable record of source, model version and human decision.

Deliberately not

A legal opinionContract DNA tells you what changed and why it might matter. Whether to sign is yours and your counsel's.
Automatic approvalNo finding is ever marked "fine to sign". Every output is an input to a human decision.
"Compliant with law X" stampsWe don't issue compliance verdicts we can't evidence.
Full contract lifecycle managementNo templating, negotiation workflow, obligations tracking or renewals calendar — yet.
E-signatureSign wherever you already sign.
Single-document "risk scoring"v1 is about change between versions, not a grade for a lone contract.
05 — Who it's for

People who sign contracts
without a legal department behind them.

Or with a small one that is already three redlines deep.

Startup founders

Customer MSAs, vendor terms, SAFE side letters. You negotiate them yourself and need to know, fast, what the other side actually changed.

B2B SaaS teams

Enterprise customers return your paper heavily marked. Catch the liability cap, the audit right and the data clause before sales says "it's basically our template".

Agencies & consultants

Statements of work and framework agreements that keep evolving. See scope, payment and IP shifts across versions in one view.

Procurement

Compare supplier redlines against your standard terms and prioritise what goes to legal — with the evidence already attached.

Small legal & compliance teams

Triage, not replacement. Spend your hours on the two critical changes, not on finding them.

Investors & advisors

Portfolio companies send you "the latest version". Know what moved since the one you read.

06 — Pilot pricing

Priced per comparison.
No unlimited plan, on purpose.

Every comparison costs us real compute, so we don't sell "unlimited". Plans come with a monthly allowance of standard comparisons and clear limits. Pilot pricing below is what we are validating with early customers; it may change before general availability, and pilot customers keep what they signed up for.

Starter $39/ mo 15 comparisons / mo
  • 1 user
  • Clause-level diff & change classes
  • Severity & review flags
  • Evidence-linked PDF report
Professional $99/ mo 60 comparisons / mo
  • 1 user
  • Everything in Starter
  • Version history per contract
  • Advanced review view
Team $129/ mo 100 comparisons / mo
  • 3 users
  • Everything in Professional
  • Team notes & human sign-off
  • Decision records per change
Business & Enterprise Talk to us Up to 10 users · custom quota
  • Executive view & reporting
  • Advanced controls
  • Security review, SSO, data residency, SLA on request
What a comparison is

One standard comparison = two text-based versions of one document, up to 60 pages combined. Longer documents, scanned PDFs needing OCR and re-analysis after edits are counted separately and shown before they run. Every pilot account starts with 3 free comparisons. Top-up packs and annual billing (two months free) are planned for general availability.

07 — FAQ

Straight answers.

Is this legal advice?

No. Contract DNA is an AI-assisted review tool: it tells you what changed between two versions and why that change may matter commercially. It does not tell you whether to sign, and it does not replace your lawyer. Every report carries that scope statement.

Does it give a "risk score" out of 100?

Deliberately not. A model's confidence is not the size of your exposure. What you get is a review priority per change — critical, material, minor — plus an explicit "needs human review" state when the evidence is insufficient. Where a number helps (a liability cap halving, a notice period shrinking) it is quoted from the text, not invented.

What happens when the model isn't sure?

It says so. Findings must cite the exact source spans they rely on, and they are checked against a schema and a set of policy rules. A finding without evidence is not shown as a verified finding — it is routed to human review with a note on what is missing (as in the sub-processor example above).

Can I analyse a single contract, not two versions?

Not in the first release. v1 is built around the question "what changed between the version I sent and the one that came back". Single-document review is on the roadmap once the comparison engine has earned trust in pilots.

What file types and languages?

Text-based PDF and DOCX. Scanned PDFs need OCR, which we flag and price separately. The pilot is English-first; other languages are being evaluated on real pilot documents before we commit.

What happens to my contracts?

Confidential documents are sent to the analysis model only with your consent under a data-processing agreement; sensitive content is not kept in logs beyond what the audit record needs, and retention, deletion and regional-processing terms are agreed in writing before the pilot starts. Ask us for the current DPA.

Which AI model do you use?

A frontier commercial model for analysis, behind a deterministic diff and a validation layer, with a cheaper model for first-pass extraction where it is good enough. We benchmark candidates on expert-labelled changes and will switch when the numbers say so. The model and prompt version that produced each finding is recorded in the report, so a result is always reproducible to its source.

When can I use it?

We are onboarding a small number of pilot customers now, starting with a concierge run on your real (or anonymised) documents. Request access below and tell us roughly how many contracts a month you handle.

08 — Pilot access

Send us the pair of versions you least want to read.

We'll run it, walk you through the report, and tell you honestly what it caught and what it missed. Pilot seats are limited; founders and small teams go first. A handful of emails total, no spam.

We store your email and answers to contact you about the Contract DNA pilot — nothing else, shared with no one. Unsubscribe with one reply. See our privacy policy.