Extract data from contracts and agreements
Unstract reads contracts and agreements, from MSAs bundled with SOWs and order forms to scanned, signed copies and their amendments, and returns each term with the clause it came from to your contract repository or CLM.
15 days?? our std is 60 — check §2.3 — RL
MSA · Quarryline / Halden & Rowe · Page 1 of 47
{ "customer": "Halden & Rowe Foods Inc", "provider": "Quarryline Systems LLC", "effective_date": "11/01/2026", "initial_term": "36 months", "auto_renewal": "yes", "non_renewal_notice": "15 days", "payment_terms": "Net 45", "annual_fees": 480000, "liability_cap": "12 months' fees", "governing_law": "Delaware"}
Trusted by legal and contract teams around the globe
Every counterparty sends its own paper
A contract signed on your own template is the easy case. The rest of the repository was signed on someone else's form, and it shows.
Printed, signed in ink and scanned back crooked
The renewal clause sits somewhere new on every form
Notice periods changed in pen and initialled at signing
The MSA, its SOWs, order forms and an amendment in one PDF
Fees in an exhibit, the price increase in a renewal letter
Someone reads each one and keys the parties, dates and notice periods into a tracker, and a renewal window missed by a week locks the company into another year.
Unstract reads every contract and agreement in the file, pulls the terms you name with the clause and page they came from, flags the ones that depart from your standard, and sends the record to your contract repository or CLM.
Parse the contract, extract the terms, run the review
LLMWhisperer reads the pages, Document Studio returns the terms, and Flow runs the work around them. Use one for the contracts in front of you and connect the rest as the volume grows.
Read any contract or agreement as text with its clause numbers in place
Contracts come in as signed PDFs, scans of wet-ink signature pages and photocopied legacy agreements from before anyone kept a repository. LLMWhisperer reads each one and keeps the layout, so a clause stays under its number, a fee schedule stays a table, and a notice period changed in pen sits beside the printed figure it replaced.
Pass the text to your own LLM, or make parsing the first step of a longer contract process.
Learn more about LLMWhispererGet structured key terms from every contract and agreement
Name the terms you track, from parties and renewal windows to payment terms, liability caps and governing law, and Document Studio returns them as JSON for every counterparty's form. That is contract metadata extraction with a source: each value carries the clause and page it came from, and a term that disagrees with an SOW or amendment arrives flagged. Unstract reports what the contract says. Whether a clause is acceptable stays with your lawyers.
Deploy it as an API, run it as an ETL pipeline over a folder of signed contracts, or make extraction one step in an orchestrated process.
Learn more about Document StudioRun contract intake from inbox to repository
Describe how your team takes in a contract, and Flow's agents build the workflow: third-party paper is picked up from email and the contract request form, bundled PDFs are split into the MSA, SOWs and order forms, each is read, and every extracted term is set beside your playbook's standard position and fallback. You approve the workflow once and it runs the same way on every contract, then the key terms, dates and obligations land in your contract repository or CLM, with renewal and notice dates tracked and clean contracts handed off for signature.
Set the stopping points once: any term outside the playbook, an uncapped liability, an unusual governing law. Only those contracts go to legal counsel or a contract manager, routed by contract type and value, with the clause beside the playbook position. The lawyer makes the call.
Learn more about FlowPull the terms from your contracts today. Add the review workflow later.
Start for free to parse and extract your own contracts now. Running contract intake through Flow starts with a consultation.
Contracts on any paper, and the documents that change them
Documents
- Master services agreements
- Statements of work
- Order forms
- Vendor agreements
- Customer agreements
- Non-disclosure agreements
- Supplier quality agreements
- Vendor compliance agreements
- Contract manufacturing agreements
- Inventory consignment agreements
- Intercompany agreements
- Fee payment agreements
- Contract renewal notifications
- Data processing agreements
- Amendments and addenda
- Scanned legacy contracts with wet-ink signatures
Fields captured
Processes these contracts feed
Built for the people who live with the contract after signature
Counterparty paper read before the first redline, so review starts from the clauses that depart from your standard positions.
The whole repository as one dataset, renewal and notice dates tracked, legacy scans included, without a project to rekey them.
Fees, payment terms and price increase caps from every vendor and supplier agreement, ready before the renewal conversation starts.
Key terms from a data room or a client's contract file pulled with the clause and page they came from, ready for review.
Less time keying contracts, more time on the clauses that matter
Deal terms stay between the parties
A contract carries the price you negotiated, the liability you agreed to carry and terms both sides promised to keep confidential. Read across a repository, those terms show every counterparty what everyone else got.
- Contracts are encrypted in transit and at rest.
- Uploaded agreements are not used to train models.
- Access by role, matter and contract type. Every review and correction is recorded against the contract.
- Processed contracts are deleted on the retention schedule you set.
- Self-hosted options are available for legal teams and law firms that keep contract files inside their own environment.
What legal and contract teams ask first
Yes, when the OCR keeps the layout. LLMWhisperer reads signed PDFs, scans and photocopies and keeps each clause under its number, so the extraction step can find the renewal term in §2.3 instead of guessing from a run of loose text. Document Studio then returns the terms you named, with the clause and page for each.
Yes. Document Studio uses LLMs to extract data from contracts on any counterparty's form: parties, dates, term and renewal, fees, liability cap, indemnity and governing law. It works on contracts it has not seen before, with no templates to build, and each value points back to the clause it came from.
Yes. Name the initial term, renewal term, auto-renewal and non-renewal notice period as fields, and each contract returns them with their clause. Flow can then compute the date notice is due and send it to your contract repository or CLM, so a 15-day window is on the calendar before it opens.
Yes. Flow splits a bundled PDF into the MSA, each SOW, each order form and any amendment, then calls the extraction on each part. Every part comes back as its own record, linked to the agreement it sits under, and terms that disagree between them arrive flagged.
An endpoint per document type, a schema you define, and a source for every value. Document Studio deploys exactly that: POST a contract, get back JSON with each term and the clause and page it came from. For contract extraction software that runs on a folder rather than a call, the same extraction runs as an ETL pipeline.
Unstract does the reading and hands the result to your CLM. It takes PDFs, scans, phone photos and Word files, keeps their layout, and returns the same fields whatever the format, so the CLM receives structured metadata instead of an image it cannot search.
No. Unstract extracts what the contract says and shows the clause and page each term came from. It can flag a term that departs from the standard you gave it, such as a 15-day notice where you expect 60. Whether to accept, negotiate or reject it is for your lawyers, and Unstract gives no legal advice.
The contract stops in a review queue with both values and the pages they came from. A contract manager or counsel picks the right one, checks the order of precedence clause if needed, and the decision is recorded against the contract.
Yes. LLMWhisperer reads handwriting alongside printed text and handles skewed and faded scans. A notice period struck through and initialled comes out beside the printed figure, so the extraction can take the change and flag it for review.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Contracts are encrypted in transit and at rest, not used to train models, and kept only as long as your retention setting allows. Legal teams and firms that need it can self-host; the Trust Center has the controls.
Yes. Start for free, upload an MSA and one of its SOWs, and check the terms that come back against the pages. Running contract intake for the whole repository through Flow starts with a consultation built around your playbook and your contract repository or CLM.
Bring one counterparty's contract file to the consultation
The MSA, its SOWs and order forms, the latest amendment and the scan with the initialled changes. We read them together and show each term beside the clause it came from.