Automate contract review
Unstract reads third-party paper as it arrives, compares each term with the playbook you write, and sends only the deviations to a lawyer, with the clause text beside your standard position.
Trusted by legal and contract teams around the globe
Third-party paper waits in a queue for a first read
Your playbook already says which positions you accept and where you give ground. The counterparty's contract arrives on their own form, and a lawyer reads it clause by clause to find the few terms that matter.
Every clause read by hand while the business waits to sign
A counterparty NDA scanned crooked, a stamp over the term
An uncapped liability clause where your standard is 12 months
Three rounds of redlines before anyone rechecks the cap
An earlier agreement with the same vendor nobody checked
Standard contracts sit in the same queue as risky ones, so the business waits for a signature and counsel spends the day on terms the playbook already settles.
Unstract reads each contract as it arrives, compares every term with your playbook and earlier agreements with the same party, and sends only the deviations to a lawyer.
From the legal inbox to your CLM, without the keying
Five steps, run on their own for every contract. Parsing by LLMWhisperer, extraction by Document Studio, the whole run by Flow.
Pick up third-party paper wherever it lands
Counterparty contracts arrive in the legal inbox and through the contract request form: NDAs, MSAs with their SOWs, order forms, vendor and customer agreements, and redlined drafts from the other side. Each one is picked up where it arrives and tied to its counterparty and to earlier agreements with the same party, one record per contract.
Nobody has to forward a contract to legal and wait for someone to notice it.
Read every contract, then pull the terms that matter
LLMWhisperer reads each contract as text with its layout kept, so a clause stays under its number and a fee table stays a table, even on a signed scan. Document Studio then extracts the terms you defined: parties, effective date, term and renewal, payment terms, liability cap, indemnities, governing law, termination and data protection terms, each with the clause and page it came from.
The same term definitions run on every counterparty's form, whatever clause number they use.
Check every term against your playbook before anyone reads it
Each extracted term is compared with the standard position and the fallback in the playbook you write, and with earlier agreements with the same party. A term outside the playbook is flagged with the clause text beside your standard position. Unstract does not decide whether a clause is acceptable and gives no legal advice: counsel or the contract manager makes that call.
Set the stopping points once (any term outside the playbook, an uncapped liability, an unusual governing law) and only those contracts wait for a person.
Send each deviation to the lawyer who owns it
Contracts within the playbook move on for signature under the approval rules you set. A contract with a deviation goes to the right reviewer by contract type and value: a contract manager below your threshold, counsel above it. Unstract does not negotiate or redline on its own; the reviewer decides what to send back to the other side.
Counsel spends the day on the clauses outside the playbook, not on NDAs that match it.
Record the terms where legal already works
Key terms, dates and obligations go to your contract repository or CLM, such as Ironclad or Docusign CLM, with renewal and notice dates tracked. Approved contracts are handed off for signature in e-signature tools such as Docusign or Adobe Acrobat Sign, and every decision a person made is recorded against the contract.
Nobody rekeys a signed contract into a tracker, and the notice date is on the calendar before it opens.
See your playbook run on last week's contracts.
Bring the playbook and the third-party paper your team received last week. We set each term beside your standard position and show which contracts would have gone straight to signature.
Every contract that reaches legal for review
Documents
- Contracts
- Non-disclosure agreements
- Master services agreements
- Statements of work
- Order forms
- Data processing agreements
- Vendor and customer agreements
- Redlined drafts
- Amendments and addenda
- Earlier agreements with the same party
Fields captured
Our agents are extroverts.
Cloud storage like S3, Google Drive, Dropbox and Box. Databases and warehouses like Snowflake, BigQuery, Postgres and SQL Server. Accounting, ERP and CRM systems like QuickBooks, Xero, SAP, NetSuite, Salesforce and HubSpot. Project trackers like Jira, Asana, ClickUp and Linear. And anything with an API.
Live on one contract type first
No developers on your side and no change to how your lawyers sign off. The review runs on your own playbook and contracts and proves itself on one contract type before it takes on more.
Book a consultation
We go through your playbook and a few recent contracts together: which terms you check, where you accept a fallback, and who approves what.
Built on your playbook and contracts
The terms, the standard positions and fallbacks, the approval rules and the connection to your contract repository or CLM are set up on your own paper, not samples.
Pilot on NDAs, then roll out
One contract type, often NDAs, runs live first. When counsel trusts the flags, MSAs, SOWs and vendor agreements follow with their own playbook positions.
Built for the people who sign off on third-party paper
AI contract review software that clears standard paper on its own and puts only the clauses outside the playbook in front of counsel.
One playbook applied the same way to every contract, with each deviation and each decision recorded for reporting.
Vendor agreements checked for payment terms, liability and data protection before signature, approved under the thresholds you set.
A first pass on client contracts against the client's own playbook, the clause text beside each standard position, ready for a lawyer.
Standard contracts signed sooner, deviations in front of counsel
Their terms and your playbook stay private
Third-party paper carries the counterparty's pricing, the liability each side agreed to carry and terms both sides promised to keep confidential. Your playbook sits beside it and shows exactly where your team will give ground.
- Contracts and playbooks are encrypted in transit and at rest.
- Contracts and playbooks are never used to train models.
- Access by role, matter and contract type, with every review decision recorded against the contract.
- Retention you set: processed contracts are deleted on your schedule.
- Self-hosted deployment for legal teams and law firms that keep contract review inside their own environment.
What legal teams ask before they automate review
In three steps. LLMWhisperer reads the contract with its clause numbers in place, Document Studio extracts the terms you defined with the clause and page for each, and Flow compares each term with your playbook's standard position and fallback. A term outside the playbook is flagged with the clause text beside your standard, ready for a lawyer.
Part of it is. The repeatable work fits well: reading the contract, comparing each term with a playbook you wrote, and routing deviations by contract type and value. The interpretation stays with your lawyers. Unstract gives no legal advice and does not decide whether a clause is acceptable.
By comparing each extracted term with a written standard. You record the standard position and fallback for each term in your playbook, and every contract is checked against it and against earlier agreements with the same party. A 15-day notice period where you expect 60, or a liability clause with no cap, is flagged with the clause beside it.
Every term as a structured field, the clause text and page it came from, and a comparison with your own standards rather than a generic risk score. That is the difference between AI contract analysis a lawyer can check in seconds and a summary they have to verify against the whole contract.
Flow sends the key terms, dates and obligations to your contract repository or CLM, such as Ironclad or Docusign CLM, and hands approved contracts off for signature in tools such as Docusign or Adobe Acrobat Sign. Renewal and notice dates are tracked from the moment the contract is recorded.
No. Unstract shows which terms fall outside your playbook and what your standard position and fallback are. Counsel or the contract manager decides what to accept, what to redline and what to send back to the other side, and each decision is recorded against the contract.
For each term you track, your standard position and the fallback you will accept, plus the approval thresholds by contract type and value and the conditions that always stop a contract, such as an uncapped liability or an unusual governing law. Unstract applies what you wrote and nothing else.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Contracts and playbooks are encrypted in transit and at rest, never used to train models, and deleted on the retention schedule you set. Legal teams and law firms can run it self-hosted; the Trust Center lists the controls in detail.
Most teams start with NDAs. In a consultation we set up the review on your playbook, your approval rules and your contract repository or CLM, run it on live contracts, and add MSAs, SOWs and vendor agreements once counsel trusts the flags. No developers are needed on your side.
Bring your playbook and three recent contracts
An NDA, a vendor MSA and the redlined draft that took the longest. We check each term against your playbook live and show the clause behind every flag.